Launching & Internet Explorer platform priorities

At //build 2014, we talked about our commitment to building a deeper partnership with Web developers. We started by launching the beta of which included a first peek at features in development for the next version of Internet Explorer. The positive reception has been great to see, along with the feedback on what could improve.

Later in April, @IEDevChat kicked off our first monthly #AskIE session, with IE engineers responding to over 100 questions in 2 hours, with a total of 2.4 million people exposed to the #AskIE hashtag. Here’s the team hard at work answering questions:

IE team answering questions from #AskIE session

Launching with new features

Today, after some of our team members host the Microsoft Astronaut’s Welcome Reception at JSConf 2014, we are happy to announce that we are removing the beta tag from! We’ve incorporated a number of improvements based on your feedback. Here’s a look at just some of the changes we’ve made:

  • Open Sourced – the data in status.modern.IE is useful for many purposes and many developers have expressed an interest in contributing to the project. Starting today, the entire site (including the data that backs it) is available on GitHub under the Apache V2 license. We also expose the IE support data as a service, provided under the Creative Commons Attribution v2 license. Check out our Readme for more.
  • Improved Search & Filter – we heard the feedback that the Web platform is vast and finding the features you care about was a bit tricky in the original beta site. The new “Interop” menu lets you easily enter in your browser support interests to find features available in the Web platform.
  • Deep Linking – via HTML5 History and Angular routing, status.modern.IE enables you to deep link to a feature you want to share with others. For example, go straight to GamePad API status.
  • Better Mobile Support & Performance – nearly 20% of our visitors are from mobile devices. We’ve further optimized the site to make sure you can get at the latest browser status while discussing the Web over coffee or testing out your site in IE11 for Windows Phone 8.1 Developer Preview.

New filters on status.modern.IE

We’re also announcing a new set of features that are now In Development for Internet Explorer, including:

  • Web Audio
  • Media Capture
  • ES6 Promises
  • HTTP/2
  • And more….

Head on over to status.modern.IE to find the full list!

These features form a part of our commitment to delivering interoperable implementations for the latest features on the modern Web. The current list of features “in development” is not an exhaustive representation of what we will deliver in the next version, but an indication of what we currently have highest confidence in delivering. There are several other features that we realize are very important and are working on a plan to support – stay tuned for more updates in the future.

Looking ahead: our priorities

Beyond the specific features that our developers are working on right now, we’d like to share more about the vision and priorities of the IE Platform team working on the HTML5 capabilities for IE. We’re big believers in the Web because of its broad reach that touches so many people, be they users, developers or businesses. From that belief, we have rallied the team around a simple people-centric and pragmatic vision:

The Web should just work for everyone – users, developers and businesses.

At first glance this is a seemingly simple and obvious goal. Like most good vision statements, though, we use it to shape our priorities as we make inevitable trade-offs and design choices. For example, if a Web standard demands one behavior but other browsers and Web sites expect a different behavior then we implement the interoperable design so the sites “just work” for our users. We then engage with the standards working groups to update the standard to the interoperable behavior. Most of all this goal encourages pragmatism rather than always standing on a narrow principle.

With that mindset, we set our top priorities which reflect the most significant ways that we believe the Internet Explorer platform can help to achieve that vision:

  • Get users current. Everyone wins when more IE users are running the latest version of the browser. We will continue to build features (like Enterprise Mode IE) and partner with teams internal and external to Microsoft to enable users and businesses to confidently move to the latest version of IE.
  • Security. Users must feel secure running IE and businesses must feel secure deploying IE in their environments. We will continue to invest deeply in security features that provide broad mitigations to potential vulnerabilities.
  • Interoperability and compatibility. Everyone wants sites written a decade ago to just keep working, but everyone also wants the latest HTML5 features for great experiences on the modern Web. We will work to ensure that we do a great job at both, ensuring improved backwards capability and interoperability with the latest HTML5 features across modern browsers.

We look forward to sharing more with you on how we plan to make those priorities a reality in the coming months.

We’re confident that this direction will allow us to make a positive impact on the Web and make significant strides towards the vision of ‘the Web just works for everyone.’ We look forward to hearing your feedback @IEDevChat! Be sure to join us for the next #AskIE session, live from JSConf on Thursday, May 29th @ 1PM-3PM EST.

— Sam George, Partner Group Program Manager, Internet Explorer

P.S. Charles Morris and Jacob Rossi from the team also joined Larry Larsen from Channel 9 to talk about today's announcements:

Comments (49)
  1. pmbAustin says:

    There's a lot of emphasis on the features of the rendering engine.  And that's good.  But it'd be equally nice to see a place that focused on the User Experience (UX/UI)… for both Modern and Desktop IE.  Is there a "best place" for that kind of feedback and forward looking notifications of what you're working on?

  2. Paul Topping says:

    Still nothing on MathML support, much needed by education and for accessibility

  3. Yannick says:

    Nice website! Hope those features will be available soon!

  4. Charles Morris [MSFT] says:

    @pmbAustin – Thanks for the feedback – you're right that we're focused on communicating platform plans for now in order to help developers plan ahead. We are working on some improved feedback mechanisms for both the platform and UX but for now you can just leave feedback here in the comments!

  5. John says:

    Considering that is built with AngularJS, you should really consider pushing Object.Observe() implementation, because that's what AngularJS 2.0 will use, and it would be a shame, that the IE vNext would need to use dirty checking fallback. That would not be a big problem if IE would be on a really modern browser development speed. And yes, by that I mean that IE is not a modern browser, because it's allways behind other browsers.

  6. YipYip says:

    I've noticed a few features missing from status.modern.IE, such as date picker.

    For an alternative, take a look at for a feature-by-feature detailed breakdown of browser support, including polyfill info, prefix info, mobile browser support, and more.  Click on "Tables" and scroll to the bottom for a grand total feature support scorecard.  

    Currently, IE11 gets 69%, Firefox v29 gets 84%, and Chrome v35 gets 88%.

  7. Yannick says:

    @Paul Topping – Right… MathML is a nice thing, but it's not "much needed", or by education, nor accessibility. We're fine now too without it.

    @YipYip – It doesn't realy matter how much a browser supports, what matters is how it supports it and if it follows the standards. And IE is doing very well on that. 🙂

  8. Gérard Talbot says:

    @Charles Morris [MSFT] and @Jacob Rossi [MSFT]


    we talked about our commitment to building a deeper partnership with Web developers.


    along with the feedback on what could improve.


    Let us imagine, just for a minute, that a lot of developers and users ask and request that, say, this comment form in IE blog for posting feedback be fixed so that it would work correctly, so that this comment form in IE blog for posting feedback would function normally, so that this comment form in IE blog for posting feedback would … huh… just work as expected. For everyone. Now, here's my question: why would it take Microsoft more than 6 years to honor such fairly reasonable request? … with dozens and dozens of posts coming from dozens and dozens of users, developers, etc about such request? Why??

    You ask for feedback and you got feedback.

    Gérard Talbot

  9. Gérard Talbot says:

    @Charles Morris [MSFT] and @Jacob Rossi [MSFT]


    we talked about our commitment to building a deeper partnership with Web developers.


    along with the feedback on what could improve.


    I personally wrote in an email to Travis Leithead in 2008 indicating that I would not continue to contribute bug reports or reduced test cases or anything unless the connect Microsoft IE feedback would be considerably and significantly improved. You wanted feedback on what could be improved and you got detailed feedback on what could be improved. In emails. And in this blog. Several times. And from various sources, not just from me.

    Gérard Talbot

  10. Gérard Talbot says:

    @Charles Morris [MSFT] and @Jacob Rossi [MSFT]


    we talked about our commitment to building a deeper partnership with Web developers.


    along with the feedback on what could improve.


    I've asked many months ago why Microsoft submitted CSS2.1 tests that have been reviewed and flagged as imprecise and/or incorrect for more than 3 years ago have not yet been accordingly corrected. I never got a reply on this.

    I have suggested that this blog should be moderated; abrasive remarks, anonymous posting, name-calling, insinuations, etc … are not that rare.

    IE software developers, IE project managers, etc post and ask for feedback in this blog almost every months or so and they get feedback. And some are relevant, constructive, positive feedback.

    Gérard Talbot

  11. Beento says:

    So if e.g. says "Not currently planned" what exactly does that mean? Only not in the next version or in general for the foreseeable future? And is there any venue for lobbying in favor of it?

  12. Benno says:

    @Yannick: How's it not needed for accessibility?…/microsoft-cripples-display-math-ie10-11.html

  13. Beento says:

    @Yannick: How's it not needed for accessibility? See…/microsoft-cripples-display-math-ie10-11.html

  14. Beento says:

    Just noticed you even linked to the bug tracker entries of the other browsers, that's great! (BTW: while you are using the short domain for Google Chrome you aren't using the one for Firefox[Number]).

  15. Cosmin says:

    Great features, thank you for your hard work. I have a question which is bothering me for a few years now. How about enhancing font rendering for cleartype and subpixel aliasing on non-HD displays ? The fonts look worse in IE than in all other browsers, which prevents me from using Internet  Explorer, as much as I would like to use it, fonts are not readable, not comparable to text in concurrent browsers. Thank you again.

  16. NumbStill says:

    Great direction and great to see the site (and the data) open sourced. Now I can be always up to date using RSS with the latest changes –…/ie-status.json.atom

    Do you have anything to announce regarding a no-new-vendor-prefixed-features policy?

  17. aaa says:

    A security hole unsolved to IE8 (2014.05)…/ZDI-14-140

  18. The Deeds says:

    Thanks for

    Please add CSS resize and outline-offset properties to your backlog:…/css3-resize-and-outline-offset-properties-missing. Couldn't find them on

  19. Chris W. says:

    @cosmin – are you using Win8.x? If so, this is a known bug. Err "feature". They changed how subpixel anti-aliasing works in Windows 8. It's now greyscale, not RGB. Many users report a degradation in appearance but this is considered "by-design".

    pmbAustin makes a good note about Ux feedback and priority going forward. Of course, at least you all weren't on the Australis team. 😉

    A few tidbits of my own for IE going forward:

    1) Fragmentation. What happened with XP (and to a lesser extent Vista) can't be allowed to happen again. I get the rationale of the back-porting of Direct2D & all to XP & won't re-litigate that (particularly with support now ended) – but Vista is now in extended support and has been blocked from IE10+. Next year (iirc) 7 will enter "extended support". If that means IE releases are going to be shut off, you all might as well fold up tent.

    With IE no longer considered a "platform component", it makes no sense to knee-cap yourselves unless necessary. You should focus on getting the newest version of IE onto the most users. Who cares what version of Windows they are running? (Within reason). Is the priority IE or selling Windows licenses? (It can be both!)

    2) Extensibility. This has been a long-time issue with IE. It's probably not a big deal for most consumers which is probably why you all still have the marketshare you do – but it's a real PITA to write a BHO vs an "extension" in Chrome or Firefox. It's not 1997 anymore. We need some sort of simplified, easier-to-access way. Viewing the IE Add-ons Gallery is like going into a K-Mart store – it's just too painful to do.

  20. Bart says:

    IE only needs one feature for now: auto updates! Firefox and Chrome have it. If IE would finally have it too, then it could be on par with the other browsers much sooner. It wouldn't be so painfully fragmented as it is now and innovation on the web platform would accelarate even more dramatically then it does now, no longer held back by IE.

  21. Ashley says:

    How can you say you're committed to getting everyone on the latest version of IE when IE11 isn't even available on Windows 8.0? So much for that 'automatically install updates' option. StatCounter shows that Windows 8.1 hasn't even overtaken Windows 8.0 in usage share yet, and that there's a sizable chunk of IE10 users still around, probably due to Windows 8.0. All other browser makers have the latest version available for Windows 8.0. What exactly is going on there, and can you assure us this nonsense isn't going to happen again in future?

  22. Jacob Rossi [MSFT] says:

    @beento – the bug links for both Chrome and Mozilla come from the chromium dashboard feed. To update it, you'll need to request that from them here:…/chromium-dashboard

    @cosmin Thanks for the feedback. We prioritized improvements in IE11 for increasingly common high resolution displays. We think we have some of the best high DPI support of browsers on Windows. If you haven't already, please send us some example cases (URLs and screenshots) as well as info about your display (resolution, size, graphics card) at and we'll see if there's anything we can do. If you know how to grab a dxdiag report, that would be even better. Chris W is correct in his description of our change from RGB to grayscale. Thanks!

    @NumbStill – Thanks, and feel free to contribute to the project! Regarding prefixes, nothing new to share at the moment, but this is something we're always refining and rethinking as we realize prefixes are often problematic.

    @TheDeeds thanks, please file an issue for adding these over at the project on GitHub:…/Status.IE

    @Chris W. Getting our users current and extensibility are problems we acknowledge and are thinking about. Getting our users current is one of our top priorities, in particular.

    @Bart Actually, IE does already auto update by default.That's made a big improvement in getting our users current, but we know that we need to do more. There are some tough challenges that are preventing some users from updating (enterprise compatibility, older hardware with out of date operating systems, driver issues, etc) and we're working hard to solve those.

    @Ashley this particular case of out of date IE installs is one we're definitely investigating (no solutions to share yet). May we ask what is preventing you from updating to 8.1 with IE11?

  23. Luiz Oliveira says:

    As there is no other place to make suggestions about the end user's perspective to Internet Explorer, I suggest here to do an alignment of resources of Internet Explorer for Metro and for Desktop. Some very useful features like support for read mode, and synchronization of Bookmarks should be taken for the Internet Explorer Desktop, at least in Windows 7. Sometimes we work on computers that are not updated to the latest version of Windows, and is not under our control to update them, it ends up forcing users to third-party services will instead of Internet Explorer to replace certain resource shortages in the Desktop version.

  24. Stop says:

    Please just stop making browsers, please

  25. pmbAustin says:

    The number one most needed UI feature on Modern IE (and Windows Phone IE) is an ability to quickly jump to the top and bottom of long pages.  So many sites have "endlessly scrolling pages" (think twitter, Facebook, etc.), and it's frequently desired to "get back to the top" or "jump to the bottom (of what has already rendered, obviously)".  Safari in iOS allows you to touch the status bar to do this.  For Modern IE, we either need a gesture, or preferably, the implementation of "semantic zoom".  If you pinch to zoom out, you should be able to zoom out to see the entire (so far rendered) page, and then be able to touch any spot on it to jump to that spot (top, bottom, anywhere in the middle).  Similar to the way the start screen semantic zooming works.

    This is a HUGE usability issue, as I'm constantly and endlessly flicking to get to the top or bottom of long pages, and it's just tedious and annoying.  It's impossible to "grab" scroll-bars with your finger to get it done, so there needs to be some touch-centric way of doing this.  This is my number one gripe with the "modern" versions of the browsers (on both windows phone and Surface).

  26. Ashley says:

    @Jacob Rossi – Don't ask me! I have no issues at all, I am using Windows 8.1 no problem. But StatCounter shows that since the release of Windows 8.1, Windows 8.0 share hardly dropped (see: – it peaked at 8.15% and in about six months dropped only about 0.35%. This suggests basically nobody is updating from Windows 8.0 to 8.1, even though it is a free update. I have no idea why this is, I'm sure people at Microsoft are better placed to answer. However since IE11 is only available on Windows 8.1 and Windows 7, not Windows 8.0, there's a huge chunk of users stuck on IE10 who are not getting updated. Why is IE11 not available on IE10? Why should users be forced to go through an OS update to update their browser? It hardly seems Microsoft are serious about getting everyone on the latest version of IE if it's not available for an 18 month old version of Windows. It's IE9-not-on-XP all over again – which has had very long term impact on the web platform, since StatCounter again shows IE8 is *still* the second most used version of IE after IE11. How do we know this won't be repeated? Are you actually going to sort this out or will IE12 just add more fragmentation with chequered support for your own OS?

  27. @Ashley: The same folks who didn't move from Windows 8 to Windows 8.1 are the same folks who wouldn't have installed IE11 anyway.

  28. Compatibility View Mode Support? Yes, right? says:


    Will still support quirks mode and compatibility view? I kinda need it for my 7 year old project.


  29. Ashley says:

    @EricLaw – but what about the new "Install new versions automatically" option? Users should be getting the latest version of IE without having to do anything, like Chrome and Firefox, so the web isn't clogged up with old versions of IE holding us back.

  30. David says:

    I build web applications and currently have a 13,000 user base in corporate environments.  Given that nearly 30% of my users are locked into using IE8 due to "corporate rules",, its features and most of CSS3 are just a distant dream…

    Perhaps efforts should be focused on getting corporates to wake up because us developers can only do so much

  31. Charles A says:

    need to support MathML!

  32. Swansea University says:

    +1 for MathML

  33. no name says:

    IE12 should correspond to Windows 7 succeedingly! Thank you for your consideration.

  34. Jacob Rossi [MSFT] says:

    @David That's a scenario we care deeply about helping.  Have you read our recent post about Enterprise Mode for IE11? This feature is aimed at helping corporations move to the latest version, while having a high fidelity emulation of IE8 for the internal legacy sites that still require it.…/stay-up-to-date-with-enterprise-mode-for-internet-explorer-11.aspx

  35. Yannick says:

    Hey IE team, when are we actualy going to see something from the next IE?

  36. Sardoc says:

    I agree with what Chris W. said about fragmentation. I sure wouldn't mind having IE 12 released for Vista and 2008, as these systems are more than capable to handle it (even if it means some features would have to be removed, which I don't think would be necessary anyway, then at least the browser would be a lot more standards-compliant). This, and the fact that 2008 still is hasn't reached the end of its mainstream support (Jan 2015), and it has the same codebase as Vista.

    On Win 7, there's only one aspect of IE 10/11 that I hate: grey, metro-style scrolling bar. I don't know why it was changed, but the new scrollbar just made it harder to navigate on websites with lots of content. It becomes so small I just can't see it until I either use the mouse wheel or just click somewhere on the bar, so that it moves. I'd really appreciate if it was reverted back to the good, old system scrolling bar.

  37. Sheila says:

    In the Modern IE, I would like to access my current browser history by long pressing or click and holding the left and right arrows on the current web page; just like can now in the desktop IE.

  38. L. says:

    Another +1 for MathML.

  39. Frankie says:

    When Microsoft adds support for new technology you folks are darn good but it is the user experience that utterly kills me both as a user and a developer.

    I want my file menu on top, in fact just put it directly to the right of the IE icon and keep the title in the center, merge the two toolbars but don't condense it like Firefox unless the width is too short for the (centered) title.

    I can't use IE with it's messed up toolbars. The command bar belongs on the left and the favorite bar on the right but it's backwards!

    I have my address bar taking up half the width of my browser and then my bookmarks on the same vertical toolbar to the right also using half the width, why can't IE do this?

    I really need a DEDICATED downloads and history button and add the favorites to the command list.

    Let us remove and MOVE icons around on the interface! Broke Mozilla can do this but hundred billion dollar Microsoft can't?

    I want my Developers Tools not to have "F12" in front of the text, that is my next track media key and it's just weird. Also bring back the text-labels and get rid of the goofy icons in IE11 for the dev tools…I STILL can't figure out where half the stuff is and a lot of it locks up my 4GHz eight core 16GB machine for up to half a minute.

    The ability to both horizontally and vertically move toolbars like LibreOffice would make IE much nicer to use as well but keep the ability to lock toolbars please.

    The tools menu is wildly bloated, please condense it to about six or seven items, hide the more advanced stuff, alphabetize it and put Internet Options at the bottom.

    Tabs don't belong on top, that tells the user that the content represented by the tab has control over the user where as when the browser controls are over the tab it signifies that the user has control over the browser/content.

    Icons AND text labels should be available for every button and where is the Go button? A lot of us use that to GO to a page instead of reloading it and resending POST data.

    Shadow DOM could lead to new HTML5 form fields which would really help ease things for users, please also add CSS resize, tired of typing in 100×100 pixel textareas on 24 inch screen.

    Please have the properties window's TYPE show text/html or application/xml instead of the useless Windows Shell description.

    Add support for open source audio and video codecs, for goodness sakes IE supports WebGL but not audio and video elements?

    Make it clear that SHIFT+F5 clears the cache and forces all requests to be fresh from the server, IE is too ambiguous about that and I simply don't trust clearing the cache.

    When deleting cookies add the option with Adobe to kill off Flash cookies used by shady marketers.

    Make infinite loop of JavaScript alert dialogs provide a temporarily-disable checkbox but re-enable them after reloading the page (not closing and reopening the browser).

    Make the PC personal again and you could regain a lot of loyalty, esp from Opera diaspora.

  40. T says:

    @Frankie, instead of writing these "essays" here in comment box, go to where the issues belong. Then send us the URL to your feedback page here so if others share your opinion, they can vote AND you can slap that URL at any forum in future.

    Another way is to send a tweet and share tweet URL with the world to get a +1 / attention.

    Otherwise, everything you say here goes to drain!


    ^^This is the right way of doing it. No matter what a fool (such as @pmbAustin) think about himself when leaving those "valued" comments here for the last whole decade. Pity, what a waste of electrons and brain cells!

  41. pmbAustin says:

    From this very page, @T, let me quote to you from Charles Morris [MSFT]:

    "We are working on some improved feedback mechanisms for both the platform and UX but for now you can just leave feedback here in the comments!"

  42. __hAl__ says:

    The article mentions the IE11 developer preview for windows Phone 8.1.

    When I tried this version before it constantly reloads pages that were already fetched whereas the current browser in IE8 does not.

    That is a real headache especially if you just travelled onward to an area with a very slow connection (like when you are in a train or bus).

    Please fix this terrible regression.

  43. __hAl__ says:

    Meant to say 'WP8' of course, not IE8

  44. Tom says:

    @T, there is also a permalink option if you click # next to the alias. You can then copy the link and use it for reference. Is this enough to make a case you were referring to?

    Connect has decades old unresolved issues for IE. Even leaving comments here, twitter or any other platform doesn't make any difference if they tend to ignore our feedback (super detailed or otherwise) with those canned messages; "we are looking into it" and after 10 years, "we are still looking into it". IE team is not hard-core enough anyway to win the hearts of power users, web designers and developers. Especially, not after they decided to dump extensions (probably to promote their Store apps model). This kind of pointless cunning strategies have never worked for Microsoft but do they care? No! So, should we care? YOU would be "fool" if you think so..

    @pmbAustin, that's their lame excuse. Its takes hardly 5 minutes to configure a feedback channel on which does great stuff related to feedback. Besides UV is doing good for Visual Studio and ASP teams for years now.

    @Microsoft CEO to the last person standing, Web browser is not "just another free application comes with Windows". It is the versatile heterogeneous OS. So please treat it like one!

  45. Gérard Talbot says:



    Connect has decades old unresolved issues for IE. Even leaving comments here, twitter or any other platform doesn't make any difference if they tend to ignore our feedback (super detailed or otherwise) with those canned messages; 'we are looking into it' and after 10 years, 'we are still looking into it'.


    Exactly. I entirely agree with you.

    They make you file bug reports, then wait, but then you have to re-file the same bug reports again later when the next IE is in beta.

    If connect IE feedback had been corrected and improved accordingly immediately and as soon as 2006 or 2007 or 2008, then the bug reports of the bugs which have not been fixed would be available, accessible, viewable by anyone and everyone. And we wouldn't have to refile the same bug reports again. I'm not talking about feature requests here or some kinds of customizations.

    Microsoft IE team has not developed good tools and good protocols (certainly has not improved such tools and protocols) like other mainstream browser manufacturers have, therefore it often mishandles the feedback from its users.

    The same can be said about this blog and its bugs. It never should have taken 6 years and dozens of people complaints just to fix comment posting.

    Gérard Talbot

  46. asif sait says:

    internet is not working please check the error thanks

  47. next aaa says:

    Does a desktop also become like this, as for IE12? It should detach succeedingly and should provide.

    Please correspond also to Windows 7.…/internet-explorer-12-will-include-substantial-changes-to-the-ui

  48. doris cannon says:

    looooking for a video taken 23 May 1014 of Me and '''''''scott cannon dancing

  49. DocOck says:

    Is there a way to get IE off of Server 2012?

Comments are closed.

Skip to main content