Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't open links since 8.2.5 on Chrome: "pop-up blocked" #254

Closed
TiTi opened this issue Nov 28, 2018 · 12 comments
Closed

Can't open links since 8.2.5 on Chrome: "pop-up blocked" #254

TiTi opened this issue Nov 28, 2018 · 12 comments

Comments

@TiTi
Copy link

@TiTi TiTi commented Nov 28, 2018

Description

Last update today or yesterday broke a lot of links in my Chrome, either left or middle clic.
A message "pop-up blocked" appears in the url toolbar.

I have no other choice but to disable Ghostery for now 😢

It affects a lots of websites. Sometimes the link is working somehow.
Steps to reproduce I'm submitting always fail.

It works fine (as usual) when deactivating Ghostery.

Important note:
I'm using Chrome beta (but never had issue with ghostery before)

[pop-ups are blocked by default in Chrome]

Expected Behavior

Url is opened, either in current tab (left click) or another (middle click)

Actual Behavior

A message "pop-up blocked" appears in the url toolbar.

Steps to Reproduce

  1. Go to a website like https://www.qwant.com/?q=ghostery&t=web
  2. Left click a search result
    (it works fine when deactivating Ghostery)

Other sample:

  1. Go to imgur.com
  2. Click any image/gif with left click: it works
  3. Go back to home page
  4. Click any image/gif with middle click: it doesn't work
    (it works fine when deactivating Ghostery)

Versions

  • Browser: Chrome Version 71.0.3578.62 (Official Build) beta
  • OS: Windows 10
@meredy
Copy link

@meredy meredy commented Dec 1, 2018

I experience the same issue, but seemingly only since 8.2.6 was released

@joeczucha
Copy link

@joeczucha joeczucha commented Dec 12, 2018

I'm experiencing the same issue, but with a strange caveat:

I have an iMac in my office and a Macbook Pro at home. I'm running Chrome Version 71.0.3578.80 on both and have recently restarted both browsers/machines. To test, I'm running in "incognito mode" with Ghostery (version 8.2.6) as the only active extension on both.

On the iMac - if I visit BBC News, hold CMD and click a link, I get "Pop up blocked".

On the MBP - if I do the same, the link opens in a new tab without issue.

Disabling Ghostery on the iMac causes it to function in the same way as the MBP (i.e. the new tab opens).

I thought that I may have just previously white-listed the site but the same thing happens on Wikipedia, Amazon etc. so I don't think that's the case.

Sorry that I don't have more insight but I figured that I'd let you know, just in case I can provide some logs or anything to help work out what's different between the two machines.

Edit: I just tried uninstalling and reinstalling Ghostery but it's made no difference

@TiTi
Copy link
Author

@TiTi TiTi commented Dec 16, 2018

I don't have the issue anymore with Chrome Version 72.0.3626.17 (Official Build) beta (64-bit)
Ghostery in version 8.2.6

I suppose it was a Chrome issue?

@TiTi TiTi closed this Dec 16, 2018
@doktorJung
Copy link

@doktorJung doktorJung commented Dec 30, 2018

I'm just encountering this issue with Version 71.0.3578.98 (Official Build) (64-bit), and I see no updates available. I hope I can get 72 soon!

@DanielRuf
Copy link

@DanielRuf DanielRuf commented Jan 1, 2019

I'm just encountering this issue with Version 71.0.3578.98 (Official Build) (64-bit), and I see no updates available. I hope I can get 72 soon!

You have to get Chrome beta or test the Canary version.

https://www.google.com/intl/de_ALL/chrome/beta/
https://www.google.com/intl/de_ALL/chrome/canary/

@doktorJung
Copy link

@doktorJung doktorJung commented Jan 1, 2019

Thanks, I might give it a try!

@Sn-a-ke
Copy link

@Sn-a-ke Sn-a-ke commented Jan 10, 2019

ghostery - 8.2.6
Browser: chrome - 71.0.3578.98 (Official Build) (64-bit)
OS: win7(64)

-same behavior

@aloker
Copy link

@aloker aloker commented Jan 10, 2019

Same problem here. I'd appreciate a solution that does not require me to wait for Chrome 72 (29/1/19) or install a beta version.

@jingtra
Copy link

@jingtra jingtra commented Jan 10, 2019

Same problem here.

@doktorJung
Copy link

@doktorJung doktorJung commented Jan 10, 2019

Here's the Chromium ticket I opened a while back, it's being investigated as mentioned in the article above: https://bugs.chromium.org/p/chromium/issues/detail?id=918268

(It was sorta dismissed as a Ghostery issue at first, but there's movement on it now!)

[edit: it was linked in the AP article too, so I suppose this post is a little redundant.]

@doktorJung
Copy link

@doktorJung doktorJung commented Jan 11, 2019

They've rolled back an experiment, so restarting Chrome should resolve the issue once it propagates.

https://bugs.chromium.org/p/chromium/issues/detail?id=918268#c36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
8 participants