Linked by Thom Holwerda on Wed 11th Mar 2009 09:11 UTC, submitted by poundsmack
Apparently, Internet Explorer is on its way out. JCXP.net is saying that Internet Explorer 8 will be the last traditional version of Microsoft's web browser, and that Microsoft's next web browser will be based on a promising Microsoft Research project dubbed "Gazelle".
Thread beginning with comment 352660
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-06
I don't know if I would go that far, but they were both non standard in different ways. In some ways IE was dumb (document.all), other ways ended up getting rolled into the specifications because they were either useful or made more sense (element.innerHTML, element.style.*, XmlHttpRequest), and some things they still do more intelligently then the standard way (the ie box model)
But IE was supporting Netscape custom extensions while Netscape wasn't supporting IE custom stuff. If you think about that, IE deserved its widespread usage. Then Microsoft tried to be the Web itself and failed.
Anyway, what I was stating is the custom browser battle goes far beyond CSS standards support. The battle has moved from supporting your own extensions for HTML/CSS to being able to connect HTML and browser context to my specific platform.
This way I can inject my platform into HTML context, whatever it might be (.NET, Android, those FF extensions and so on...).
Member since:
2006-02-05
I don't know if I would go that far, but they were both non standard in different ways. In some ways IE was dumb (document.all), other ways ended up getting rolled into the specifications because they were either useful or made more sense (element.innerHTML, element.style.*, XmlHttpRequest), and some things they still do more intelligently then the standard way (the ie box model)