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

COEP: Should reports be visible to reporting observers? #5634

Closed
jugglinmike opened this issue Jun 11, 2020 · 1 comment
Closed

COEP: Should reports be visible to reporting observers? #5634

jugglinmike opened this issue Jun 11, 2020 · 1 comment
Labels
topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal.

Comments

@jugglinmike
Copy link
Contributor

The Reporting API reads:

A report type is a non-empty string that specifies the set of data that is contained in the body of a report.

When a report type is defined (in this spec or others), it can be specified to be visible to ReportingObservers, meaning that reports of that type can be observed by a reporting observer. By default, report types are not visible to ReportingObservers.

COEP uses two report types ("coep", "coep-navigation") without formally defining them. The default value is clear, but like any default (especially for a developing standard), it is difficult to say whether it's being used intentionally.

Are COEP reports intended to be withheld from reporting observers? If so, would the editors accept a patch to explicitly state that intent?
@yutakahirano yutakahirano added the topic: cross-origin-embedder-policy Issues and ideas around the new "require CORP for subresource requests and frames and etc" proposal. label Jun 11, 2020
@yutakahirano
Copy link
Member

Thank you! COEP reports should be visible to ReportingObservers. I'll include that in #5454.

This was referenced Jun 11, 2020
Merged
Merged
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

No branches or pull requests
2 participants
@jugglinmike @yutakahirano