David Hyatt <[EMAIL PROTECTED]> wrote: > Requesting the root favicon.ico automatically I will make configurable > through a pref. The <link> solution is still coming and will be > implemented also, and it will support multiple image formats, and it > will be used in lieu of favicon.ico if specified by a Web page. > > A special icon cache won't be required with some clever RDF work. I'll > be sure to write something up on that when I get into implementing the > feature for actual bookmarks.
If you only use references by the link element the normal image cache would be enough. You only need a special caching if you want bookmarks to keep their icon permanently. But as mentioned earlier: For me 'bookmark icons' are the least interesting use of implementing <link rel="icon" ...>. > The intent here is not to emulate IE. It is to hijack the feature and > do it better than IE. That means supporting <link> and supporting > multiple image formats. Let's not get hung up over the /favicon.ico > part. Heck, I had to support that just to test the darn feature. :) > > /favicon.ico is designed just to be the fallback when no <link> is > specified, and I'll be sure to make it pref configurable so we can > flip it on and off as we determine whether or not it's going to be a > necessity or not. Thanks for the clearification! Two questions remain: * If an icon is referenced in a webpage by the link element it should be displayed immediately, on page loading. * If no icon is referenced in the HTML and if blind-fishing for /favicon.ico is enabled this should _only_ be requested on bookmarking, never at page loading. Greeting, Michi -- Homepage: <http://michael.nahrath.de> PGP-ID: 0x9A4C704C PGP-fingerprint: 3ABA ADC6 6713 4FB5 36D0 B0BD D7D7 517F 9A4C 704C
