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

[Public WebGL] texture/renderbuffer deletion behavior when they are bound to non-bound framebuffer

According to GLES2 spec, if a texture/renderbuffer object is bound to
the currently-bound framebuffer and it's deleted, it is first
detached.  However, if the framebuffer is not currently bound, then it
"is specifically NOT detached ... Detaching ... is the responsibility
of the application."

This sounds to me like a security issue where crash could happen.  I
suggest to make it stronger for WebGL spec that no matter the
framebuffer is bound or not, when one of its attachment is deleted, we
always detach first.

Please advise.
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: