Script 'mail_helper' called by obssrc Hello community, here is the log from the commit of package wayland-protocols for openSUSE:Factory checked in at 2022-07-31 23:00:14 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/wayland-protocols (Old) and /work/SRC/openSUSE:Factory/.wayland-protocols.new.1533 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "wayland-protocols" Sun Jul 31 23:00:14 2022 rev:28 rq:989703 version:1.26 Changes: -------- --- /work/SRC/openSUSE:Factory/wayland-protocols/wayland-protocols.changes 2022-02-11 23:08:23.870770524 +0100 +++ /work/SRC/openSUSE:Factory/.wayland-protocols.new.1533/wayland-protocols.changes 2022-07-31 23:00:23.807596356 +0200 @@ -1,0 +2,20 @@ +Tue Jul 12 20:14:54 UTC 2022 - Bj��rn Lie <bjorn.lie@gmail.com> + +- Update to version 1.26: + + This release introduces the new staging protocol single pixel + buffer, which together with the viewporter extension enables + clients to easily create arbitrarily sized single color + surfaces. + + Xdg-shell now also supports compositors announcing to surfaces + some window management capabilities it supports. + + The text input protocol saw a clarification to an easily + misinterpreted paragraph, which if interpreted in a different + way than the new clarification makes clear hindered correct + behavior from being implemented. + + This is also the first release which mandates new protocol + extensions to follow RFC 2119 wording. + + Apart from has so far been mentioned, this release also comes + with the usual clarifications, improved annotations, and other + minor fixes. + +------------------------------------------------------------------- Old: ---- wayland-protocols-1.25.tar.xz wayland-protocols-1.25.tar.xz.sig New: ---- wayland-protocols-1.26.tar.xz wayland-protocols-1.26.tar.xz.sig ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ wayland-protocols.spec ++++++ --- /var/tmp/diff_new_pack.95K6yp/_old 2022-07-31 23:00:24.239597611 +0200 +++ /var/tmp/diff_new_pack.95K6yp/_new 2022-07-31 23:00:24.243597622 +0200 @@ -18,7 +18,7 @@ Name: wayland-protocols -Version: 1.25 +Version: 1.26 Release: 0 Summary: Wayland protocols that add functionality not available in the core protocol License: MIT @@ -32,7 +32,7 @@ BuildRequires: c++_compiler BuildRequires: c_compiler -BuildRequires: meson >= 0.54.0 +BuildRequires: meson >= 0.55.0 BuildRequires: pkgconfig BuildRequires: pkgconfig(wayland-scanner) BuildArch: noarch ++++++ wayland-protocols-1.25.tar.xz -> wayland-protocols-1.26.tar.xz ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/.gitlab-ci/debian-install.sh new/wayland-protocols-1.26/.gitlab-ci/debian-install.sh --- old/wayland-protocols-1.25/.gitlab-ci/debian-install.sh 1970-01-01 01:00:00.000000000 +0100 +++ new/wayland-protocols-1.26/.gitlab-ci/debian-install.sh 2022-07-07 17:48:25.346891400 +0200 @@ -0,0 +1,14 @@ +#!/bin/sh -eux + +# Note: don't forget to bump FDO_DISTRIBUTION_TAG when editing this file! + +git clone --branch 1.20.0 --depth=1 https://gitlab.freedesktop.org/wayland/wayland +cd wayland/ +git show -s HEAD +meson build/ -Dtests=false -Ddocumentation=false +ninja -j${FDO_CI_CONCURRENT:-4} -C build/ install +cd .. +rm -rf wayland/ + +echo "/usr/local/lib" >/etc/ld.so.conf.d/local.conf +ldconfig diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/.gitlab-ci.yml new/wayland-protocols-1.26/.gitlab-ci.yml --- old/wayland-protocols-1.25/.gitlab-ci.yml 2022-01-28 17:00:40.727420800 +0100 +++ new/wayland-protocols-1.26/.gitlab-ci.yml 2022-07-07 17:48:25.346891400 +0200 @@ -19,8 +19,9 @@ .debian: variables: FDO_DISTRIBUTION_VERSION: bullseye - FDO_DISTRIBUTION_PACKAGES: 'build-essential pkg-config libwayland-dev meson' - FDO_DISTRIBUTION_TAG: '2021-11-09.0' + FDO_DISTRIBUTION_PACKAGES: 'build-essential pkg-config meson git ca-certificates libffi-dev libexpat1-dev libxml2-dev' + FDO_DISTRIBUTION_TAG: '2022-01-19.0' + FDO_DISTRIBUTION_EXEC: 'env FDO_CI_CONCURRENT=${FDO_CI_CONCURRENT} ./.gitlab-ci/debian-install.sh' check-commit: extends: @@ -52,3 +53,8 @@ - ninja -C build - meson test -C build - ninja -C build install + artifacts: + name: wayland-protocols-$CI_COMMIT_SHA + when: always + paths: + - $CI_PROJECT_DIR/build/meson-logs diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/MEMBERS.md new/wayland-protocols-1.26/MEMBERS.md --- old/wayland-protocols-1.25/MEMBERS.md 2022-01-28 17:00:40.728420700 +0100 +++ new/wayland-protocols-1.26/MEMBERS.md 2022-07-07 17:48:25.346891400 +0200 @@ -11,5 +11,5 @@ (@eskilblomfeldt) - Weston: Pekka Paalanen <pekka.paalanen@collabora.com> (@pq), Daniel Stone <daniel@fooishbar.org> (@daniels) -- wlroots/Sway: Drew DeVault <sir@cmpwn.com> (@ddevault), - Simon Ser <contact@emersion.fr> (@emersion) +- wlroots/Sway: Simon Ser <contact@emersion.fr> (@emersion), + Simon Zeni <simon@bl4ckb0ne.ca> (@bl4ckb0ne) diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/README.md new/wayland-protocols-1.26/README.md --- old/wayland-protocols-1.25/README.md 2022-01-28 17:00:40.728420700 +0100 +++ new/wayland-protocols-1.26/README.md 2022-07-07 17:48:25.347891300 +0200 @@ -141,6 +141,26 @@ only be done by creating a new major version of the extension. ``` +## Use of RFC 2119 keywords + +Descriptions of all new protocols must use (in lowercase) and adhere to the +proper meaning of the keywords described in +[RFC 2119](https://www.rfc-editor.org/info/rfc2119). + +All protocol descriptions that follow the guidelines in RFC 2119 must +incorporate the following text in their toplevel protocol description section: + +``` +The key words "must", "must not", "required", "shall", "shall not", "should", +"should not", "recommended", "may", and "optional" in this document are to +be interpreted as described in IETF RFC 2119. +``` + +Note that not all existing protocol descriptions conform to RFC 2119. Protocol +maintainers are encouraged to audit their descriptions, update them as needed +to follow RFC 2119 guidelines, and mark them as conformant in the way described +in the previous paragraph. + ## Backward compatible protocol changes A protocol may receive backward compatible additions and changes. This diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/meson.build new/wayland-protocols-1.26/meson.build --- old/wayland-protocols-1.25/meson.build 2022-01-28 17:00:40.729421000 +0100 +++ new/wayland-protocols-1.26/meson.build 2022-07-07 17:48:25.347891300 +0200 @@ -1,6 +1,6 @@ project('wayland-protocols', - version: '1.25', - meson_version: '>= 0.54.0', + version: '1.26', + meson_version: '>= 0.55.0', license: 'MIT/Expat', ) @@ -39,6 +39,7 @@ 'xdg-activation': ['v1'], 'drm-lease': ['v1'], 'ext-session-lock': ['v1'], + 'single-pixel-buffer': ['v1'], } protocol_files = [] diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/stable/presentation-time/presentation-time.xml new/wayland-protocols-1.26/stable/presentation-time/presentation-time.xml --- old/wayland-protocols-1.25/stable/presentation-time/presentation-time.xml 2022-01-28 17:00:40.729421000 +0100 +++ new/wayland-protocols-1.26/stable/presentation-time/presentation-time.xml 2022-07-07 17:48:25.347891300 +0200 @@ -198,7 +198,7 @@ </entry> </enum> - <event name="presented"> + <event name="presented" type="destructor"> <description summary="the content update was displayed"> The associated content update was displayed to the user at the indicated time (tv_sec_hi/lo, tv_nsec). For the interpretation of @@ -256,7 +256,7 @@ <arg name="flags" type="uint" enum="kind" summary="combination of 'kind' values"/> </event> - <event name="discarded"> + <event name="discarded" type="destructor"> <description summary="the content update was not displayed"> The content update was never displayed to the user. </description> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/stable/viewporter/viewporter.xml new/wayland-protocols-1.26/stable/viewporter/viewporter.xml --- old/wayland-protocols-1.25/stable/viewporter/viewporter.xml 2022-01-28 17:00:40.729421000 +0100 +++ new/wayland-protocols-1.26/stable/viewporter/viewporter.xml 2022-07-07 17:48:25.348891500 +0200 @@ -111,12 +111,6 @@ when the surface state is applied. A NULL wl_buffer does not raise the out_of_buffer error. - The x, y arguments of wl_surface.attach are applied as normal to - the surface. They indicate how many pixels to remove from the - surface size from the left and the top. In other words, they are - still in the surface-local coordinate system, just like dst_width - and dst_height are. - If the wl_surface associated with the wp_viewport is destroyed, all wp_viewport requests except 'destroy' raise the protocol error no_surface. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/stable/xdg-shell/xdg-shell.xml new/wayland-protocols-1.26/stable/xdg-shell/xdg-shell.xml --- old/wayland-protocols-1.25/stable/xdg-shell/xdg-shell.xml 2022-01-28 17:00:40.730420800 +0100 +++ new/wayland-protocols-1.26/stable/xdg-shell/xdg-shell.xml 2022-07-07 17:48:25.348891500 +0200 @@ -29,7 +29,7 @@ DEALINGS IN THE SOFTWARE. </copyright> - <interface name="xdg_wm_base" version="4"> + <interface name="xdg_wm_base" version="5"> <description summary="create desktop-style surfaces"> The xdg_wm_base interface is exposed as a global object enabling clients to turn their wl_surfaces into windows in a desktop environment. It @@ -117,7 +117,7 @@ </event> </interface> - <interface name="xdg_positioner" version="4"> + <interface name="xdg_positioner" version="5"> <description summary="child surface positioner"> The xdg_positioner provides a collection of rules for the placement of a child surface relative to a parent surface. Rules can be defined to ensure @@ -401,7 +401,7 @@ </request> </interface> - <interface name="xdg_surface" version="4"> + <interface name="xdg_surface" version="5"> <description summary="desktop user interface surface base interface"> An interface that may be implemented by a wl_surface, for implementations that provide a desktop-style user interface. @@ -577,7 +577,7 @@ </interface> - <interface name="xdg_toplevel" version="4"> + <interface name="xdg_toplevel" version="5"> <description summary="toplevel surface"> This interface defines an xdg_surface role which allows a surface to, among other things, set window-like properties such as maximize, @@ -615,19 +615,19 @@ Set the "parent" of this surface. This surface should be stacked above the parent surface and all other ancestor surfaces. - Parent windows should be set on dialogs, toolboxes, or other + Parent surfaces should be set on dialogs, toolboxes, or other "auxiliary" surfaces, so that the parent is raised when the dialog is raised. - Setting a null parent for a child window removes any parent-child - relationship for the child. Setting a null parent for a window which - currently has no parent is a no-op. - - If the parent is unmapped then its children are managed as - though the parent of the now-unmapped parent has become the - parent of this surface. If no parent exists for the now-unmapped - parent then the children are managed as though they have no - parent surface. + Setting a null parent for a child surface unsets its parent. Setting + a null parent for a surface which currently has no parent is a no-op. + + Only mapped surfaces can have child surfaces. Setting a parent which + is not mapped is equivalent to setting a null parent. If a surface + becomes unmapped, its children's parent is set to the parent of + the now-unmapped surface. If the now-unmapped surface has no parent, + its children's parent is unset. If the now-unmapped surface becomes + mapped again, its parent-child relationship is not restored. </description> <arg name="parent" type="object" interface="xdg_toplevel" allow-null="true"/> </request> @@ -1100,9 +1100,44 @@ <arg name="width" type="int"/> <arg name="height" type="int"/> </event> + + <!-- Version 5 additions --> + + <enum name="wm_capabilities" since="5"> + <entry name="window_menu" value="1" summary="show_window_menu is available"/> + <entry name="maximize" value="2" summary="set_maximized and unset_maximized are available"/> + <entry name="fullscreen" value="3" summary="set_fullscreen and unset_fullscreen are available"/> + <entry name="minimize" value="4" summary="set_minimized is available"/> + </enum> + + <event name="wm_capabilities" since="5"> + <description summary="compositor capabilities"> + This event advertises the capabilities supported by the compositor. If + a capability isn't supported, clients should hide or disable the UI + elements that expose this functionality. For instance, if the + compositor doesn't advertise support for minimized toplevels, a button + triggering the set_minimized request should not be displayed. + + The compositor will ignore requests it doesn't support. For instance, + a compositor which doesn't advertise support for minimized will ignore + set_minimized requests. + + Compositors must send this event once before the first + xdg_surface.configure event. When the capabilities change, compositors + must send this event again and then send an xdg_surface.configure + event. + + The configured state should not be applied immediately. See + xdg_surface.configure for details. + + The capabilities are sent as an array of 32-bit unsigned integers in + native endianness. + </description> + <arg name="capabilities" type="array" summary="array of 32-bit capabilities"/> + </event> </interface> - <interface name="xdg_popup" version="4"> + <interface name="xdg_popup" version="5"> <description summary="short-lived, popup surfaces for menus"> A popup surface is a short-lived, temporary surface. It can be used to implement for example menus, popovers, tooltips and other similar user @@ -1173,10 +1208,6 @@ nested grabbing popup as well. When a compositor dismisses popups, it will follow the same dismissing order as required from the client. - The parent of a grabbing popup must either be another xdg_popup with an - active explicit grab, or an xdg_popup or xdg_toplevel, if there are no - explicit grabs already taken. - If the topmost grabbing popup is destroyed, the grab will be returned to the parent of the popup, if that parent previously had an explicit grab. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/staging/drm-lease/drm-lease-v1.xml new/wayland-protocols-1.26/staging/drm-lease/drm-lease-v1.xml --- old/wayland-protocols-1.25/staging/drm-lease/drm-lease-v1.xml 2022-01-28 17:00:40.730420800 +0100 +++ new/wayland-protocols-1.26/staging/drm-lease/drm-lease-v1.xml 2022-07-07 17:48:25.349891400 +0200 @@ -120,7 +120,7 @@ </description> </event> - <event name="released"> + <event name="released" type="destructor"> <description summary="the compositor has finished using the device"> This event is sent in response to the release request and indicates that the compositor is done sending connector events. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/staging/single-pixel-buffer/README new/wayland-protocols-1.26/staging/single-pixel-buffer/README --- old/wayland-protocols-1.25/staging/single-pixel-buffer/README 1970-01-01 01:00:00.000000000 +0100 +++ new/wayland-protocols-1.26/staging/single-pixel-buffer/README 2022-07-07 17:48:25.350891400 +0200 @@ -0,0 +1,4 @@ +Single-pixel buffer protocol + +Maintainers: +Simon Ser <contact@emersion.fr> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/staging/single-pixel-buffer/single-pixel-buffer-v1.xml new/wayland-protocols-1.26/staging/single-pixel-buffer/single-pixel-buffer-v1.xml --- old/wayland-protocols-1.25/staging/single-pixel-buffer/single-pixel-buffer-v1.xml 1970-01-01 01:00:00.000000000 +0100 +++ new/wayland-protocols-1.26/staging/single-pixel-buffer/single-pixel-buffer-v1.xml 2022-07-07 17:48:25.350891400 +0200 @@ -0,0 +1,69 @@ +<?xml version="1.0" encoding="UTF-8"?> +<protocol name="single_pixel_buffer_v1"> + <copyright> + Copyright �� 2022 Simon Ser + + Permission is hereby granted, free of charge, to any person obtaining a + copy of this software and associated documentation files (the "Software"), + to deal in the Software without restriction, including without limitation + the rights to use, copy, modify, merge, publish, distribute, sublicense, + and/or sell copies of the Software, and to permit persons to whom the + Software is furnished to do so, subject to the following conditions: + + The above copyright notice and this permission notice (including the next + paragraph) shall be included in all copies or substantial portions of the + Software. + + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR + IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, + FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL + THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER + LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING + FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER + DEALINGS IN THE SOFTWARE. + </copyright> + + <description summary="single pixel buffer factory"> + This protocol extension allows clients to create single-pixel buffers. + + Compositors supporting this protocol extension should also support the + viewporter protocol extension. Clients may use viewporter to scale a + single-pixel buffer to a desired size. + + Warning! The protocol described in this file is currently in the testing + phase. Backward compatible changes may be added together with the + corresponding interface version bump. Backward incompatible changes can + only be done by creating a new major version of the extension. + </description> + + <interface name="wp_single_pixel_buffer_manager_v1" version="1"> + <description summary="global factory for single-pixel buffers"> + The wp_single_pixel_buffer_manager_v1 interface is a factory for + single-pixel buffers. + </description> + + <request name="destroy" type="destructor"> + <description summary="destroy the manager"> + Destroy the wp_single_pixel_buffer_manager_v1 object. + + The child objects created via this interface are unaffected. + </description> + </request> + + <request name="create_u32_rgba_buffer"> + <description summary="create a 1��1 buffer from 32-bit RGBA values"> + Create a single-pixel buffer from four 32-bit RGBA values. + + Unless specified in another protocol extension, the RGBA values use + pre-multiplied alpha. + + The width and height of the buffer are 1. + </description> + <arg name="id" type="new_id" interface="wl_buffer"/> + <arg name="r" type="uint" summary="value of the buffer's red channel"/> + <arg name="g" type="uint" summary="value of the buffer's green channel"/> + <arg name="b" type="uint" summary="value of the buffer's blue channel"/> + <arg name="a" type="uint" summary="value of the buffer's alpha channel"/> + </request> + </interface> +</protocol> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/tests/meson.build new/wayland-protocols-1.26/tests/meson.build --- old/wayland-protocols-1.25/tests/meson.build 2022-01-28 17:00:40.731421000 +0100 +++ new/wayland-protocols-1.26/tests/meson.build 2022-07-07 17:48:25.351891500 +0200 @@ -1,6 +1,6 @@ prog_scan_sh = find_program('scan.sh') -dep_scanner = dependency('wayland-scanner', native: true) -prog_scanner = find_program(dep_scanner.get_pkgconfig_variable('wayland_scanner')) +dep_scanner = dependency('wayland-scanner', version: '>=1.20.0', native: true) +prog_scanner = find_program(dep_scanner.get_variable(pkgconfig: 'wayland_scanner')) libwayland = [ dependency('wayland-client'), @@ -14,7 +14,7 @@ test(test_name, prog_scan_sh, args: protocol_path, env: [ - 'SCANNER=@0@'.format(prog_scanner.path()), + 'SCANNER=@0@'.format(prog_scanner.full_path()), ] ) endforeach diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/unstable/fullscreen-shell/fullscreen-shell-unstable-v1.xml new/wayland-protocols-1.26/unstable/fullscreen-shell/fullscreen-shell-unstable-v1.xml --- old/wayland-protocols-1.25/unstable/fullscreen-shell/fullscreen-shell-unstable-v1.xml 2022-01-28 17:00:40.733420800 +0100 +++ new/wayland-protocols-1.26/unstable/fullscreen-shell/fullscreen-shell-unstable-v1.xml 2022-07-07 17:48:25.352891400 +0200 @@ -217,7 +217,7 @@ </interface> <interface name="zwp_fullscreen_shell_mode_feedback_v1" version="1"> - <event name="mode_successful"> + <event name="mode_successful" type="destructor"> <description summary="mode switch succeeded"> This event indicates that the attempted mode switch operation was successful. A surface of the size requested in the mode switch @@ -228,7 +228,7 @@ </description> </event> - <event name="mode_failed"> + <event name="mode_failed" type="destructor"> <description summary="mode switch failed"> This event indicates that the attempted mode switch operation failed. This may be because the requested output mode is not @@ -239,7 +239,7 @@ </description> </event> - <event name="present_cancelled"> + <event name="present_cancelled" type="destructor"> <description summary="mode switch cancelled"> This event indicates that the attempted mode switch operation was cancelled. Most likely this is because the client requested a diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml new/wayland-protocols-1.26/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml --- old/wayland-protocols-1.25/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml 2022-01-28 17:00:40.736420900 +0100 +++ new/wayland-protocols-1.26/unstable/linux-explicit-synchronization/linux-explicit-synchronization-unstable-v1.xml 2022-07-07 17:48:25.355891500 +0200 @@ -219,7 +219,7 @@ 'immediate_release' event it is automatically destroyed. </description> - <event name="fenced_release"> + <event name="fenced_release" type="destructor"> <description summary="release buffer with fence"> Sent when the compositor has finalised its usage of the associated buffer for the relevant commit, providing a dma_fence which will be @@ -236,7 +236,7 @@ <arg name="fence" type="fd" summary="fence for last operation on buffer"/> </event> - <event name="immediate_release"> + <event name="immediate_release" type="destructor"> <description summary="release buffer immediately"> Sent when the compositor has finalised its usage of the associated buffer for the relevant commit, and either performed no operations diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/unstable/tablet/tablet-unstable-v2.xml new/wayland-protocols-1.26/unstable/tablet/tablet-unstable-v2.xml --- old/wayland-protocols-1.25/unstable/tablet/tablet-unstable-v2.xml 2022-01-28 17:00:40.739421100 +0100 +++ new/wayland-protocols-1.26/unstable/tablet/tablet-unstable-v2.xml 2022-07-07 17:48:25.357891600 +0200 @@ -1156,7 +1156,7 @@ </event> <event name="leave"> - <description summary="enter event"> + <description summary="leave event"> Notification that this pad is no longer focused on the specified surface. </description> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/wayland-protocols-1.25/unstable/text-input/text-input-unstable-v3.xml new/wayland-protocols-1.26/unstable/text-input/text-input-unstable-v3.xml --- old/wayland-protocols-1.25/unstable/text-input/text-input-unstable-v3.xml 2022-01-28 17:00:40.740421000 +0100 +++ new/wayland-protocols-1.26/unstable/text-input/text-input-unstable-v3.xml 2022-07-07 17:48:25.358891500 +0200 @@ -422,9 +422,14 @@ The serial number reflects the last state of the zwp_text_input_v3 object known to the compositor. The value of the serial argument must be equal to the number of commit requests already issued on that object. + When the client receives a done event with a serial different than the - number of past commit requests, it must proceed as normal, except it - should not change the current state of the zwp_text_input_v3 object. + number of past commit requests, it must proceed with evaluating and + applying the changes as normal, except it should not change the current + state of the zwp_text_input_v3 object. All pending state requests + (set_surrounding_text, set_content_type and set_cursor_rectangle) on + the zwp_text_input_v3 object should be sent and committed after + receiving a zwp_text_input_v3.done event with a matching serial. </description> <arg name="serial" type="uint"/> </event>