Port subresource_filter to Headless Chrome. |
||||
Issue descriptionAssuming the activation mechanism is decoupled from filtering, here is what needs to be done: 0. Make //headless directly depend on //components/subresource_filter. 1. Provide a way to supply the ruleset to subresource_filter other than Component Updater, e.g., a take it from a local file. 2. Create an activation mechanism in //headless, because the current one resides in //chrome layer (Safe Browsing).
,
May 15 2017
,
May 15 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 15 2018
It would be nice to have this, since we are planning (potentially web visible) interventions using this technology. However, it is not time critical. No longer needs to be R-V-G either. |
||||
►
Sign in to add a comment |
||||
Comment 1 by pkalinnikov@chromium.org
, Mar 21 2017