-
Notifications
You must be signed in to change notification settings - Fork 100
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
Please prepare for ANGLE support of Microsoft Edge #38
Comments
We have some vague heuristics that try to guess the presence of ANGLE without an unmasked renderer, that I guess will need to be updated. @pjcozzi Any insights into what the new rules should be? |
No, but all I did last time was just run WebGL Report in different scenarios and see what the most unique difference was - could work again here. |
I found a sample of WEBGL_debug_renderer_info extension survey results - Codeflow
|
ANGLE is used almost everywhere now. For example ANGLE is used on Safari on MacOS Also, the current check under the WebGL2 tab it will say "ANGLE: Yes, D3D9" but WebGL2 support requires D3D11 Given that ANGLE is used almost everywhere I'd suggest you just get rid of parts about ANGLE. |
The following is the display result of WebGL Report on Microsoft Edge of Windows 10 Insider Preview 17093.
I noticed that
ANGLE
is supported in the item ofUnmasked Renderer
. However, the judgment ofANGLE
isNo
.I think that it is good to do
ANGLE
detection with theUnmasked Renderer
.The text was updated successfully, but these errors were encountered: