Feature request: Target by WEBGL compatibility
See original GitHub issueAwesome project, I’m using it within babel-preset-env
Is it conceivable to add a WEBGL query? For those who builds games, etc…
PS: Related to @AndyBarron request https://github.com/ai/browserslist/issues/91#issuecomment-267815631
Unrelated:
- Don’t you should add
yarn.lock
in.gitignore
and remove it from SCM? - About files field over
.npmignore
http://stackoverflow.com/a/37421736/1480391
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
WebGL browser compatibility - Unity - Manual
Unity Web Request ... Targeting shader models and GPU features in HLSL ... WebGL · Introducing WebGL · WebGL browser compatibility · WebGL...
Read more >[Feature Request] WebGL Support · Issue #69 · mellinoe/veldrid
As Mono supports WebAssembly now, and Veldrid supports OpenGL ES now, it seems to me that WebGL should be doable (right?)
Read more >WebGL best practices - Web APIs - MDN Web Docs - Mozilla
WebGL is a complicated API, and it's often not obvious what the recommended ways to use it are. This page tackles recommendations across...
Read more >Feature Request - Deploying AR to WebGL - Unity Forum
Hi I am being tasked with building an AR portal application that will work on both iPads and the web via a url....
Read more >WebGL 2.0 Achieves Pervasive Support from all Major Web ...
Now, with support for WebGL 2.0 in Safari 15 for both macOS and iOS, we're happy to report that “compatible browsers” includes pretty...
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
@yvele it could be awesome, but it will dramatically increase Browserslist size and kill any client-side usage.
@ai I understand… I could just use caniuse-api to build a browserslist query…
But it’s quite confusing, both browserslist (
>1%
, etc…) and caniuse-api allows to make a “query”… I can’t really understand what are the separation of concerns here. You seem to say that feature/engine is the separation… Why? It doesn’t look user friendly…Whouldn’t a single browser query API (that outputs a list of browsers) be awesome?