Browser guide / Chrome
Start with a compatible extension and its documented filters. Then test the rules that matter to your everyday browsing.
Chrome’s declarativeNetRequest API supports rules that let the browser act on matching requests. An extension using that API manages supported rules within the browser’s capabilities. A text subscription may need processing before it can serve that role.
Do not judge compatibility from a product name alone. Read the extension’s documentation for supported syntax, optional subscriptions, and behaviors that depend on browser version. Avoid relying on old installation instructions without checking their current context.
Confirm that the intended extension is enabled and permitted for the site being tested. Review its filter settings and any site-specific exceptions. A rule cannot explain a result if the tool is inactive in that browsing context.
Record the Chrome version, extension version, and relevant list settings. This simple baseline makes comparisons useful and gives a maintainer enough context to investigate a reproducible problem.
If a page stops working after adding a subscription, disable that new subscription and repeat the same task. If the failure remains, examine other recent settings and the site’s own behavior. Do not assume every error on a filtered page was caused by the blocker.
Where the tool exposes matched-rule information, use it to identify a specific dependency before adding an exception. Keep exceptions narrow and review them when the underlying site or rule changes.
Include login, playback, navigation, and consent choices in your test set. Compare the same tasks rather than relying only on the number of ads you can see. For request-level inspection, distinguish an observed browser request from a claim about every measurement made by a site.
Read the complete Chrome filtering guide, then compare plugin permissions and list support or the domain-level alternative.
A compatible extension or other supported integration is needed to interpret and apply a subscription. Follow that tool’s current documentation.
The extension engine, supported APIs, permissions, and format support may differ. Compare the actual configurations rather than assuming equivalence.
From Ad Block List Lab
Understand how Chrome blockers apply rules, evaluate permission requests, and diagnose everyday problems with a repeatable workflow that keeps browser settings, list changes, and site behavior in context.
6 min readAn extension supplies the engine. Filter lists supply the matching rules. Understand both before changing your browser setup.
Explore this topicA hostname is only part of a web request. Understand what domain-level filtering can see before expecting page-level precision.
Explore this topic