In Addition To Project Spartan, Windows 10 Will Include Internet Explorer
An anonymous reader writes After unveiling its new Project Spartan browser for Windows 10, Microsoft is now offering more details. The company confirmed that Windows 10 will also include Internet Explorer for enterprise sites, though it didn't say how exactly this will work. Spartan comes with a new rendering engine, which doesn't rely on the versioned document modes the company has historically used. It also provides compatibility with the millions of existing enterprise websites specifically designed for Internet Explorer by loading the IE11 engine when needed. In this way, the browser uses the new rendering engine for modern websites and the old one for legacy purposes.
Firefox still is the add-on king.
Chrome addons still don't allow certain modifications of the user interface. Tree Style Tabs is fabulous, especially now we're all using widescreen resolutions:
https://addons.mozilla.org/en-US/firefox/addon/tree-style-tab/
Chrome still can't match this. They try, but it's clearly trying to work around the limitations Google has put into their product:
https://chrome.google.com/webstore/detail/sidewise-tree-style-tabs/biiammgklaefagjclmnlialkmaemifgo
I hate to break it to you but despite a few failures its still a better browser than Chrome, IE, and Opera. The part that was bad was Firefox copied Chrome and Microsoft in various ways in regards to the UI. However you can't solve that by switching to other browsers that are just as bad or worse. Firefox still has several privacy and security advantages over the other browsers and whatever crashing / memory leaks were eventually solved. Plus there were measures put in place to make crashing less irritating. You might argue IE has some security features Firefox is/was missing, but once you factor in the lack of source code and an open development model its a mute point. Particularly when these features have or will be added at some point- or are really OS specific anyway and its up to the OS developers to implement those features.
Kinda. It wasn't impossible to write cross platform browser stuff in the late 1990s, when most corporations started this whole "We'll standardize on browser X" policy making, but it required a discipline that had most developers throwing their hands up in the air in disgust.
Unfortunately the situation in the late 1990s was:
- The major browsers were incompatible.
- IE4+ was the most standard. Yes, really. Those versions had a relatively complete implementation of CSS.
- IE came preinstalled with the standard operating system of that time.
That was it. That was why corporations went with it. It's why they adopted the monoculture in the first place. If Netscape had been a little quicker with Mozilla, or been more enthusiastic about CSS in Netscape 4.x, and if CSS had been a little more complete, things might have been different.
You are not alone. This is not normal. None of this is normal.
Chrome uses Webkit specific css and not W3C. It claims it supports more standards but like IE 6 it is not standardized.
It is like IE 4 in many ways as websites need to use Webkit specific hacks.
http://saveie6.com/