Closed
Bug 265996
Opened 20 years ago
Closed 20 years ago
favicon corruption
Categories
(Core :: Networking: Cache, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: bugs, Assigned: darin.moz)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041002 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041002 Firefox/0.10.1 The downloading of favicons from various sites, such as http://www.discogs.com/, http://freedesktop.org/, and http://www.gmane.org/ results in corrupt favicons that look horrible in the tabs. The problem is hard to reproduce, since it seems to occur at random and some sites may work one time and then not work the next. Reproducible: Sometimes Steps to Reproduce: 1. Open http://www.discogs.com/ or some other site with a favicon. Actual Results: Favicon winds up looking like a fly that's been stepped on, then run over by a car, and then had a safe dropped on it. Expected Results: A crisp favicon, displaying, for example, a vinyl record (http://www.discogs.com/), the freedesktop logo (http://www.discogs.com/), or a bold capital G, rotated 270 degrees counter-clockwise. This bug has also hit me when using epiphany. I initially reported it as a bug in that software, see http://bugzilla.gnome.org/show_bug.cgi?id=133457.
| Assignee | ||
Comment 1•20 years ago
|
||
hmm... how is this a cache bug? reporter: can you reproduce this using a more recent mozilla build, like mozilla 1.8a4?
I can't reproduce this with firefox 0.10.1; favicon handling is very different between firefox and mozilla 1.8, though. However, i have no idea where the corruption that you're seeing is coming from.
| Reporter | ||
Comment 3•20 years ago
|
||
Your post on favicon handling being different between firefox and mozilla got me thinking. It seemed to be working fine in mozilla at first, but then I remembered that firefox was working through my local squid proxy, whereas mozilla wasn't. So I turned the proxy on for mozilla as well and lo and behold - favicon corruption. Sorry for bothering you with this.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
V/invalid. heh. thanks for the update.
Status: RESOLVED → VERIFIED
QA Contact: core.networking.cache → benc
You need to log in
before you can comment on or make changes to this bug.
Description
•