Favicon.ico request & display cannot be turned off using current options menu

RESOLVED WONTFIX

Status

()

Firefox
Preferences
RESOLVED WONTFIX
13 years ago
12 years ago

People

(Reporter: dvd_id10t, Assigned: Ben Goodger (use ben at mozilla dot org for email))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

The 1.0 released version of FireFox always tries to get some sort of icon from a
site, in order to add that icon to the bookmark, and some other things.

I don't want my browser to display such icons.  I looked through
tools->options... and a few other places, and found no easy way to turn off the
icon search.

This is one feature of IE that I could do without.  At least give me a way to
turn it off.

Reproducible: Always

Steps to Reproduce:
1. Go to any website, watch Firefox attempt to find favicon.ico.
2. Try and turn off favicon.ico search in tools->options...

Actual Results:  
I found no way to turn off favicon search.

Expected Results:  
Let me turn off the search and display of favicons.
This is something that's too obscure for users to wrap their heads around.  Use
about:config and filter on favicon, but this doesn't need UI.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WONTFIX
(Reporter)

Comment 2

13 years ago
(In reply to comment #1)
> This is something that's too obscure for users to wrap their heads around.  Use
> about:config and filter on favicon, but this doesn't need UI.

I'm a user, and I managed to figure out that I don't like, or want, favicons. 
How exactly am I supposed to figure out what I need to change in about:config to
get them to go away?
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs,
filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in before you can comment on or make changes to this bug.