[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] Signed Int to Float Convertion Problem

Uploaded https://github.com/KhronosGroup/WebGL/pull/2486 documenting the differences in behavior. Kirill, based on your testing, is the change to the WebGL 2.0 specification needed, or could that one be left alone (and a conformance test added)?

Please review. Thanks.


On Tue, Aug 15, 2017 at 1:42 PM, Kenneth Russell <kbr@google.com> wrote:
This is in the fixed function part of the hardware. There's no possibility for emulating the behavior. Since WebGL's hosted on top of a large range of OpenGL versions, it's impossible to guarantee OpenGL ES 2.0's behavior in WebGL 1.0 contexts.

To be honest since this hasn't come up until now I'm inclined to simply mention this in the differences section of the spec and not change the spec. Adding a query to determine the underlying behavior would only slow down startup time for most WebGL apps and add yet more code to the browser for a corner case.


On Tue, Aug 15, 2017 at 12:47 PM, Mark Callow <khronos@callow.im> wrote:

On Aug 15, 2017, at 12:34, Zhenyao Mo <zmo@chromium.org> wrote:

But WebGL1 could be implemented on top of ES2 or ES3, so the question
is do we want to emulate ES2's behavior for WebGL1 implemented on top
of ES3 or desktop GL.

Yes and IIRC it is acceptable for ES implementations to return an ES3 context even when an ES2 context is requested.

I don’t know how practical emulation is.