Tudor Brindus ae2f3ecb68 xwm: implement _NET_CLIENT_LIST_STACKING ... This property is present on all modern X11 instances. The nonpresence of it requires applications to fall back to XQueryTree-based logic to determine stacking logic (e.g., to determine what surface should get Xdnd events). These code paths are effectively untested nowadays, so this makes it more likely for wlroots to "break" applications. For instance, the XQueryTree fallback path has been broken in Chromium for the last 10 years. It's easy enough to maintain this property, so let's just do it. Fixes #2889.		2021-05-31 10:41:29 +02:00
..
backend	backend/x11: use common renderer and allocator	2021-05-21 22:13:54 +02:00
render	render/gles2: fix texture cleanup on destroy	2021-05-30 10:11:09 -04:00
types	types/wlr_buffer: introduce wlr_buffer_cap	2021-04-28 20:55:57 +02:00
util	util/uuid: replace with util/token, remove libuuid	2021-04-11 19:09:36 +02:00
wlr	xwm: implement _NET_CLIENT_LIST_STACKING	2021-05-31 10:41:29 +02:00
xcursor	xcursor: make cursor data and metadata const	2021-02-05 10:04:20 +01:00
xwayland	xwm: implement _NET_CLIENT_LIST_STACKING	2021-05-31 10:41:29 +02:00
meson.build	render: make GLES2 renderer optional	2021-04-17 16:39:40 +02:00