New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 635802 link

Starred by 1 user
Status: Assigned
Owner:
zmo@chromium.org
Cc:
█ kbr@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

WebGL2 in chrome OSX failure with uniform block arrays

Project Member Reported by gman@chromium.org, Aug 9 2016 
Version: 54.0.2824.0 (Official Build) canary (64-bit)
OS: OSX 10.11.6

What steps will reproduce the problem?
(1) Run the attached program (or go to https://jsfiddle.net/greggman/xy8ygu7o/)

What is the expected output?

The program links

What do you see instead?

ERROR: Interface blocks with the same name but different fields/layout: Lights


But AFAICT they are the same but I'm still an ES3 noob so maybe I'm doing something wrong.

Note: This example used to work and it still works in Firefox as of version 48
glsl-3.0-mis-matching-layout.html
1.3 KB View Download

Comment 1 by zmo@chromium.org, Aug 9 2016 

The default precision in vertex shader is highp, and you declare the precision in fragment shader as mediump, thus the mismatch.

Comment 2 by zmo@chromium.org, Aug 9 2016

Status: WontFix (was: Untriaged)
Desktop might allow this, but I just checked GLSL ES 3 spec, it is required for uniform precision to match. So Chrome behavior is correct, Firefox is not conformant yet.

Comment 3 by gman@chromium.org, Aug 14 2016 

Can you at least fix the error message so it says "mis-matching precision" instead of "different fields/layout"? That's extremely mis-leading

Comment 4 by gman@chromium.org, Aug 14 2016 

or maybe just `different fields/layouts/precision" would be enough

Comment 5 by zmo@chromium.org, Aug 15 2016

Cc: -zmo@chromium.org
Owner: zmo@chromium.org
Status: Assigned (was: WontFix)
Sure. I'll fix the error message.

Comment 6 by lafo...@chromium.org, Jun 20 2017

Components: -Internals>GPU>WebGL Blink>WebGL
►

Sign in to add a comment