Closed Bug 350440 Opened 19 years ago Closed 14 years ago

Wrong icon (favicon) assigned to bookmark upon viewing error page

Categories

(Firefox :: Bookmarks & History, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: 32768, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b2) Gecko/20060826 BonEcho/2.0b2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b2) Gecko/20060826 BonEcho/2.0b2 If you have a bookmark for a site that no longer exists and results in an error page, revisiting that bookmark will cause the wrong icon to be assigned to the bookmark. Reproducible: Always Steps to Reproduce: 1. Navigate to non-existant location such as http://www.sduhdakfhguhkuhs.com 2. Bookmark this page 3. Navigate to http://www.google.com/ 4. Load the bookmark that goes to the non-existant page Actual Results: google.com icon is assigned to the sduhdakfhguhkuhs.com bookmark Expected Results: Either the warning icon (exclamation mark), or no icon, should be assigned to the sduhdakfhguhkuhs.com bookmark
I can reproduce it under MacOS and the build: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1b2) Gecko/20060827 BonEcho/2.0b2 ID:2006082703
(In reply to comment #2) > Maybe a duplicate of bug 271359 ( > https://bugzilla.mozilla.org/show_bug.cgi?id=271359 ) ? > It's possible, but it doesn't seem like it to me and there doesn't _seem_ to be enough information to know for sure. Bug 271359 seems to refer to some sort of race condition where you try to load a second bookmark while another site is currently loading. This bug has clear steps to reproduce, and occurs even if the current site has fully loaded. This bug also refers to the error pages which (correct me if I'm wrong) I don't think existed back then. If someone can reproduce both bugs and can figure out that it is the same cause then do merge.
(In reply to comment #3) > (In reply to comment #2) > > Maybe a duplicate of bug 271359 ( > > https://bugzilla.mozilla.org/show_bug.cgi?id=271359 ) ? > > > > It's possible, but it doesn't seem like it to me and there doesn't _seem_ to be > enough information to know for sure. > > Bug 271359 seems to refer to some sort of race condition where you try to load > a second bookmark while another site is currently loading. > > This bug has clear steps to reproduce, and occurs even if the current site has > fully loaded. This bug also refers to the error pages which (correct me if I'm > wrong) I don't think existed back then. > > If someone can reproduce both bugs and can figure out that it is the same cause > then do merge. > Agreed. I confirm on "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b2) Gecko/20060826 BonEcho/2.0b2".
Status: UNCONFIRMED → NEW
Ever confirmed: true
It is very unlikely that this will be fixed before the coming Firefox 2.0; even if you would have a safe patch I wouldn't give this much chance. The next release will use Places and in this new bookmarks/history system this bug is not present anymore.
Can someone with privileges nominate this bug as blocker for Firefox 4 ? Because I don't want that this bug will be still forgotten for more years...
(In reply to comment #15) > Can someone with privileges nominate this bug as blocker for Firefox 4 ? > Because I don't want that this bug will be still forgotten for more years... if it's not a regression from 3.6 to 4, it won't get blocking regardless its age. So it would be a useless nomination.
The wrong favicon appearing is not critical data loss.
Partially, because it overwrite favicon with this yellow triangle with "!" in center. It's the same like it will be overwriting bookmark name or address.
Can you reproduce in Firefox 4 RC/Final?
I can't, but nice will be when someone who also experienced bug confirm this. Because sometimes bug appear, sometimes not, as far I remember. :)
Can't reproduce it anymore and no word from other users, so closing this one as WORKSFORME. If someone feel otherwise, please reopen.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.