Re: [Public WebGL] Bug in context-lost.html conformance test: getContextAttributes should not return null

[Gregg Tavares (社用) <gman@google.com>]

That might be a bug in the test but just fyi, the attributes can change when the context is restored. As an example: Find a win box with 2 GPUs. Disable 2nd GPU, run a WebGL program, enable 2nd GPU, disable first GPU. In an idea WebGL impl the context would be lost on the first gpu and restored on the second. The second will have different capabilities (different limits) and might have different bugs (different features disabled like anti-aliasing)

On Mon, Oct 22, 2012 at 1:05 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

https://www.khronos.org/registry/webgl/sdk/tests/conformance/context/context-lost.html tests that getContextAttributes() returns null if the context has been lost.

But per the spec, getContextAttributes never returns null.  So as far as I can tell, the test is wrong.  And it just started failing in Gecko when I fixed the spec bug we had and stopped returning null in the lost-context case.

It would probably be better to test that even in lost-context cases the attributes returned are the ones the context was created with.

-Boris

-----------------------------------------------------------
You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl
-----------------------------------------------------------