Closed
Bug 1135949
Opened 11 years ago
Closed 10 years ago
gl.readPixels not returning correct RGBA data in FF35
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: yowhann, Unassigned)
References
()
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36
Steps to reproduce:
As an example, here's an example code snippet I found that illustrates the issue. http://codepen.io/anon/pen/XJMQwV
readPixels just reads the image data from the webGL canvas on the left and draws it on the right. In firefox 35 for windows readPixels returns [0, 0, 0, 0] for the RGBA data of all pixels read so nothing is drawn on the right.
Actual results:
readPixels just reads the image data from the webGL canvas on the left and draws it on the right. In firefox 35 for windows readPixels returns [0, 0, 0, 0] for the RGBA data of all pixels read so nothing is drawn on the right. It functions as expected in all other browsers. Firefox 34 and below behaves correctly, this appears to be a regression issue.
Expected results:
Expected Behavior is that readPixels returns the RGBA data of each pixel read.
| Reporter | ||
Updated•11 years ago
|
| Reporter | ||
Updated•11 years ago
|
Summary: readPixel not returning correct RGBA data in FF35 → gl.readPixels not returning correct RGBA data in FF35
Moving to Core/WebGL component
Component: Untriaged → Canvas: WebGL
Product: Firefox → Core
This seems to work OK for me on Windows; could be an OSX only issue.
Keywords: regression
| Reporter | ||
Comment 3•11 years ago
|
||
Hi Vladimir, this is only reproduces in Firefox 35 on Windows 7 x86.
When updating on the same machine to Firefox 36, this issue does not reproduce.
OS: Mac OS X → Windows 7
Comment 4•10 years ago
|
||
This was fixed in 36, which is now Release.
Severity: blocker → normal
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Priority: P2 → --
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•