Skip to content
This repository has been archived by the owner on Oct 11, 2020. It is now read-only.

Ghostery & uBlock-Edge #50

Closed
affe42 opened this issue Jan 7, 2017 · 9 comments
Closed

Ghostery & uBlock-Edge #50

affe42 opened this issue Jan 7, 2017 · 9 comments

Comments

@affe42
Copy link

affe42 commented Jan 7, 2017

Describe the issue

It seems that you cannot run Ghostery (7.1.1.5) and uBlock (1.10.2) at the same time. One or the other always shows zero detections.

Is this Edge extensions API restriction or something else? I'm happy to bug Ghostery's devs if it's their fault. :-)

One or more specific URLs where the issue occurs

Screenshot in which the issue can be seen

Steps for anyone to reproduce the issue

Your settings

  • Browser/version: Edge 38.14393.0.0
  • uBlock Origin version: 1.10.2
Your filter lists
Your custom filters (if any)
@japborst
Copy link

japborst commented Jan 7, 2017

Perhaps because the other one has already blocked the request, so there's nothing left for the other one? How is the behaviour in Chrome, for example?

@affe42
Copy link
Author

affe42 commented Jan 7, 2017

On other chromium-based browsers they complement, not exclude each other. For example, with Opera, you can easily get three layers of filtering: Opera's built-in, Ghostery & uBlock Origin.

@japborst
Copy link

japborst commented Jan 7, 2017

Right. And you can confirm there is no overlap between blocked requests?

@affe42
Copy link
Author

affe42 commented Jan 7, 2017

Yes, on Opera I can selectively disable/enable either one (Ghostery / uBlock) and the other will immediately (after reload) see the resources not filtered by the other any more. On Edge, if uBlock is active, Ghostery doesn't filter anything, even if you disable uBlock from it's settings panel.

@nicole-ashley
Copy link
Owner

Yeah, I noticed this when Gostery came out and I tried it myself. I'm not sure what the issue is but it does appear to be browser-side and either a bug or intentional implementation detail on Microsoft's side (I haven't asked them about it to know which).

I followed these steps:

  1. Install uBlock, Adblock Plus, and Ghostery.
  2. Disable all but uBlock in the browser. uBlock catches requests.
  3. Enable Gostery. Ghostery catches requests, uBlock doesn't.
  4. Disable uBlock, enable Adblock Plus. Adblock Plus catches requests, Ghostery doesn't.
  5. Disable Adblock Plus, enable uBlock. uBlock catches requests, Ghostery doesn't.
  6. Disable Ghostery, enable Adblock Plus. Adblock Plus catches requests, uBlock doesn't.

So it would appear that only the latest extension to bind to request handlers is given access to them; all previous bindings are lost.

@scottlow
Copy link

This is a known issue that we have recently fixed: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/10276685/

It should be fixed in the most recent Windows Insider Preview build (15007) that dropped earlier today and I'm in the process of sending the fix in for approval to back-port to Anniversary Update builds now.

@affe42
Copy link
Author

affe42 commented Jan 13, 2017

Thanks for the info!

@nicole-ashley
Copy link
Owner

nicole-ashley commented Jan 13, 2017

Thanks @scottlow, I can confirm this appears to be working in 15007! Thanks!

gorhill referenced this issue in uBlockOrigin/uAssets Feb 6, 2017
@affe42
Copy link
Author

affe42 commented Apr 8, 2017

The fix has been now released with Windows 10 Creators Update. Ghostery & uBlock are running together like they should :-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants