JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.
Chrome now supports SVG favicons! https://chromium-review.googlesource.com/c/chromium/src/+/1541185 …
Pro tip: you don’t need any HTML to declare a favicon. Host your SVG file at /favicon.ico and serve it with the correct MIME type (image/svg+xml). https://mathiasbynens.be/notes/rel-shortcut-icon … 
-
Genuine question: Pro tip or a hack that happens to work? Doesn’t seem like a best practice to me(?)
Which part exactly? All browsers request /favicon.ico by default (see link in tweet for my old write-up). And file extensions don’t matter on the web; MIME types do. I see nothing wrong with this.
-
-
But how would you handle the fallback for browsers that don't support SVG favicon?
-
If you need a fallback, then definitely use <link rel=icon>. I just won’t be doing that:https://twitter.com/mathias/status/1196820845915705344 …
- Još 1 odgovor
Novi razgovor -
-
-
OK. Personally, I’d avoid it, because you’d need a custom setup for your server (e.g. npx serve doesn’t work out of the box). And working locally with the file (via SVG editors etc.) becomes more complicated.
-
But avoiding one request is indeed a nice benefit.
- Još 2 druga odgovora
Novi razgovor -
-
-
I anyway generate my favicon and set it during runtime
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
"file extensions don't matter on the web" How exactly does YOUR server determine the MIME type of a file when serving it?
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.