e673a4bda0
In Wayland, mouse coordinates are not updated after all x11 clients have left, causing the mouse information to remain at the position left by the last x11 client. However, if CheckMotion is called at this point for other reasons (such as window mapped, reactive, etc.), xwayland might continue to send enter events to x11 clients, even if the mouse is actually on a Wayland client. This MR introduces and checks pointer_enter_count to determine if the mouse has left an x11 client and is now on a Wayland client. When it's confirmed that the mouse is no longer on an x11 client but on a Wayland client, returning TRUE in sprite_check_lost_focus causes XYToWindow to return to the root window, preventing further enter events from being sent to x11 clients. Part-of: <https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/2112>
X Server
The X server accepts requests from client applications to create windows, which are (normally rectangular) "virtual screens" that the client program can draw into.
Windows are then composed on the actual screen by the X server (or by a separate composite manager) as directed by the window manager, which usually communicates with the user via graphical controls such as buttons and draggable titlebars and borders.
For a comprehensive overview of X Server and X Window System, consult the following article: https://en.wikipedia.org/wiki/X_server
All questions regarding this software should be directed at the Xorg mailing list:
https://lists.freedesktop.org/mailman/listinfo/xorg
The primary development code repository can be found at:
https://gitlab.freedesktop.org/xorg/xserver
For patch submission instructions, see:
https://www.x.org/wiki/Development/Documentation/SubmittingPatches
As with other projects hosted on freedesktop.org, X.Org follows its Code of Conduct, based on the Contributor Covenant. Please conduct yourself in a respectful and civilized manner when using the above mailing lists, bug trackers, etc: