Open Bug 1473601 Opened 2 years ago Updated 3 months ago
Investigate caching favicon requests better
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.
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.
You need to log in before you can comment on or make changes to this bug.