Writing Adblock Plus filters page

[Gingerbread Man]

1. ​https://adblockplus.org/en/filters#whitelist

Sometimes you will notice that one of your filters that is usually working quite well blocks in some case blocks something that it shouldn't be blocking.
There's a second, redundant "blocks" in there. You could change the above to
Sometimes you will notice that one of your filters that is usually working quite well, in some case blocks something that it shouldn't be blocking.

All mentions of version requirements need to go away, for two reasons. First of all, the versions listed as required are ancient at this point. The highest listed is 1.3.5, which was released on March 25th, 2011. No excuse not to have at least a version that old, so that's just useless information in a document that's already very lengthy and somewhat difficult to understand.
Secondly, the page was originally written back when Adblock Plus was Firefox-specific. The version numbers listed are meaningless for people using other browsers.

2. ​https://adblockplus.org/en/filters#anchors

Remove (requires Adblock Plus 1.1 or higher) from the bottom of this section.

3. ​https://adblockplus.org/en/filters#separators

Remove (requires Adblock Plus 1.1 or higher) from the end of the second paragraph.

4. ​https://adblockplus.org/en/filters#options

Remove (Adblock Plus 1.2 and higher required) from the elemhide example.

Remove the donottrack example. ​Do-Not-Track support was removed back in 2012.

5. ​https://adblockplus.org/en/filters#elemhide_domains

Note: Due to the way how element hiding is implemented, you really can only limit it to full domain names. You cannot use any other part of the address and you cannot use domain as a replacement for domain.example,domain.test.

That's not true. You can limit filters to TLDs, like so:
org##div

Remove (requires Adblock Plus 1.1 or higher) from the beginning of the second paragraph.

Element hiding rules with domain limitation can be used to hide browser's user interface elements as well. This only applies to Firefox, Seamonkey and related browsers. This should be made clear.

6. ​https://adblockplus.org/en/filters#elemhide_css

In general, any CSS selector supported by Firefox can be used for element hiding.
(note that not all selectors are supported by Firefox yet).
Turn these into general statements, rather than Firefox-specific.

7. ​https://adblockplus.org/en/filters#elemhide_simplified

I can't get this to work. If support has been removed, this section should be deleted as well.

[philll]

Thanks for the hint! We are starting to scan/update the whole website contents of adblockplus.org by this/next week step by step. I will definitely let the whole filter page check by a developer.

[juliandoucette]

Thanks for the hint! We are starting to scan/update the whole website contents of adblockplus.org by this/next week step by step. I will definitely let the whole filter page check by a developer.

@philll, @saroyanm, what were the results of this?

[philll]

The page should be rewritten when updating the leftovers that did not move to the help center. Nothing happened here.

[juliandoucette]

@lisa & @arthur can you take a look at this? Does it make sense to at least remove invalid content before we launch the help center?

[lisabielik]

@juliandoucette

I agree with @philll - the page should be rewritten. For now, we aren't adding this document to the help center (the goal is to add it down the road, after ABP and ABB topics are all added).

@arthur, is this document accurate? I think we should update or remove anything that's no longer accurate/relevant.

[arthur]

@juliandoucette @lisabielik
Unfortuntely, my name was mispelled when so I learned about this issue just yesterday.

Agreeing on the suggestion in 1.

I agree on removing the old version requirements but what about newer ones like for $websocket (2.8 in ABP for FF)? If we want to keep it, we probably should also mention Chrome's version requirements.

Agreeing on removing the donottrack paragraph.

Regarding TLDs in element hiding filters: true. What wbout changing

Note: Due to the way how element hiding is implemented, you really can only limit it to full domain names. You cannot use any other part of the address and you cannot use domain as a replacement for domain.example,domain.test. to

Note: You cannot use domain as a replacement for domain.example,domain.test.

And add something like this before it: You can limit element hiding filters to top-level domains as well. Example: com##.sponsor would be applied on any domain ending with .com.

Element hiding rules with domain limitation can be used to hide browser's user interface elements as well. This only applies to Firefox, Seamonkey and related browsers. This should be made clear.

Agree. I assume it applies to all Gecko-based browsers but I'm not entirely sure.

6. ​​https://adblockplus.org/en/filters#elemhide_css

In general, any CSS selector supported by Firefox can be used for element hiding. (note that not all selectors are supported by Firefox yet). Turn these into general statements, rather than Firefox-specific.

Not sure how it looks like today. Are there any selectors that aren't supported by current browsers?

7. ​​https://adblockplus.org/en/filters#elemhide_simplified

I can't get this to work. If support has been removed, this section should be deleted as well.

I cannot confirm this. #div(id=content) does hide the content for me on eyeo.com. So I think this section should stay for now.

[juliandoucette]

@wspee can you please get to the bottom of this and update the ticket description.

[philll]

I still think that the official filter documentation is not something that will live in the help center.

[juliandoucette]

Migrated to ​https://gitlab.com/eyeo/websites/web.adblockplus.org/issues/51