4 ms·

WebGL 2 practically does not exist on Android. Implementation ranges from "horribly broken" to "barely usable". I've catalogued this before: https://twitter.co

WebGL 2 practically does not exist on Android. Implementation ranges from "horribly broken" to "barely usable". I've catalogued this before: https://twitter.com/JasperRLZ/status/1208593692203859968 https://twitter.com/JasperRLZ/status/1208593692203859968

fulafel 7y ago
Interesting. The Looking at Chrome tests about WebGL2 conformance (https://cs.chromium.org/chromium/src/content/test/gpu/gpu_tests/test_expectations/webgl2_conformance_expectations.txt https://cs.chromium.org/chromium/src/content/test/gpu/gpu_te...) it would look like Android is no worse than other platforms wrt known failing test cases (with link to relevant bugs) there. Firefox seems similar: https://hg.mozilla.org/mozilla-central/file/tip/dom/canvas/test/webgl-conf/mochitest-errata.ini https://hg.mozilla.org/mozilla-central/file/tip/dom/canvas/t... (The conformance part is maintained by Khronos so there should in theory be less bias than vendors own tests)
- Jasper_ 7y ago
  Chrome on Android passes things through to the system OpenGL driver. This is almost certainly a case of terrible platform drivers, but there's nothing I can really do about that.
  - fulafel 7y ago
    It'll still have to go through ANGLE or other GL sandboxing layer to be safe, and there are other OpenGL-backed Chrome platforms (Mac, Linux) that also have driver bugs. If vendor GL driver bugs hurt more on Android, maybe it's just for lack of testing which would lead to browsers or ANGLE adding workarounds for driver bugs. (There are amazing heaps of driver bug workarounds in ANGLE that rewrite malfunctioning GL calls) edit: I guess in theory they might just rely on the Android sandbox without going through the ANGLE GLES implementation, since that should nominally be already hardened for untrusted code. But that sounds too risky from a security POV given how a lot of Android devices in practice don't get timely security updates etc.

fulafel 7y ago

Interesting. The Looking at Chrome tests about WebGL2 conformance (https://cs.chromium.org/chromium/src/content/test/gpu/gpu_tests/test_expectations/webgl2_conformance_expectations.txt https://cs.chromium.org/chromium/src/content/test/gpu/gpu_te...) it would look like Android is no worse than other platforms wrt known failing test cases (with link to relevant bugs) there. Firefox seems similar: https://hg.mozilla.org/mozilla-central/file/tip/dom/canvas/test/webgl-conf/mochitest-errata.ini https://hg.mozilla.org/mozilla-central/file/tip/dom/canvas/t... (The conformance part is maintained by Khronos so there should in theory be less bias than vendors own tests)

Jasper_ 7y ago
Chrome on Android passes things through to the system OpenGL driver. This is almost certainly a case of terrible platform drivers, but there's nothing I can really do about that.
- fulafel 7y ago
  It'll still have to go through ANGLE or other GL sandboxing layer to be safe, and there are other OpenGL-backed Chrome platforms (Mac, Linux) that also have driver bugs. If vendor GL driver bugs hurt more on Android, maybe it's just for lack of testing which would lead to browsers or ANGLE adding workarounds for driver bugs. (There are amazing heaps of driver bug workarounds in ANGLE that rewrite malfunctioning GL calls) edit: I guess in theory they might just rely on the Android sandbox without going through the ANGLE GLES implementation, since that should nominally be already hardened for untrusted code. But that sounds too risky from a security POV given how a lot of Android devices in practice don't get timely security updates etc.