Closed Bug 1035473 Opened 10 years ago Closed 5 years ago

WebGL 1.0.3 conformance/textures/texture-attachment-formats.html

Categories

(Core :: Graphics: CanvasWebGL, defect, P3)

x86_64
Windows
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: wlitwinczyk, Assigned: wlitwinczyk)

References

(Blocks 1 open bug)

Details

(Whiteboard: webgl-conformance gfx-noted)

The following WebGL 1.0.3 conformance test fails: http://www.khronos.org/registry/webgl/sdk/tests/conformance/textures/texture-attachment-formats.html ------------------ After some investigating I'm not sure if the test is correct. For the test cases: LUMINANCE, UNSIGNED_BYTE and LUMINANCE_ALPHA, UNSIGNED_BYTE it assumes that the single value from the texture should be propagated to R, G, and B in a ReadPixels() call. I tried to find an explanation of what should happen for this case in the WebGL spec and the OpenGL ES 2.0 spec, but came up empty (if someone knows where it is, that'd be helpful!). For comparison I replicated the test using native OpenGL (using an OpenGL ES 2.0 context) on Linux and got the same results as what FF currently does: (64, 0, 0, 255), only copying to the red channel.
@Walter Litwinczyk Please update the platform to include Windows 7. I tested with the D3D9, D3D11, and native OGL backends on Firefox Nightly38.0a1 (2015-01-30) and it failed on all 3. However it passes on both Chrome 42.0.2291.1 canary and IE 11.
Please also add webgl-conformance whiteboard.
Whiteboard: webgl-conformance gfx-noted
Blocks: 1193526
No longer blocks: 1193526
Ubuntu 16.04 is working with Intel HD 5000. 50.0a1 (2016-06-23)
Summary: webgl-1.0.3 conformance failure texture attachment formats → WebGL 1.0.3 conformance/textures/texture-attachment-formats.html
With Intel HD 4000 on Windows 10 and d3d11 backend, I'm getting 1 failure at: testing: RGB, UNSIGNED_SHORT_5_6_5 FRAMEBUFFER_COMPLETE PASS should be 0,0,0,255 FAIL at (0, 0) expected: 57,125,189,255 was 189,125,58,255
OS: Linux → Windows
Still failing with 52.0a1 (2016-09-20) (32-bit)
Tested this to fail on - Samsung Galaxy S4 GT-I9500 - Android 5.0.1, Kernel 3.4.5-5676501, Fennec 55.0a1 (2017-05-19) - Imagination PowerVR SGX 544MP, OpenGL ES 2.0 build 1.10@2359475 but passes on - Apple MacBook Pro 13" 2016 - macOS Sierra 10.12.3 - Firefox Nightly 55.0a1 (2017-05-21) (64-bit) - Intel Iris Graphics 550 1536 MB 4.1 INTEL-10.22.29 - Apple Mac Mini (Late 2012) - Ubuntu 16.04 Xenial, Kernel 4.4.0-78-generic 64-bit - Firefox 55.0a1 (2017-05-22) (64-bit) - Intel HD Graphics 4000, Intel Mesa DRI Ivybridge Mobile, OpenGL 3.3 (Core Profile) Mesa 12.0.6 - Apple Mac Pro (Late 2013) - OS X El Capitan 10.11.6 - Firefox 55.0a1 (2017-05-22) (64-bit) - AMD FirePro D500 4.1 ATI-1.42.15 - HP Notebook 14-am009no 14" - Windows 10 Home - Firefox 55.0a1 (2017-05-22) (64-bit) - Intel HD Graphics (Intel HD 400?) Direct3D 11, 20.19.15.4509 9-1-2016, OpenGL ES 3.0 (ANGLE 2.1.0.dec065540d5f) - Haswell - Windows 10 Home 64-bit - Firefox 55.0a1 (2017-05-22) (64-bit) - 2x ASUS NVidia GeForce GTX 1080 Ti Direct3D 11, v22.21.13.8189 (4-19-2017), OpenGL ES 3.0 (ANGLE 2.1.0.dec065540d5f) - Intel NUC6i7KYB Skull Canyon - Windows 10 Pro 10.0.14393 64-bit, Firefox 55.0a1 (2017-05-22) (64-bit) - Intel Iris Pro Graphics 580, 21.20.16.4534 (10-7-2016), OpenGL ES 3.0 (ANGLE 2.1.0.dec065540d5f) - Supermicro X10DAX 1.02 - Linux Mint 18 Sarah, Kernel 4.4.0-36-generic 64-bit, Firefox 55.0a1 (2017-05-22) (64-bit) - ASUS GeForce GTX 1060 OpenGL 3.2.0, NVIDIA 370.28 - Microsoft Surface Pro 2 - Windows 10 Pro, Firefox 55.0a1 (2017-05-22) (64-bit) - Intel HD Graphics 4400 Direct3D11 v20.19.15.4331 (11-18-2015), OpenGL ES 3.0 (ANGLE 2.1.0.dec065540d5f) - LG Nexus 5 - Android 6.0.1, Kernel 3.4.0-gcf10b7e (hammerhead M4B30Z), Fennec 55.0a1 (2017-05-19) - Qualcomm Adreno 330, OpenGL ES 3.0 V@127.9 AU@(GIT@I98aee987eb) - Google Pixel XL - Android 7.1.2, Kernel 3.18.31-g416bf43 (marlin N2G47O), Fennec 55.0a1 (2017-05-19) - Qualcomm Adreno 530, OpenGL ES 3.2 V@145.0 (GIT@Idb2b4cb785) - Samsung Galaxy S7 Edge SM-G935F - Android 7.0, Kernel 3.18.14-11104523 (NRD90M), Fennec 55.0a1 (2017-05-19), ARM Mali-T880, OpenGL ES 3.2 v1.r12p1-03dev0.228ab63cced004f840e7dd47b762a1d0 - Huawei P10 Plus - Android 7.0, Kernel 4.1.18-gfd75bbb (VKY-L29), Fennec 55.0a1 (2017-05-19) - ARM Mali-G71, OpenGL ES 3.2 v1.r2p0-02dev0.f7269486f3e0e3b308edf85872e361f4 - LG Nexus 4 - Android 5.1.1 Kernel 3.4.0-perf-gdffc258 (occam LMY48T), Fennec 55.0a1 (2017-05-19) - Qualcomm Adreno 320, OpenGL ES 3.0 V@104.0 AU@ (GIT@Id3510ff6dc) (no WebGL 2, missing standard_derivatives) - Samsung Nexus 10 - Android 5.1.1 Kernel 3.4.67-g84ad5a4 (mantaray LMY49J), Fennec 55.0a1 (2017-05-19) - ARM Mali-T604, OpenGL ES 3.1 (no WebGL2 because of lack of renderbuffer_color_float & renderbuffer_color_half_float) - Apple MacBook Air 13" Mid-2011 - macOS Sierra 10.12.3 - Firefox 55.0a1 (2017-05-22) (64-bit) - Intel HD Graphics 3000 2.1 INTEL-10.2.12 (no WebGL 2, missing transform_feedback extension)

I consider this fixed, and any buggy driver for this test should get its own bug.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.