Do you really want thousands of toggles in your browser settings, so you can choose what web standards are rendered?Ĭhrome is like the old IE in that it is the dominant browser. 'The ability to turn WebGL on/off is not included in the standard Settings interface of of Google Chrome' because Chrome just renders WebGL content. In September 2021, Safari returned to fully supporting WebGL. In mid-2020, Safari started supporting WebGL again as an experimental feature. At that time, Chrome and Firefox released versions that supported the new WebGL standard. Safari, Chrome, and Firefox supported WebGL until WebGL 2.0 was released in January 2017. Apple is a member of the group that develops it, and has been from the beginning. Browsers render code built to agreed standards.įor WebGL has been a standard since 2011. Web browsers are not like word processors, with proprietary formats. Browser devs code to standards, not websites. Web developers code to standards, not to browsers. You're never going to get the Linux fans (of which there are many in the Web developer community) or those in corporate environments standardized on Windows to develop on Safari when Apple doesn't allow them to run Safari. Services like BrowserStack are great for showing where there's a problem, but not terribly effective for diagnosing and fixing the problem. Before bringing Edge to Linux and MacOS, at least Microsoft offered free virtual machine packages for Web development. You can't even legally virtualize MacOS except on Apple hardware.

They'd need to allow people who don't own Apple products to use the browser.Īs I said before, as long as using Safari is tied to owning specific hardware, it's never going to be the targeted browser.

Arguably, that is currently Chrome though historically it has been Firefox (and still is in some people's opinions).įor Apple, providing a better environment for development wouldn't be just about the tools built-in to the browser (though those could seriously use an upgrade. We try to design for all browsers, but the one that gives us the best developer tools is naturally the first browser we test in.

No one I know would code specifically for Chrome, just as we didn't code specifically for Firefox 15 years ago. But arguing the specifics ignores the flawed premise. Click to expand.To begin with, I'd say this rather ignores that there are enough inconsistencies between the WebKit, Blink and Gecko engines that indeed, if you design specifically for Safari, there is a good chance elements will be broken in Chrome and Firefox.

How to enable webgl in chrome on mac