Closed Bug 1619649 Opened 6 months ago Closed 2 months ago

Ship COOP+COEP (aka "resab")

Categories

(Core :: DOM: Core & HTML, task, P2)

task

Tracking

()

RESOLVED FIXED
mozilla79
Tracking Status
firefox79 --- fixed

People

(Reporter: annevk, Assigned: tt)

References

Details

(Keywords: dev-doc-complete)

Attachments

(2 files)

We should flip the following three preferences to be enabled by default on early beta or earlier (with the exception of Android where they will remain disabled), once all dependencies of this bug are fixed, and only as long as browser.tabs.documentchannel and javascript.options.shared_memory continue to be enabled on early beta or earlier:

browser.tabs.remote.useCrossOriginOpenerPolicy
browser.tabs.remote.useCrossOriginEmbedderPolicy
dom.postMessage.sharedArrayBuffer.withCOOP_COEP

High-level documentation continues to be at https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer/Planned_changes.

(This is a follow-up to bug 1594748 following a number of design changes to the technology.)

Intent to ship: https://groups.google.com/d/msg/mozilla.dev.platform/-hYWoob95LI/k160l4k7AwAJ

Priority: -- → P2

try for Central as Beta simulation: https://treeherder.mozilla.org/#/jobs?repo=try&revision=8156c3a98d4581ea39ae6320634271052d5d42d0
Edit: The result looks bad, but the m-c which I am using is also not rather new. I wonder if some of failures are related to bug 1635783 (which is fixed). So here is another try push: https://treeherder.mozilla.org/#/jobs?repo=try&revision=66562531266d151ca2d0061cf440e5652d984c4d

We might also want to see the result for the late Beta simulation, but I guess checking the result for the early Beta should be enough for now.

I'm starting to think that once the remaining issues are addressed we should go for shipping, as it's not clear to me that enabling on early beta or earlier but no further will give us much additional benefit.

Shipping would at least require an "Intent to ship". It's not clear to me if anything is needed beyond that, but Mike will look into it I hope.

Flags: needinfo?(mconca)

(In reply to Anne (:annevk) from comment #2)

Shipping would at least require an "Intent to ship". It's not clear to me if anything is needed beyond that, but Mike will look into it I hope.

I talked to a few folks and it seems the intent-to-ship is the main blocker. I understand a quick check-in with Luke and/or ekr is also happening prior to this.

Flags: needinfo?(mconca)
Summary: Enable COOP+COEP (aka "resab") on early beta or earlier → Ship COOP+COEP (aka "resab")
Attachment #9158862 - Attachment description: Bug 1619649 - Ship COOP+COEP; → Bug 1619649 - Set the prefs for COOP header, COEP header, and postMessage SAB to true on all channels;
Assignee: nobody → ttung
Status: NEW → ASSIGNED
Pushed by ttung@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e82b2460bff0
Set the prefs for COOP header, COEP header, and postMessage SAB to true on all channels; r=nika
https://hg.mozilla.org/integration/autoland/rev/00d72d88ddce
Update a few wpt tests' expectations; r=nika,annevk
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
See Also: → 1648685
You need to log in before you can comment on or make changes to this bug.