Ian Thomas <[EMAIL PROTECTED]> wrote: > Support for IE-style 'favicons' next to bookmarks will shortly be added > to Mozilla, as a result of bug > http://bugzilla.mozilla.org/show_bug.cgi?id=32087 > > There are two ways for selecting the correct favicon > 1) Using the icon specified in the relevant <LINK> tag in the header of > the HTML page > 2) If there is no link tag, then automatically trying favicon.ico
I can't find reference at the moment, but wasn't there (at least ideas for) an extension to http:-headers (... now I found it, it is all described in the bug!)? Might be an interesting third way to apply an icon to a whole site with only one line of text in the .htaccess file. > I have no problem with the first method, since it only happens if the > webpage author indends it to happen. > > However, if the webpage author has not thought about using favicon.ico > then the second method will create a 404 on the server every time it is > bookmarked (or possibly just visited, I'm not sure when the favicon is > called for) and slow down web access. Relying on the link-element gives us the opportunity to do it much better than IE does. _If_ an icon is linked inside a page, we can display the icon immediately whereas IE needs the site to be bookmarked first (and even then is qute unreliable ...). I think, doing like Konquerror and requesting /favicon.ico at each call for a page should be out of discussion. That would produce far too much bogus traffic and far too many 404-Errors in webserver's logfiles. Not having the icon before a page is bookmarked is the real weakness of IE's way to use it. What authors realy would like is an icon attached to their site in the beginning, without user action. To achieve this the _will_ implement the neccesary link tag. > Since this is an eyecandy feature, I think we should only be using the > LINK method. The argument that some sites will have to change too many > pages should not be inportant, since any large site should have a method > of changing the design on many pages at once (dreamweaver will do this) > and on small sites it should be easy to do it manually. It will be the easiest for datebase driven sites (yahoo was named earlier ...). Only one extra line in the main template file ... Of course http://mozilla.org should be an example. > Please post your opinions in reply to this post, DO NOT post your > opinions on this subject in the bug report mentioned above. ACK! And sorry for spaming the bug earlier today! What disappoints me in general about David's implementation: All the basics have been worked out inside this bugzilla-bug. Read the first 10 postings again, there was a complete solution of implementing <link rel="icon" href="..." type="..."> in a way that was much mightier than IE's favicon: Multiple graphic formats and displaying the icon at page loading, not at bookmarking. And implementing this would stil be downwards compatible at least with all existing sites that allready use <link rel="shortcut icon" ...>. To me it seems like 'butonator' completely ignores all this discussion's results and the prior consensus, if he writes what I read "we have to do exactly like IE, even if we know that it is a bad thing". There was so much more chance in implementing <link rel="icon" ...> Greeting, Michi -- Jetzt auch mit PGP-Schl�ssel: <http://michael.nahrath.de/pgp.asc>
