_NET_CLIENT_LIST_STACKING has bottom-to-top stacking order.
But, currently, _NET_CLIENT_LIST_STACKING is using workspace order for windows, only ordering windows within a workspace subgroup in the focus order. Though, even that ordering is not completely bottom-to-top.
I have an application that uses _NET_CLIENT_LIST_STACKING in order to determine the currently focused window.
Yes, it should have used _NET_ACTIVE_WINDOW, but it is trying to work around some kind of bug.
Steps to Reproduce
Switching the currently active window in a workspace that is not the very last one, I see this:
❯ while true; xprop -root _NET_CLIENT_LIST_STACKING ; sleep 1s; end
Problem Description
Freedesktop spec on
_NET_CLIENT_LIST_STACKING
says:But, currently,
_NET_CLIENT_LIST_STACKING
is using workspace order for windows, only ordering windows within a workspace subgroup in the focus order. Though, even that ordering is not completely bottom-to-top.I have an application that uses
_NET_CLIENT_LIST_STACKING
in order to determine the currently focused window. Yes, it should have used_NET_ACTIVE_WINDOW
, but it is trying to work around some kind of bug.Steps to Reproduce
Switching the currently active window in a workspace that is not the very last one, I see this:
Notice how the change happens in the middle of the list. Rather than in the last element.
Configuration File
Please include the smallest full configuration file that reproduces the problem you are experiencing:
Checklist
xmonad
commita2259bb3091429f4293d371e13fd5a2ee8da30db
Sun Sep 18 16:27:14 2022 +0200xmonad-contrib
commitfce5558b625df3693a1455eb251e68bb2c6980de
Thu Oct 27 07:45:48 2022 +0200