According to the GL_ARB_gpu_shader5 specification its main transparent addition is implicit conversion. There’s also things like breaking down/building a float by pieces (frexp/ldexp), packing/unpacking vectors into/from a large scalar, and float <-> int bitwise conversions. It’s a rather huge spec, so it might be tricky to figure out what parts of the shader are leveraging these operations by review (if any). If I have some time I may take them apart in a branch and figure out where the issue is specifically by adding things one step at a time and make a pull request with any fixes. Considering it affects even the simple vertex shader that does nothing but pass vUv and sets gl_Position, it can hopefully be mostly remedied by small changes to widely a shared block.
Facing the issue in Safari 10.1 (12603.1.30.0.34) on Mac.
Safari 11 shipped before the bug was fixed, so you’ll get the error shown in the page. Safari Tech Preview has the fix, so should be a blank page. I just verified on STP 41.
This message disappeared when upgrading to FF 57. I think we can close the issue now.
I’m also seeing this in Safari 11.0.2 on MacOS 10.13.2 😞
My understanding is that the official fix is in Safari 11.1 (see above)
oh god, what have I done…
yes, ff nightly from january 3rd still complains about GL_ARB_gpu_shader5 and dumps all the shaders to the console. in one project I even had to
According to the GL_ARB_gpu_shader5 specification its main transparent addition is implicit conversion. There’s also things like breaking down/building a float by pieces (frexp/ldexp), packing/unpacking vectors into/from a large scalar, and float <-> int bitwise conversions. It’s a rather huge spec, so it might be tricky to figure out what parts of the shader are leveraging these operations by review (if any). If I have some time I may take them apart in a branch and figure out where the issue is specifically by adding things one step at a time and make a pull request with any fixes. Considering it affects even the simple vertex shader that does nothing but pass vUv and sets gl_Position, it can hopefully be mostly remedied by small changes to widely a shared block.
Facing the issue in Safari 10.1 (12603.1.30.0.34) on Mac.

Try this test:
https://trac.webkit.org/export/220983/webkit/trunk/LayoutTests/fast/canvas/webgl/no-info-log-for-simple-shaders.html
Safari 11 shipped before the bug was fixed, so you’ll get the error shown in the page. Safari Tech Preview has the fix, so should be a blank page. I just verified on STP 41.
This message disappeared when upgrading to FF 57. I think we can close the issue now.
I’m also seeing this in Safari 11.0.2 on MacOS 10.13.2😞
My understanding is that the official fix is in Safari 11.1 (see above)