Back to "Dynamic-filtering"

First: Whitelist directives override both dynamic filtering and static filtering. Whitelist directives appear in the Whitelist pane in the dashboard, and they are used to completely disable filtering. The big blue power button in the popup UI is used to easily whitelist the current site/page.

Dynamic allow/block rules override static filtering rules.

• Use allow to force requests to be allowed regardless of whether they would normally be blocked by static filtering.
  • Useful to fix sites broken by false positives in EasyList, EasyPrivacy (or any other static filter lists).
• Use block to force requests to be blocked regardless of whether they would normally be allowed by static filtering.
  • Useful to block with 100% certainty, to bypass exception filters with which you may disagree in EasyList, EasyPrivacy (or any other static filter lists).

There is a precedence logic for dynamic filtering cells:

Local rules override global rules.

• Local setting for example.com override global setting for example.com.

The party-specific cells override the type-specific cells.

• 3rd-party override images
• example.com override images

The more specific the party, the higher the precedence.

• example.com overrides 1rd-party scripts
• www.example.com overrides example.com

Party-specific and type-specific cells override party-specific cells:

• 3rd-party frames overrides 3rd-party

All cells override the all cells. The local all cell overrides the global all cell.

The UI is designed in such way that the precedence logic should become obvious with usage.