audreyfeldroy / favicon-cheat-sheet

Obsessive cheat sheet to favicon sizes/types. Please contribute! (Note: this may be in flux as I learn new things about favicon best practices.)
MIT License
9.85k stars 413 forks source link

Recommend not to use any HTML for the main favicon #11

Closed mathiasbynens closed 10 years ago

mathiasbynens commented 10 years ago

See http://mathiasbynens.be/notes/rel-shortcut-icon.

Also, recommend default file names for touch icons, as per http://mathiasbynens.be/notes/touch-icons.

audreyfeldroy commented 10 years ago

Thanks for submitting this :)

I noticed an inconsistency that I'm curious to hear your and others' thoughts about:

  1. You say that shortcut icon is "considered harmful" because it:

    a. "doesn’t show up in section 4.12.5 of the HTML5 specification on ‘link types’" b. is "proprietary to Internet Explorer".

  2. By the same reasoning, isn't relying implicitly on the name apple-touch-icon-precomposed just as harmful because it:

    a. doesn't show up in HTML5 specification section 4.12.5.5, Link type "icon" (only /favicon.ico is mentioned) b. is proprietary to Apple

@mathiasbynens Really sorry to bother you about this. I genuinely do want to collaborate and have a lot of respect for all that you've done in this area, so your thoughts would be much appreciated.

grayghostvisuals commented 10 years ago

I've been following the HTML5 Boilerplate and leaving out the favicon link all together. The favicon is picked up automatically, but I do use an .ico and .png in my root directory to cover both scenarios. Works on all browsers -even IE8. :thumbsup:

mathiasbynens commented 10 years ago

@audreyr

By the same reasoning, isn't relying implicitly on the name apple-touch-icon-precomposed just as harmful […]

Yes. The difference is that for favicon.ico you don’t need the HTML anyway, so it’s a no-brainer. For touch icons, you do (if you want broad support, at least).

@grayghostvisuals “Both scenarios”? Simply placing a /favicon.ico on the server enables the favicon in every browser.

grayghostvisuals commented 10 years ago

@mathiasbynens I guess I'm just being OCD for those that won't display a .png. I have noticed most of our current browsers support .png favicons w/out the link ref and honestly it's a bit easier to make a .png over an .ico.

Start @ 2:42 http://css-tricks.com/video-screencasts/122-the-state-of-favicons/

audreyfeldroy commented 10 years ago

@mathiasbynens Okay, thanks. This pull request to stop recommending HTML for the main favicon is generally good. I can merge this in if you:

Again, I like this overall. But I know this is a lot to ask, so if you don't have time to resubmit, I can make the changes and credit you as the git commit author.

@grayghostvisuals I think it's actually better to provide only favicon.ico and not favicon.png:

mathiasbynens commented 10 years ago

I won’t have time for this so feel free to edit my changes as you like! (Also I’m not really familiar with RST. So awkward compared to Markdown!)

Add a bulleted list of what browsers "every relevant desktop browser" refers to

Every browser/version all the way back to IE6, except for SeaMonkey. (It has a setting for /favicon.ico that is disabled by default, as explained in the post.)

audreyfeldroy commented 10 years ago

Cool, thanks @mathiasbynens, really appreciate everything!

audreyfeldroy commented 10 years ago

Just FYI this is merged but I'm still working on formatting. I may have to move this to Markdown like you said.

grayghostvisuals commented 10 years ago

@audreyr Thanks :beers: