We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Context: #70 #71
Given that most reporting API providers are crossed origins, we propose to allow this feature by default for 3rd-party iframes.
User should be able to opt out the feature with the corresponding Permissions Policy.
The text was updated successfully, but these errors were encountered:
[Explainer] Update to fetch-based design
d798762
- Previous discussions about fetch-based API are in WICG#70, WICG#52, WICG#50, WebKit/standards-positions#85 (comment) - Related new discussions in WICG#72, WICG#73, WICG#74, WICG#75, WICG#76, WICG#77
[Explainer] Update to fetch-based design (#71)
00a1f78
- Previous discussions about fetch-based API are in #70, #52, #50, WebKit/standards-positions#85 (comment) - Related new discussions in #72, #73, #74, #75, #76, #77
Some followup discussion on whether to introduce Permission Policy in whatwg/fetch#1715 (comment)
Sorry, something went wrong.
Permissions policy and request limit are handled together in #87 (comment) and whatwg/fetch@8d237d0. Closing this issue.
No branches or pull requests
Context: #70 #71
Given that most reporting API providers are crossed origins, we propose to allow this feature by default for 3rd-party iframes.
User should be able to opt out the feature with the corresponding Permissions Policy.
The text was updated successfully, but these errors were encountered: