Don't you always want your favicon at / regardless because everything that grabs favicons automatically will look there, and not parse your /index.html to figure out what the meta tag is?
Other than that, this seems very handy!
Favicon Cheatsheet
31–40 of 55 posts
Re: Favicon Cheatsheet
#32Earlier quoted context omitted.
That's what I thought too, until I did more research on ICO and couldn't come up with an answer for "Why use png in addition to ico?" in the FAQ (well, except for touch devices where ico isn't supported). Notice how that FAQ question is empty. But if you could submit a pull request with a bulleted list of PNG advantages over ICO, I'd be happy to include it. Seriously.
PNG is a properly specified format with written documentation. ICO has many undefined and assumed values. The only reason you would use ICO for favicons instead of PNG is that it supports multiple images.
What's your GitHub username? I'd be very interested in hearing more specifics and possibly collaborating to adjust the recommendations if needed.
Re: Favicon Cheatsheet
#33This collection of vendor-specific hacks is an excellent demonstration of the failure of the Web standards process.
>an excellent demonstration of the failure of the Web standards process After reading the wikipedia article, it appears that IE is the only browser that doesn't support the W3C standard. It's high time to stop supporting the monstrosity that is IE. All webapps and websites should be built for standards-compliant web browsers, and prompt the user to install one if they are on IE, and simply refuse to work otherwise. T…
Good luck with that.
Re: Favicon Cheatsheet
#34Here's an idea for an app: 1. Upload a large, centered image, and have it spit out all of these different sized, optimized favicon images for me. The initial image should be large enough to accommodate all lower sizes. Any takers? :)
The thing is, it's pretty much impossible to optimize images for such small sizes. If you want perfect favicons, you'll have to make them yourself.
Look at this example: http://www.typophile.com/node/60577 (Youtube's old favicon)
Re: Favicon Cheatsheet
#35Earlier quoted context omitted.
>an excellent demonstration of the failure of the Web standards process After reading the wikipedia article, it appears that IE is the only browser that doesn't support the W3C standard. It's high time to stop supporting the monstrosity that is IE. All webapps and websites should be built for standards-compliant web browsers, and prompt the user to install one if they are on IE, and simply refuse to work otherwise. T…
Good luck with that.
Why is it so unlikely? The simple fact is that demand for the internet is inelastic. There is no good reason to not install Firefox. It is open-source, standards-compliant, more secure, as fast (if not faster) than IE. All it takes is for companies to say no - you have to spend 5 minutes installing a different browser (and you'll be glad you did).
Time to grow some balls.
Re: Favicon Cheatsheet
#36Why don't we have mipmapping on the web? I've never heard anyone suggest it before, but it seems like a good solution to this problem and all the other pixel ratio kinds of problems.
Re: Favicon Cheatsheet
#37Earlier quoted context omitted.
Good luck with that.
Why is it so unlikely? The simple fact is that demand for the internet is inelastic. There is no good reason to not install Firefox. It is open-source, standards-compliant, more secure, as fast (if not faster) than IE. All it takes is for companies to say no - you have to spend 5 minutes installing a different browser (and you'll be glad you did). Time to grow some balls.
Try telling that to enterprise IT.
Re: Favicon Cheatsheet
#38"Forcing a Favicon Refresh ... For yourself and all site visitors: Append a query string. (TODO: find out if any browsers have problems with this.)"
Don't do this - it prevents the file from being cached by some proxies [1]. Instead, use a filename-based approach to 'cache busting' [2].
[1] http://www.stevesouders.com/blog/2008/08/23/revving-filename... [2] https://github.com/h5bp/server-configs-apache/blob/master/.h...
Re: Favicon Cheatsheet
#39Could not believe we should be considering giving so many different favicon sizes from 195px (Opera Speed Dial) down to 16px. Wider SVG support in favicons would be welcome.
> Wider SVG support in favicons would be welcome. I believe SVG still has no support for hinting (or not enough to be worth talking about). Because of the resolution range, either extremely strong rasterizer hinting (supporting not only pixel-snapping but the complete addition or removal of features and the like) or multiple bitmaps is necessary to avoid getting either blocky output at "high" resolutions or a blurry…
SVG has a "shape-rendering:crispEdges" option that you can use to snap lines to pixels. See this blog post for more details:
http://simurai.com/post/19895985870/icon-sharpness-limbo
Re: Favicon Cheatsheet
#40Earlier quoted context omitted.
Why is it so unlikely? The simple fact is that demand for the internet is inelastic. There is no good reason to not install Firefox. It is open-source, standards-compliant, more secure, as fast (if not faster) than IE. All it takes is for companies to say no - you have to spend 5 minutes installing a different browser (and you'll be glad you did). Time to grow some balls.
Try telling that to enterprise IT.
Let's say Google said it. "If you want to use Google, then you need to stop using IE." There would be some complaining, but they'd get it done.
That's where the "balls" part comes in: you have to tell your users, that you just don't support their platform. Happens all the time, but for some reason browsers are treated specially and we all live in fear of losing the IE market share.