Closed
Bug 832774
Opened 12 years ago
Closed 11 years ago
WebGL Conformance canvas/drawingbuffer-test.html has failures
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 847714
People
(Reporter: pyalot, Assigned: guillaume.abadie)
References
Details
(Whiteboard: webgl-conformance)
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20130104151925
Steps to reproduce:
Run https://www.khronos.org/registry/webgl/sdk/tests/conformance/canvas/drawingbuffer-test.html
Actual results:
testing canvas width = 16416, height = 8
FAIL Unable to fetch WebGL rendering context for Canvas
FAIL context does not exist
Expected results:
testing canvas width = 16416, height = 8
PASS context exists
Reporter | ||
Comment 1•12 years ago
|
||
Test performed on all platforms with the same browsers (Chrome: 24.0.1312.52, Firefox: 18.0)
Ubuntu 12.10, Driver Nvidia 304.64, GPU GTX-460):
- FF: fails (same error)
- Chrome: passes
OSX 10.7.4, Driver ATI 7.18.18, GPU ATI Radeon HD 6750M
- FF: fails (same error)
- Chrome: fails (other error)
Windows 7, Driver AMD 9.2.0.0, GPU AMD Radeon HD 6900
- FF: fails (same error)
- Chrome: passes
Updated•12 years ago
|
Component: Untriaged → Canvas: WebGL
Product: Firefox → Core
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: webgl-conformance
Comment 2•12 years ago
|
||
From https://etherpad.mozilla.org/webgl-1-0-2 :
Linux+Mac+Windows:
canvas/drawingbuffer-test.html (18 of 20 passed)
failed: Unable to fetch WebGL rendering context for Canvas
failed: context does not exist
It looks like we're failing to create contexts with too-large sizes, instead of reducing the drawingbuffer size.
Note that Chrome has been clamping drawingbuffer dimensions to 4096 unconditionally... check if doing the same would be enough to pass the test on at least some hardware.
assign to: jgilbert
Assignee: nobody → jgilbert
Assignee | ||
Comment 4•11 years ago
|
||
Good Morning,
I was planing to fix that before I found this ticket. Have you started already ? Or can I fix it ?
Assignee | ||
Updated•11 years ago
|
Assignee: jgilbert → gabadie
Comment 5•11 years ago
|
||
I believe the proper bug for this is bug 847714.
Assignee | ||
Comment 6•11 years ago
|
||
Ok I mark this bug as duplicate and I will fix 847714 with my working patch.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•