[DNR] Prototype of regexFilter condition
Categories
(WebExtensions :: Request Handling, enhancement, P2)
Tracking
(firefox112 fixed)
Tracking | Status | |
---|---|---|
firefox112 | --- | fixed |
People
(Reporter: robwu, Assigned: robwu)
References
(Blocks 3 open bugs)
Details
(Whiteboard: [wecg])
Attachments
(1 file)
Implement the matcher for URLs using a regular expression.
This is also a prerequisite for implementing the regexSubstitution
option of the redirect
action.
In a later stage, the set of supported regular expressions should be restricted to enable optimizations. Ultimately the declarativeNetRequest.isRegexSupported
method can be used to validate the format.
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
There is currently no clear definition of what regexpFilter should support. A way to prototype is to just allow the syntax of whatever that is available (e.g. JS RegExp or Rust's regex
crate that we already use via RustRegex) and then document that there may be restrictions in the future.
Another approach is to agree on what syntax should be supported in regexFilter
before implementation.
There is a thread to discuss how regexFilter should look like across browsers at https://github.com/w3c/webextensions/issues/344 .
Assignee | ||
Comment 2•2 years ago
|
||
Comment 4•2 years ago
|
||
bugherder |
Description
•