-
Notifications
You must be signed in to change notification settings - Fork 71
Open
Labels
needs-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first timesupportive: chromeSupportive from ChromeSupportive from Chromesupportive: safariSupportive from SafariSupportive from Safari
Description
Proposal: Exclude Matching
Background
While some APIs such as Content scripts or scripting support excludeMatches, there are others that don't have such option.
menus/contextMenus is a commonly used example where documentUrlPatterns is insufficient for this purpose.
Other examples include: webRequest.RequestFilter urls.
Another example would be disabling context menus on (chrome/moz)-extension://.
Proposal
Provide a method to exclude match in APIs the don't have them
Suggestions
A few possibilities:
- Consider negative matching in Match patterns
As once suggested in Exclude in Match patterns, a negative match pattern that would simply translate toexcludeMatches
e.g.["*://*.example.org/*", "!*://*.example.org/support/*"] - Add additional matching property (e.g. similar to
scripting) to APIs that don't have it
polywock and tophffregante and carlosjeurissen
Metadata
Metadata
Assignees
Labels
needs-triage: firefoxFirefox needs to assess this issue for the first timeFirefox needs to assess this issue for the first timesupportive: chromeSupportive from ChromeSupportive from Chromesupportive: safariSupportive from SafariSupportive from Safari