cairo-dock-team team mailing list archive

[Fabounet <fabounet03@xxxxxxxxx>]

"Which is probably reasonable and seems to follow the standard"
I was thinking the exacte opposite :-)
If the goal is to have a window that is considered as another application
(than chromium), then the WM_CLASS should be set to something else.
As we can see, the WM_CLASS is still "Chromium". The window name (the first
string) is used to distinguish between instances of the same app, but we
precisely don't want to consider a web app as a chromium process (if I'm
understanding correctly the goal).
Now, we (all WM and dock-like programs) are forced to make a special-case
code, and swap window name and class name :-/

This seems like a hack to me, but well, I guess we don't have choice here.
So ok for applying your patch (and thank you very much for providing it by
the way ;-) )


2013/10/22 Jay Schmidek <jay@xxxxxxxxxxx>

> Chromium sets the class of the window to the name of the browser and the
> window instance name to the specific app. Which is probably reasonable and
> seems to follow the standard, so I think it unlikely that they would be
> willing to change the behavior.
>
> Application shortcuts look like this btw:
> WM_CLASS(STRING) = "mail.google.com__mail_u_0", "Chromium"
>
> Gnome Shell and Unity properly handle this already.
> In BAMF they have a special case for web app windows:
> http://bazaar.launchpad.net/~unity-team/bamf/trunk/view/head:/src/bamf-matcher.c#L1489
>
> --
>
> https://code.launchpad.net/~shim/cairo-dock-core/special-case-class-for-chromium-apps/+merge/191898
> You are requested to review the proposed merge of
> lp:~shim/cairo-dock-core/special-case-class-for-chromium-apps into
> lp:cairo-dock-core.
>

-- 
https://code.launchpad.net/~shim/cairo-dock-core/special-case-class-for-chromium-apps/+merge/191898
Your team Cairo-Dock Devs is requested to review the proposed merge of lp:~shim/cairo-dock-core/special-case-class-for-chromium-apps into lp:cairo-dock-core.