-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
[html] Test COEP derivation in shared workers #20899
[html] Test COEP derivation in shared workers #20899
Conversation
Thanks for writing this! It would help if variable names were consistent. E.g., consistently refer to frame or owner for the frame. Now, it's not clear to me how you deal with the worker failing to load. If the owner/frame requires COEP and the worker does not, how is that handled? (Also, "default COEP" is not entirely clear to me, "without COEP" / "with COEP" or "none" / "require-corp" would be clearer.) I also think it'd be worth adding Hope that helps. |
html/cross-origin-embedder-policy/resources/shared-worker-fetch.js.py
Outdated
Show resolved
Hide resolved
0ccd8b7
to
a77c21f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've rebased and addressed (my own) review comments. If bots are green, I think this can be merged.
When #27226 is merged, I will rebase this PR again. |
a77c21f
to
bc798de
Compare
This may be incorrect. I'm trying to verify that COEP is initialized according to the new algorithm for workers. I'm second-guessing myself because Chromium 78 fails the interesting cases: