[Webkit-unassigned] [Bug 47964] New: If WebGL is running on top of a strict version of OpenGL ES it should make sure attribs have buffers assigned at all times

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=47964

           Summary: If WebGL is running on top of a strict version of
                    OpenGL ES it should make sure attribs have buffers
                    assigned at all times
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebGL
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: gman at google.com
                CC: zmo at google.com


Chromium has a strict version of OpenGL ES 2.0 that does all the attrib array bounds checking needed by WebGL so it would be nice if WebGL in webkit didn't redundantly do bounds checking.

Unfortunately, when removing the current bounds checking the issue comes up that WebGL can call drawArrays or drawElements when attributes are enabled but no buffer has been assigned. This crashes OpenGL (both the Chromium version and real OpenGL)

The suggested solution is to create a dummy buffer, assign it to every attribute at initialization time,

If the user deletes a buffer or calls vertexAttribPointer with NULL then instead of putting NULL in the buffer, assign the dummy buffer to the attrib in question

This avoids having to check that buffers are assigned at draw time. It add the complication that when querying the state of an attrib you have to shadow its state since if the dummy buffer is assigned you should be telling the user that no buffer is assigned.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.