Closed
Bug 1170885
Opened 10 years ago
Closed 9 years ago
WebGL 2 - Drawing fails in tex-mipmap-levels test (npot?)
Categories
(Core :: Graphics: CanvasWebGL, defect)
Core
Graphics: CanvasWebGL
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: u480271, Unassigned)
References
()
Details
(Whiteboard: [gfx-noted])
WebGL2 Non-Power of 2 texture conformance test.
On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
PASS getError was expected value: NO_ERROR : Should be no errors from setup.
test mipmap level ranges
PASS getError was expected value: NO_ERROR : fillTexture(8,8,2) should succeed
PASS getError was expected value: NO_ERROR : fillTexture(4,4,3) should succeed
PASS getError was expected value: NO_ERROR : fillTexture(2,2,4) should succeed
PASS getError was expected value: NO_ERROR : texParameter(TEXTURE_BASE_LEVEL) should succeed
PASS getError was expected value: NO_ERROR : texParameter(TEXTURE_MAX_LEVEL) should succeed
PASS getError was expected value: NO_ERROR : texParameter(TEXTURE_MAG_FILTER) should succeed
PASS getError was expected value: NO_ERROR : texParameter(TEXTURE_MIN_FILTER) should succeed
PASS getError was expected value: NO_ERROR : clearAndDrawQuad should succeed
FAIL at (0, 0) expected: 0,0,255,255 was 0,0,0,255
PASS getError was expected value: NO_ERROR : generateMipmap should succeed
FAIL at (0, 0) expected: 255,0,0,255 was 0,0,0,255
PASS getError was expected value: NO_ERROR : fillTexture(8,8,2) should succeed
PASS getError was expected value: NO_ERROR : fillTexture(4,4,3) should succeed
PASS getError was expected value: NO_ERROR : texParameter(TEXTURE_BASE_LEVEL) should succeed
PASS getError was expected value: NO_ERROR : texParameter(TEXTURE_MAX_LEVEL) should succeed
PASS getError was expected value: NO_ERROR : clearAndDrawQuad should succeed
PASS incomplete; should draw with [0, 0, 0, 255]
PASS successfullyParsed is true
TEST COMPLETE
Comment 1•9 years ago
|
||
These seem to work now.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•