content-security-policy/frame-ancestors/frame-ancestors-from-serviceworker.https.html.ini WPT FAIL with Fission
Categories
(Core :: DOM: Security, defect, P3)
Tracking
()
People
(Reporter: cpeterson, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-backlog1])
Comment 1•4 years ago
|
||
This will be fixed by the changes within Bug 1599131 - keeping it open for now.
Reporter | ||
Comment 2•4 years ago
|
||
The DOM Fission team is relying on feature teams to debug and fix Fission failures in their tests. If the failure looks like a bug in Fission's DOM or IPC changes, you can send the bug back to me.
We're hoping to enable Fission for a subset of Nightly users in early Q3, so we would like WPT tests to be green for Fission by end of Q2. Whether a particular test failure actually blocks shipping Fission is up to the discretion of the feature team. You all would know better than the DOM Fission which test failures are most important.
You can enable Fission when running WPT tests locally using mach wpt --enable-fission
.
Updated•4 years ago
|
Reporter | ||
Comment 3•4 years ago
|
||
Tracking WPT Fission bugs for Fission M6b (Q2)
Updated•4 years ago
|
Comment 4•4 years ago
|
||
The .ini file was removed within Bug 1599131, marking as a duplicate.
Updated•4 years ago
|
Reporter | ||
Comment 5•4 years ago
|
||
Clearing Fission Milestone for bugs resolved as duplicates. We don't need to track duplicates.
Description
•