Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/alexperezortuno/ce-blocker/llms.txt

Use this file to discover all available pages before exploring further.

The Dashboard is the main view of Traffic Blocker. It lists every URL blocking rule you have configured and gives you full control over adding new rules, editing existing ones, changing their priority order, enabling or disabling the blocker, and clearing everything at once. All changes are reflected in Chrome’s declarativeNetRequest dynamic rules in real time.

Adding a Rule

1

Enter an initiator domain (optional)

Type a domain in the first input field (e.g. tracker.ads.com) to restrict the rule to requests that originate from that domain. Leave this field blank to apply the rule to all origins — the extension will automatically set excludedInitiatorDomains: ['localhost'] so local development traffic is never blocked.
2

Enter a URL filter pattern

Type a URL filter pattern in the second input field, for example *://*.example.com/*. The pattern supports wildcard matching consistent with the Chrome declarativeNetRequest specification.
3

Submit the rule

Press Enter or click the Add rule button. If the exact urlFilter value already exists in your rule list, a warning toast appears and the duplicate is not added.
Rules are stored in chrome.storage.local under the blocker key. They persist across browser restarts.

Enabling / Disabling Blocking

The toggle switch in the top-right corner of the Dashboard controls whether blocking is active. When the switch shows ON, all stored rules are registered as dynamic rules in declarativeNetRequest and network requests are actively blocked. When you switch it OFF, every dynamic rule is removed from Chrome — but your stored rules remain intact in chrome.storage.local — so re-enabling the blocker immediately restores them without any data loss.

Searching Rules

A search bar appears automatically below the navigation icons when you have more than one rule (i.e., at least 2). Typing in the search bar filters the rule list in real time, matching against both the urlFilter pattern and any initiatorDomains associated with each rule. Clearing the search field restores the full list.

Editing a Rule

Click any rule row to open the Edit Rule modal. The modal exposes three fields:
FieldRequiredNotes
URL FilterYesThe URL pattern to block.
Initiator DomainsNoComma-separated list of domains that trigger the rule.
Excluded DomainsNoComma-separated list of domains exempted from this rule.
Click Save to apply your changes. The rule is updated immediately and Chrome’s dynamic rules are synchronized.
The edit modal has two action buttons: Save (blue, confirms changes) and Delete (red, the modal’s cancel-side button). Clicking Delete removes the rule entirely and is equivalent to clicking the X button on the rule row directly.

Reordering Rules

Each rule row has an up chevron (▲) and a down chevron (▽) button on the right side. Clicking these moves the rule one position up or down in the list. The buttons are disabled at the top or bottom of the list respectively. Rule order corresponds directly to matching priority — the first matching rule wins when a network request matches multiple rules.

Deleting a Rule

Click the X button on any rule row to delete it. A toast notification appears for 5 seconds with an Undo button. Clicking Undo within that window restores the rule to its original position in the list. After 5 seconds the deletion becomes permanent.

Clear All Rules

The trash icon in the Dashboard header removes every rule and disables the blocker in a single action. Because this is irreversible, a confirmation dialog appears first showing the exact number of rules that will be deleted. The blocker’s isEnabled state is set to false and chrome.storage.local is updated accordingly.

Build docs developers (and LLMs) love