August 18, 2015 10:00 am

Previewing our first platform updates for Microsoft Edge

By / Senior PM Lead, Microsoft Edge Developer Experience

Yesterday, we moved Microsoft Edge Dev out of beta, and we are now directing all traffic from to our new Platform Status page, which has significant improvements to performance and clarity. Today, we are excited to give the first look at our initial wave of feature updates to the Microsoft Edge web platform, starting with the following new features now in development for EdgeHTML.

New Microsoft Edge platform features in development


File APIs



These features are in development now and will start to appear soon in preview builds for Windows Insiders prior to being released to the general public. In addition to these new features, several features we previously announced will start to appear in preview builds soon, including:

Our Platform Status page has been updated to reflect these announcements – we look forward to sharing preview implementations in the coming weeks!

New roadmap details on Platform Status

In addition to these updates, we’ve also made improvements to Platform Status to address feedback. One of the most common pieces of feedback we have received on Platform Status is that there’s a lack of clarity around items listed as “Under Consideration.” To address this, we are opening our roadmap up even more with new “backlog priority” labels for Status items. Here we will give some insight into where individual technologies fall on our backlog for future releases.

While we can’t always commit to a specific timeframe, you can think of our priority levels as corresponding to:

  • High – On deck; We intend to begin development soon
  • Medium – On our backlog; Development is likely for a future release
  • Low – Investigating; We are still evaluating the technology. There may be significant spec stabilization, foundational work, or additional community input required before we can begin development

You can see a few examples today at on Platform Status, including:

Over the coming weeks, we will be adding these priority labels to the existing set of technologies marked “Under Consideration” on Platform Status, to provide more insight into our plans. We hope that sharing these insights can help developers plan ahead and give a broad sense of when they can expect key technologies to be available in Microsoft Edge. Combined with other vendors’ release status (which we aggregate on Platform Status), this is useful to understand when technologies are or will be broadly interoperable on the web, and safe to build into your sites.

We are eager to hear your feedback on the features above, and encourage you to help us rank platform features by voting on the Microsoft Edge Developer UserVoice! If you have any questions or want to give feedback on these plans, we encourage you to reach out to @MSEdgeDev on Twitter or share your thoughts in the comments below.

Kyle Pflug, Program Manager, Microsoft Edge

Updated January 20, 2016 11:26 am

Join the conversation

  1. URLs would be much easier to read if words that the URL alias contain were separated with, say, a dash, e.g.:

    cssmutabilitypseudoclasses => css-mutability-pseudo-classes

    Also, it would be nice to make term/definition lists opened by default and only closed if JS is enabled, so that all content was visible/accessible if JS is disabled. That’s what Unobtrusive JS principle is about.

    Finally, using `history.pushState()` is redundant and harmful here since it’s used obtrusively and all such URLs actually display exactly the same page if JS disabled. Regular anchors would be more appropriate here. Alternatively, provide a separate dedicated page for each feature instead of listing them all on the same page.

  2. It is great to see all the work on the rendering engine. Now someone just needs to pay attention to the missing features in the chrome surrounding the engine. No matter how good your engine becomes, people like me will never use the browser with it’s broken tabs implementation, lack of back button history, no drag-drop support for links, missing bookmarklet support, and a whole host of basic browser features.

    • Thanks for the great feedback! Just to clarify, the MS Edge Dev Blog is focused on the web platform (EdgeHTML and Chakra), so we typically won’t include app features in our roadmap previews. There’s lots of great work in the pipe there as well, and the Insider Program is the best place to try it out!

  3. Really guys? No, really? On the information page which reports statuses you color-coded categories, not statuses?

  4. Will the platform update include any update to accessibility support for screen readers in Edge?