Merge pull request #140 from pyalot/master

Conformance glsl test for large loop compile
Restructured pyalot's large-loop-compile test to check (a) that the context isn't lost during shader compilation or program linking, and that (b) compilation and linking don't take an unreasonably long time. Whether the compilation and link succeeded is no longer tested.
Merge pull request #141 from kenrussell/largeloop

Restructured pyalot's large-loop-compile test to check (a) that the cont...
remove redundant functions
remove document.getElementById where it's not needed
Fix width="XXpx" height="YYpx" to width="XX" height="XX"
Merge pull request #142 from greggman/remove-redundant-funcs

Remove redundant funcs
Revert back to pyalot's original loop as it looks like the more complex form is still being unrolled.
Merge pull request #143 from kenrussell/largeloop

Revert back to pyalot's original loop as it looks like the more complex ...
Remove/Refactor the calls to initNonKhronosFramework

In many samples the code would do this

    if (window.initNonKhronosFramework) {
      window.initNonKhronosFramework(true);
    }

Problems with that approach

1.  When is it needed?

    Apparently it's needed for any test run in as a WebKit layout test.
    That doesn't seem like it should be bleeding into every test.

    Solution: Move it to `WebGLTestUtils.create3DContext` and from
    `description`.

    It's now called for almost all tests automatically. A flag
    makes sure it will only be called once.

2.  What does the 'true' mean? Other places call it with 'false'.

    It turns out 'true' appearently tells WebKit's testing harness not
    to timeout the test.

    Solution: Change the 'true' calls to ` initTestingHarnessWaitUntilDone`
Merge pull request #144 from greggman/remove-nonkhronos-checks

Remove/Refactor the calls to initNonKhronosFramework
removed the outdated extension proposal WEBGL_fbo_color_attachments