Omnibus ad-blocking bug for May 2008

RESOLVED FIXED

Status

RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: alqahira, Assigned: alqahira)

Tracking

({fixed1.8.1.17})

unspecified
PowerPC
macOS
fixed1.8.1.17
Dependency tree / graph
Bug Flags:
camino1.6.2 +

Details

Attachments

(1 attachment)

Another month, another set of ads to block....
http://www.excite.co.jp/world/ 
(Japanese-English/Korean/Chinese translation service)
they've now added an ad to the right of the input textarea.

a[href*="adimp.excite.co.jp"] {display:none !important;}

That also blocks a bunch of text only ads towards the bottom of the page.
Lots of ads on

http://www.stratfordbeaconherald.com/ArticleDisplay.aspx?e=1056576&auth=Laura+Cudworth%2C+STAFF+REPORTER

While the images themselves seem to be living in a fairly innocuous place, they're all linked to kestrel.ospreymedialp.com , so maybe we can use that somehow.
(In reply to comment #1)
> a[href*="adimp.excite.co.jp"] {display:none !important;}
> 
> That also blocks a bunch of text only ads towards the bottom of the page.

I think I'd rather use 

a:link[href*="adimp.excite.co.jp"] img
table.ad_table

than blocking the text links the other way.
Created attachment 324241 [details] [diff] [review]
May omnibus ad-blocking

This fixes these sites plus all the dependent bugs.  I generalized the existing netavenir rule because we discovered in bug 435800 that they serve from .com and .fr.
Assignee: nobody → alqahira
Status: NEW → ASSIGNED
Attachment #324241 - Flags: superreview?(sfraser_bugs)
Oopsie, I realise now that I forgot to link to bug 436766, which has (had ?, because I don't see it, right now).

Updated

11 years ago
Attachment #324241 - Flags: superreview?(sfraser_bugs) → superreview+
(In reply to comment #5)
> Oopsie, I realise now that I forgot to link to bug 436766, which has (had ?,
> because I don't see it, right now).

Let's get that next month; I want to discuss those first ;)

Landed on the trunk.  Nominating for 1.6.2, but it may not have enough baking time before we spin.
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Flags: camino1.6.2?
Resolution: --- → FIXED
This has baked on the trunk for two weeks now with no complaints, so I'm going to land it for 1.6.2 (in part so ad-blocking doesn't get so far behind on the branch).
Flags: camino1.6.2? → camino1.6.2+
Landed on 1_8 in advance of 1.6.2.
Keywords: fixed1.8.1.16
You need to log in before you can comment on or make changes to this bug.