@gerhard Awesome, that’s it! The favicon shows up if I disable the topic count on browser icon.
So there’s probably a bug there.
1 Like
AFAICT the topic count that replaces the favicon is
<link href="data:image/png;base64, [a whole mess of stuff]" rel="icon">
I guess it would be troublesome to have actual image files for all possible count values, but maybe the lower (more common?) ones could be?
EDIT
“AFAICT” - confirmed
1 Like
So, is this a bug, a misconfiguration, or something else?
I don’t really know.
My guess is that when not logged in there is no possibility of there being a notification count favicon and so the site favicon is used.
But when logged in, (and the Setting is checked) the notification count favicon is used as a replacement favicon.
I’m thinking it has more to do with browser behavior than Discourse code. But as you have had the same problem using more than one browser, maybe there is something that could be done in the Discourse code to solve it.
Even then I can’t help but think this is a rather low priority problem. Do most users even notice favicons? My feeling is in the tab maybe not so much, but in “favorites” it would be more so.
Yes, and this appears to work on this instance (Discourse Meta). Just not for my instance.
Exactly, I would say it’s either a setup problem on my side, or a Discourse bug.
It’s surprisingly annoying: like most people, I have many tabs open, and the Discourse tab becomes hard to spot because it doesn’t have an icon. It’s minor, but annoying.
To recap:
- On all browsers: Everything appears to work fine when ‘Topic count on browser icon’ is disabled.
- Firefox & Chrome: Favicon appears briefly then disappears when ‘Topic count on browser icon’ is enabled, even though the topic count should be 0. It seems like some late JavaScript removes the icon or replaces it with a blank one regardless of the actual topic count.
- IE 11: The favicon appears but it doesn’t carry any topic count.
In pictures, with ‘Topic count on browser icon’ enabled (look at icon in tab):
Chrome:
Firefox:
IE 11:
This is different than the original topic, if you want to open a bug on that (off by default) feature, go ahead and create a new topic.