[Public WebGL] Why does the set of pname arguments for which the behavior of getShaderParameter is defined not match GL ES?

Boris Zbarsky [email protected]
Tue Apr 17 19:37:20 PDT 2012

The spec defines the behavior of getShaderParameter for the following 

GL ES section 6.1.8 defines non-error-generating behavior of GetShaderiv 
for the following pnames: SHADER_TYPE, DELETE_STATUS, COMPILE_STATUS, 

At first glance, Gecko allows passing all 5 of the pname values defined 
in GL ES.  Is the WebGL spec intending to disallow passing 
INFO_LOG_LENGTH and SHADER_SOURCE_LENGTH?  If so, it might need to 
explicitly say so somewhere....


You are currently subscribed to [email protected]
To unsubscribe, send an email to [email protected] with
the following command in the body of your email:
unsubscribe public_webgl

More information about the public_webgl mailing list