Matthew Thomas wrote: > Having to insert <link rel="icon" > href="http://www.microsoft.com/your/browser/spams/me/for/favicon.ico";> > in every page on my site, so as to avoid all my pages getting the icon > of my Web hosting provider (who I have no semantic relationship with > whatsoever), means that I am having to opt out of the icon feature > rather than opting in. That's wrong, for *any* Mozilla distribution.
Why? If you're with a hosting provider where you don't have your own domain, you're probably already subjected to other, ruder forms of intrusion, such as popup windows or ad banners. I see the /favicon.ico thing as a great convenience. I can define an icon for my whole site in one hit, and then use <link> to selectively override it for certain pages. This, I believe, offers the most flexibility one could possibly want. > It's the Webmaster, not the user, who needs to be able to set the pref > to determine whether their server gets hit for the icon. And ... well, > look at that! There *is* a way for the Webmaster to set the pref. If > they want the hit on the server, they use LINK. If they don't, they > should not need to do anything. Opt-in, not opt-out. But <link> doesn't scale. Even on my relatively small site, I have enough pages for me not to bother wanting to go around and stick a <link> element on every page. What if I move the icon files around? I have to update all the pages. ptooey. Not everyone has convenient automatic chrome generation scripts like mozilla.org has. -Ben
