-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Brave 1.16.68 on Mac is reporting that WebGL GLSL highp precision isn't supported #12366
Comments
I have confirmed that this issue also affects Brave 1.16.68 on Windows 10 Version 10.0.18362.720 |
Verification PASSED on
Visited https://webglreport.com and ensured that Verification PASSED on
Visited https://webglreport.com and ensured that Verification passed on
Visited https://webglreport.com and ensured that |
Still not working ... |
Description
As of 1.16.68 Brave on a desktop Mac reports that high precision WebGL shader variables aren't supported. This has not been the case before this update. Chrome Version 86.0.4240.111 (Official Build) (x86_64) works without issue, along with Safari and Firefox. All report support for
highp
WebGL shader variables.Steps to Reproduce
The following Javascript will return false, where previously the correct result was returned.
The call to
getShaderPrecisionFormat
returns:A visit to https://webglreport.com/ in Brave reports under Fragment Shader that float/int precision =
mediump/lowp
whereas the latest Chrome correctly reportshighp/highp
. Interestingly, it looks like for a WebGL2 context Brave behaves correctly.I'm a complete novice when it comes to the Brave codebase but a recent commit by @pilgrim-brave may possibly be related? Apologies if this is totally unrelated.
Actual result:
Brave reports that high precision WebGL shader variables aren't supported.
Expected result:
Previously Brave has reported support correctly.
Reproduces how often:
Easily reproduced.
Brave version (brave://version info)
Version 1.16.68 Chromium: 86.0.4240.111 (Official Build) (x86_64)
The text was updated successfully, but these errors were encountered: