There's also a reporting API, so you can gather data on requests that failed as a result of Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy. Once you do this, your page will not be able to load cross-origin content unless the resource explicitly allows it via a Cross-Origin-Resource-Policy header or CORS headers ( Access-Control-Allow-* and so forth). You can make a page cross-origin isolated by serving the page with these headers: Cross-Origin-Embedder-Policy : require-corp Check if SharedArrayBuffer is used by any of your third-party resources to understand impact and guidance.
If you intend to enable cross-origin isolation to continue using SharedArrayBuffer evaluate the impact this will have on other cross-origin elements on your website, such as ad placements.
If you don't think you can make this change in time, you can register for an origin trial to retain the current behavior until at least Chrome 109. SharedArrayBuffer is currently available in Desktop Chrome, but from Chrome 92 it will be limited to cross-origin isolated pages.However, it's only available to pages that are cross-origin isolated. SharedArrayBuffer is currently supported in Firefox 79+, and will arrive in Android Chrome 88.It's fair to say SharedArrayBuffer has had a bit of a rough landing on the web, but things are settling down. To secure more time to introduce ways to relax the requirement to enable cross-origin isolation, we've decided to postpone the restriction on SharedArrayBuffer on desktop described in this article to Chrome 106 (originally Chrome 103). To secure more time to reliably relax the requirement to enable cross-origin isolation, the deprecation trial of SharedArrayBuffer on desktop will be extended until Chrome 109.
0 kommentar(er)
