Opened on 12/16/2015 at 11:35:01 AM
Closed on 08/29/2019 at 05:48:47 PM
#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): |
Description
Environment
ABP 1.9.4 for Chrome, Tabsbook 1.35 ( https://chrome.google.com/webstore/detail/tabsbook/mchbdiagjpehpcfldofefibcblcjkomd/related ), Google Chrome 48.0.2564.41 beta-m (64-bit).
How to reproduce
- Install Tabsbook extension.
- Open a new tab.
- Open a page inspector and go to the Network tab.
- Refresh content of the page.
- Open a new tab with URL: http://www.tabsbook.ru/express-panel/?utm_medium=ext&utm_source=chrome-ext (same as in a frame on the extension's page)
- Repeat steps 3 and 4 there.
Observed behaviour
On step 4 there (likely) will be no failed resource downloads.
In particular script http://www.tabsbook.ru/___ajax___/no_upd_sess/ads.php?r=... will be loaded.
On step 6 the same script will be blocked. If not - add filter "/ads.php?" into ABP.
Expected behaviour
Script "http://www.tabsbook.ru/___ajax___/no_upd_sess/ads.php?r=..." and a few other will be blocked.
Attachments (0)
Change History (4)
comment:1 Changed on 12/16/2015 at 01:10:02 PM by mapx
- Cc kzar sebastian mapx added
comment:2 Changed on 12/18/2015 at 02:54:18 PM by greiner
- Cc greiner added
comment:3 Changed on 07/26/2016 at 09:33:24 AM by kzar
- Component changed from Unknown to Platform
comment:4 Changed on 08/29/2019 at 05:48:47 PM 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.
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?