Closed
Bug 600756
Opened 14 years ago
Closed 14 years ago
favicon from previous location persists until new page finishes loading
Categories
(Firefox :: Tabbed Browser, defect)
Firefox
Tabbed Browser
Tracking
()
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
blocking2.0 | --- | beta8+ |
People
(Reporter: Margaret, Assigned: Margaret)
Details
Attachments
(2 files, 1 obsolete file)
24.50 KB,
image/png
|
Details | |
4.33 KB,
patch
|
Details | Diff | Splinter Review |
After bug 597673 landed, we stopped hiding the favicon while the tab is busy, but we don't update the favicon until the page finishes loading.
When we fix this we should try to find a way to avoid clearing the icon for same-host location changes, or at least page refreshes/reloads.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → margaret.leibovic
Comment 1•14 years ago
|
||
(In reply to comment #0)
> After bug 597673 landed, we stopped hiding the favicon while the tab is busy,
> but we don't update the favicon until the page finishes loading.
We update the favicon as soon as we get a new one -- the exact point actually depends on the site.
> When we fix this we should try to find a way to avoid clearing the icon for
> same-host location changes, or at least page refreshes/reloads.
Ideally we would also avoid clearing the icon when the new one would be available shortly after.
Updated•14 years ago
|
blocking2.0: --- → beta8+
Assignee | ||
Comment 2•14 years ago
|
||
This patch immediately fades out the old favicon on location change and then replaces it with the blank page icon after a delay.
Attachment #481053 -
Flags: review?(dao)
Assignee | ||
Comment 3•14 years ago
|
||
Oops, I forgot a line.
Attachment #481053 -
Attachment is obsolete: true
Attachment #481056 -
Flags: review?(dao)
Attachment #481053 -
Flags: review?(dao)
Assignee | ||
Comment 4•14 years ago
|
||
Bug 602964 makes this invalid.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Assignee | ||
Updated•14 years ago
|
Attachment #481056 -
Flags: review?(dao)
You need to log in
before you can comment on or make changes to this bug.
Description
•