Open Bug 1572513 Opened 3 months ago Updated Last month

Abort and BFCache handling for COEP headers

Categories

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

defect

Tracking

()

People

(Reporter: junior, Assigned: valentin)

References

(Depends on 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

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.

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

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

Assignee: nobody → valentin.gosu
Depends on: 1583863
You need to log in before you can comment on or make changes to this bug.