The WebGL extension registry contains specifications for extensions to the core WebGL API. Most of these extensions are incorporated directly from the OpenGL ES or OpenGL extension registries, and refer to those extensions for their behavioral definition. Because WebGL extensions are specified as Web IDL interfaces, each specification also includes the IDL to which each implementation will comply.
An extension template is available for the submission of
new proposed extensions. New extension proposals should be emailed to the
public WebGL mailing list.
When writing a new extension specification, it is recommended to check out
the public WebGL repository. See the
WebGL wiki page Using
Github to contribute. The extension registry files are located
under extensions/.
Each extension object is fetched from
the WebGLRenderingContext by passing
the name of the extension to the getExtension method,
i.e.: context.getExtension("OES_texture_float").
WebGL API extensions may derive from many sources, and the naming of each extension reflects its origin and intent.
ARB, OES and KHR tags should be used for
mirroring functionality from OpenGL ES or OpenGL API extensions approved by the respective
architecture review boards. EXT_ and GPU vendor tags should be used for
mirroring other OpenGL ES or OpenGL API extensions. If only small differences in behavior
compared to OpenGL ES or OpenGL are specified for a given extension, the original tag should
be maintained.
WEBGL tag should be used for WebGL-specific extensions which are
intended to be compatible with multiple web browsers. It should also be used for extensions
which originated with the OpenGL ES or OpenGL APIs, but whose behavior has been
significantly altered.
WEBGL tag.
Extensions move through four states during their development: proposed, draft, community approved, and Khronos ratified.
By Number | By Name |
By Number | By Name |
By Number | By Name |
By Name |
Recent Revisions