306372 - [adblocking] Main ad on appleturns.com not blocked with new adblocking file

Status: VERIFIED WONTFIX

(Camino Graveyard :: General, defect)

Description

[Samuel Sidler (old account; do not CC)]

As mentioned in comment 2 of bug 306332, the main ad on appleturns.com is no
longer blocked by Camino's built-in adblocking.

Comment 1

[Samuel Sidler (old account; do not CC)]

I carried this over from bug 306332, but I don't see it.

Markus, can you tell us exactly which ad you see and possibly take a screenshot
of it and attach it to this bug? Thanks...

Comment 2

[Markus Haenchen]

Attachment: Screenshot of ad blocker in 29 Aug nightly build

Comment 3

[Markus Haenchen]

Attachment: Second screenshot: 0.9a2

Comment 4

[Markus Haenchen]

First screenshot: nightly build with "A whole lot more" ad on www.appleturns.com
(and the download link on Adobe's page visible); ad block on as visible on
www.macosxhints.com page.

Second screenshot: latest alpha build (0.9a2) with ad on www.appleturns.com
blocked (but download link on Adobe's page also blocked). First ad in the right
column on www.macosxhints.com blocked more space efficiently than in the nigthly
build. 

Comment 5

[Markus Haenchen]

Maybe this obvious, but when I run the second alpha build (0.9a2), switch on ad
blocking and restart it, a userContent.css file is created. If I now quit the
second alpha build and start the latest nightly build (0.9a2+, 29Aug) it reverts
back to the behaviour of the second alpha build (deleting the file and your back
to 'standard' 29 Aug nightly build behaviour).

Comment 6

[Simon Fraser [no longer active]]

If you flip between nightly builds and the 0.9a2 build, the userContent.css
created by the 0.9a2 build will confuse the results here. Before testing
anything, please delete the userContent.css file in your profile/chrome dir.

Comment 7

[Simon Fraser [no longer active]]

http://www.appleturns.com cycles through several ads, and there's not simple way
to block them all. Some of the images are hosted on the appleturns.com server,
so are not easily blockable.

In developing the adblocking CSS, I've tried to catch ads by the big commercial
ad servers, and not to overly block the "little guys" (who host selected ad
images on their own servers). This is why, for example, you'll still see the odd
ad image on http://www.macintouch.com/. In addition, it's very difficult to
block these one-off images without getting too mnay false hits.

So I'm WONTFIXING this.