Provide way of handling unsupported DNR rules
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- api
Research direction
Start by reading the issue and linked TPAC discussion in pull request #448, focusing on static DNR rulesets and the reported Chrome and Firefox behavior. Determine Safari's behavior and compare the suggested getFailedRules() and isRuleSupported() approaches; the work is done when a compatible handling design is agreed.
Written by the indexing model from the issue text.
Description
In our TPAC meeting on Tuesday (https://github.com/w3c/webextensions/pull/448), it was brought up that there is currently no easy way to support new types of DNR rules while being compatible with browsers that do not recognise them. This is primarily an issue for static rulesets.
It was mentioned that Chrome has a hard-error when any DNR rule in a ruleset fails to load, and Firefox has a soft failure where the rules are ignored. The behaviour in Safari needs to be determined.
There were suggestions to add API methods like getFailedRules() or isRuleSupported().
- Dominant language
- Bikeshed
- Stars
- 711
- Forks
- 95
- Avg merge
- 10d 11h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from w3c/webextensions
-
admin task topic: ai tpac 2026
Difficulty 5/5 Over a week Newbie friendliness 35/100
w3c/webextensions#1094 · 1 comment · 1 reaction ·
-
implemented: firefox implemented: safari needs-triage: chrome topic: menus
Difficulty 5/5 Over a week Newbie friendliness 35/100
w3c/webextensions#1090 · 1 comment ·
-
needs-triage: chrome needs-triage: firefox needs-triage: safari proposal topic: menus topic: permissions
Difficulty 5/5 Over a week Newbie friendliness 45/100
w3c/webextensions#1089 · 2 comments ·
-
implemented: safari needs-triage: chrome needs-triage: firefox topic: menus
Difficulty 5/5 Over a week Newbie friendliness 35/100
w3c/webextensions#1088 · 1 comment ·
-
inconsistency needs-triage: chrome needs-triage: firefox needs-triage: safari topic: permissions topic: storage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
w3c/webextensions#1087 · 1 reaction ·
All issues in w3c/webextensions
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·