Open Bug 1835020 Opened 1 year ago Updated 1 year ago

Apply Quarantine logic to DNR filters

Categories

(WebExtensions :: Request Handling, defect, P2)

defect

Tracking

(Not tracked)

People

(Reporter: zombie, Unassigned)

References

Details

(Whiteboard: [addons-jira])

From https://phabricator.services.mozilla.com/D178597#5906316.

Splitting out from https://phabricator.services.mozilla.com/D178597#5906316 to avoid doing a full build every time I need to update one of the js patches on top of it.

To save a click, pasting the relevant bit from the referenced review:

DNR doesn’t go through canAccess because it is independent of host permissions by design, so you need to add a check for QD in the following places:

And a unit test (see restrictedDomains for example) at https://searchfox.org/mozilla-central/rev/4fc60ae5a878dfa8cb78153ed994f4d377f44dd1/toolkit/components/extensions/test/xpcshell/test_ext_dnr_system_restrictions.js

Whiteboard: [addons-jira]
Severity: -- → S2
Priority: -- → P1
Group: mozilla-employee-confidential

The Bugbug bot thinks this bug should belong to the 'WebExtensions::Request Handling' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: General → Request Handling
Priority: P1 → P2
You need to log in before you can comment on or make changes to this bug.