Enabling the WebGL Context for Chromy
See original GitHub issueI’d like to suggest that the default flags used for Chromy be removed. Instead of providing --disable-gpu,--force-device-scale-factor=1,--window-size=1024,768,
by default
I would like to have a default of something like this --force-device-scale-factor=1,--window-size=1024,768,--disable-infobars,--use-gl=any
. Why not allow or suggest flags to used via the config instead of forcing certain flags by default?
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Enabling WebGL2
Enabling WebGL2 · Go to about:flags · Press Ctrl-F or Cmd-F and search for webgl 2.0 · Find WebGL 2.0 Prototype and click...
Read more >How to Turn on WebGL in Your Browser - Lexia Help Center
Go to chrome://settings in your address bar, or click the Chrome menu in the upper-right corner of your browser window and select Settings....
Read more >How to turn on WebGL in my browser - Human Support
Go to chrome://settings in your address bar, or click the three dots in the upper-right corner of the browser window and select Settings....
Read more >How can I enable WebGL in my browser? - Super User
First, enable hardware acceleration: Go to chrome://settings. Click the Advanced ▼ button at the bottom of the page. In the System section, ...
Read more >Enable WebGL Chrome: 2022, Mac, Android - CCM.net
Scroll to Disable WebGL - Enabling this option prevents web applications from accessing the WebGL API, and click Enable: Click Relaunch Now.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
ok. then how about this. If someone overrides
engineFlags
it will be a true override – not an extension. Except for maybe the--window-size=x,y
case. In that case we can peek the array – if found, we override. If not, we go ahead and append?How do we like that?
@josephmcasey I just implemented this for you. Please update to @latest and validate if you get a chance. Cheers.