There seems to be a bug/regression in the 4.15 release.
The issue described below does not happen in the previous 4.14.1 release.
In Multi-Head setups the "focus left/right" command does not focus a
fullscreen window.
Instead it gives focus to the windows beneath that fullscreen window.
This problem does not happen when using "workspace
Here the fullscreen window will get focused properly.
For the debug logfiles I have cleaned up my i3 configuration a bit
and used that same config file in both versions.
Affected version:
Binary i3 version: 4.15 (2018-03-10) © 2009 Michael Stapelberg and contributors
Running i3 version: 4.15 (2018-03-10) (pid 18436) abort…)
Loaded i3 config: /home/fox/.config/i3/config (Last modified: Sun 25 Mar 2018 10:56:09 AM CEST, 573 seconds ago)
The i3 binary you just called: /usr/bin/i3
The i3 binary you are running: i3
Unaffected version:
Binary i3 version: 4.14.1 (2017-09-24) © 2009 Michael Stapelberg and contributors
Running i3 version: 4.14.1 (2017-09-24) (pid 15832)bort…)
Loaded i3 config: /home/fox/.config/i3/config (Last modified: Sun 25 Mar 2018 10:56:09 AM CEST, 884 seconds ago)
The i3 binary you just called: /usr/bin/i3
The i3 binary you are running: i3
URL to a logfile as per https://i3wm.org/docs/debugging.html:
Affected version (4.15) : https://paste.foxxx0.de/PYjjR/
Unaffected version (4.14.1) : https://paste.foxxx0.de/2um/
What I did:
For clarification purposes (regarding the logfile and the steps to reproduce),
the following assumptions are used:
What I saw:
i3 changed focus to the window BELOW the fullscreen window.
What I expected instead:
Focus should be given to the fullscreen window.
I don’t see a link to logs.i3wm.org. Did you follow https://i3wm.org/docs/debugging.html? (In case you actually provided a link to a logfile, please ignore me.)
An important detail is that the window from step 5. is floating.
Yes, in this case mpv starts in floating mode due to my for_window rule.
After that it is switched to fullscreen.
bisect: af78331ee774a0021ed07f8b1d5d41fc8ffcd837 <--- blame this guy
I know that guy, he'll probably send a PR soon to fix it :-)
Most helpful comment
bisect: af78331ee774a0021ed07f8b1d5d41fc8ffcd837 <--- blame this guy