Ben Bucksch wrote: > I am unhappy to inform you that David Hyatt sneaked in* a change to the > default pref so that /favicon.ico is now retrieved by default, see bug > 109843 (but please comment here). This is contrary to what he previously > <http://bugzilla.mozilla.org/show_bug.cgi?id=108823#c14> said to do. >
For 0.9.6. Did you really read that bug as some sort of permanent capitulation? If so, I apologize, and perhaps should have been more clear. The favicon pref was disabled for 0.9.6, because I had not completed the work to implement the miss cache (as I outlined in bug 108823). The pref needed to default to off, because the implementation was not complete. > * not announced in any relevant bugs or discussion We're in the middle of a milestone. Enabling this pref now doesn't inconvenience anyone, and it enables us to get some wider testing of the feature to ensure that everything is working properly. (Some good bugs on ICOs have been filed from people who would not have turned on the feature otherwise.) > * bug intentionally filed in the wrong module It was filed in Browser-General. I didn't even know there was a "GUI Features" XPApps component until someone moved it to that component. There was no intentional filing of the bug in the wrong module, and for you to accuse me of doing that intentionally is just plain childish. > The only thing irritating me is that Brendan said: > >> The consensus among mozilla.org staff is that it's ok for this pref to >> be on by >> default, at least until we get a storm of protests from webmasters (we >> may not). > I'm seeing a lot of ridiculous assumptions and accusations being made about the general architecture of the feature itself. If you're going to hurl inflammatory remarks in this newsgroup and/or make grossly inaccurate judgments based on incorrect assumptions about the architecture of the favicon feature, at least get your facts straight. Dave ([EMAIL PROTECTED])
