القواعد الديناميكية وتصحيح أخطاء declarativeNetRequest

declarativeNetRequest supports two rule kinds. Static rules ship in JSON files in the manifest. Dynamic rules are added at runtime and persist across restarts.

Dynamic rules let your extension adapt to user choices without an update.

You need the declarativeNetRequest permission. For dynamic rules at runtime, that is all you require.

Each rule has an id, a priority, an action, and a condition. The condition decides which requests match.

Use updateDynamicRules to add rules. Pass them in the addRules array.

The same call removes rules by listing their IDs in removeRuleIds. Adds and removes can happen together.

Every dynamic rule needs a unique numeric id. Reusing an existing ID without removing it first causes an error.

When multiple rules match, priority decides which wins. Higher priority takes precedence; allow rules can override block rules at the same level.

If you want rules that vanish when the browser closes, use updateSessionRules instead. They never persist to disk.

For debugging, enable the feedback permission and listen to onRuleMatchedDebug to see which rule fired for each request.

Call getDynamicRules to list everything currently active. This is essential when a rule misbehaves and you need to confirm what is installed.

There is a cap on the number of dynamic rules. Audit and remove stale rules instead of piling on, and group conditions where possible to stay efficient.

Test your dynamic rules knowledge.

You learned dynamic request rules:

• Add and remove with updateDynamicRules
• Keep IDs unique and use priority for conflicts
• Use session rules for temporary state
• Debug with onRuleMatchedDebug and getDynamicRules
• Respect rule count limits

Runtime rules let your extension adapt without shipping an update.