Smarter loading of favicons, handling of spinner state, etc.

NEW
Unassigned

Status

()

5 years ago
4 years ago

People

(Reporter: rnewman, Unassigned)

Tracking

Trunk
All
Android
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
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.
Component: General → Favicon Handling
You need to log in before you can comment on or make changes to this bug.