In development mode, Jax wraps WebGL calls so that it can call gl.checkError() after each one, and hopefully produce a meaningful stack trace.
However, this functionality was previously disabled under Chrome due to performance issues so serious that even in development mode it was not really viable.
Since then, Firefox has implemented functionality that raises very detailed warnings. If webgl.verbose is true, it includes a line number and reference to the OpenGL ES specification. If false, it raises a single warning that GL errors were encountered. Either way, Firefox now handles this scenario much more effectively than Jax ever could.
Since it's no longer useful in Firefox and not viable in Chrome, it makes sense to deprecate the wrapper methods completely, in favor of direct calls to the GL context.
In development mode, Jax wraps WebGL calls so that it can call gl.checkError() after each one, and hopefully produce a meaningful stack trace.
However, this functionality was previously disabled under Chrome due to performance issues so serious that even in development mode it was not really viable.
Since then, Firefox has implemented functionality that raises very detailed warnings. If
webgl.verboseis true, it includes a line number and reference to the OpenGL ES specification. If false, it raises a single warning that GL errors were encountered. Either way, Firefox now handles this scenario much more effectively than Jax ever could.Since it's no longer useful in Firefox and not viable in Chrome, it makes sense to deprecate the wrapper methods completely, in favor of direct calls to the GL context.