[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] WebGL conformance test

The original bug for which the multisample-corruption.html test was
written was considered a security bug at the time because it allowed
uninitialized video memory to be read back by WebGL applications. At
this point the bug has been worked around and is publicly visible, so
a link to the original bug report has been added to the test. Thanks
for the feedback.


On Mon, Jun 30, 2014 at 10:04 AM, Brandon Jones <bajones@google.com> wrote:
> The conformance tests check to ensure that the browser is conforming to the
> WebGL specs by running a bunch of WEbGL commands and checking the results. A
> lot of times the basic pattern is:
> DoSomethingWrong();
> CheckToMakeSureTheRightErrorWasGenerated();
> DoSomethingWrite();
> CheckToMakeSureThereWasNoError();
> CheckToMakeSureTheOutputWasRight();
> The conformance tests also check known issues in various drivers to make
> sure they don't affect the output of WebGL content. The
> MultisampleCorruption test, for example, creates many large multisampled
> surfaces and ensures you can render to them correctly because we've observed
> problems on some GPUs where doing that resulted in garbage rendering. The
> WebGL implementation needs to be aware of that issue and work around it.
> On 1404139280393, Amit Kumar <che.amit@gmail.com> wrote:
>> Hi,
>> I am new to webgl and this mailing list. I have a query. Can someone
>> explain me what conformance/rendering/multisample-corruption.html test is
>> doing, I couldn't find 'what does multisample-corruption means?
>> --
>> Regards,
>> Amit Kumar
>> Noida
>> 91 9971115174

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