HTML and CSS Reference
Table 9-1. Functions That Modify State
WebGL also allows the state of itself or its objects to be queried. These calls should be avoided, as they can be
very costly, and, at their worst, they can cause the pipeline to stall completely.
The only real exception to this rule, with regard to global state, is during the startup process, as the application can use
this time to determine what features are available with the implementation, such as the number of texture units present.
With shader programs it's perfectly valid to query the uniform information after creation; however, this should
only happen once, as the value returned will be unchanged. The information for setting the value later can easily be
stored by the application for future use.
During development it's highly recommended that you check for any errors, using getError after every call.
Yet, this should not go into production. The Khronos Group, the consortium that oversees the WebGL specification,
Dart through noSuchMethod invocations.
Any calls enumerated in Table 9-2 will query the state of WebGL.
Table 9-2. Functions That Query State