3 ms·
The problem has been that IE contained alot of proprietary extensions, which were never a part of the standard. Since IE had most of the marketshare, people use
by Skinney 13y ago
The problem has been that IE contained alot of proprietary extensions, which were never a part of the standard. Since IE had most of the marketshare, people used IE, and thus things break when other browsers don't support the same extensions.
Sites following standards should still work. While we have different parsers, they should all be supported today.
NaCl is not a standard, and only works in Chrome, which I can't see changing. ActiveX is a proprietary IE extension, and will never work outside IE. Same with VB script, same with Dart etc.
I had to port an application to IE7 last week, and it works fine in all browsers that has come out since. And this is a EmberJS app using ajax heavily. The web is a great place, as long as you stick to the standards and nothing but the standards. Luckily, the standards are evolving, meaning you can do more and more within the standards, without tying yourself to browser-specific extensions which was the problem in the early IE days.