Issue 5315 - Add support for Microsoft Edge

README.md

 Adblock Plus for Chrome, Opera, Microsoft Edge and Firefox
 ==========================================================
 
 This repository contains the platform-specific Adblock Plus source code for
 Chrome, Opera, Microsoft Edge and Firefox. It can be used to build
 Adblock Plus for these platforms, generic Adblock Plus code will be extracted
 from other repositories automatically (see _dependencies_ file).
 
 Note that the Firefox extension built from this repository is the new
 [WebExtension](https://developer.mozilla.org/en-US/Add-ons/WebExtensions).
@@ skipping 14 matching lines @@
 ### Building the extension
 
 Run one of the following commands in the project directory, depending on your
 target platform:
 
     ./build.py -t chrome build -k adblockpluschrome.pem
     ./build.py -t edge build
     ./build.py -t gecko-webext build
 
 This will create a build with a name in the form
-_adblockpluschrome-1.2.3.nnnn.crx_, _adblockplusedge-1.2.3.nnnn.appx_ or _adblockplusfirefox-1.2.3.nnnn.xpi_.
+_adblockpluschrome-1.2.3.nnnn.crx_, _adblockplusedge-1.2.3.nnnn.appx_ or
+_adblockplusfirefox-1.2.3.nnnn.xpi_.
 
 Note that you don't need an existing signing key for Chrome, a new key
 will be created automatically if the file doesn't exist.
 
 The Microsoft Edge build _adblockplusedge-1.2.3.nnnn.appx_ is unsigned and
 is only useful for uploading into Windows Store, where it will be signed. For
 testing use the devenv build.
 
 The Firefox extension will be unsigned, and therefore is mostly only useful for
 upload to Mozilla Add-ons. You can also also load it for testing purposes under
 _about:debugging_ or by disabling signature enforcement in Firefox Nightly.
 
 ### Development environment
 
 To simplify the process of testing your changes you can create an unpacked
 development environment. For that run one of the following commands:
 
     ./build.py -t chrome devenv
     ./build.py -t edge devenv
     ./build.py -t gecko-webext devenv
 
 This will create a _devenv.*_ directory in the repository. You can load the
 directory as an unpacked extension, under _chrome://extensions_ in Chrome,
 under _about:debugging_ in Firefox or in _Extensions_ menu in Microsoft Edge,
 after enabling extension development features in _about:flags_.

[kzar, 2017/06/22 11:23:37]

Nit: I think the part about enabling the features in about:flags should be
broken into a second sentence. As it stands that is kind of confusing, the
reader might think they need to enable that feature in Firefox and Chrome too.

 After making changes to the source code re-run the command to update the
 development environment. In Chrome and Firefox the extension should reload
 automatically after a few seconds.
 
 Builds for Microsoft Edge do not automatically detect changes, so after
 rebuilding the extension you should manually force reloading it in Edge by
 hitting the _Reload Extension_ button.
 
 Running the unit tests
 ----------------------
 
 To verify your changes you can use the unit test suite located in the _qunit_
 directory of the repository. In order to run the unit tests go to the
 extension's Options page, open the JavaScript Console and type in:
 
     location.href = "qunit/index.html";
 
 The unit tests will run automatically once the page loads.
 
 Linting
 -------
 
 You can lint the code using [ESLint](http://eslint.org).
 
     eslint *.js lib/ qunit/ ext/ chrome/
 
 You will need to set up ESLint and our configuration first, see
 [eslint-config-eyeo](https://hg.adblockplus.org/codingtools/file/tip/eslint-config-eyeo)
 for more information.