In addition to [1]Weston 16 nearing release and its release candidate out today, the Wayland 1.26 release candidate was just issued with a few notable changes on top of the more typical bug fixing.

New to Wayland 1.26 is the wl_pointer.warp event. The wl_pointer.warp event addition intends to address a shortcoming where with Wayland right now in some situations the Wayland client cannot obtain the correct position information for the pointer. Open-source developer YaNing Lu explained of the issue in [2]the merge request :

"The original wl_pointer.button event does not contain the position information. In some scenarios, the client cannot obtain the correct position information. For example, when the mouse focus is on a button and the mouse does not move but the window size changes, the client cannot update the position information through the motion event, resulting in incorrect mouse position.

Therefore, This event should be sent when the local coordinates of a pointer change as a result of surface being moved/resized/fullscreened."

So now with Wayland 1.26+, the new (correct) pointer position can be notified without an end-user-initiated motion event. There is patches pending for this event with KDE KWin, GNOME Mutter, and wlroots. Plus Qt and SDL are among the toolkits ready with their implementations.

Wayland 1.26 RC1 also adds a new wl_fixes.ack_global_remove request to deal with a possible race condition. The WAYLAND_DEBUG timestamps are also now better formatted to make them easier to read/compare between other logs.

More details on today's Wayland 1.26 RC1 release via [3]Wayland-devel .



[1] https://www.phoronix.com/news/Wayland-Weston-16-Alpha

[2] https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/340

[3] https://lore.freedesktop.org/wayland-devel/-Ppab1BlrXbXvKwok-5WA3ohwqMovJGchqsCmF7qFdoDznIykeyly1AyQQMub66aLExGGDZNNHSG6h5MQpY2EzFc0c_32wItTwTFDdtAZnA=@emersion.fr/T/#u