-
Notifications
You must be signed in to change notification settings - Fork 595
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
Wasm demo: Report an error when opengl context cannot be created #896
Comments
They work for me on the same version of Chromium. |
On Firefox everything works fine. On Chromium in a place where should be wasm sixtyfps demo apps, it's just white. |
E.g. https://sixtyfps.io/releases/0.1.6/demos/slide_puzzle/ when I open Developer Console I see:
|
Yes, I know. It works for me on Firefox on Arch Linux, and on Chromium on Ubuntu. But not on Arch Linux. Based on stack trace , are you able to identify control flow ? Otherwise, if you would have some debugging build with tracing information dumped to console, I am more then happy to try it out and post here results from console. |
Perhaps this is a webgl related problem. What graphics card do you have? Does this demo work for you in Chrome? https://mdn.github.io/webgl-examples/tutorial/sample3/ What does https://webglreport.com/ report for your setup? |
I agree, we should show an alert in that case. |
The main() of our demo could return a Result<> instead of unwrap'ing the Slint result. |
That would be very nice, indeed! I think for that to work, we need to provide an implementation of We could perhaps have a weak dependency on wasm-bindgen in i-slint-core and then implement it there, but that would imply that wasm-bindgen becomes a public dependency in our API, I guess. |
Demos does not work on Chromium 97.0.4692.99 Arch Linux.
(However they work in Firefox...)
The text was updated successfully, but these errors were encountered: