APB blocking complete CSS files?

Mav · Post by **Mav** » Sat May 12, 2007 7:35 pm

I'm using easylist(USA), and apparently it blocks the css of this site: http://www.tamesideadvertiser.co.uk/

I can't find the rule that blocks the css. Why is there no way to see which rules are in effect on the current page? Like making the lines red?

edit: hmpfrz.. just found the rule.. it's "sidead", which is in the domain name.... I think it's pretty stupid that it can match part of the domain like that. :/

rick752 · Post by **rick752** » Sat May 12, 2007 8:00 pm

EVERYTHING is blocked there.
I just removed that from the EasyList ... works ok now.

I think it's pretty stupid that it can match part of the domain like that. :/

Besides "sidead", be lucky that "advert", "advertise", or "advertiser" aren't in the list too (at least not in MY list)

That domain name is just asking for trouble

chewey · Post by **chewey** » Sat May 12, 2007 9:04 pm

rick752 wrote:That domain name is just asking for trouble

It indeed is, I just clicked the link expecting a blank page.

However, it displayed well with my list, the -er on advertise saved me.

That's out of sheer luck though

Mav · Post by **Mav** » Sun May 13, 2007 2:20 am

Hehe. Blaming the site instead of the blocking rules or APB. Same happened with the sIFR thread here. :/ As webdesigner and a user of ABP I'm torn between two sides. I love the ad blocking part, but hate the fact that it is tearing up website layout for no good reason.

That "sidead" rule does have a count of 800+ for me, so it's doing a good job of blocking some ads. It would be wrong to remove it from the list I think. It's not the rule that is the problem imho, it's ABP that can block complete css files that is the problem.
So, why is ABP even capable blocking css files? It should only block certain parts of the page, the ads themselves. I can understand blocking js-scripts and the hiding of certain elements with 'element hiding helper', I use that too. But I don't think it should be able to block complete css files like in this case is happening.

rick752 · Post by **rick752** » Sun May 13, 2007 3:59 am

The css thing could easily be fixed in the filters so none would be blocked ... just allow them all with:

Code: Select all

@@$stylesheet

... but there have been instances where ads have initiated through (or ad parameters defined with) css files.

But it is simple to allow all css files if you want that.

chewey · Post by **chewey** » Sun May 13, 2007 4:25 am

Mav wrote:Hehe. Blaming the site instead of the blocking rules or APB.

Sure, where would be the fun otherwise?

Seriously: You may not have noticed, but all the filter list authors on this
thread (that's rick and me) were ready to treat that as a false positive,
and rick indeed adjusted his filter rules (I got lucky and didn't need to).

We're not that all-powerful.

Yet.

rick752 · Post by **rick752** » Sun May 13, 2007 4:38 am

btw Mav:

This wasn't just a false-positive for the css file .... it blocked EVERYTHING that was part of that domain.