Bug 215407
Summary: | Introduce "cross-origin-isolated" permission | ||
---|---|---|---|
Product: | WebKit | Reporter: | yhirano |
Component: | Page Loading | Assignee: | Chris Dumez <cdumez> |
Status: | NEW | ||
Severity: | Normal | CC: | achristensen, anthony.bowker, beidson, cdumez, chi187, ggaren, hypertree, lolwebkitbugtracker, tibor.klajnscek, tomac, webkit-bug-importer, wilander, youennf, ysuzuki |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Bug Depends on: | |||
Bug Blocks: | 218943, 218944 |
yhirano
Introduce "cross-origin-isolated" permission to allow a document to
control whether nested documents can access features that require
securer context, even when COOP+COEP are enabled.
https://github.com/whatwg/html/pull/5752
https://github.com/whatwg/html/issues/5435
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/66919726>
Sanjay Kumar
Hello, any comments, updates here ?
Without support for these headers we really can't do SharedArrayBuffers and Atomics - which means no pthreads either.
Mozilla has taken the lead on this and enabled it last year. Chrome is going to enforce it soon too - though they already allow SharedArrayBuffers on both Android and Desktop.
Apple makes great CPUs (and devices) but you give up that advantage when you disable multithreading. Please support these headers so we can have supercharged multithreaded WASM powered webapps. Thank you.
Yusuke Suzuki
@Chris this is also related to SharedArrayBuffer thing.