Open Bug 1598800 Opened 3 months ago Updated 1 month ago

Fix dom/tests/browser/browser_localStorage_e10s.js and dom/tests/browser/browser_localStorage_snapshotting_e10s.js for Fission

Categories

(Core :: Storage: localStorage & sessionStorage, defect, P2)

defect

Tracking

()

Fission Milestone M4.1

People

(Reporter: cpeterson, Assigned: janv)

References

(Blocks 1 open bug)

Details

Jan, Hsin-Yi's DOM test spreadsheet for Fission says you will investigate these browser_localStorage_e10s test failures this week (Nov 18). Do you have any updates?

We had to finish something for 71, I'll try to address this bug this week.

Component: DOM: Core & HTML → Storage: localStorage & sessionStorage

It's not very hard to fix browser_localStorage_e10s.js, I have patch for that.
I'm still working on fixing browser_localStorage_snapshotting_e10s.js

Actually, after more thinking about this, there's more work to be done. The goal of these tests is to verify that localStorage data accessed from different content processes for given origin is consistent. However, current fission makes it so that a new process is not created for the same origin in these tests, so the consistency is not tested. I asked around if it will be ever possible (with fission) to have different processes for the same origin and the answer is yes, so we need to figure out how to modify these tests to create different processes for the same origin.

I spoke with Nika, a new process can be created by setting these headers:
cross-origin-embedder-policy
cross-origin-opener-policy

You need to log in before you can comment on or make changes to this bug.