Google Page-Hiding Snippet un-hide logic is delayed by tracker tailing leaving the document blank with opacity:0 for at least 4 seconds
Categories
(Core :: Networking: HTTP, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox-esr60 | --- | wontfix |
firefox57 | --- | wontfix |
firefox58 | --- | wontfix |
firefox59 | --- | wontfix |
firefox60 | --- | wontfix |
firefox61 | --- | wontfix |
firefox62 | --- | fix-optional |
People
(Reporter: frick, Unassigned)
References
Details
(Keywords: regression, Whiteboard: [necko-triaged][comment 5 explanation])
Reporter | ||
Comment 1•7 years ago
|
||
Comment 2•7 years ago
|
||
Updated•7 years ago
|
Comment 3•7 years ago
|
||
Reporter | ||
Comment 4•7 years ago
|
||
Comment 5•7 years ago
|
||
Comment 6•7 years ago
|
||
Updated•7 years ago
|
Updated•7 years ago
|
Comment 7•7 years ago
|
||
Comment 8•7 years ago
|
||
Updated•7 years ago
|
Comment 9•6 years ago
|
||
Comment 10•6 years ago
|
||
Comment 11•6 years ago
|
||
Comment 12•6 years ago
|
||
This is a dupe of bug 1516552 as far as I can tell (see https://bugzilla.mozilla.org/show_bug.cgi?id=1516552#c15 and https://bugzilla.mozilla.org/show_bug.cgi?id=1484713#c18). The page in comment 0 has the same code snippet and comment 4 verifies this also.
I don't think this has anything to do with tailing. We just end up blocking GA/GTM, and as a result we don't run their async initializer, so the backup 4 second timeout initializer is used, hence the delay observed.
Feel free to dupe against that bug unless there is any other work that's supposed to be done here besides the solution proposed there...
Comment 13•6 years ago
|
||
Thanks. The difference here is that bug 1484713 manifests when Tracking Protection is enabled, something we don't ship by default. Tailing (shipped default on) may cause this delay to manifest as well.
OTOH, I don't see this delay much while browsing myself.
I'll duplicate this to 1516552, which seems like a general solution.
Comment 14•6 years ago
|
||
I think the only possible way that tailing can make this happen is if it delays the loading of the GA/GTM script by so long that the 4-second timeout kicks in before that... Actually, now that I think about that, if my guess there is true, then that problem wouldn't be fixed if we fixed bug 1516552, since that bug is purely about the resource being blocked. Perhaps there is more to this bug then?
(But similar to you, I can't reproduce this right now either...)
Comment 15•6 years ago
|
||
Ups, yes. When we block, we can replace. But when we delay, we likely are not going to replace with a shim...
The purpose of tailing /is/ to delay. And the use case from comment 0 reproduced this very well, when the snippet was deployed.
I can't think of a solution except referring the scripts in question as sync or defer (which actually hurts the web and perfomance...) or do some kind of a whitelisting on our side.
Since 57, I've hit just one other page that was manifesting this delay during my daily browsing.
Some googling for this issue shows that it's not anything that people would widely suffer from.
I'm changing to WONTFIX.
Description
•