@kbr, we wrote the radar description at https://docs.google.com/document/d/1xKMCfZLaoMu_WfTsS50psSYfGR070o6p4I-fpPR-qaA/edit. Could you please review and file it?

Thanks Yang. Reviewed and updated it. The final Radar text I submitted was also a bit different / more condensed. In the future please provide one way to reproduce the bug rather than two, and if there's already a WebGL conformance test for it, it's not necessary to produce a separate test (or feel free to submit pull requests clarifying the conformance test). Filed Radar 34539495.

Also it would have been helpful to know whether it works on the 10.13 betas.

Hi @kbr, I have verified this bug can also be reproduced on MacOS Version 10.13 Beta (17A362a)

Thanks Jiawei. Updated the Radar with that information. (Now that 10.13 is publicly released as of today, it would also be helpful if you could confirm with that version.)

Hi, I have confirmed this issue is still available with macOS 10.13.

Thanks Jiawei.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

We'll need to fix this in order to reach 100% WebGL 2.0 conformance on macOS again.