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
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 |
LGTM to experiment from 132 to 134 inclusive.
--
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/2862bb57-5bac-46e9-86b6-4294083fb8a5n%40chromium.org.