Closed Bug 1620708 Opened 4 years ago Closed 4 years ago

cookies/samesite/iframe-reload.https.html.ini WPT FAIL with Fission

Categories

(Core :: Networking: Cookies, defect, P2)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1594529
Fission Milestone M6
Tracking Status
firefox76 --- wontfix
firefox77 --- fixed

People

(Reporter: cpeterson, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Valentin, can you please have a look at this bug?

Flags: needinfo?(valentin.gosu)
Priority: -- → P2
Whiteboard: [necko-triaged]

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.

I am not totally sure what to think about this test.
That particular test show up as failing on all browsers: https://wpt.fyi/results/cookies/samesite/iframe-reload.https.html?label=master&aligned
I don't completely understand how it works. Maybe the test is simply incompatible with fission?
Andrea, you added the expected-fail in bug 1615389. Do you remember if that was the case?

Flags: needinfo?(valentin.gosu) → needinfo?(amarchesini)

The reason why this test fails is that the iframe is loaded with the wrong content-type (DOCUMENT instead of SUBDOCUMENT).
This bug is a dup of bug 1594529.

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(amarchesini)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.