WebGL 1.0.3 conformance error: conformance/rendering/framebuffer-texture-switch.html

RESOLVED FIXED

Status

()

RESOLVED FIXED
4 years ago
2 years ago

People

(Reporter: lukebenes, Unassigned)

Tracking

(Blocks: 1 bug)

39 Branch
x86_64
Windows
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: webgl-conformance gfx-noted)

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0
Build ID: 20150224030228

Steps to reproduce:

https://www.khronos.org/registry/webgl/sdk/tests/conformance/rendering/framebuffer-texture-switch.html?webglVersion=1


Actual results:

conformance/rendering/framebuffer-texture-switch.html (6 of 9 passed)

    failed: at (0, 0) expected: 255,255,255,255 was 0,0,0,255




Expected results:

Chrome passes all the tests. Firefox fails the test with ANGLE, but passes with the OpenGL backend.
Component: Untriaged → Canvas: WebGL
Product: Firefox → Core
Whiteboard: webgl-conformance → webgl-conformance gfx-noted
(Reporter)

Updated

3 years ago
No longer blocks: 845345
Summary: WebGL conformance error: conformance/rendering/framebuffer-texture-switch.html → WebGL 1.0.3 conformance error: conformance/rendering/framebuffer-texture-switch.html

Comment 1

3 years ago
This test was reproduced to fail on the following Windows systems:
 - MACBOOK_PRO_WIN, SURFACE, WINDBOX, HASWELL, HPOMEN

The failure did not occur on the following systems:
 - SPARK, GIADA, MACBOOK_AIR_OSX, MACBOOK_AIR_WIN, MACBOOK_PRO_OSX, MACMINI, MACPRO, NEXUS-4, NEXUS-5, NEXUS-10

See https://bugzilla.mozilla.org/show_bug.cgi?id=1178601 for hardware configuration details of these systems. Interestingly, the failure did not occur on MACBOOK_AIR_WIN, even though it is a Windows computer.

Updated

3 years ago
OS: Windows 7 → Windows
(Reporter)

Updated

3 years ago
Blocks: 1193526
Blocks: 1246063
No longer blocks: 1193526
(Reporter)

Comment 2

2 years ago
Passing on Intel HD 4000 on Windows 10 with both d3d9 and d3d11 backend.
50.0a1 (2016-06-25)
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.