1572513 - Abort and BFCache handling for COEP headers

Status: RESOLVED FIXED

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

Description

[Junior [inactive]]

https://phabricator.services.mozilla.com/D40143#1241568

Hmm. I think I'd prefer it if we didn't set the COEP here. Theoretically at this point the document could have the load aborted, in which case the previous document would now have the COEP of the document it was trying to load imposed on it, or we could navigate through the BFCache and end up at the wrong document.

Comment 1

[Anne (:annevk)]

Should this also block bug 1477743? It only blocking a closed bug doesn't really make it visible.

Comment 2

[Junior [inactive]]

It's in 3.1.4: https://mikewest.github.io/corpp/#integration-html
Theinitialize the Document object algorithm sets the embedder policy for Documents to which a browsing context is navigated by adding a new step directly after Referrer Policy is initialized in step 6:

    Let document’s embedder policy be the result of obtaining an embedder policy from response.

Not sure if it makes sense to set the policy in Document::StartDocumentLoad like we set the Referrer-Policy
https://searchfox.org/mozilla-central/rev/15cff10fa2d10fcc763b22e909412dcd6e9c4e88/dom/base/Document.cpp#2989

Comment 3

[Valentin Gosu [:valentin] (he/him)]

Attachment: Bug 1572513 - Set the embedder policy when intializing the Document object r=nika

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/3020047e7580
Set the embedder policy when intializing the Document object r=nika

Comment 5

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/3020047e7580