Could you please move this request into "Moderated forums / Future development" for further discussion?
As I understand feature requests is supposed to be moved there if they are worthy to look at them at least a little bit closer.
Lain_13 wrote:here is no way to block their advertisements by generic part in the request (instead of filename they have alphanumerical hash-like string right after the domain name with current sitename somewhere in the middle). There are no way to hide their ads by object names because they always random
lewisje wrote:Maybe there could be a new syntax made for "XPath-based element-hiding rules" (maybe starting with ##$ instead of ##)...... (but Firefox has supported XPath since 1.5) or its uselessness on HTML (rather than XHTML) documents (but I also read that the XPath API allows traversal of HTML documents not explicitly serialized as XML).
guest1337 wrote:Lool this freaking works!!!11oneeleven
- Code: Select all
site.net##html > body > table > tbody > tr > td:nth-of-type(2)
Actually, i don't care if it's XPath syntax or this CSS syntax as long as they mention the same. But you should freaking definitely add this feature to element hiding helper! Since attributes combined with object path make much less fake positives so i could now commit my rules if i want! Tools i used (Dom Inspector + XPather + manual convertion from XPath to CSS) and adding the rule after clicking through 5 settings windows are not very handily.
So, is it possible to implement such a thing? I think it is not complicated and could be implemented as an extension to the existing popup functionality without adding new $flag.
Lain_13 wrote:> There are no way to hide their ads by object names because they always random
Here I remembered different guys not related to this case. They not only randomized IDs of objects but randomized internal structure of their ads too. So, XPath doesn't work for them.
Users browsing this forum: No registered users and 7 guests