Added a feature that hides the “Block this site” entry from the right-click context menu. This is useful when you want the extension to stay active without showing its blocking action in the browser menu.
Added a feature that blocks access to the Chrome Extensions page. When enabled, trying to open chrome://extensions redirects the user to a built-in block page instead of letting the Extensions page load. This helps prevent access to browser extension settings in restricted or focused browsing setups.
sub_frame elements (iframes) are blocked, ensuring other resources from the same domain aren't mistakenly blocked
Improved detection of website navigation on Single Page Applications (SPAs) by using webNavigation. The extension can now instantly block content when users navigate using browser history, instead of waiting 5+ seconds for periodic checks.
Removed iframe option setting checking from Advanced Rules conditions
Advanced Rules provide users with precise, granular control over content blocking. Instead of blocking entire websites or categories, users can create custom rules that target specific URLs, API endpoints, or resource types. This enables sophisticated blocking strategies tailored to individual needs.
Fixed styles issue with Rules table
declarativeNetRequest
Added excludedInitiatorDomains to the network blocking rule to prevent blocking resources that are loaded from the same domain.
This ensures resources on the same domain (like scripts or styles) aren't mistakenly blocked
Fixed a bug where White List Mode would incorrectly block frames, stylesheets, and scripts from whitelisted domains when the 'Block site frames in other sites' option was enabled.
script, xmlhttprequest, and stylesheet in declarativeNetRequest rules.chrome.storage.sync to chrome.storage.local for improved performance.