Closed
Bug 1250877
Opened 8 years ago
Closed 8 years ago
[e10s] WhatsApp Web favicon disappears soon after loading
Categories
(Firefox :: Tabbed Browser, defect)
Firefox
Tabbed Browser
Tracking
()
RESOLVED
DUPLICATE
of bug 1184739
People
(Reporter: djc, Unassigned)
Details
Since a few days or so, the WhatsApp Web favicon disappears soon after the initial page load (the default globe icon does not appear in its place). Since I have WhatsApp in a pinned tab, this looks a bit weird, especially when the tab is being highlighted (for notification status).
Comment 1•8 years ago
|
||
I'm guessing this should be in some frontend component. I think I've seen this myself after the content process crashed.
Reporter | ||
Comment 2•8 years ago
|
||
I just checked, and I only see this with e10s enabled.
Reporter | ||
Comment 3•8 years ago
|
||
(Sorry for the extra notification: the e10s thing explains the "few days or so" timeline, since I only recently enabled e10s.)
Reporter | ||
Updated•8 years ago
|
Component: Untriaged → Tabbed Browser
Comment 4•8 years ago
|
||
(In reply to Dirkjan Ochtman (:djc) from comment #3) > (Sorry for the extra notification: the e10s thing explains the "few days or > so" timeline, since I only recently enabled e10s.) Can you check if this was a regression during e10s development with mozregression? At least going back to when we enabled e10s by default on Nightly to make it easier to test would help.
Reporter | ||
Comment 5•8 years ago
|
||
I tried with the 2015-03-01 build, and this showed the same problem. Does it make sense to go back further?
Flags: needinfo?(dirkjan)
Comment 6•8 years ago
|
||
(In reply to Dirkjan Ochtman (:djc) from comment #5) > Does it make sense to go back further? Nope, that's probably good enough, thanks.
Updated•8 years ago
|
Summary: WhatsApp Web favicon disappears soon after loading → [e10s] WhatsApp Web favicon disappears soon after loading
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•