-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
Self signed certificates don't lead to error but just to blank page #1615
Comments
I'm debugging this. One thing I noticed is that there's an wolvic/app/src/common/shared/com/igalia/wolvic/browser/engine/Session.java Lines 1240 to 1245 in 71ec70e
However, the returned result of this function is not used in the Chromium implementation: wolvic/app/src/common/chromium/com/igalia/wolvic/browser/api/impl/TabWebContentsObserver.java Line 119 in 71ec70e
Seems like it should be used somewhere to show the error page? |
Yes, I think we could use the same error page as with gecko |
Currently when errors happen when loading a website, Wolvic with Chromium backend just returns a blank page. This fix allows Wolvic with Chromium backend to return an error page customized to each error. Fix Igalia#1615
Configuration
Wolvic version: Wolvic Chromium 1.1
Wolvic build ID: 183021044
Hardware: Quest 3
Steps to Reproduce
Current Behavior
Get a blank page, no content, no error or warning
Expected Behavior
Expect a warning or error message, ideally allowing to accept and go through anyway
Possible Solution
Follow what the Quest or Chrome or Firefox do, namely provide the option to accept temporarily the certificate after showing the problem
Context
Developing content often means self-hosting on LAN urls, e.g. https://192.168.0.123:3000/index.html and providing HTTPS is required to get WebXR.
Error Logs and Stack Traces
The text was updated successfully, but these errors were encountered: