Closed
Bug 1750022
Opened 3 years ago
Closed 3 years ago
Make tests in layout/base/tests/ dFPI compatible
Categories
(Core :: Privacy: Anti-Tracking, task, P2)
Core
Privacy: Anti-Tracking
Tracking
()
RESOLVED
FIXED
98 Branch
Tracking | Status | |
---|---|---|
firefox98 | --- | fixed |
People
(Reporter: timhuang, Assigned: bvandersloot)
References
Details
(Whiteboard: [fxatps-dFPI-Mochitests])
Attachments
(1 file)
Convert following tests to be dFPI compatible
- layout/base/tests/test_bug607529.html
- layout/base/tests/test_bug629838.html
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee: nobody → bvandersloot
Assignee | ||
Comment 1•3 years ago
|
||
We are fixing mochitests that fail when network.cookie.cookieBehavior = 5, i.e. when we enable Total Cookie Protection.
This is most often due to the test assuming that an origin will always have access to its storage state when embedded as
a third party.
In this case I had to request storage access to allow an embedded iframe to use a BroadcastChannel to communicate with top-level pages of the same origin.
This was only a problem in the XOrigin case where the test html file is loaded in an embedded iframe and then can't communicate with the top-level window it created.
Pushed by bvandersloot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/25b8169c5503
Make tests in layout/base/tests/ dFPI compatible, r=smaug,anti-tracking-reviewers,timhuang
Comment 3•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox98:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 98 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•