Policy flag Disable3DAPIs is not reflected in chrome://gpu
Reported by
james.br...@gmail.com,
Dec 20 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Steps to reproduce the problem: 1. Visit https://get.webgl.org/ to verify that WebGL is functional 2. Visit chrome://gpu and note its contents 3. Set the policy "Disable3DAPIs" through policy file, Group Policy, or at the command line 4. Visit https://get.webgl.org/ to verify that WebGL is disabled 5. Visit chrome://gpu and note that contents have not changed, everything looks fine and there is nothing to suggest that WebGL content won't display. What is the expected behavior? GPU diagnostics page should show an indicator that 3D APIs are disabled by policy. What went wrong? GPU diagnostics page does not reflect that 3D APIs are disabled. Did this work before? No Chrome version: 63.0.3239.84 Channel: stable OS Version: 10.0 Flash Version:
,
Dec 20 2017
,
Dec 20 2017
This should be an easy fix.
,
Aug 27
Ping? It's most of a year later and as far as I can tell this problem persists.
,
Aug 27
I cleaned up the ways we disable WebGL and how we convey such decisions to users. So about:gpu is showing GPU capabilities. Unless WebGL is blacklisted on a specific GPU, otherwise about:gpu will display WebGL as enabled. However, when a webpage tries to create a WebGL context and if the policy of "Disable3DAPIS" is applied, then context creation will fail and return an error message saying something like "WebGL is disabled by group policy".
,
Aug 28
Do you have an approximate version when this improved error message launched (or will launch)? Our corporate systems have an older Chrome and as far as I know the error in the WebGL-backed application I'm using is pretty unhelpful. Hopefully the passed-through error message will improve automatically when we get to the relevant Chrome version. In the interim, is there a different settings page (or chrome:// URL) that I can direct users to check to see if this policy currently impacts them? In a locked-down corporate environment, checking the relevant registry key might not be possible.
,
Aug 28
Try chrome://policy .
,
Aug 28
The exact error message is "disabled by enterprise policy or commandline switch" I think this is firstly available in Chrome M63.
,
Aug 29
Thanks kainino, that's exactly what I was looking for -- I don't know why I hadn't found it before. zmo, there's a good chance the application isn't passing through the error message returned when context creation fails, so I'll investigate that and file an issue with them.
,
Aug 29
Right, the app needs to hook up with that error message and display to users. Browser itself won't display it automatically. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Dec 20 2017