-
Notifications
You must be signed in to change notification settings - Fork 439
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
When WASM is disabled in browser, it displays a blank page #1507
Comments
This is indeed something that has popped up recently because the enhancement of "enhanced security". The default template only checks for the presence of Javascript, but not webassembly. It's an easy change indeed. This can be changed either upstream in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type:
NPE version: WASM https://nuget.info
OS version: Windows 11
Installed from: Not Applicable
In the case of a BUG:
What is the current result?
Displays a blank page when WASM is disabled, or when enhanced security is enabled!
What is the expected result?
It should display a landing page with info on why WASM is disabled, either offer steps to enable WASM (like disabling enhanced security) or to install NPE desktop app from MS Store.
Are there any workarounds? yes
Enable WASM in the browser (sometimes by disabling the enhanced security)
In case of a FEATURE REQUEST:
It is often confusing for regular people to know about WASM and to know why the page hasn't been working. It takes a look into console log in Dev Tools to know that the site is WASM enabled and it needs WASM to work.
Sometimes, orgs enable enhanced security by policy and it's not possible to bypass that and that disables some of the experimental features in the browser including WASM. Providing a simple landing page detecting those features and providing help may do some good and help relieve frustrations of those users.
NOTE: This could be simple and I'll help if the team has not enough time to look into this. Just point me to where the appropriate source files are and I'll do the rest. Thanks!
The text was updated successfully, but these errors were encountered: