Let's say you add this element hiding rule:
##*[alt*=text]
This should hide any element with an alt attribute that contains "text" in it. However, it seems that the filter is case sensitive. It will not block "Text" or any other case.
I have not tested to see if it is just certain pages or not. Is there a way to make it case-insensitive all the time?
Can't get a filter to be case insensitive
Re: Can't get a filter to be case insensitive
Its not an issue with adblock, its CSS that is case sensitive.
Re: Can't get a filter to be case insensitive
I thought it might be cause.fanboy wrote:Its not an issue with adblock, its CSS that is case sensitive.

... Is there any alternative that would not be case sensitive? Would switching to the old non-css style work?
Is there any technical way to make ABP support case-insensitivity?
As you know, the case sensitivity makes it difficult to write effective filters.

Re: Can't get a filter to be case insensitive
BTW, thanks for confirming that part about the CSS though. 

Re: Can't get a filter to be case insensitive
I believe that the old style merely translated the filter into CSS, which was inefficient.Kevin_Ar18 wrote:Would switching to the old non-css style work?
The only way that I can think of is to simultaneously create all possible rules (e.g. ###advert would result in #advert, #Advert, ###ADvert, ###ADVert and all the other possible permutations of lower and upper case letters). I don't really think that this would be an ideal solution for performance reasons and the lack of control that subscription authors would have - an exception for a rule would apply to all variations of the id of the element.Kevin_Ar18 wrote:Is there any technical way to make ABP support case-insensitivity?
Re: Can't get a filter to be case insensitive
Thanks. That's what I had in mind too.Michael wrote:The only way that I can think of is to simultaneously create all possible rules (e.g. ###advert would result in #advert, #Advert, ###ADvert, ###ADVert and all the other possible permutations of lower and upper case letters).
Could it not be made into an option instead of the default or done via something in regex... or some other way perhaps that would make it easy? In other words, it can be turned on and off. In this way, the option to use case-insensitivity would give greater power to writing filters.Michael wrote:the lack of control that subscription authors would have - an exception for a rule would apply to all variations of the id of the element.
Still, that doesn't solve the problem of "how" to make it work.
