-
Notifications
You must be signed in to change notification settings - Fork 831
fix: WebView2 local content mapping on Wasm
#21651
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
Conversation
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-21651/docs/index.html |
|
🤖 Your WebAssembly Skia Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-21651/wasm-skia-net9/index.html |
|
The build 179183 found UI Test snapshots differences: Details
|
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-21651/docs/index.html |
|
🤖 Your WebAssembly Skia Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-21651/wasm-skia-net9/index.html |
|
The build 180684 found UI Test snapshots differences: Details
|
GitHub Issue: part of #21601, closes #21685
PR Type:
What is the new behavior? 🚀
The URI is correctly mapped to the location of the document.
For commit b3ac3eb:

Seeing some COEP issues when loading the document locally. Iframe refuses to display the content:
From my testing, I was able to resolve this by adding CORS header manually in the DevTools. Should we do that automatically for the user?
PR Checklist ✅
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Runresults.