First, background: I am not a xorg developer, but I develop the XKB library used by most Wayland compositors (xkbcommon). The behavior there is the same.
IMO it is worth having a discussion about the behavior. A nice thing about XKB is that it has a specification. It is easier to discuss behavioral changes against a spec than hard-to-understand X code, or 150 comments bugs. Therefore, my proposal for you (or anyone else who is interested in changing the behavior) is to provide a patch against the spec. Even if the actual spec will never change, I still think that a clear proposal, which also considers possible side effects, is the first step forward here.
Nikolay,
First, background: I am not a xorg developer, but I develop the XKB library used by most Wayland compositors (xkbcommon). The behavior there is the same.
IMO it is worth having a discussion about the behavior. A nice thing about XKB is that it has a specification. It is easier to discuss behavioral changes against a spec than hard-to-understand X code, or 150 comments bugs. Therefore, my proposal for you (or anyone else who is interested in changing the behavior) is to provide a patch against the spec. Even if the actual spec will never change, I still think that a clear proposal, which also considers possible side effects, is the first step forward here.
The current spec and the most relevant section is here: https:/ /www.x. org/releases/ current/ doc/kbproto/ xkbproto. html#Key_ Actions
The current source for the above spec is in the kbproto repository here: https:/ /cgit.freedeskt op.org/ xorg/proto/ kbproto/ tree/specs/ ch06.xml? id=kbproto- 1.0.7#n586