In Bug 941868 we tried -- and failed -- to cut down the number of places in which we respond to tab events by fetching and setting a favicon. This bug is a follow-up to try again. Notable scenarios: * Tab restore. * Back handling. * Document-driven location changes. * Opening external links. * Tab switching. * about:home, which is part of a set of special-cased URLs that are synchronously enfaviconed during display... and still suffer a later asynchronous load that's immediately discarded.
You need to log in before you can comment on or make changes to this bug.