GNOME Bugzilla – Bug 654661
Incorrect window matching for Chromium app launchers
Last modified: 2013-09-07 01:42:28 UTC
Created attachment 192015 [details] sample desktop launcher file Add the attached file to ~/.local/share/applications. Two scenarios: #1: launch chromium-browser, then launch "Google Calendar" #2: launch "Google Calendar", then launch chromium-browser When you switch windows with alt+tab, it works properly for scenario #2 (the calendar is considered a separate app from the regular browser), but scenario #1 fails (both are regrouped as the "chromium" app).
Some additional info (replicated here BTW- this has been bugging me for a couple of days): Running the following command: xprop WM_CLASS against the calendar window (run from the attached shortcut) gives the following: WM_CLASS(STRING) = "chromium-browser", "www.google.com__calendar_render" whilst vanilla chromium-browser gives the following: WM_CLASS(STRING) = "chromium-browser", "Chromium-browser" There's a (closed) bug on chromium regarding this here: http://code.google.com/p/chromium/issues/detail?id=20587 They seem to think they've fixed the issue but I'm not sure it's been fully understood, or even if it's actually a chromium bug. What is strange is that Gnome works as expected, if you open a chrome application shortcut first (ie #2 above). It then treats the chrome application shortcut as one group, and any new chrome windows (including any new chrome app shortcuts, unfortunately ) go in the "chromium-browser", "Chromium-browser" group. Unity breaks in a similar fashion, and so does cairo dock.
This should have been fixed by bug 673657. *** This bug has been marked as a duplicate of bug 673657 ***