3 ms·
Is it just me, or are that others that think "Didn't it support that yet?!" at every IE release? I don't use Windows so I never use IE anymore, but I'd think IE
by lucb1e 13y ago
Is it just me, or are that others that think "Didn't it support that yet?!" at every IE release? I don't use Windows so I never use IE anymore, but I'd think IE9 or 10 would support WebGL by now...
- bskap 13y agoIE 9 was released only 11 days after WebGL was standardized.
- coldtea 13y agoSo? It didn't prevent other browsers for having a mostly working implementation that they could improve upon with time.
- bskap 13y agoAnd they supported those mostly working implementations for about 6 weeks. Microsoft supports their releases for years.
- drivebyacct2 13y agoIs that even true now that IE11 keeps itself auto-updated to the latest major version?
- chc 13y agoWebGL was bleeding-edge when IE 9 was released, and there were still very valid concerns about its security for a while after that. Opera implemented it, but disabled it due to these concerns. After their nightmarish history with security, Microsoft are very focused on hardening Windows — so I wouldn't exactly call it regressive to leave WebGL out of IE 10, which was probably feature-frozen in early 2012.
- gsnedders 13y agoOpera didn't disable it due to security concerns per se — rather more just the general bugginess of Opera's hardware acceleration. I wouldn't consider crash bugs in general security issues. Equally, there is software rendered mode, but it's pointlessly slow to enable. Note the prior concerns are still just as true today as they were a few years ago — graphics drivers are still relatively easy to find crash bugs in, leading browser vendors to try and hack around and avoid hitting those bugs in all too many cases. :(
- bmm6o 13y ago> I wouldn't consider crash bugs in general security issues You should, until proven otherwise. If it crashes because it's reading an invalid memory location (for instance), it's a matter of time before someone figures out how to place executable code there. I have no problem with MS's original position. WebGL forces your hardware drivers to run random code downloaded from the internet. I'm frankly surprised that the other browser vendors ran ahead with it so quickly and that we haven't heard about any exploits caused by it.
- yuhong 13y agoOn that matter, it is not difficult for someone who knows how to use WinDbg or similar to see if a crash is exploitable. For example, in user mode, null pointer accesses are generally not exploitable. I personally was able to get an IE6/IE7 bug described in http://www.satzansatz.de/cssd/pseudocss.html#fltadjacent http://www.satzansatz.de/cssd/pseudocss.html#fltadjacent fixed in the May 2013 security update by proving there is an exploitable crash.
- judah 13y agoAdditionally, Microsoft was on record saying they believed plugins like Silverlight provided sufficient 3d capabilities, and that WebGL was huge surface area for security vulnerabilities. They've apparently reversed that stance.
- mey 13y agoSince Windows 8, MS has reversed it's stance on Silverlight and browser plugins in general. I don't disagree with Microsoft's point in this article. http://blogs.technet.com/b/srd/archive/2011/06/16/webgl-considered-harmful.aspx http://blogs.technet.com/b/srd/archive/2011/06/16/webgl-cons... I assume that they've decided to work towards solving the security issues instead of simply staying away from the issue. Long term I hope this means more stable and reliable video drivers :)