-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Test cross origin isolation with webview extensions #158792
Comments
Servers that don't set the CORP header:
|
VolarBlocked linkshttps://cdn.jsdelivr.net/gh/johnsoncodehk/sponsors/sponsors.png Other issuesI'm unable to get the extension working in the web. The |
I worked through the golden scenario of jupyter. Everything worked as expected in regards to COI. However, the surface area of Jupyter is much bigger, so there can still be surprises. |
Refs: #137884
Complexity: 4
Create IssueBackground: On vscode.dev, we have the ability to enable cross origin isolation - that's the enabler for shared array buffers which unlocks many interesting scenarios (like "vscode-wasi") and 1st level TypeScript/Pylance support. Enabling cross origin isolation (COI) requires us to set two http header COOP and COEP. The latter means only resources that are OK with being embedded will load. This doesn't affect resources from VS Code itself but can affect resources that extensions load. They need to be served with the CORP header.
Testing: Check-off one of the extensions below and play around with their webview (or notebook renderering) features, like GitLens settings editor etc. Observe dev tools for errors
https://insiders.vscode.dev/
with the?vscode-coi
-query partThe sample below is GitHub issue notebook. Notice how avatars aren't loading and how each request shows as blocked.
The text was updated successfully, but these errors were encountered: