But is that really a useful distinction when many of those browsers are at less than 1% market share (and possibly no longer receive updates)? This is not a feature critical to the functioning of a website, so adopting it won’t break anything other than the presence of an icon for a minority of users. It’s still a choice to be made of course, I just think it’s a perfectly valid choice either way. It’s very different to adopting some new JavaScript syntax with the potential to completely break your site for many users, or CSS changes without a fallback that break the layout when not supported.
Maybe I’ll consider using SVG favicons when the standard way is supported by more than 35% of the current browsers on caniuse.
It seems to imply that it is 66.94%, with mainly Safari doing its own thing. Am I reading it wrong?
It’s 66.94% of users, but 35% of the browsers.
But is that really a useful distinction when many of those browsers are at less than 1% market share (and possibly no longer receive updates)? This is not a feature critical to the functioning of a website, so adopting it won’t break anything other than the presence of an icon for a minority of users. It’s still a choice to be made of course, I just think it’s a perfectly valid choice either way. It’s very different to adopting some new JavaScript syntax with the potential to completely break your site for many users, or CSS changes without a fallback that break the layout when not supported.