Closed Bug 927982 Opened 12 years ago Closed 9 years ago

WebGL 1.0.4 conformance test error in conformance/glsl/misc/shaders-with-name-conflicts.html

Categories

(Core :: Graphics: CanvasWebGL, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jujjyl, Unassigned)

References

Details

(Keywords: foxfood, Whiteboard: webgl-conformance)

On my laptop with the specs Windows 7 Home Premium 64-bit Intel(R) Core(TM) i5-2557M CPU @ 1.70GHz (4 CPUs), ~1.7GHz 4096MB RAM Intel(R) HD Graphics 3000 Intel(R) GPU driver version 9.17.10.2932 Intel(R) GPU driver date 12/14/2012 (up-to-date) running https://www.khronos.org/registry/webgl/sdk/tests/conformance/glsl/misc/shaders-with-name-conflicts.html with both Firefox 24 stable and Firefox 27.0a1 Nightly (2013-10-17) gives output: test: shaders with conflicting uniform/attribute names should fail test vertex shader test fragment shader FAIL [unexpected link status] shaders with conflicting uniform/attribute names should fail PASS successfullyParsed is true TEST COMPLETE
Whiteboard: webgl-conformance
Chrome passes all the tests. Firefox 39.0a1 (2015-02-24)nightly fails the test with both the ANGLE and OpenGL backends.
Reproduced the failure on several hardware configurations: - SPARK, GIADA, MACBOOK_AIR_OSX, MACBOOK_AIR_WIN, MACBOOK_PRO_OSX, MACBOOK_PRO_WIN, MACMINI, MACPRO, NEXUS-4, NEXUS-5, NEXUS-10, SURFACE, WINDBOX, HASWELL, HPOMEN See https://bugzilla.mozilla.org/show_bug.cgi?id=1178601 for hardware configuration details of these systems.
Keywords: foxfood
OS: Windows 7 → All
Hardware: x86 → All
Ubuntu 16.04 w/ Intel GPU passes this test. 50.0a1 (2016-06-09)
Windows 10 Intel HD 4000, both d3d9 and d3d11 tests pass that were previously failing.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Summary: WebGL conformance test error in conformance/glsl/misc/shaders-with-name-conflicts.html → WebGL 1.0.4 conformance test error in conformance/glsl/misc/shaders-with-name-conflicts.html
You need to log in before you can comment on or make changes to this bug.