conformance/extensions/webgl-draw-buffers.html
Reported by
lukebe...@gmail.com,
Aug 8 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36 Example URL: https://www.khronos.org/registry/webgl/conformance-suites/1.0.3/conformance/extensions/webgl-draw-buffers.html?webglVersion=1 Steps to reproduce the problem: Visit https://www.khronos.org/registry/webgl/conformance-suites/1.0.3/conformance/extensions/webgl-draw-buffers.html?webglVersion=1 What is the expected behavior? All test pass What went wrong? test that gl_FragColor broadcasts FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 test setting first half to NONE and clearing FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 test setting first half to NONE and drawing FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 FAIL at (0, 0) expected: 255,0,0,255 was 0,255,0,255 Does it occur on multiple sites: No Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 54.0.2823.0 (64-bit) Channel: canary OS Version: 16.04 Flash Version: Shockwave Flash 22.0 r0 I bisected this regression down to Revision 405821 is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: b You are probably looking for a change made after 405807 (known good), but no later than 405821 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/7fc01f2b3c636f54eb2a56ed0929fa142a0046ab..7bc4a4651fcd75f35182711ae50a7c8a51c1adfc
,
Aug 8 2016
,
Aug 8 2016
Yes, it is a bug we need to fix in Chrome moving forward. We need to emulate the broadcasting. Let me take this.
,
Aug 17 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4c906855f2edfa5f9f7cdee659ba225a58719d1d commit 4c906855f2edfa5f9f7cdee659ba225a58719d1d Author: jmadill <jmadill@chromium.org> Date: Wed Aug 17 18:48:45 2016 Roll ANGLE 3416ff3..d2f59bb https://chromium.googlesource.com/angle/angle.git/+log/3416ff3..d2f59bb BUG=637037, 635433 TBR=kbr@chromium.org TEST=bots CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2245373005 Cr-Commit-Position: refs/heads/master@{#412599} [modify] https://crrev.com/4c906855f2edfa5f9f7cdee659ba225a58719d1d/DEPS
,
Dec 2 2016
The correct behavior has been implemented. |
||||
►
Sign in to add a comment |
||||
Comment 1 by lukebe...@gmail.com
, Aug 8 2016