I'm using Adblock Plus for Chrome, and I'm having trouble adding an element exception.
Blocked element: yahoo.com##.ft
I've tried:
@@yahoo.com##.ft
yahoo.com@@.ft
@@.ft
Nothing is working...
Exception help
Re: Exception help
add
to your custom filters
Code: Select all
~yahoo.com##.ft
Re: Exception help
Unfortunately neither of those worked.
The blocked element (yahoo.com##.ft) comes from the Adversity block list. I'm not sure if that makes a difference. Do the filter lists get processed before or after the custom filters?
The blocked element (yahoo.com##.ft) comes from the Adversity block list. I'm not sure if that makes a difference. Do the filter lists get processed before or after the custom filters?
Re: Exception help
This filter has now been removed.
________________________________
ABP Subscriptions
ABP Development Builds
Submit an issue report with Adblock Plus
ABP Subscriptions
ABP Development Builds
Submit an issue report with Adblock Plus
Re: Exception help
There isn't much of an "element-hiding exception" functionality; the closest possible thing would be an exception rule with the $elemhide option, like @@||yahoo.com^$elemhide, but that would disable all element-hiding on yahoo.com and all subdomains.
Also, I don't think the order in which filters are processed matters: Rather, all rules of a certain type have the same precedence.
As an example, if one element-hiding filter was ~yahoo.com##.ft (meaning "hide all elements with class 'ft' on any domain that is not yahoo.com or any subdomain") and another was yahoo.com##.ft (meaning "hide all elements with class 'ft' on yahoo.com or any subdomain"), then together they would mean "hide all elements with class 'ft' on any domain that is not yahoo.com or any subdomain, and hide all elements with class 'ft' on yahoo.com or any subdomain," which is equivalent to saying "hide all elements with class 'ft'" (that is, to ##.ft), and this is independent of the order of appearance or of whether any filter appeared in a subscription or in the custom filters, basically because the logical "AND" and "OR" do not depend on order; in particular, ~yahoo.com##.ft does not mean "prevent elements with class 'ft' from being hidden on yahoo.com or any subdomain," that is, ~ does not specify a whitelist, but rather a "negative domain" ("cover all domains but this" rather than "protect this domain").
Also, I don't think the order in which filters are processed matters: Rather, all rules of a certain type have the same precedence.
As an example, if one element-hiding filter was ~yahoo.com##.ft (meaning "hide all elements with class 'ft' on any domain that is not yahoo.com or any subdomain") and another was yahoo.com##.ft (meaning "hide all elements with class 'ft' on yahoo.com or any subdomain"), then together they would mean "hide all elements with class 'ft' on any domain that is not yahoo.com or any subdomain, and hide all elements with class 'ft' on yahoo.com or any subdomain," which is equivalent to saying "hide all elements with class 'ft'" (that is, to ##.ft), and this is independent of the order of appearance or of whether any filter appeared in a subscription or in the custom filters, basically because the logical "AND" and "OR" do not depend on order; in particular, ~yahoo.com##.ft does not mean "prevent elements with class 'ft' from being hidden on yahoo.com or any subdomain," that is, ~ does not specify a whitelist, but rather a "negative domain" ("cover all domains but this" rather than "protect this domain").
There's a buzzin' in my brain I really can't explain; I think about it before they make me go to bed.