Pocket stories show "Oops! Something’s gone awry..." when Strict ETP is enabled
Categories
(Core :: Privacy: Anti-Tracking, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox-esr102 | --- | unaffected |
firefox102 | --- | unaffected |
firefox103 | --- | unaffected |
firefox104 | --- | verified |
People
(Reporter: yoasif, Assigned: twisniewski)
References
(Regression, )
Details
(Keywords: nightly-community, regression)
Attachments
(1 file)
STR:
- Enable Strict ETP
- Navigate to: https://getpocket.com/explore/item/8-tips-to-follow-for-when-you-re-walking-for-weight-loss
What happens:
Pocket shows message:
Oops! Something’s gone awry...
There’s been an error. Try refreshing your page and see if that fixes things. If you’re still seeing the issue, please contact our support team.
Expected result:
I see the story.
Console shows:
Google Publisher Tags is being shimmed by Firefox. See https://bugzilla.mozilla.org/show_bug.cgi?id=1713685 for details. sandbox eval code:1:9
Some cookies are misusing the “SameSite“ attribute, so it won’t work as expected 30
Google Analytics and Tag Manager is being shimmed by Firefox. See https://bugzilla.mozilla.org/show_bug.cgi?id=1713687 for details. sandbox eval code:1:9
5:56.95 INFO: No more integration revisions, bisection finished.
5:56.95 INFO: Last good revision: 2df2a290e5fd4f4d1e09744aefefa49ee4f499cc
5:56.95 INFO: First bad revision: 70ef6a243844593f29385e5592b787ecf4252574
5:56.95 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2df2a290e5fd4f4d1e09744aefefa49ee4f499cc&tochange=70ef6a243844593f29385e5592b787ecf4252574
Reporter | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Set release status flags based on info from the regressing bug 1770329
Comment 2•2 years ago
|
||
:twisniewski, since you are the author of the regressor, bug 1770329, could you take a look?
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 3•2 years ago
|
||
Yes, I have a fix pending. Basically after the revamp of the shim in bug 1770329, it seems like we don't have to remove any elements anymore (which is the cause of this bug). I've got a patch in the works, and will land it ASAP.
Assignee | ||
Comment 4•2 years ago
|
||
Updated•2 years ago
|
Pushed by twisniewski@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/cfee4cb2727f don't remove elements in the GPT SmartBlock shim when their slots don't need any content; r=ksenia,webcompat-reviewers
Comment 6•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Comment 7•2 years ago
|
||
Reproduced the issue with Firefox 104.0a1 (2022-07-13) on Windows 10x64. Loading the page from comment 0 with ETP set to strict will display a Oops! Something’s gone awry...
error.
The issue is verified fixed with Firefox 104.0b5 (20220802185803) on Windows 10x64, macOS 11 and Ubuntu 21. The page is correctly loaded while having the ETP set to strict.
Description
•