Khronos Public Bugzilla
Bug 565 - gl-object-get-calls fails with last case "getError expected: NO_ERROR. Was INVALID_ENUM"
gl-object-get-calls fails with last case "getError expected: NO_ERROR. Was IN...
Status: NEW
Product: WebGL
Classification: Unclassified
Component: Conformance Tests
1.0
PC Linux
: P3 normal
: ---
Assigned To: 3dweb Working Group email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-12-08 18:28 PST by Jin Yang
Modified: 2011-12-08 18:28 PST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jin Yang 2011-12-08 18:28:06 PST
// Test cases where name == 0
#1 gl.deleteTexture(texture);
#2 shouldBe('gl.getFramebufferAttachmentParameter(gl.FRAMEBUFFER, gl.COLOR_ATTACHMENT0, gl.FRAMEBUFFER_ATTACHMENT_OBJECT_TYPE)', 'gl.NONE');
#3 gl.deleteRenderbuffer(renderbuffer);
#4 shouldBe('gl.getFramebufferAttachmentParameter(gl.FRAMEBUFFER, gl.DEPTH_ATTACHMENT, gl.FRAMEBUFFER_ATTACHMENT_OBJECT_TYPE)', 'gl.NONE');
#5 gl.deleteBuffer(buffer);
#6 shouldBeNull('gl.getVertexAttrib(1, gl.VERTEX_ATTRIB_ARRAY_BUFFER_BINDING)');
#7 glErrorShouldBe(gl, gl.NO_ERROR);

From spec, line 2 and line 4 will cause error "GL_INVALID_ENUM":
GL_INVALID_ENUM is generated if there is no attached object at the named attachment point and pname is not GL_FRAMEBUFFER_ATTACHMENT_OBJECT_TYPE.

So line 7 will fail because the gl error is "GL_INVALID_ENUM"

Tested with linux 32bit on Nvidia & Intel platform with chromium browser, both failed...