Intent to Ship: WebGL 2.0

Kenneth Russell

unread,

Oct 26, 2016, 5:41:01 PM10/26/16

to blink-dev

Contact emails

z...@google.com, k...@google.com

Spec

https://www.khronos.org/registry/webgl/specs/latest/2.0/

Summary

WebGL 2.0 upgrades WebGL to the OpenGL ES 3.0 feature set. This long-awaited upgrade narrows the graphics feature gap between desktop computers and mobile devices.

"Intent to Implement" blink-dev discussion:

https://groups.google.com/a/chromium.org/d/topic/blink-dev/t7J4Zft8dHk/discussion

Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes.

Demo link

(These demos can all be run in Dev Channel by enabling the WebGL 2.0 prototype in about:flags)

https://toji.github.io/webgl2-particles-2

https://www.khronos.org/webgl/wiki/Getting_a_WebGL_Implementation#Demos

https://floooh.github.io/oryol-webgl2/

http://files.unity3d.com/jonas/tele-5.5b2/

Debuggability

Fully debuggable via DevTools, as is WebGL 1.0.

Interoperability and Compatibility Risk

WebGL 2.0's conformance test suite is open source at https://github.com/KhronosGroup/WebGL . The majority of the tests were ported from drawElements' comprehensive OpenGL ES test suite, which defines Android's OpenGL ES conformance. Many regression tests have been added during the months of development for issues that were discovered by the implementers, as well as developers testing the API.

The test suite is over eight times the size of the WebGL 1.0 test suite, and is running on Chromium's tryservers against a subset of CLs. (The suite is too large to run against every CL that affects the browser.) The tests are so thorough that they have uncovered bugs in every desktop GPU vendor's graphics drivers, most of which have been either fixed or worked around. None of these bugs impact security of the API; they are all issues that affect rendering correctness.

Because the test suite is so comprehensive, there is very little chance of interoperability bugs between browsers. There will be no major changes to the WebGL 2.0 API after shipment.

Firefox aims to ship WebGL 2.0 in the same timeframe (January) as we are hoping to ship it in Chrome.

OWP launch tracking bug

http://crbug.com/641635

Entry on the feature dashboard

https://www.chromestatus.com/features/6694359164518400

Kenneth Russell

unread,

Oct 26, 2016, 6:42:34 PM10/26/16

to blink-dev

One note: I forgot to send this out earlier -- all of our development time's been going into addressing the last remaining conformance test issues on the bots. We're hoping to get this turned on well before the M56 branch point, so prompt feedback would be greatly appreciated. Thanks.

Rick Byers

unread,

Oct 26, 2016, 7:12:22 PM10/26/16

to Kenneth Russell, blink-dev

Hurray for interop testing! Just out of curiosity, are current test results across different implementations available anywhere?

I see this is also in development in WebKit and development is likely in Edge.

LGTM1 to ship.

Kenneth Russell

unread,

Oct 26, 2016, 7:30:55 PM10/26/16

to Rick Byers, blink-dev

On Wed, Oct 26, 2016 at 4:11 PM, Rick Byers <rby...@chromium.org> wrote:

Hurray for interop testing! Just out of curiosity, are current test results across different implementations available anywhere?

The WebGL conformance rules [1] require a 100% pass rate in order to call an implementation conformant. Both Chrome and Firefox are aiming for this number. Some tests are still affected by driver bugs on certain platforms. We'll likely disable these tests for the 2.0.0 shipment, and turn them back on in 2.0.1 as soon as the bugs are fixed.

Chromium's status was reported publicly recently at the Silicon Valley WebGL meetup [2]. Modulo a couple of test failures, on the configurations where Chromium intends to submit conformance results, it's passing 100%. The tests are run on several bots on the chromium.gpu.fyi [3] waterfall, for example these Win [4], Linux [5], and Mac [6] bots. They're also run on these optional Win [7], Linux [8], and Mac [8] trybots. The list of failing tests for which there are still suppressions is here [10]. (The long lists of suppressions are for configurations on the FYI waterfall on which we don't intend to submit conformance results.)

Thanks for your feedback and support!

-Ken

[1] https://github.com/KhronosGroup/WebGL/blob/master/sdk/tests/CONFORMANCE_RULES.txt

[2] https://www.khronos.org/webgl/wiki/Presentations#September_2016_WebGL_Meetups

[3] https://build.chromium.org/p/chromium.gpu.fyi/console

[4] https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20(NVIDIA)

[5] https://build.chromium.org/p/chromium.gpu.fyi/builders/Linux%20Release%20(NVIDIA)

[6] https://build.chromium.org/p/chromium.gpu.fyi/builders/Mac%2010.10%20Retina%20Release%20(AMD)

[7] https://build.chromium.org/p/tryserver.chromium.win/builders/win_optional_gpu_tests_rel

[8] https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_optional_gpu_tests_rel

[9] https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_optional_gpu_tests_rel

[10] https://chromium.googlesource.com/chromium/src/+/master/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py