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 Statistics view gives you a running total of every network request that Traffic Blocker has intercepted and blocked since the extension was installed (or since the last reset). To open it, click the bar chart icon on the Dashboard. The view displays a large numeric counter alongside a reset button in the top-right corner.

Blocked Traffic Counter

The counter shown in the Statistics view reflects the cumulative number of blocked requests. The background service worker listens for chrome.webRequest.onErrorOccurred events and increments the stored counter each time it sees an error of net::ERR_BLOCKED_BY_CLIENT — the error Chrome reports when declarativeNetRequest blocks a request. The Statistics view reads this value from chrome.storage.local and auto-refreshes every 5 seconds, so the number stays current without needing to reopen the popup. The refresh is handled by a setInterval timer that is started when the view mounts and cleared when it unmounts.
The counter reflects requests blocked since the extension was first installed (or since the last reset). It does not distinguish between rule categories.

Resetting the Counter

Click the rotate icon button in the top-right corner of the Statistics view to reset the counter. A confirmation dialog appears:
  • Click Reset to proceed. The extension sets settings.blocked to 0 in chrome.storage.local, the on-screen counter drops to 0 immediately, and a success toast confirms the reset.
  • Click Cancel to leave the counter unchanged.

Storage

The blocked request count is persisted to chrome.storage.local under the settings key:
{
  "settings": {
    "blocked": 4217
  }
}
Because the value lives in chrome.storage.local, it survives the popup being closed and reopened, Chrome restarts, and extension updates. The counter only returns to zero when you explicitly reset it via the Statistics view.

Build docs developers (and LLMs) love