-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cross-origin isolation tracking issue #294
Labels
Comments
swissspidy
added a commit
that referenced
this issue
Mar 27, 2024
swissspidy
added a commit
that referenced
this issue
Mar 27, 2024
Otherwise the setting persists, even when switching browsers. See #294
With 5605028 there is now at least a nicer fallback: |
This was referenced Apr 25, 2024
6 tasks
Looks like there is a proposal for an alternative to cross-origin isolation, see #674 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related:
SharedArrayBuffer is required for things like ffmpeg.wasm and wasm-vips and for this cross-origin isolation is needed.
There is a MutationObserver and a PHP class to make this as smooth as possible, but there are still some quirks here and there.
See also
Cross-Origin-Embedder-Policy: credentialless
status: https://developer.chrome.com/blog/coep-credentialless-origin-trial/Known issues
Plugins using web workers
wp-content/plugins/wordpress-seo/js/dist/analysis-worker.js
workerCross-Origin-Embedder-Policy: require-corp
header (This is required regardless of same-origin or cross-origin).htaccess
rule to set the headerglobalThis.Worker
to always turn URLs into blob URLs?Broken embed previews in the editor
One cannot easily embed iframes in COEP environments.
There are two relevant headers/configs:
Cross-Origin-Embedder-Policy: credentialless
(not supported in Safari)<iframe credentialless>
(not supported in Safari or Firefox)#384 fixed this for Chrome, but other browsers don't yet support
credentialless
iframes.So in Firefox and Safari, embed previews in the editor look like this:
Relevant resources:
Potential workaround:
The text was updated successfully, but these errors were encountered: