The Syncthing favicon shown in my browser tab (across Firefox, Edge or Brave web browsers) is currently stuck in the notification state of ‘Notify’ (a white exclamation mark concentrically circumscribed in a filled black disk). Furthermore, no other state icons are shown regardless of whether the client is paused/resumed/syncing.
Heeding this question (though not strictly applicable as I am neither bookmarked nor restricted to Firefox), I deleted the browsers’ cache, restarted Syncthing and restarted the computer. None of these have solved the issue.
The main culprit is probably browser-side caching, rendering this status-icon rather useless. Here, it only seems to work somewhat well in Chrome…
But there’s also some weirdness under the hood, as here it gets triggered by the Syncthing-instance which serves the GUI having an ‘undefined’ connection state no matter what is actually happening. Sounds a bit weird to me, but alright.
I honestly think it’s probably best to move away from having an adaptable fav-icon and move it to somewhere inside the actual GUI.
I think it can’t be browser-side caching - since I barely use Edge, this was the first time the URL http://127.0.0.1:8384/ was ever entered into it, yet the bug sprung straight away. Also, clearing the cache made no difference.
The stuck warning-favicon has become a great source of anxiety for me - every now and then my eyes would wander to the tab making me fear if the sync has actually stopped (connection loss, drive full etc), then I would go and look at the page, find it was crying wolf, yet come away feeling uneasy that something, somewhere, deep down, must be broken and I will discover years later that sync hadn’t really been working at the time …
As to moving the badge inside the GUI, ironically, I disagree. Having a tiny notification badge right on the tab is pretty convenient (when it works properly)- at a glance the user can tell if Syncthing needs attention, or not, without having to open the page/tab.
Probably because it’s a double-folded issue; some oddness in deciding which icon to show combined with browser-side favicon caching (which I think is mostly a separate system/mechanism).
When the condition within the brackets is met, sure. But I personally doubt whether that’s possible as it’s usually not expected that the favicon changes on the fly and the results vary quite a bit depending on the used browser (when testing locally).
But I’m no front-end expert so perhaps there are possibilities. But otherwise no icon beats a faulty one any day.