LUMINANCE and ALPHA textures should not be renderable

Check that attaching these texture types results in an incomplete
framebuffer instead of trying to render to that framebuffer. This helps
to ensure that unspecified rendering to these texture types is not
supported in any implementation, maintaining compatibility.

For reference, see OpenGL ES 2.0 spec section 4.4.5 Framebuffer
Completeness, specifically table 4.5. "Renderbuffer image formats", which
enumerates all renderable formats. Rendering to other formats is not
specified.
Revert change to the frozen 1.0.2. suite

Changing future versions of the conformance suite is enough, the 1.0.2
test should also pass in case the new more stringent version passes.
Merge pull request #304 from NVIDIA/fix-luminance-alpha

LUMINANCE and ALPHA textures should not be renderable
Based on feedback from Guillaume Abadie on public_webgl, removed invalid call of "isVertexArrayOES()" from oes-vertex-array-object test, as far back as version 1.0.1 of the conformance suite.
Merge pull request #306 from kenrussell/vao-test

Based on feedback from Guillaume Abadie on public_webgl, removed invalid...
Fix checkCanvas utility function JSDoc to correspond to what it does
Merge pull request #307 from NVIDIA/fix-utils-check

Fix checkCanvas utility function JSDoc to correspond to what it does
adding fake black texture tests for desktop computer
Account for literal constants taking up uniform storage

According to GLSL ES spec 10.0.17 Appendix A section 7:

"When calculating the number of uniform variables used, any literal
constants present in the shader source after preprocessing are included
when calculating the storage requirements. Multiple instances of
identical constants should count multiple times."
Better explanation of literal constants taking up space
Based on feedback from Brian Cornell on public_webgl, clarified that length of ArrayBufferView is actually byteLength in all compressed texture extensions.
Merge pull request #311 from kenrussell/compressedtex

Based on feedback from Brian Cornell on public_webgl, clarified that len...
Don't use premultiplied alpha in most GLSL generator tests

Many GLSL function conformance tests can generate superluminal color
values, where red, green or blue > alpha. Since browsers don't do
clamping for these color values before they are unpremultiplied and
encoded as PNG when toDataURL is called, the on-screen display of these
tests did not reflect the actual numeric values generated by the shader.
This complicated debugging failed tests. Fix this by switching to a
context with a non-premultiplied drawing buffer in these tests.

This issue does not affect the programmatic comparison of test results,
since that is being done using readPixels.
Revert change to the frozen 1.0.1 suite

It makes sense to fix displaying superluminal values in 1.0.2, since lots
of implementations are still working on conformance, but with 1.0.1 it's
better to avoid this kind of changes.
Merge pull request #312 from NVIDIA/fix-superluminal-display

Don't use premultiplied alpha in most GLSL generator tests
Merge pull request #310 from NVIDIA/fix-uniform-limits

Account for literal constants taking up uniform storage
Use absolute, not relative canvas position when logging errors

checkCanvasRectColor used to log position relative to the corner of the
rectangle being checked. Logging absolute canvas position makes more
sense when analyzing errors, so switch to that in the new and 1.0.2
versions of the conformance suite.
fix some request from Ken Russell about the new test added.
change the bugzilla link directly showing the bug bug fix on Firefox.
Commit partial updates so I can merge upstream changes.