WEBGL_debug_shaders zmo@chromium.org Members of the WebGL working group 7

WebGL uses the GLSL ES 2.0 spec on all platforms, and translates these shaders to the host platform's native language (HLSL, GLSL, and even GLSL ES). For debugging purpose, it is useful to be able to examine the shader after translation. This extension exposes a new function getTranslatedShaderSource for such purposes.

[NoInterfaceObject] interface WEBGL_debug_shaders { DOMString getTranslatedShaderSource(WebGLShader shader); }; If no source has been defined, compileShader() has not been called, or the translation has failed for shader, an empty string is returned; otherwise, return the translated source.

1) Should this extension be made available on ordinary web pages?

Earlier versions of this extension noted the following concerns:
1. The precise pattern of how the original shader is translated may yield personally-identifiable information to the web page about the kind of graphics card in the user's computer.
User agents (web browsers) should carefully consider whether or not to expose this extension in non-privileged settings due to these concerns.
On the other hand, benefits of exposing this information to general web pages include:
1. Tools for WebGL developers can provide more detailed information about how the input shader is translated to run on the graphics card, potentially helping the developers make their applications run faster.

Initial revision. Assigned WebGL extension number. Clarify the meaning of "privileged". Fixed mistake where extension still indicated draft status. Renamed "New Functions and Methods" section to "New Functions". Removed webgl module per changes to Web IDL spec. Ratified by Khronos Board of Promoters. Added issue on privacy considerations, replacing security section. Added NoInterfaceObject extended attribute.