On 2014-05-06 9:53 AM, Benoit Jacob wrote: > By default, WebGL does not allow FLOAT to be passed for > the type parameter of the texImage2D method. The OES_texture_float > extension make that allowed.
I have trouble seeing how this could break current implementations. If a page somehow looks for the error as a feature or version check it should still get the correct answer. > There are more examples. Even when OES_texture_float is supported, FLOAT > textures don't support linear filtering by default. That is, in turn, > enabled by the OES_texture_float_linear extension, > http://www.khronos.org/registry/webgl/extensions/OES_texture_float_linear/ This looks similar. Are there extensions which cause rendering differences merely by enabling them? E.g. everything in webgl2 is exposed on a 'webgl' context, and calling getExtension to enable extensions which are also webgl2 core features is a no-op? I guess the returned interface description would need new spec language in webgl2 if there are ever extensions with the same name written against different versions of the spec. Is this what you mean about considering (and writing tests for) all the interactions? It looks like doing so would violate to webgl1 spec. "An attempt to use any features of an extension without first calling getExtension to enable it must generate an appropriate GL error and must not make use of the feature." https://www.khronos.org/registry/webgl/specs/1.0/#5.14.14 It would be like getExtension was silently called on context creation. -r _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
