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.

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

COEP shouldn't take effect in data URL frames. #23785

Closed
wants to merge 1 commit into from

Conversation

yutakahirano
Copy link
Contributor

Related to whatwg/html#4930.

@yutakahirano
Copy link
Contributor Author

Chrome and Firefox pass the current test, which means they will fail with this change.

I'm puzzled by the Firefox behavior because they pass no-secure-context.html.

@annevk
Copy link
Member

annevk commented May 27, 2020

What's the basis for making this change? data: URLs are a secure context. If they do not enforce the policy you could have a way to smuggle non-cross-origin isolated data into a cross-origin isolated process, no?

@yutakahirano
Copy link
Contributor Author

I saw old comments such as whatwg/html#5198 (comment) and the (current) Chromium implementation and thought that data URLs are not secure contexts.

But you changed the spec after that, right? w3c/webappsec-secure-contexts#69 w3c/webappsec-secure-contexts#72

@annevk
Copy link
Member

annevk commented May 27, 2020

Yeah, I did. I'll update the comment in that issue.

@yutakahirano
Copy link
Contributor Author

Thanks!

@annevk annevk deleted the yhirano/coep-data-url branch May 27, 2020 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants