Closed
Bug 1258211
Opened 9 years ago
Closed 9 years ago
WebGLRenderingContext.checkFramebufferStatus returns 0 instead of INVALID_ENUM when target isn't a frame buffer
Categories
(Developer Documentation Graveyard :: API: Miscellaneous, defect)
Developer Documentation Graveyard
API: Miscellaneous
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Craig.Gidney, Unassigned)
Details
(Whiteboard: gfx-noted)
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20160210153822
Steps to reproduce:
According to the MDN docs at https://developer.mozilla.org/en-US/docs/Web/API/WebGLRenderingContext/checkFramebufferStatus , WebGLRenderingContext.checkFramebufferStatus is supposed to return INVALID_ENUM if the target argument is not gl.FRAMEBUFFER. Actually it returns 0, so either the docs needs to be updated or firefox is doing the wrong thing.
Run this snippet:
var gl = document.createElement('canvas').getContext('webgl');
var code = gl.checkFramebufferStatus(-1);
console.log({actual_code: code, INVALID_ENUM_CODE: gl.INVALID_ENUM});
Actual results:
Object { actual_code: 0, INVALID_ENUM_CODE: 1280 }
Expected results:
Object { actual_code: 1280 , INVALID_ENUM_CODE: 1280 }
Updated•9 years ago
|
Flags: needinfo?(jgilbert)
Whiteboard: gfx-noted
Comment 1•9 years ago
|
||
This is a docs issue.
Status: UNCONFIRMED → NEW
Component: Canvas: WebGL → API: Miscellaneous
Ever confirmed: true
Flags: needinfo?(jgilbert)
Product: Core → Developer Documentation
Version: 44 Branch → unspecified
Comment 2•9 years ago
|
||
Thanks, updated!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•