gri3-wm

Commit Graph

Author	SHA1	Message	Date
Michael Stapelberg	7ad32fd2d1	tests: replace http:// with https:// where appropriate This was done automatically using: % sed -i 's,http://build.i3wm.org,https://build.i3wm.org,g' testcases/t/*.t	2017-09-24 10:19:50 +02:00
Ingo Bürk	5dbfb05c85	Use the EWMH support window rather than the root window as an input focus fallback. If no other window is available on the active workspace, we now select the EWMH support window (used to indicate that an EWMH-compliant window manager is preent) as the focus window rather than the root window. The NET_WM_ACTIVE window will still be set to XCB_WINDOW_NONE to pretend that no window is actually focused. This fixes the issue that when using the root window, a fallback mechanism in X11 takes effect which routes keyboard input to the window under the cursor, independent of whether that window has the input focus. Using the EWMH window instead, we can avoid this behavior. We cannot simply set it to XCB_WINDOW_NONE as this would discard all keyboard events, breaking keybindings. fixes #1378	2015-09-13 20:29:02 +02:00

Author

SHA1

Message

Date

Michael Stapelberg

7ad32fd2d1

tests: replace http:// with https:// where appropriate

This was done automatically using:

% sed -i 's,http://build.i3wm.org,https://build.i3wm.org,g' testcases/t/*.t

2017-09-24 10:19:50 +02:00

Ingo Bürk

5dbfb05c85

Use the EWMH support window rather than the root window as an input focus fallback.

If no other window is available on the active workspace, we now select the EWMH support window (used to indicate that an EWMH-compliant window manager is preent) as the focus window rather than the root window. The NET_WM_ACTIVE window will still be set to XCB_WINDOW_NONE to pretend that no window is actually focused.
This fixes the issue that when using the root window, a fallback mechanism in X11 takes effect which routes keyboard input to the window under the cursor, independent of whether that window has the input focus. Using the EWMH window instead, we can avoid this behavior. We cannot simply set it to XCB_WINDOW_NONE as this would discard all keyboard events, breaking keybindings.

fixes #1378

2015-09-13 20:29:02 +02:00

2 Commits (5e2f13a28c4fd7348914dfd999026d0e30424cd5)