On Fri, Jan 20, 2017 at 08:09:57PM +0100 I heard the voice of Tadziu Hoffmann, and lo! it spake thus: > > I can confirm this (tested with chromium-55 and a freshly compiled > ctwm-4.0.0-pre.20161230 on openSUSE 13.2 x86_64).
Well, well. I upgraded 54->55 this week, and now I see it too. Amusingly, I can mess with the navbar just fine, and scroll or click around the webpage no problem, but I can't pull up the top menu, or the right-click menu on the page, unless I explicitly f.focus the browser. > Of course, ctwm can give chromium the focus, but for some other > strange reason, chromium does not set the "Client accepts input or > input focus" window manager hint. Specifically, it now sets *NO* WM hints at all. This seems to have happened a couple years ago (on master; who knows where it filtered out into releases). https://chromium.googlesource.com/chromium/src.git/+/1d0990b27c92582c49522705943422fd329a3a02%5E%21/#F0 They made some change to how they set inactive flags, which is fine, but in the process they completely eliminated setting WM_HINTS at all. This is reminiscent of a thread we had a couple years back <https://www.mail-archive.com/[email protected]/msg00211.html> on a similar issue. I guess that means I don't get to keep ignoring it... > Comment out the test beginning on line 3128 in file > "event_handlers.c" ("If the window takes input...") (but leave the > inner test, "4 or 4a"). I think in this case the better fix would be to step back and setup artificial hints in the AddWindow() process when we get none at all. Right now we don't really see the difference between "window doesn't want input" and "window didn't tell us a goddamn thing[0]"; trying to paper over that down at the places its used is probably going to cause more problems than it fixes. Chrome sure has picked up a lot of other weird and annoying things. Last spring[1] it apparently started noticing and stashing and restoring _NET_WM_DESKTOP, so it saves and restores the occupation. Now when I fire it up, nothing happens, until I happen to flip back to the last desktop I had it in, and then, oh, hey, there you are! Except it doesn't know that some ultra-advanced super-modern WM's (like, say, ctwm) can have things in MULTIPLE desktops at once, so THAT doesn't work right either. For even more fun, it sets WM_NAME as UTF8_STRING too, which is completely bogus. [0] And, hey, why should it? ICCCM has only been around since X11R2, there hasn't been time for chrome to catch up to it... [1] https://chromium.googlesource.com/chromium/src.git/+/06405c5944436b431f26037fdc93340842c51de5 -- Matthew Fuller (MF4839) | [email protected] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
