Comments on: Defender of the Favicon

By: Laurent V.

Laurent V. — Fri, 18 Jul 2008 09:30:32 +0000

ridiculous

By: Spocke

Spocke — Thu, 17 Jul 2008 18:16:45 +0000

This is just super cool. People have to much time and to little to do but still I love it. :)

By: p01

p01 — Thu, 17 Jul 2008 16:08:16 +0000

Schill: Haven't dug how to get Safari to update the favicon either. Also now, DEFENDER of the favicon falls back to Canvas display if the user agent do not support toDataURL(), like Safari 3.1.2 Unless IE8 behaves funny like Safari, I see no problem to generate a favicon for it ... not using Canvas of course. Per RFC 2397, base64 encoding is not required. A good old escape( String.fromCharCode.apply( String, yourBytesArray ) ); will work and perform well in case one's rendering approach does not provide native base64 encoding.

By: Schill

Schill — Thu, 17 Jul 2008 15:09:39 +0000

It’s worth noting the JS-generated favicon doesn’t seem to work in Safari, nor IE (versions with broken data: support, anyway.) Perhaps the community here may have some ideas.. ;)

In Safari at least, I can display a favicon using a data: URI in a within the HTML and Safari will pick this up, but won’t apply the data: URIs generated by javascript. (Maybe bad formatting, MIME type, DOM change isn’t quite right, or ?) .. I’m using XBM for what it’s worth, and p01 is using canvas, exporting to PNG as noted. With data: you should be able to provide several base64-encoded formats – PNG, BMP, XBM etc.. it’s possible Safari doesn’t support PNG nor XBM in favicons, but I haven’t really dug into it yet.
FWIW it appears that this whole process seems to make Firefox churn a bit doing garbage collection (related thread.)

By: V1

V1 — Thu, 17 Jul 2008 14:02:23 +0000

great game, To bad javascript games are easy to cheat with :(

By: genericallyloud

genericallyloud — Thu, 17 Jul 2008 13:20:55 +0000

BRILLIANT!!!!!