Closed Bug 944550 Opened 8 years ago Closed 10 months ago

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

Categories

(Firefox for Android Graveyard :: Favicon Handling, defect)

All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: rnewman, Unassigned)

References

Details

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
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.