Opened 5 years ago

Closed 12 months ago

#3422 closed defect (rejected)

ABP for Chrome doesn't block ads in a frame on a page created by another extension

Reported by: Lain_13 Assignee:
Priority: Unknown Milestone:
Module: Platform Keywords: closed-in-favor-of-gitlab
Cc: kzar, sebastian, mapx, greiner Blocked By:
Blocking: Platform: Chrome
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):



ABP 1.9.4 for Chrome, Tabsbook 1.35 ( ), Google Chrome 48.0.2564.41 beta-m (64-bit).

How to reproduce

  1. Install Tabsbook extension.
  2. Open a new tab.
  3. Open a page inspector and go to the Network tab.
  4. Refresh content of the page.
  5. Open a new tab with URL: (same as in a frame on the extension's page)
  6. Repeat steps 3 and 4 there.

Observed behaviour

On step 4 there (likely) will be no failed resource downloads.
In particular script will be loaded.
On step 6 the same script will be blocked. If not - add filter "/ads.php?" into ABP.

Expected behaviour

Script "" and a few other will be blocked.

Change History (4)

comment:1 Changed 5 years ago by mapx

  • Cc kzar sebastian mapx added

comment:2 Changed 5 years ago by greiner

  • Cc greiner added

comment:3 Changed 4 years ago by kzar

  • Component changed from Unknown to Platform

IIRC it's not possible to block these requests with the Chrome extension API. I thought there was another issue about that on our issue tracker but I can't find it, can you remember Sebastian?

comment:4 Changed 12 months ago by sebastian

  • Keywords closed-in-favor-of-gitlab added
  • Resolution set to rejected
  • Status changed from new to closed

Sorry, but we switched to GitLab. If this issue is still relevant, please file it again in the new issue tracker.

Note: See TracTickets for help on using tickets.