Skip to content
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

Inform user why WebGL is not available #1225

Open
pyalot opened this Issue Sep 18, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@pyalot
Copy link
Contributor

pyalot commented Sep 18, 2015

It is frequently the case that a WebGL context cannot be obtained for reasons todo with blacklists, performance caveats etc.

The Web Application programmer has insufficient information to devise a meaningful message to the user in such cases.

A UA should offer the capability to a Web Application to display the reason why WebGL will not run, and if possible offer an actionable advise to the user how this situation can be rectified.

@pyalot

This comment has been minimized.

Copy link
Contributor Author

pyalot commented Sep 18, 2015

@kenrussell

This comment has been minimized.

Copy link
Contributor

kenrussell commented Sep 18, 2015

As discussed on the mailing list, the webglcontextcreationerror's statusMsg should provide some baseline information. Is that information inadequate?

@treeform

This comment has been minimized.

Copy link

treeform commented Sep 18, 2015

Hey @kenrussell, I wrote the original email I was not aware that statusMessage has any thing useful. So far I only managed to make it produce "Web page was not allowed to create a WebGL context." by disabling webGL in about://flags in chrome. I will be tracking other messages that it gets to see if its good enough. If it is - great - thats exactly what I want, maybe i was just missing documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.