Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

HTTPS Everywhere extension for Microsoft Edge #5101

Closed

Description

@martinsuchan

Microsoft released in July 2016 Windows 10 Anniversary Update which comes with a new version of Microsoft Edge browser that supports Extensions.
These extensions use similar structure and API as Chrome extensions - porting the existing HTTPS Everywhere extension should be then really easy.

Documentation for developing Edge extensions is available here:
https://developer.microsoft.com/en-us/microsoft-edge/platform/documentation/extensions/

Activity

  1. TheRyuu commented on Aug 5, 2016

    @TheRyuu

    Just to update the AU is now out for Windows 10 and so is the documentation for developing extensions[1]. Hopefully minimal modifications are required since it is just the WebRequest API with some minor technical differences to Chrome's.

    Just for reference uBlock Origin requires minimal changes to get it working[2].

    [1] https://developer.microsoft.com/en-us/microsoft-edge/platform/documentation/extensions/
    [2] gorhill/uBlock#1486 (comment)

  2. jeremyn commented on Aug 12, 2016

    @jeremyn
    Contributor

    The current HTTPS-Everywhere development and build process is *nix-centric. I was recently told here that people using Windows 10 who want to contribute to HTTPS-Everywhere need to use some sort of Linux VM. However the equivalent of ChromeDriver for Edge, WebDriver, which allows for command-line browser testing, must be installed on Windows 10. So it seems to me that the build process needs to be made to work on Windows 10, or at least a parallel build process just for Edge needs to be created, before an Edge extension could be created.

  3. Artoria2e5 commented on Sep 26, 2016

    @Artoria2e5
    Contributor

    MS Edge uses the common WebExtensions API, which is used by Opera as well. For me it's fine to have the tests come later than the proof of concept alphas.

    P.S. WebDriver is also a common W3C API.

    Regarding the conversion tool, It looks generally like a lint tool that also adds a bridge for the chrome object. Attached is a sample of its bridge scripts, generated for Stylish 1.3.1-1. (Warning: heavy use of ES6.)
    bridge.zip

  4. dxgldotorg commented on Apr 7, 2017

    @dxgldotorg
  5. martinsuchan commented on Apr 7, 2017

    @martinsuchan
    Author
  6. elyscape commented on Apr 7, 2017

    @elyscape

    @WilliamFeely I don't see how that's relevant to the purpose of this extension.

  7. dxgldotorg commented on Apr 7, 2017

    @dxgldotorg
  8. jeremyn commented on Apr 7, 2017

    @jeremyn
    Contributor

    Let's not turn this into a discussion about boycotting Windows or Edge. HTTPS Everywhere means providing HTTPS rewrite protection wherever possible, including on Edge.

    I believe @Hainish has the WebExtension rewrite on his to-do list. If anyone wants to help make HTTPS Everywhere available on Edge, that effort is welcome, and they should coordinate their work with him.

  9. xt0rted commented on Apr 7, 2017

    @xt0rted

    I was trying to get Stylus working in Edge and ran into a number of issues where html5 templates & the extensions api aren't feature complete compared to Chrome, even in v15 which was released this/next week.

    I'm not sure if templates are used anywhere but the DocumentFragment api is only partially implemented so properties like .firstElementChild don't work.

    The extensions api I had issues with was

    chrome.tabs.query({ currentWindow: true }, function(tabs) { ... });

    When the currentWindow option is set to true, even with other options, the result is always undefined. Setting it to false returns a result, but that's not how either plugin is using it so it's a blocking issue. I reached out to the Edge team about this and they passed the question on to a team member to look into and confirm if it's a bug, but I haven't heard anything on it yet.

  10. robinhood2014 commented on Apr 11, 2017

    @robinhood2014

    Well, this is not good. I replaced every instance of "chrome.xxx" (where "xxx" represents functions of Google Chrome) with "myBrowser.xxx", and even removed all comments from all JavaScript files referenced in manifest.json, and the Edge Extension Toolkit is still reporting manifest.json as malformed.
    HTTPS Everywhere Prototype.zip

  11. Artoria2e5 commented on Apr 11, 2017

    @Artoria2e5
    Contributor

    The toolkit does some heavy linting on the manifest. Have you checked for errors around things like the icon stuffs?

  12. robinhood2014 commented on Apr 11, 2017

    @robinhood2014

    According to the toolkit, only the manifest file has errors.

  13. Artoria2e5 commented on Apr 11, 2017

    @Artoria2e5
    Contributor

    I fed the 2017.4.5 directory to the toolkit. This time it spits out the error as:

    manifest.json  .author : invalid type: object (expected string)
    

    The current value provided is in fact a violation of WebExtentions Spec, as per https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/author. Fixing that gives a "ready to go" message for the extension.

  14. gloriousjob commented on Apr 14, 2017

    @gloriousjob

    Hi all,

    I created this zip and it seems to work on my machine. Just extract it and sideload the extension.
    https_everywhere_edge.zip

    The process I followed was fairly simple (though it took a few tries to figure out and get working):

    1. Extracted the chrome extension.
    2. Opened manifest.json and made the following changes:
      a. changed author to "author": "eff.software.projects@gmail.com" since braces are non-standard (https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/author)
      b. Added the following subproperty to "background": ,"persistent": true
      c. Added the following property: "locale": "en"
      d. Added the following property: "minimum_edge_version": "33.14281.1000.0"
    3. Opened all js files with chrome references and placed this code at the top:
      if (typeof msBrowser !== 'undefined') { chrome = msBrowser; } else if (typeof browser !== 'undefined') { chrome = browser; }
  15. 102 remaining items

  16. dxgldotorg commented on Sep 23, 2019

    @dxgldotorg
    Contributor

    Since EdgeHTML Edge is about to be replaced with Chromium Edge, there may be no more point in developing the Edge addon, as Chromium Edge is fully compatible with Chrome extensions, and can even access the Chrome Web Store to download and install extensions.

  17. pipboy96 commented on Sep 23, 2019

    @pipboy96
    Contributor

    @dxgldotorg Do you think we shouldn't publish the extension in Edge's extension store?

  18. zoracon commented on Sep 23, 2019

    @zoracon
    Contributor

    @zoracon @andresbase What's the current status of this?

    This is being held up by the Manifest V3 planning and auditing. "Edgium" is still in Dev channel at the moment so monitoring when they will officially publicly release

  19. iNViTiON commented on Sep 23, 2019

    @iNViTiON
  20. zoracon commented on Sep 24, 2019

    @zoracon
    Contributor

    @zoracon It's in public beta channel. Not only in dev channel. https://blogs.windows.com/windowsexperience/2019/08/20/introducing-microsoft-edge-beta-be-one-of-the-first-to-try-it-now/

    Right, however my reasoning still applies. Hopefully there is news soon for public release since they have it on Beta

  21. pipboy96 commented on Sep 24, 2019

    @pipboy96
    Contributor

    @zoracon Would it make sense to start preparing now to get ready for official release? Manifest V3 should be prioritized though.

  22. FranklinYu commented on Sep 25, 2019

    @FranklinYu
    Contributor

    Right, however my reasoning still applies.

    Sorry but I disagree. This reasoning holds for Dev channel, but public beta should be a signal for browser extension developer to start testing their extensions. For example if HTTPS-Everywhere break in Chrome beta I would report a bug here instead of waiting for the bug to propagate into Chrome stable.

  23. zoracon commented on Sep 25, 2019

    @zoracon
    Contributor

    Right, however my reasoning still applies.

    Sorry but I disagree. This reasoning holds for Dev channel, but public beta should be a signal for browser extension developer to start testing their extensions. For example if HTTPS-Everywhere break in Chrome beta I would report a bug here instead of waiting for the bug to propagate into Chrome stable.

    @FranklinYu that's a good point about testing, but there has been a few reporting stability out of the extension since the dev channel. And my last comment was more geared toward the fact Chrome plans on changing this extension ecosystem in a very large way. So I have been committing more time and resources to Manifest V3 in the Chrome environment.

    I admit there has not been much publicly said from HTTPSE about Manifest V3. But that's also due to the fact that the new API has new updates even up until the past few weeks. We have publicly asked certain features from the API for HTTPSE to still function. So far they have been 75% of the way granted.
    #17268

  24. ExE-Boss commented on Jan 9, 2020

    @ExE-Boss
    Contributor

    That’s probably because webRequest can do anything with web requests, like redirecting the request to HTTPS or blocking it entirely, and as such, is also used by adblockers to block remote advertisments and trackers, and because of that, Google’s management wants developers to switch to declarativeNetRequest, which greatly limits what can be done and increases their advertising margins.

    Without webRequest, adblockers can only block advertisements by hiding them with display: none !important; in a user origin styleshhet, but by that point, the request has already reached the advertiser’s servers, and so they can still track you.

  25. pipboy96 commented on Jan 9, 2020

    @pipboy96
    Contributor

    @ExE-Boss I guess when this hits we will have to shift focus from Chrome to Firefox and Chromium forks (Brave, eloston's Ungoogled Chromium, etc).

  26. nicole-ashley commented on Jan 9, 2020

    @nicole-ashley

    It will be interesting to see what Microsoft does about Manifest v3 in the new Edge.

  27. nicole-ashley commented on Jan 11, 2020

    @nicole-ashley

    Microsoft have not taken a stance on Manifest v3 yet. I've even asked their dev team personally.

  28. zoracon commented on Feb 3, 2020

    @zoracon
    Contributor

    HTTPS Everywhere is now in the Edge store. Please report issues to Github if you see them :)
    https://microsoftedge.microsoft.com/addons/detail/fchjpkplmbeeeaaogdbhjbgbknjobohb

  29. pipboy96 commented on Feb 4, 2020

    @pipboy96
    Contributor

    @zoracon There is a problem with an icon:

    Screenshot of Edge store

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions