Replies: 1 comment 1 reply
|
Question for xwayland-satellite. niri does not treat it as any special client, it has no knowledge of anything xwayland related. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Use Case / Problem Description
Currently,
window-ruleprovideson-xdg-activate "ignore", which works as intended for native Wayland clients attempting to snatch focus usingxdg-activation-v1.However, legacy X11 / XWayland applications (particularly Java/Compose Multiplatform desktop apps, Electron, or older media suites) do not request activation tokens cooperatively. Instead, they fire programmatic X11 focus requests (
_NET_ACTIVE_WINDOWor directXSetInputFocuscalls) throughxwayland-satellite.On multi-monitor setups, this allows an XWayland background window (e.g., a media player auto-advancing to the next episode) to rip keyboard focus away from an active Wayland/XWayland surface (such as a game or full-screen editor) on another display output.
Proposed Solution
Introduce a window rule or global toggle to suppress programmatic focus attempts originating specifically from XWayland surfaces unless triggered by explicit pointer/user action:
All reactions