Xwayland has its own XYToWindow() handler to account for the case when the pointer leaves an X11 surface to enter another Wayland native window (which of course are unknown to Xwayland). When that occurs, Xwayland will treat it as if the pointer had entered the root window so that the X11 clients receive an appropriate leave event. When the pointer leaves the X11 surface, Xwayland will call CheckMotion() to update the sprite coordinates and possibly the cursor. However, CheckMotion() will call back into the XYToWindow() handler, which will then pretend the window has entered the root window, and that may cause the wrong cursor to be applied. To avoid the issue, change the order we do things, by calling CheckMotion() first prior to clear up the internal focus window so that the first call to XYToWindow() will return the correct X11 window so we get to update the cursor correctly. Closes: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1811 Signed-off-by: Olivier Fourdan <ofourdan@redhat.com> Part-of: <https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1915> |
||
---|---|---|
.. | ||
kdrive | ||
vfb | ||
xfree86 | ||
xnest | ||
xquartz | ||
xwayland | ||
xwin | ||
meson.build |