Location:
State:
Carrier
Country
Status

Previewing our first platform updates for Microsoft Edge


Yesterday, we moved Microsoft Edge Dev out of beta, and we are now directing all traffic from status.modern.ie 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

CSS

  • CSS Mutability Pseudo-classes
    • :read-write
    • :read-only

  • CSS Range Pseudo-classes
    • :in-range
    • out-of-range

  • CSS initial keyword
  • CSS unset keyword

File APIs

  • a[download] attribute

Forms

  • input type=text selectionDirection
  • input type=time
  • input type=datetime-local
  • <meter> element
  • oninvalid event handler for the element document and window

Graphics

  • Canvas ellipse
  • Canvas blending modes
  • <picture> element
  • SVG external content

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:

  • Extended srcset and sizes
  • <template> element
  • WebRTC – Object RTC API
  • Pointer Lock (Mouse Lock)

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 hope to begin development in an upcoming iteration
  • 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:

  • Shadow DOM (High)
  • Custom Elements (Medium)
  • Web Notifications (Medium)

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

Previewing our first platform updates for Microsoft Edge | Microsoft Edge Dev Blog

Previewing our first platform updates for Microsoft Edge