OpenGL-Registry icon indicating copy to clipboard operation
OpenGL-Registry copied to clipboard

OES_viewport_array: Missing INVALID_RANGE error from ScissorArrayvOES()

Open jamieTaylorIMG opened this issue 8 years ago • 4 comments

The function ScissorArrayvOES() added by OES_viewport_array is missing this entry in its error section/listing:

"An INVALID_VALUE error is generated if is negative."

This should probably be added to make it consistent with ViewportArrayvOES() and DepthRangeArrayfvOES(). Also, this error message as used to describe ViewportArrayvOES() has an unnecessary '>' character at the end.

jamieTaylorIMG avatar Jul 21 '17 16:07 jamieTaylorIMG

It's been noted that in section 2.3 - Command Execution (OpenGL ES 3.2 Specification), there is a general error called out for all negative values provided to sizei parameters:

If a negative number is provided where an argument of type sizei or sizeiptr is specified, an INVALID_VALUE error is generated.

So technically the error is there, it's just not called out. We're raising a bug internally to try to resolve this inconsistency.

ghost avatar Oct 25 '17 13:10 ghost

The internal issue is https://gitlab.khronos.org/opengl/API/issues/52

pdaniell-nv avatar Oct 31 '17 19:10 pdaniell-nv

Although it took a while, we did address the missing sizei < 0 error (which was quite widespread) in the core specs. While it would be nice to eventually do this in the separate extension documents, it's a huge amount of tedious work of limited benefit; if you were to propose a PR matching the error in the GL 4.6 spec in this specific case (or as many cases in different extensions as you had energy for), we are open to it, otherwise it isn't going to happen anytime soon.

oddhack avatar Apr 17 '19 08:04 oddhack

Assigning this back to @jamieTaylorIMG as I'm not planning to do it for extensions, unless the WG specifically tasks me with it.

oddhack avatar May 13 '19 12:05 oddhack