ray-lothian

So since the incognito context is separate, the extension should not allow altering the preferences in the context, which is fixed now. Thanks for the report. Also, a new bug...

Do you have the "0.4.8" release? https://microsoftedge.microsoft.com/addons/detail/block-site/deiilejafkhhgekckholkdhfhopcnmeb

What is your browser?

Right but there are some cases where an external library may need to be verified later. For instance, in my case, I've just started using this library in my browser...

There is no bulletproof method to hide browser type. For instance, a website can detect your browser type with a simple CSS matching such as: ```js CSS.supports('-moz-appearance', 'none') ``` This...

I just tried on "118.0b9 (64-bit)" and pausing works for me. Do you see any error in the console? about:debugging#/runtime/this-firefox

@xverges, can you try the following rules on the console tab? release blocking ```js await chrome.declarativeNetRequest.updateDynamicRules({ removeRuleIds: [999], addRules: [{ 'id': 999, 'priority': 5, 'action': { 'type': 'allow' }, 'condition':...

Thanks @xverges This looks like a core API error. I might need to switch back to the polyfill until it is fixed. The problem is I am not able to...

@xverges same error for `browser`? ```js await browser.declarativeNetRequest.updateDynamicRules({ removeRuleIds: [999], addRules: [] }); ```

This extension uses "declarativeNetRequest" rules to block or redirect pages. Since there isn't an observer in place to monitor requests, there's no means of tracking the sequence of redirects either.