What's New in EdgeHTML 14
Here are the changes shipped with EdgeHTML 14, as of the Windows 10 Anniversary Update (08/2016, Build 14393). For an overview of changes to the overall Microsoft Edge browser, see Introducing EdgeHTML 14 with the Windows 10 Anniversary Update.
Here's the permalink for the following list of changes: https://aka.ms/devguide_edgehtml_14.
The Fetch API utilizes the
fetch method for fetching resources. In the past this was achieved with
XMLHttpRequest. Not only is fetch simpler to use, it also provides lower level access to requests and responses. Read more about the Fetch API in the Microsoft Edge blog post, Fetch (or the undeniable limitations of XHR).
New features (on by default)
- Default parameters (ES2015)
- Exponentiation operator (ES2016)
- Array.prototype.includes (ES2016)
- Object.values and object.entries (ES2017)
Web Authentication API (FIDO 2.0 Web API)
The Web Authentication (formerly FIDO 2.0 ) API in Microsoft Edge enables web applications to use Windows Hello biometrics for user authentication so that you and your users can avoid all the hassles and risks of password management, including password guessing, phishing, and keylogging attacks. The current Microsoft Edge (ms- prefixed) implementation is based on an earlier draft of the Web Authentication specification and is likely to change in the future. Read more about Web Authentication: Web authentication and Windows Hello.
Web Notifications allow sites to display notifications to alert users outside the context of the webpage and the browser, keeping users informed of new messages or alerts and allowing sites to improve user engagement. Web Notifications in Microsoft Edge are fully integrated with the notification platform and Action Center in Windows 10, providing a consistent experience with other apps across the system and easy controls over permissions and Quiet Hours. Check out Web Notifications in Microsoft Edge for more information.
Web Speech API
New APIs in EdgeHTML 14
Here's the full list of new APIs in EdgeHTML 14. They are listed in the format of [interface name].[api name].