This statement is incorrect. In WebKit's WebGL implementation it will
On Thu, Dec 16, 2010 at 12:54 AM, Gregg Tavares (wrk) <firstname.lastname@example.org
> On Wed, Dec 15, 2010 at 6:53 PM, Adrienne Walker <email@example.com
>> El día 15 de diciembre de 2010 15:59, Gregg Tavares (wrk)
>> > Here's the other problem I have with this extension.
>> > #2) To be able to write lost context conformance tests
>> > #3) To test the browser's handing of lost context.
>> > The problem with but #2 and #3 is that this extension WILL NOT ACHIEVE
>> > EITHER OF THOSE GOALS.
>> Failing to test absolutely everything does not imply a failure to test
>> anything. Again, why are you arguing so strongly against increased
>> test coverage?
> I'm not arguing against increased test coverage. I'm arguing against an
> extension that will not actually provide any actual test coverage.
> The only way you can really test your actual implementation is to wrap all
> calls to OpenGL (not webgl) and then at some number of calls, start ignoring
> the calls and returning lost context from eglSwapBuffers or eglMakeCurrent
> The extension proposed doesn't do this. It will test almost zero paths
> through an actual WebGL implementation.