Microsoft Edge Developer Guide
We've partnered with other browsers and the web community in adopting MDN Web Docs as the definitive place for useful, unbiased, browser-agnostic documentation for current and emerging standards-based web technologies. You can find details about EdgeHTML API support directly in each page of the MDN web reference library. Visit Microsoft Edge's Platform status for the latest features supported in Microsoft Edge.
What's new in EdgeHTML 16
Here's a list of the new and updated features shipped in the current release of the Microsoft Edge platform, as of the Windows 10 Fall Creators Update (10/2017, Build 16299). For changes in specific Windows Insider Preview builds, see the Microsoft Edge Changelog and What's New in EdgeHTML.
Here's the permalink for the following list of changes: https://aka.ms/devguide_edgehtml_16.
New and updated features
CSS Grid Layout
Microsoft Edge now supports the unprefixed implementation of CSS Grid Layout. Grid Layout defines a two-dimensional grid-based layout system which enables more layout fluidity than possible with positioning using floats or scripts. The example below uses CSS Grid Layout to create the structure for a basic web page.
F12 Developer Tools
This release we started a major F12 DevTools refactoring effort for improved robustness and performance, and also added a bunch of new features you can start using today on Windows Insider builds. Check out Microsoft Edge F12 Developer Tools for more on what's changed!
Payment Request API
The Payment Request API is an open, cross-browser standard that enables browsers to act as an intermediary between merchants, consumers, and payment methods (e.g. credit cards) that consumers have stored in the cloud. The API in EdgeHTML 16 has been updated to match the latest W3C Payment Request API specification. This includes:
- Support for the
- Support for the
- Support for the
- The default value for the
resultparameter changed from " " to "unknown"
Service Workers are event-driven scripts that run in the background of a web page. Service workers enable functionality previously only available with native apps like intercepting and handling requests from the network, managing and handling background sync, local storage, and push notifications. Support for service worker is still in development, but you can test out your PWA in Microsoft Edge with our experimental service worker support by enabling the service worker feature in about:flags.
WebVR for Microsoft Edge has added support for motion controllers. These controllers have a precise position in space, allowing for fine grained interaction with digital objects in virtual reality.
WebVR has also been optimized to support two different types of experiences.
Windows Mixed Reality PCs - Desktops and laptops with integrated graphics. When plugged into these devices, our immersive headsets will run at 60 frames per second.
Windows Mixed Reality Ultra PCs - Desktops and laptops with discrete graphics. When plugged into these devices, our immersive headsets will run at 90 frames per second.
Both setups will support the same immersive video and gaming experiences.
For more info about the upcoming Windows Mixed Reality updates, check out the Windows Mixed Reality holiday update blog post.
For guides and demos, head over to the WebVR Developer Guide.
Since the WebVR spec is still in development, Microsoft Edge's implementation may change later down the line.
New APIs in EdgeHTML 16
Here's the full list of new APIs in EdgeHTML 16. They are listed in the format of [interface name].[api name].
Although the following APIs are exposed in the DOM, the end-to-end behavior of some might still be in development. Refer to Microsoft Edge platform status for the official word on feature support.