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

Popup Blocker blocks opening New Tab #2145

Closed
Nerdy314159265 opened this issue Nov 12, 2016 · 4 comments
Closed

Popup Blocker blocks opening New Tab #2145

Nerdy314159265 opened this issue Nov 12, 2016 · 4 comments

Comments

@Nerdy314159265
Copy link

I recently switched Popup Blocking to be on for all sites by default, so that I don't have to add a specific site to get protection from malicious popups. However, one caveat of this is that for some reason uBlock will block a new tab from opening via Middle-Mouse or the Context Menu. This issue seems to vary from site to site.

On Google: It would auto-close any new tabs made

On Github: It would allow new tabs but would disallow the "Search Google for" tabs.

Steps to Reproduce:

  1. Add "no-popups: * true" to your filter rules
  2. Try opening new tabs via the Middle-Mouse hotkey or Context Menu options on various sites

Settings:
no-popups: * true

    • 3p block
    • 3p-frame block
    • 3p-script block
      behind-the-scene * 3p noop
      behind-the-scene * 3p-frame noop
  • Browser/version: Version 54.0.2840.71 m
  • uBlock Origin version: 1.9.16

My Filter List:

uBlock Filters - Experimental
EasyList + Peter Lowe’s Ad server list‎
All Privacy
All Malware Domains
All Social

@gorhill
Copy link
Owner

gorhill commented Nov 12, 2016

No popups:

Caveat for Chromium-based browsers: Due to Chromium API limitations, it's not always possible for uBlock to determine for sure whether a new tab being opened is that of a popup, or is the result of a legitimate click on a link by the user. So if the no-popups switch is in use, you may not be able to open a link in a new tab through the context menu.

@gorhill gorhill closed this as completed Nov 12, 2016
@shmerl
Copy link

shmerl commented Sep 27, 2017

This can be an issue with Firefox 57 now too, since it's using Web extensions. So it's not only Chromium-based browsers anymore.

@gorhill
Copy link
Owner

gorhill commented Sep 27, 2017

See #2919.

@shmerl
Copy link

shmerl commented Sep 27, 2017

Ah, great. Thanks for the pointer!

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

No branches or pull requests

3 participants