Document-Isolation-Policy allows a document to enable crossOriginIsolation for itself, without having to deploy COOP or COEP, and regardless of the crossOriginIsolation status of the page. The policy is backed by process isolation. Additionally, the document non-CORS cross-origin subresources will either be loaded without credentials or will need to have a CORP header.
None
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
Two crashes have been reported (crbug.com/394350439 and crbug.com/393480086) which will force us to turn down the experiment in M132 and M133. We would like to give enough time to tester to report any additional issues, so we'd like to extend the trial by 2 milestones.
None.
None
Our Origin Trial will only be supported on Windows, Mac and Linux at first, as support on Android requires more development work due to the different process allocation model. We will add support on Android as soon as possible. Support on Android WebView is not possible due to the lack of process isolation.
https://wpt.fyi/results/html/document-isolation-policy?label=experimental&label=master&aligned
Origin trial desktop first | 132 |
Origin trial desktop last | 134 |
Origin trial extension 1 end milestone | 136 |
That still puts you within the 6 milestones you can get for free
- so, LGTM to extend to 137.
If you truly want to stop at 136, you can do that too. But you've
got an extra milestone in case you need it.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67a63f67.2b0a0220.2908d.02b2.GAE%40google.com.