Fix gl.isBuffer for buffers that are marked for deletion but still attached

This commit is contained in:
Anthony Ramine 2018-08-25 19:17:24 +02:00
parent 7b673de4d6
commit 4cf944eab8
2 changed files with 1 additions and 26 deletions

View file

@ -2759,7 +2759,7 @@ impl WebGLRenderingContextMethods for WebGLRenderingContext {
// https://www.khronos.org/registry/webgl/specs/latest/1.0/#5.14.5
fn IsBuffer(&self, buffer: Option<&WebGLBuffer>) -> bool {
buffer.map_or(false, |buf| {
self.validate_ownership(buf).is_ok() && buf.target().is_some() && !buf.is_marked_for_deletion()
self.validate_ownership(buf).is_ok() && buf.target().is_some() && !buf.is_deleted()
})
}

View file

@ -1,25 +0,0 @@
[oes-vertex-array-object.html]
[WebGL test #74: References from unbound VAOs keep Color buffer alive]
expected: FAIL
[WebGL test #65: References from unbound VAOs keep Color buffer alive]
expected: FAIL
[WebGL test #68: References from unbound VAOs keep Color buffer alive]
expected: FAIL
[WebGL test #73: References from unbound VAOs keep Position buffer alive.]
expected: FAIL
[WebGL test #71: References from unbound VAOs keep Color buffer alive]
expected: FAIL
[WebGL test #70: References from unbound VAOs keep Position buffer alive.]
expected: FAIL
[WebGL test #64: References from unbound VAOs keep Position buffer alive.]
expected: FAIL
[WebGL test #67: References from unbound VAOs keep Position buffer alive.]
expected: FAIL