We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
5.0.176
Chrome 131
Windows 11
AdGuard Base filter
No response
Preconditions: The limit is not exceeded by other extensions installed or by enabled filters.
Steps to reproduce:
Developer mode
service worker
Console
await chrome.declarativeNetRequest.updateEnabledRulesets({enableRulesetIds: ['ruleset_3']})
The set of enabled rulesets exceeds the rule count limit. is displayed.
The set of enabled rulesets exceeds the rule count limit.
internal error is displayed
internal error
The issue is related to Chrome issue https://issues.chromium.org/issues/367440970 It have been already fixed and the fix will be available in Chrome 132 version.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Please answer the following questions for yourself before submitting an issue
AdGuard Extension version
5.0.176
Browser version
Chrome 131
OS version
Windows 11
Ad Blocking
AdGuard Base filter
Privacy
No response
Social
No response
Annoyances
No response
Security
No response
Other
No response
Language-specific
No response
What Tracking protection options do you have enabled?
No response
Issue Details
Preconditions:
The limit is not exceeded by other extensions installed or by enabled filters.
Steps to reproduce:
Screenshot 1
Developer mode
service worker
of AdGuard extension and switch toConsole
tabExpected Behavior
The set of enabled rulesets exceeds the rule count limit.
is displayed.Actual Behavior
internal error
is displayedScreenshots
Screenshot 1
Additional Information
The issue is related to Chrome issue https://issues.chromium.org/issues/367440970
It have been already fixed and the fix will be available in Chrome 132 version.
The text was updated successfully, but these errors were encountered: