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

Re: [Public WebGL] Should GLfloat and GLclampf be typedefs for "unrestricted float"?



Note that the ES 2.0 specifications clamping behavior is modified by http://www.khronos.org/registry/gles/extensions/EXT/EXT_color_buffer_half_float.txt in that output, blend and clear clamps are removed when the target is floating point.


On Mon, Nov 19, 2012 at 2:18 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

I just tried updating Firefox to handle "float" per WebIDL spec. Specifically, attempts to pass non-finite floats to an argument that takes "float" are supposed to throw; "unrestricted float" is the type that allows all floating-point values.

There are two tests in the WebGL test suite that fail with this change.  Specifically, https://www.khronos.org/registry/webgl/sdk/tests/conformance/misc/type-conversion-test.html passes in NaN for arguments that take a "float" in a bunch of places. So does https://www.khronos.org/registry/webgl/sdk/tests/conformance/more/conformance/quickCheckAPI-L_S.html in a few spots.

What's the expected behavior?  Is this a bug in the tests or in the spec?  To be consistent with the tests, the spec should probably use "unrestricted float" in place of "float"...

-Boris

-----------------------------------------------------------
You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl
-----------------------------------------------------------