siphyo / adblock-plus-japanese-filter

Automatically exported from code.google.com/p/adblock-plus-japanese-filter
0 stars 0 forks source link

JavaScript Error on Intel download pages #43

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
不具合報告の URL(URL of your Issue Report)
(Firefox で Adblock Plus アイコンを右クリックし「この page
での不具合を報告」。送信後に表示される URL。例:
https://reports.adblockplus.org/...)
-https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=17570

不具合の症状(Describe the problem.)
-Try to download "Remove_Intel_Menu.reg", but not successful. Also in Log Panel 
there is "GET 
https://tags.tiqcdn.com/utag/intel/profile-downloadcenter/prod/utag.js 
net::ERR_BLOCKED_BY_CLIENT"

ABP Japanese Filters が不具合の原因と考えられる根拠(Why do
you think ABP Japanese
Filters are responsible for the problem?)
-||tiqcdn.com^

利用/購読しているすべてのフィルタ(Which
filter/subscription do you use?)
-abp_jp.txt

その不具合はいつから発生し始めたのか(When did the
problem start to occur?)
-

以前の正常動作はどういったものだったのか(Describe
normal operation before the problem.)
-

画面上の不具合発生場所(Where in the monitor does the problem
occur?)
-

スクリーンショット URL(Screenshot URL)
-

エラーコンソールに JavaScript
等のエラーがあればその内容(Copy JavaScript errors from Error
Console)
- GET https://tags.tiqcdn.com/utag/intel/profile-downloadcenter/prod/utag.js 
net::ERR_BLOCKED_BY_CLIENT

問題の再現手順(What steps will reproduce the problem?)
1.
2.
3.

問題再現のためのサンプル URL(URL examples to reproduce the
problem.)
- Open the page
- Try to doanload the .reg file

期待される正常動作(What is the expected output?)
- Download successfully

利用環境でのバージョン(What version of the product are you
using? On what
operating system?)
-アドオン(Add-on):uBlock
-ブラウザ(Browser):Chrome 38.0.2125.122
-JavaScript:
-OS:Windows 8.1

追加情報(Please provide any additional information.)
-
-

Original issue reported on code.google.com by xupa...@gmail.com on 12 Nov 2014 at 3:50

GoogleCodeExporter commented 8 years ago
Thank you for reporting.

I'm shocked to find that functions called in first-party JavaScript are defined 
in the third-party script(utag.js).

That is called "Tight-Coupling", worse design of software.

Anyway I found a way to mitigate it by blocking the root JavaScript :-p

Update your subscription to confirm the fix.

Original comment by k2ja...@gmail.com on 15 Nov 2014 at 3:21