codehenry / xmonad

Automatically exported from code.google.com/p/xmonad
0 stars 0 forks source link

Problems with toggling focus on Chrome #603

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. In tiling mode, open up Chrome
2. Open up another window, say urxvt
3. Try toggling back and forth the focus with <Mod-Tab>

What is the expected output? What do you see instead?
Chrome should be responding to keyboard, mouse movement. But it just does not 
seem to realize it is on focus.

What version of the product are you using? On what operating system?
xmonad 0.11.1
ghc 7.10.1
Chrome 43 beta
Arch Linux

Are you using an xmonad.hs?  Please attach it and the output of "xmonad
--recompile".
The problem persists even without an xmonad.hs

Please provide any additional information below.
In the attached image, you can see that the currently focused window is 
red-bordered (lower right), but it's not responding to keyboard strokes or 
anything unless I explicitly move the cursor there and click on it.

Original issue reported on code.google.com by p...@cnphil.com on 30 Apr 2015 at 4:36

Attachments:

GoogleCodeExporter commented 8 years ago
Does your xmonad.hs use EwmhDesktops? If not, please try configuring it:
http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-EwmhDesktops.html

Increasingly, recent gtk3 does not actually speak X11 but only the Wayland 
emulation parts of EWMH, which means that it is less and less compatible with 
non-Gnome3 and plays less and less well with applications that are not based on 
the same or later version of gtk3. I suspect whatever gtk3 this Chrome is using 
simply does not recognize X11 focus any more, only Wayland emulation focus. 
This suggests that Chrome will in the future not be worth the effort on X11 at 
all, unless you run nothing but Gnome3 environment and approved 
Gnome3-compatible programs.

Original comment by allber...@gmail.com on 30 Apr 2015 at 4:48

GoogleCodeExporter commented 8 years ago
Chrome 42 or older does not have this problem.

I've tested Chrome 43 under i3 and Plasma 5, both works. Seems to be xmonad's 
issue.

Original comment by p...@cnphil.com on 30 Apr 2015 at 4:49

GoogleCodeExporter commented 8 years ago
Yes, I imagine both come with Wayland emulation aka EWMH out of the box. You 
must explicitly configure that in xmonad via EwmhDesktops; only ICCCM support 
is enabled by default.

Original comment by allber...@gmail.com on 30 Apr 2015 at 4:52

GoogleCodeExporter commented 8 years ago
Solved after configuring EWMH.

Thank you so much for the quick response! :-)

Original comment by p...@cnphil.com on 30 Apr 2015 at 5:00

GoogleCodeExporter commented 8 years ago

Original comment by allber...@gmail.com on 30 Apr 2015 at 5:24

GoogleCodeExporter commented 8 years ago
Relevant reference doc for configuration: 
http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-EwmhDesktops.html

Original comment by s...@google.com on 10 Jul 2015 at 6:39