It has been incredibly exciting to see such strong engagement and support from web browser enthusiasts and others over the past year with The Browser You Loved to Hate campaign. With over 25 million total video views worldwide to date, we know we struck a chord with you. Whether you were simply entertained or began to question your assumptions about Internet Explorer, we are happy to entertain and help people learn that something’s changed with IE.
Just one year ago, we launched The Browser You Loved to Hate – a Tumblr dedicated to telling the story of Internet Explorer’s comeback. Whether it was introducing you to Eugene or Officer Cupcake, reminiscing about the 90’s or letting you know that comebacks do indeed come in many shapes and sizes, there was one common theme – reintroducing you to the new Internet Explorer. So, if you are someone who hasn’t been happy with IE in the past or someone who simply hasn’t used IE in a while, we hope the Browser You Loved to Hate has been fun and gotten you to take a second look at IE.
And so on this one year anniversary, we wanted to say thanks to our supporters. And for all of you who are still on the fence about IE, we invite you to take a look at the new Internet Explorer.
Internet Explorer Marketing Manager
I wouldn't describe myself as someone who loves to hate IE. I, like most people, just want a hassle free Internet browser experience. Unfortunately with IE, there is no WebGL support, poor plugin/add on culture, poor cross platform support (even within the Windows ecosystem!), and the need to reboot the whole OS just for an update to IE! It's too much hassle.
IE = hassle
@Nathan - Microsoft actually provides full-on VMs with the various IE versions installed for free at www.modern.ie/.../virtualization-tools. Dev tools can get you close to emulating older versions, but in the end, it's just an emulation, and not the real thing. Visit that link and grab some of the VMs and you can test on the real browsers, even if you have a Mac. If you don't have the space for VMs or just think they're clunky, you can also sign up for Browserstack, which is at that link, also. It's sort of "browser testing as a service", so you can remote into all the different browser versions and test them out. If the IE guys were to have perfect emulation in IE10 for all the older browsers, then they'd essentially have to ship all of the old rendering engines, which would make the IE download pretty bloated after a while. Yea, the dev tools are pretty weak right now, but if you're looking for compat issues between different IE versions, you can't beat the real the real thing.
Nathan, a couple comments, as someone who deals with IE app compat daily, I can say the F12 tools are a great tool for enterprise developers, who despite being exposed to Firefox and Chrome, are barely taking advantage of what's in the F12 tools, let alone Firebug. Along the lines you mentioned, VS 2012 has truly industry-leading support for HTML5. It is hands-down the most full-featured HTML editor out of the box. As far as Quirks Mode, keep in mind *every* browser has a quirks mode to render non-standard HTML. IE just exposes this for the developer. Beyond Quirks mode, I agree having IE7,8, 9 modes is a double-edged sword, but again for Enterprise apps, this is a must. Testing and remediating over 2000 apps every year is extremely costly -- exposing these modes simply gives developers and IT control over when they have to migrate, rather than tying it to the deployment of a new browser (or OS that contains the latest browser). It's a evil to be sure, but a necessary evil. For these enterprise apps, having a browser release annually is painful enough, and pegging their apps to browsers that come out every 4 weeks and are only supported for this same time is completely infeasible. Likewise, IE only adopting stable features that are cross-browser compatible is huge for enterprise. It's not to say throwing stuff on the wall and seeing what sticks isn't a necessary evil as well, but IE is happy to let Google and Firefox iterate rapidly on that then, then adopt what's stable and cross-browser compatible. This is an intentional. Lastly, in regards to testing old versions of IE. You can use Windows XP Mode included with Windows 7 Pro (or other Microsoft of 3rd party virtualization technologies) to run IE6 or IE7 side by side with IE8, IE9, or IE10 on Windows 7. There are also 3rd party niche solutions to providing IE6 compatibility on Windows 7, such as Browsium Ion www.browsium.com/.../debunking-the-myth-my-application-requires-ie6.
Thank you very much for doing everything you have done in revolutionizing The Internet Explorer.
Well, unfortunately its not enough.
Please "modernize" F12 developer tools and source viewer (clickable URLs for CSS, JS and images).
That should read: take a GOOD, LONG, HARD look at Firebug (surely MS employees know it) and completely copy it. ALL OF IT.
Firebug is by far one of the best debugging tools, neck-a-neck with Chrome's inspector. Opera's Dragonfly is a mess but still provides most of the functionality that may be expected. MSIE's F12-tools are a joke. People don't even take it seriously as developer tools.
Give us the test environment for mobile browsers in F12DT (by altering the dimensions of rendering area and the resolution.. to test it against media query and adaptive designs). Chrome has it natively, FF have it via plugin and you guys would implement it when nobody would care about it (remember spellchecker story?). Please make IE useful for the software industry worldwide. If anyone can do it better, I always bet for Softies... but..
Here is another thing. let the visual studio and expression studio guys handle F12DT's UI. The current UI is the depiction of early 80's dream... btw, who designed the UI of F12 > Tools > color picker and other stuff.. seriously? After WPF in Windows 8 and 7 machines (since IE-Edge is not supported anywhere else), why would anyone want to do that way?
More on: connect.microsoft.com/.../extensibility-in-f12-developer-tools (and don't blame me for line-breaks, Connect team recently chose to ignore BR-tag while rendering the description. Who knows WHY they did that!!!!!!)
Also, emulating old IE versions is not quite right. Not only visually not quite right, but also functionally. In many cases a "native" IE is much better than emulation. It's a good function to have, but it causes developers to rely on it (which is a bad thing). I get the feeling MS never realized that.
And we NEED to test on old IE, because IE9 doesn't run on Windows XP, IE10 doesn't run on Vista, IE7 and IE8 don't run on Windows 7, and neither version can run side-by-side on any system, let alone true portable versions (hey, MS, there's a tip!)
Please hire some fresh blood in IE team, so to bring about some "freshness" in design process as well as the thought process. And appreciate people at Microsoft, who are thinking about modernizing F12DT GUI and IE menus asap coz its REALLY necessary!!