Closed Bug 1620709 Opened 4 years ago Closed 4 years ago

content-security-policy/frame-ancestors/frame-ancestors-from-serviceworker.https.html.ini WPT FAIL with Fission

Categories

(Core :: DOM: Security, defect, P3)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1599131
Tracking Status
firefox76 --- wontfix
firefox77 --- fixed

People

(Reporter: cpeterson, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [domsecurity-backlog1])

This will be fixed by the changes within Bug 1599131 - keeping it open for now.

Priority: -- → P3
See Also: → 1599131
Whiteboard: [domsecurity-backlog1]

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.

Tracking WPT Fission bugs for Fission M6b (Q2)

Fission Milestone: M6 → M6b
Severity: normal → S3

The .ini file was removed within Bug 1599131, marking as a duplicate.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE

Clearing Fission Milestone for bugs resolved as duplicates. We don't need to track duplicates.

Fission Milestone: M6b → ---
You need to log in before you can comment on or make changes to this bug.