
Thank you very much for looking into this so quickly and deeply.
Do I need to wait for the workaround to be available in a released version
of xmonad-contrib? Do I need to do something after upgrading to fix this?
Thank you,
On Sun, Jul 4, 2021 at 8:27 AM Tony Zorman
[[ I initially forgot to reply to the list so here is the email again for everyone to see. I apologize for the spam. Maybe the OP would also benefit from knowing about the windowedFullscreenFixEventHook ]]
-------------------- Start of forwarded message -------------------- From: Tony Zorman
To: Platon Pronko Subject: Re: [xmonad] Full-screen messes up tabs on google chrome Date: Sat, 03 Jul 2021 18:53:57 +0200 On Sat, Jul 03 2021 19:32, Platon Pronko wrote:
The issue still persists if Chrome window is not occupying entire screen space (e.g. if it is tiled alongside another or was floated and resized). If the Chrome window occupies the entire screen space then the issue is not triggered. The issue is also not triggered if I run xmobar, but use win+B to toggle struts off (thus Chrome again occupies the entire screen space).
Xmobar not lowering itself and Chrome expecting to be given the full screen rectangle when being full-screened seem like orthogonal issues. In fact, the latter is a known and thing and there is a workaround in current HEAD in the form of X.U.Hacks.windowedFullscreenFixEventHook[1].
[1]: https://xmonad.github.io/xmonad-docs/xmonad-contrib-0.16.999/XMonad-Util-Hac... -------------------- End of forwarded message --------------------
--
*Eyal Erez <**oneself@gmail.com*