Block re-navigation due to <meta charset> when Cross-Origin-Opener-Policy or Cross-Origin-Embedder-Policy is set
Categories
(Core :: DOM: Core & HTML, enhancement)
Tracking
()
People
(Reporter: annevk, Unassigned)
References
Details
This being a potential issue was raised by Nika in https://github.com/web-platform-tests/wpt/pull/17606#issuecomment-508154077.
From memory I think we have some desire to get rid of this eventually. Perhaps we should use COOP and COEP as signals to disable this "feature" entirely. Especially as it's not entirely clear to me what should happen if first it is COOP (or COEP) and then it is not.
What do you think Henri?
|
||
Comment 1•6 years ago
|
||
(In reply to Anne (:annevk) from comment #0)
What do you think Henri?
As noted on GitHub, I'm OK with disabling parser-initiated renavigations for COOP and COEP, if WebKit and Blink start enforcing the 1024-byte limit when COOP or COEP is in effect.
|
Reporter | |
Comment 2•6 years ago
|
||
I don't plan to pursue this. There should probably still be tests, but they can be tracked via web-platform-tests.
Description
•