Open
Bug 1473601
Opened 7 years ago
Updated 3 years ago
Investigate caching favicon requests better.
Categories
(Firefox :: Tabbed Browser, enhancement, P2)
Firefox
Tabbed Browser
Tracking
()
NEW
People
(Reporter: mossop, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: perf)
The image cache gave XUL image elements a very fast way to reload the same favicon a second time, we can replicate this in JS if we want to.
Updated•7 years ago
|
Reporter | ||
Comment 1•7 years ago
|
||
The challenge here is that we can't just blindly cache data for a given favicon url and then on subsequent pages use the cache data. We have to verify that pages are allowed to load the cached favicon since CSP and other things can block the load from one page but not another and those checks are normally performed by the channel for the load.
Blocks: tab-unloading
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•