Instant Whitelisting, Fewer False Hides & Stop Autoplay Rebuilt

Whitelisting Is Instant

Disabling SuperchargePerformance on a site used to mean reloading the page before the change fully took hold. Now it applies the moment you toggle it. Any elements that cosmetic blocking had hidden reappear immediately, with no reload required. The active tab then reloads itself once the network rules are confirmed, so suspension, throttling, and the rest of the engine catch up in the same step.

A whitelist entry now matches both the apex domain and its www version — whitelist example.com and www.example.com is covered too, and vice versa. That match is consistent across suspension, throttling, and preload, so a site you’ve disabled stays disabled no matter which form of its address you land on.

Fewer False Hides

Cosmetic blocking was hiding things it shouldn’t. Several broad class-name matches were pruned, so live sports and finance tickers, a site’s own share and social buttons, and legitimate alert banners now stay visible instead of disappearing along with the ads.

The scroll-unlock fix is also more careful. It restores scrolling on pages that freeze behind a cookie wall or an ad that never loaded — but it now leaves real modals and dialogs alone, including their backdrops and dimmers. A genuine popup you’re meant to interact with keeps its scroll-lock; only orphaned locks with nothing on screen are released.

Stop Autoplay, Rebuilt

Stop Autoplay is rebuilt to be reliable. It now stops videos that start before you’ve engaged the player, but blocks them the same way Chrome’s own autoplay policy does — so each player keeps its own controls and a click plays the video normally. Once you start a video it is never paused again, so there are no pause-and-resume fight loops, even on sites that swap their video element while you watch. It also handles the next-video case on YouTube and pauses social-feed videos as they scroll into view. Three levels in the popup: Off, Allow common video sites, or Block everywhere.

”Disable on This Site” When a Page Looks Broken

Occasionally a blocking feature breaks a page. Finding the whitelist to fix it isn’t obvious, so when a page actually renders broken, the extension now offers a one-click Disable on this site card.

It only appears on genuine breakage. The prompt stays quiet on native PDF viewers, on canvas, iframe, and shadow-DOM web apps, and on a page you simply reloaded — it waits for the page to settle, checks whether it’s truly empty rather than just slow, and has cooldowns so it never nags. Dismiss it once and it stays quiet on that site.

Sites That Look Like Ad Networks Load Again

Visiting a site whose domain merely contains an ad-related word could fail to load with ERR_BLOCKED_BY_CLIENT. Top-level navigation to those domains is no longer blocked, so the page loads normally.

Under the Hood

Two stability fixes:

• Savings banner. The celebration banner that appears when you cross a memory-saved milestone could white-screen the popup. It now renders without crashing.
• Safe-mode cleanup. When a tab that was in safe mode is closed, its temporary rule is now removed. Without this, a recycled tab ID could inherit that rule and have blocking silently disabled on a fresh page.

The safe-mode recovery prompt also no longer pops up on Chrome’s built-in PDF viewer — the check now reads the document’s content type, which is authoritative, so a normally rendered PDF is never mistaken for a broken page.

Cookie Handling & Refreshed Blocklists

The cookie banner auto-rejection engine (DuckDuckGo AutoConsent) is updated, so more cookie walls are dismissed automatically. All blocklists are refreshed across every source — 186,648 rules across three tiers: 100,000 ad and tracker domains (Free), ~64,800 privacy and telemetry (Medium), ~21,800 malware, phishing, and fraud (Pro). This is a freshness refresh, not a size change.