Full-screen messes up tabs on google chrome

Hi, I've started encountering a strange issue with xmonad and google chrome. After a full-screen chrome (e.g. by watching a youtube video and hitting "f"), the top part of chrome goes behind xmobar. If I make a layout change or open another window or app then it pops back into place, but this is a little bit annoying. I have some screenshots to try and illustrate this issue: During full-screen: https://ibb.co/z4hjC31 Before full-screen: https://ibb.co/TPPgRVS After full-screen: https://ibb.co/Y2vK1Xq Is it my setup that's the problem? Is there any way to fix it? My config file as available here: https://controlc.com/09924e80 Thank you -- There are 10 types of people, those who know binary and those who don't.

Hi, On Sat, Jul 03, 2021 at 06:43:19PM +0300, Eyal Erez wrote:
I've started encountering a strange issue with xmonad and google chrome. After a full-screen chrome (e.g. by watching a youtube video and hitting "f"), the top part of chrome goes behind xmobar. If I make a layout change or open another window or app then it pops back into place, but this is a little bit annoying. I have some screenshots to try and illustrate this issue: [...]
Looks like your xmobar isn't lowering itself on start. Do you have `lowerOnStart = False` or `overrideRedirect = False` in your .xmobarrc by any chance? -- Tomáš "liskin" ("Pivník") Janoušek, https://work.lisk.in/

Hi! Minor nitpick - your "during" and "after" screenshots seem to be the same images (after-fullscreen). Regardless, I'm able to reproduce the issue my config as well (only on Chromium, for example Firefox does not have the same issue). The problem gets even worse if the inital browser window is smaller (e.g. half or quarter of the screen). Seems that the browser uses the full-screen size for positioning contents and does not get notification about the new window size in time. Testing similar scenario under XFCE does not trigger the bug. Looks like the issue is somewhere between Xorg/Xmonad sending the resize events and Chrome/Chromium handling them. Tomas, I tried your suggestion about xmobar - doesn't seem to be the issue, different settings had no effect. Best regards, Platon Pronko On 2021-07-03 18:43, Eyal Erez wrote:
Hi,
I've started encountering a strange issue with xmonad and google chrome. After a full-screen chrome (e.g. by watching a youtube video and hitting "f"), the top part of chrome goes behind xmobar. If I make a layout change or open another window or app then it pops back into place, but this is a little bit annoying. I have some screenshots to try and illustrate this issue:
During full-screen: https://ibb.co/z4hjC31 https://ibb.co/z4hjC31 Before full-screen: https://ibb.co/TPPgRVS https://ibb.co/TPPgRVS After full-screen: https://ibb.co/Y2vK1Xq https://ibb.co/Y2vK1Xq
Is it my setup that's the problem? Is there any way to fix it? My config file as available here: https://controlc.com/09924e80 https://controlc.com/09924e80
Thank you
-- There are 10 types of people, those who know binary and those who don't.
_______________________________________________ xmonad mailing list xmonad@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad

Hi, On Sat, Jul 03, 2021 at 07:06:10PM +0300, Platon Pronko wrote:
Tomas, I tried your suggestion about xmobar - doesn't seem to be the issue, different settings had no effect.
That's truly weird. Can you post your .xmobarrc and the output of `xwininfo -root -tree`? xmobar should be the last window in the list. One might also try `checkDock --> doLower` in their manageHook, which does the same thing as xmobar with lowering on start enabled. -- Tomáš "liskin" ("Pivník") Janoušek, https://work.lisk.in/

Hi! I went even further - I killed xmobar entirely (and two another dock-like applications I use). 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). Here's screenshots from my setup (without xmobar): Before fullscreen: https://ibb.co/5xHskxz During fullscreen: https://ibb.co/S509Rrr After fullscreen: https://ibb.co/gg6hYyZ The issue does not reproduce for you? Best regards, Platon Pronko On 2021-07-03 19:10, Tomas Janousek wrote:
Hi,
On Sat, Jul 03, 2021 at 07:06:10PM +0300, Platon Pronko wrote:
Tomas, I tried your suggestion about xmobar - doesn't seem to be the issue, different settings had no effect.
That's truly weird. Can you post your .xmobarrc and the output of |xwininfo -root -tree|? xmobar should be the last window in the list.
One might also try |checkDock --> doLower| in their manageHook, which does the same thing as xmobar with lowering on start enabled.
-- Tomáš "liskin" ("Pivník") Janoušek, https://work.lisk.in/

[[ 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
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 --------------------

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*

On Sun, Jul 04 2021 14:19, Eyal Erez wrote:
Thank you very much for looking into this so quickly and deeply.
Like I said, I'm not sure that this is actually your issue (though it certainly fixes *one* issue that people often have with Chrome).
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?
You need to add this to your event hook once it is available (the documentation should tell you how to do this). Waiting for a new release is not strictly necessary, you can also compile the git version of xmonad-contrib yourself.
participants (4)
-
Eyal Erez
-
Platon Pronko
-
Tomas Janousek
-
Tony Zorman