At one point a Safari Tech Preview release mentioned "Added support for SVG favicons" - https://web.archive.org/web/20250228004931/https://webkit.or... - but then they removed it - https://webkit.org/blog/16512/release-notes-for-safari-techn... - and I haven't been able to get an explanation of what happened there.
Every browser has 2 zones: website controlled, browser controlled. There are many reasons why don't want any dynamic, website controlled content outside of website zone, inside browser zone.
Favicons are website controlled.
I'm supposing Safari's SVG implementation when moved to supporting favicons meant there were security holes, probably scripting exploits, but also potential XML exploits, so they removed until they could fix these, with a probable low priority.
on edit: ok evidently that was a stupid assumption on my part, as it got a downvote - why is it stupid though? SVG inline needs to support scripting, SVG is XML - if Safari's SVG implementation meant that SVG favicons were open to either XML exploits or scripting exploits that were not adequately handled in the first release (because sitting in the browser chrome part of code instead of web site part of code) then they might have pulled it back quickly until they could fix that.
You really want to support different file formats to maximize support. You can have additional favicons as fallback if SVG isn’t supported. This page has some info on that: https://atlasiko.com/blog/web-development/favicon-size/
And here’s a helpful generator for converting SVG to all the other file formats: https://favicon-generator.s2n.tech/
I love SVG favicons, but unfortunately Safari’s bastardized support for SVG icons make them a non-ideal choice.
Doesn't seem to work anymore but Defender of the Favicon was a playable version of defender in a 16x16px square
I use animated SVG favicons in a Firefox extension I've been building. They actually work a treat
Yeah, it is good, but it does not work in Safari.
(2021)