Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce COEP to html and fetch specs #5368

Closed
yutakahirano opened this issue Mar 18, 2020 · 4 comments · Fixed by #5454
Closed

Introduce COEP to html and fetch specs #5368

yutakahirano opened this issue Mar 18, 2020 · 4 comments · Fixed by #5454
Labels
topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal

Comments

@yutakahirano
Copy link
Member

I think it's ready to merge https://mikewest.github.io/corpp/ into https://html.spec.whatwg.org/ and https://fetch.spec.whatwg.org/. What do you think, @annevk and @mikewest?
@mikewest
Copy link
Member

I think we should at least start merging the core where we have solid agreement, just as @camillelamy is doing for COOP. I'd love to review some PRs if you'd like to write them. :)

@mikewest
Copy link
Member

By "core", I mean that the reporting stuff is still a bit new, and likely needs more review/tests/etc.

@yutakahirano
Copy link
Member Author

FYI we added tests through implementation: please see reporting.https.html and cache-storage-reporting.https.html. These fail on wpt.fyi due to the flakiness of reporting API implementation, but they pass on chromium try bots.

@mikewest
Copy link
Member

Ok. Why don't you put together some PRs with what you think is ready, and I'm happy to review them.

@domenic domenic added the topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal label Mar 18, 2020
@yutakahirano yutakahirano mentioned this issue Jun 15, 2020
Merged
3 tasks
domenic pushed a commit that referenced this issue Jun 25, 2020
@yutakahirano
Add cross-origin embedder policy
70b8bb4 
Merges https://github.com/WICG/cross-origin-embedder-policy into HTML.

Associated PRs:

* whatwg/fetch#1030
* w3c/ServiceWorker#1516
* w3c/css-houdini-drafts#992

Fixes #5368, fixes #5634, fixes
whatwg/fetch#985, and fixes
w3c/ServiceWorker#1490.

Follow-up: #4916, #4919, #4930 #5223, and #5391. (As well as defining
cross-origin isolated, per #4732.)
mfreed7 pushed a commit to mfreed7/html that referenced this issue Sep 11, 2020
@yutakahirano @mfreed7
Add cross-origin embedder policy
add7b6e 
Merges https://github.com/WICG/cross-origin-embedder-policy into HTML.

Associated PRs:

* whatwg/fetch#1030
* w3c/ServiceWorker#1516
* w3c/css-houdini-drafts#992

Fixes whatwg#5368, fixes whatwg#5634, fixes
whatwg/fetch#985, and fixes
w3c/ServiceWorker#1490.

Follow-up: whatwg#4916, whatwg#4919, whatwg#4930 whatwg#5223, and whatwg#5391. (As well as defining
cross-origin isolated, per whatwg#4732.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Introduce COEP yutakahirano/html
3 participants
@mikewest @domenic @yutakahirano