Closed Bug 190471 Opened 23 years ago Closed 22 years ago

Web site icon (favicon) can't be re-cached

Categories

(SeaMonkey :: Location Bar, defect)

x86
Linux
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: imc, Assigned: hewitt)

References

Details

User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.2.1) Gecko/20030117, build 2003011714 This is related to bug 188636 but a bit different. Obviously we don't want Mozilla to go reloading favicons all the time but it would be useful if it checked back now and again (once a week or once a month?) to see if the favicon changed. Even without that (as I realise it's controversial), it would be nice if there were a way to deliberately re-cache the icon without having to invalidate the entire cache. Reproducible: Always Steps to Reproduce: 1. Set browser.chrome.favicons to true. 2. Create a web site that doesn't have /favicon.ico 3. Visit the web site. 4. You've decided your web site should have an icon, so create /favicon.ico 5. Reload your web site. Obviously no icon (as discussed above). 6. Manually visit /favicon.ico on your web site. 7. Icon appears in the browser window but not the URL bar. 8. Go to about:cache and list the disk cache entries. Actual Results: The cache now has two entries for /favicon.ico - one saying it exists and one saying it doesn't exist. This is clearly inconsistent. Of course, when Mozilla draws the URL bar it believes the cache entry saying it doesn't exist whereas when Mozilla loads the icon as document content it presumably believes the entry saying that it does exist. Expected Results: Remove the incorrect cache entry and re-cache the icon, thus enabling it to be displayed in the URL bar.
Blocks: 113430
shift-reload works for me ... it will reload all objects on that page.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.