Microsoft Tech
Article
By Microsoft Developers

Building Extensions for Microsoft Edge

By Microsoft Developers

This article is part of a web development series from Microsoft. Thank you for supporting the partners who make SitePoint possible.

Extensions have been the top-requested end-user feature of Microsoft Edge since we launched, and we’re excited to be previewing extensions in Edge starting with Windows Insider Preview build 1429. In this talk we’ll walk through how we’re working to build a trustworthy extensions ecosystem, while making it easy for developers to easily write interoperable extensions that enhance the browsing experience.

This article is part of the web development series from Microsoft tech evangelists and engineers on practical JavaScript learning, open source projects, and interoperability best practices including Microsoft Edge browser and the new EdgeHTML rendering engine.

We encourage you to test across browsers and devices including Microsoft Edge – the default browser for Windows 10 – with free tools on dev.microsoftedge.com, including F12 developer tools — seven distinct, fully-documented tools to help you debug, test, and speed up your webpages. Also, visit the Edge blog to stay updated and informed from Microsoft developers and experts.

  • G P

    “Microsoft committed to interoperability” REALLY? I am not against Edge or Microsoft but let’s get to the reality. Besides fancy colors and fonts the real stuff is not yet fully interoperable. For instance, in Chrome extension native messaging comes by default and there is beautiful key called “allowed_origins” which tells what is allowed to load etc. However, as shown in this video it is not as simple as changing chrome to browser. No! I had to develop a UWP companion application for Edge native messaging to work only in Windows 10 Creators update and Edge version 40.150 and above! I am from Java background and busting my hands to learn Visual Studio and C# to have that UWP companion application. To add more to pain, this UWP exe along with bunch of other DLLs to be included and packaged along with Edge extension. This is no way in comparision with Chrome where those guys made it a soft walk with pure JavaScript. That is interoperability not this!! Sorry didn’t mean to hurt Edge guys but this is what I am going through right now.

Recommended
Sponsors
Get the latest in Front-end, once a week, for free.