Advanced reference · Advanced

Browser differences and protection limits

Understand why the same Shield setup can expose different permissions, counts and limits across browsers.

Overview

Shield shares its rule parsing and much of its interface between Chromium browsers and Firefox. The browser still controls which APIs, permissions and rule capacities an extension can use. Identical source settings do not make every diagnostic, count or advanced feature identical.

Use the browser’s extension settings to check that Shield is enabled and allowed to access the websites where you want protection. Permission to run on one site is not the same as access to all sites, and an ordinary website cannot grant extension permissions for you.

Browser behavior

Scroll sideways to read the whole table.

Area Chrome and other supported Chromium builds Firefox package
Request blocking Browser-managed declarative rules. The browser admits rules within its limits. Shield evaluates and cancels eligible requests through Firefox’s request API.
Production counts Blocking counts are hidden because release builds lack the development-only matching signal. Local aggregate blocked-request counts can be shown, including Blocked today.
Built-in page fixes Packaged helpers controlled by Page Fixes and protection state. Packaged helpers are included and controlled by the corresponding switches.
Custom and added-source page fixes The 1.0.2 Chrome package, also used by Edge, omits that scriptlet tier. Granting a permission does not add it. The 1.0.2 package omits that scriptlet tier. Granting a permission does not add it.
Capacity reporting Request rules can be accepted as syntax but left inactive when browser capacity is exceeded. Uses its own engine and resource bounds; Chromium capacity numbers do not describe it.

Read the exact message on your installed build. Development installations can expose capabilities that store builds do not expose, especially counting and diagnostics.

Permission limits

Browser-managed pages, extension stores and some protected documents restrict what extensions can do. A normal webpage with similar-looking content can behave differently. A private browsing window also depends on the browser’s separate permission for the extension.

Ad hiding and page fixes require access to the page. Frames containing content from a different website have their own origin and access boundaries. A fix affecting the top-level page may leave a cross-origin embed unchanged. Browser installation permission does not establish that every embedded context was modified.

Shield AdBlock 1.0.2 packages omit custom and added-source page fixes on Chrome, Edge and Firefox. Turning on Advanced Settings in Shield reveals advanced controls only. Avoid turning on unrelated browser developer settings as a general troubleshooting step.

Filtering limits

A downloaded list can contain rules Shield intentionally skips because it cannot honor them exactly. Browser capacity may then limit otherwise accepted request rules. The syntax references describe the verified subset rather than claiming full upstream compatibility.

No blocker can promise every ad will be removed without breaking websites. Ads and useful content can share the same delivery paths; page changes, first-party media and account-specific experiments can affect results. A saved rule, enabled source or successful setup is not proof of a visible outcome on one visit.

What to check

After changing permissions or settings, reload the affected page and repeat the same small check. If a browser reports a limit, inspect protection status before adding more sources. If Shield is absent or inactive on ordinary websites, follow Shield appears inactive.

Still need help? Contact support