I thought a query had been added so that an app. can determine the implementation's behavior. Perhaps I am confusing this with another extension. With such a query it becomes possible to write a test.
"Out-of-bounds reads may return values from within the buffer object or zero. Out-of-bounds writes may modify values within the buffer object or be discarded."
The "or" statements there are problematic for WebGL, are they not?
They provide a security benefit, but for any other buffer accesses (e.g. those added in a future WebGL 2/ES3.0/ES3.1), it seems that WebGL implementations will still need to do the validation and emulation of zero-read/no-op-write at which point the value of ARB_rbab for performance reasons goes down significantly.I don't understand this point. What other way of accessing the buffer can there be other than read and write?
For a WebGL based on ES 3.1 we will need to consider SSBOs,
images and textures. We should probably push for a new robustness
extension that covers those as well as buffer objects.
NOTE: This electronic mail message may contain confidential and privileged information from HI Corporation. If you are not the intended recipient, any disclosure, photocopying, distribution or use of the contents of the received information is prohibited. If you have received this e-mail in error, please notify the sender immediately and permanently delete this message and all related copies.