-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Major regression in Firefox 35 #2431
Comments
Looks like this is a manifestation of this issue which I found via this issue. Setting WebGL context alpha to false affects all framebuffers, which causes anything with alpha to go haywire in Cesium. If I force alpha to true in Context.js, everything works (though I'm not sure of the full ramifications of this change). |
Chime in on those issues and let them know it affects Cesium. We could workaround this by setting Is this in any version of Chrome? If not, we could just set |
That's what I would do, check for Firefox 35 and force it to true. We have a similar workaround already in place for Firefox 34, because that broke Cesium as well. |
OK with me. |
In Firefox 35 we need to force the context alpha to true because setting it to false affects all framebuffers. Fixes #2431 Also removed ancient workaround for a Chrome issue that was fixed in Feb 2014 as well as an unused glsl #ifdef that was left over from an older version of Firefox.
In Firefox 35 we need to force the context alpha to true because setting it to false affects all framebuffers. Fixes #2431 Also removed ancient workaround for a Chrome issue that was fixed in Feb 2014 as well as an unused glsl #ifdef that was left over from an older version of Firefox.
There appears to be a major ANGLE related regression in Firefox 35 (obviously Windows only). This causes all existing versions of Cesium to render a lot of materials incorrectly.
This was on the DX 9 back end, not sure about DX 11. Disabling Angle fixes the problem. I'll look into filing a Firefox bug, but someone should confirm that this isn't some weird bug on our end that Firefox is exposing.
The text was updated successfully, but these errors were encountered: