Chrome dev on WebGL security and Microsoft bullshit

Re:Chrome dev on WebGL security and Microsoft bullshit by magicalist on Tuesday June 21, 2011 @05:29PM (#2680503)

> The greatest concern seems to be with the way OGL handles various buffers. For example in WebGL it is possible to create bufferData stating that it's of size X and provide Y values with Y much smaller than X. What you get is a buffer full of stale data from the memory. Bad idea.

Please at least check these things before asserting them. Assuming good will, I can see how it might be easy to assume that some things that are true in desktop opengl will be true in webgl, but both the linked blog post and the webgl spec explicitly state that all buffers are initialized upon creation, and all access calls are bounds checked. Tests of this are also part of the webgl conformance suite.

If you want to see where it is specified, see here: http://www.khronos.org/registry/webgl/specs/latest/#4.1

[ Parent | on HN ]

Re:Chrome dev on WebGL security and Microsoft bullshit by hubriz on Wednesday June 22, 2011 @05:13AM (#2682368)

That is only partially correct. As mentioned before, there are two types of WebGL canvas contexts out there: webgl and experimental-webgl. Former does not put the GLX_ARB_create_context_robustness extension in place, which is basically what you're referring to.

[ Parent | on HN ]