Getting a WebGL Implementation
WebGL 1.0 is supported in the stable releases of most major browsers on both desktop and mobile platforms. Chrome, Firefox, Internet Explorer, Opera, and Safari are all known to have good WebGL support on both desktop and mobile browsers. See http://caniuse.com/#feat=webgl for availability details.
Technical issues such as known hardware problems or lack of required GPU features may prevent WebGL from running in some cases.
The WebGL 2.0 specification has recently been released, and developers can now begin experiementing with the new functionality in some browsers. Existing implementations have known functionality gaps and may lack some validation that will be present once WebGL 2.0 is available in stable builds. They are provided to encourage early developer feedback.
WebGL 2.0 requires hardware with OpenGL ES 3.0 support or comparable desktop OpenGL feature support. Not all systems capable of running WebGL 1.0 will be able to run WebGL 2.0.
See https://wiki.mozilla.org/Platform/GFX/WebGL2 for instructions on how to enable WebGL 2 in Firefox.
Please file bugs for any issues you discover with Firefox’s WebGL 2.0 implementation at https://bugzilla.mozilla.org/
Experiemental WebGL 2.0 support is available in recent Chrome Canary builds. In order to enable it you must pass the “--enable-unsafe-es3-apis” flag on the command line. At this point the flag is not accessible through about:flags. The prototype is currently available on Linux, Mac OS, and Windows.
When enabled, WebGL 2.0 contexts can be created with the “webgl2” context ID.
Please file bugs for any issues you discover with Chrome’s WebGL 2.0 implementation at https://crbug.com In addition to describing the problem please navigate to about:gpu and attach the contents of that page to your report, which will help the developers identify the problem in the case that the issue is GPU or OS specific.
Here are a few links to demos using WebGL 2.0 with which you can verify that your browser has it properly enabled. Note that due to bugs in implementations, these may not work correctly in all browsers.