On Wed, 16 Mar 2016 at 17:12:16 +0100, Michael Biebl wrote:
> I don't know what the plan is here, i.e. if iceweasel.desktop will get
> the old iceweasel icon back. Atm it is broken [1].
> If the transitional iceweasel.desktop is going to use the old iceweasel
> icon, launching the iceweasel process would result in the shell showing
> the firefox icon afaics, with your proposal.
If the Firefox maintainer wants Iceweasel to continue to be something
with its own visual identity, then yes it might make sense to have
command-line options to Iceweaselize it. I personally don't think that
would be worth the implementation effort, but it's up to the maintainer.
I don't think it makes sense for the-thing-launched-as-Iceweasel and
the-thing-launched-as-Firefox to have different icons in the Shell while
running unless the difference is also maintained elsewhere: there's only
one application really, and it's presumably going to identify itself as
Firefox in its title bar, Help->About, etc. in any case (unless special
command-line options or environment variables are added). Similarly, if
you run what you think is Iceweasel and also what you think is Firefox,
I suspect you'll get two windows (or even tabs) in the same app; it can
either identify itself as Firefox all the time, or identify itself as
whichever name you happened to have launched it under first. The latter
seems weird to me.
S
