Marco Trevisan (Treviño) 2625edec10 x11/x11-display: Set compositor selection earlier on XWayland ... When the X11 display is actually XWayland there's no point to delay the compositor selection, given that mutter itself is the compositor and doing this may cause the first X11 client that starts not to receive the right information (and in some cases misbehave). Since some toolkits are not handling the compositor selection changes properly at later times, let's make their life easier by just initializing the selection as early as the other X11 properties, given that in this case there's nothing to replace. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/2472 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970>		2023-05-15 19:04:59 +02:00
..
backends	backends/x11: Fix type confusion about object data	2023-05-14 23:15:55 +00:00
compositor	x11/x11-display: Set compositor selection earlier on XWayland	2023-05-15 19:04:59 +02:00
core	x11/x11-display: Set compositor selection earlier on XWayland	2023-05-15 19:04:59 +02:00
frames	frames: Disable XDND support on the frame window	2023-04-28 12:46:58 +02:00
meta	docs: Add missing flag documentation	2023-05-04 11:46:09 +00:00
tests	tests: Make wayland-x11-interop depends on xwayland feature	2023-05-15 11:52:35 +00:00
wayland	wayland/surface: NULL check surface resource in handle_output_bound()	2023-05-09 15:26:32 +00:00
x11	x11/x11-display: Set compositor selection earlier on XWayland	2023-05-15 19:04:59 +02:00
libmutter.pc.in
meson.build	build: Set built headers as libmutter_dep sources	2023-05-15 13:06:40 +02:00
meta-private-enum-types.c.in	build: Add missing include	2022-08-10 20:28:40 +02:00
meta-private-enum-types.h.in