[Public WebGL] WebGL2 and no mapBuffer/mapBufferRange

Zhenyao Mo [email protected]
Mon Mar 16 10:03:46 PDT 2015

If it comes to a vote, I will vote "no" for introducing something to
the core APIs that intrinsically cannot be implemented on
non-in-process WebGL implementations.

On Sun, Mar 15, 2015 at 5:11 AM, Florian Bösch <[email protected]> wrote:
> Having discussed this feature now thoroughly I will propose a resolution:
> mabBuffer[Range] and all its flags can be safely exposed
> It should be done to keep ES3 <-> WebGL 2 friction as low as possible and to
> avoid standards bifurcation
> It will require a bit more engineering (copying threads, read/write only
> array buffers) than is customary for GL features
> The performance might be better than buffer[Sub]Data, but it'll not be
> worse.
> All corner cases where the specification leaves the behavior undefined can
> be upgraded to GL errors
> Can everybody involved agree to this resolution and can we hence put that
> feature back into the WebGL 2 specification where it belongs if you want to
> achieve ES 3 implementation certification?

You are currently subscribed to [email protected]
To unsubscribe, send an email to [email protected] with
the following command in the body of your email:
unsubscribe public_webgl

More information about the public_webgl mailing list