Preview of the first updates of the Microsoft Edge web platform

The other day we brought our Microsoft Edge Dev developer portal out of beta status, and now we are redirecting all traffic from status.modern.ie to a new page with platform status , which we significantly accelerated and visually cleaned up.

Today we are happy to tell you the first details about the upcoming wave of updating the functionality of the Microsoft Edge web platform. Let's start with a story about what new features are currently in development for EdgeHTML.

Developed capabilities of the Microsoft Edge platform

CSS

• Pseudo-classes CSS Mutability
  
  • : read-write
  • : read-only
• CSS Range Pseudo Classes
  
  • : in-range
  • : out-of-range
• Initial keyword
• Unset keyword

')

File API

• Attribute a [download]

Forms

• input type = text selectionDirection
• input type = time
• input type = datetime-local
• <Meter> element
• Oninvalid event handler for elements

Graphics

• Ellipses and arcs in Canvas
• Canvas blending modes
• <Picture> element
• SVG external content

These features are now in development and before entering the public release, they will soon begin to appear in the preview builds as part of the Windows Insiders program.

In addition to this list, several features that we announced earlier will appear in the next builds, including:

• Extended support for srcset and sizes attribute
• <Template> element
• WebRTC - Object RTC API
• Pointer Lock (Mouse Lock)

The page with the status of the platform has been updated and now displays these announcements. Check out the pre-release version in the coming weeks!

New details in terms of platform development

In addition to these updates, taking into account your feedback, we also made a number of changes in the format of presentation of status on the platform. One of the key comments we received on the status of this or that functionality is a lack of clarity in what “Under Consideration” means.

Therefore, we began to add to our public plan some marks with priorities from the backlog for the relevant elements. Below we describe how we prioritize individual technologies.



Although we can not always clearly define the specific date of release of some functionality, priority levels can be viewed approximately as follows:

• High (High) - "on the table"; we plan to start development in the next iteration.
• Medium - “in the list”; Development is likely in one of the next releases.
• Low (Low) - "we study"; we are still exploring technology. It may require significant efforts to stabilize the specification, refine the functionality or require additional information from the community before we start developing.

A few examples that you can find today on the page with the status of the platform:

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

Over the coming weeks, we will add such prioritized tags to other technologies marked as “Under Consideration” on the platform status page, so that you have more transparency regarding our plans. We hope that this information will help you to better plan your own work, taking into account when the necessary functionality may appear in Microsoft Edge.

We also integrate information from other browser vendors on our page, which should be useful in terms of understanding the overall picture of compatibility on the web and the possibility of using appropriate technologies on our sites.