[Webkit-unassigned] [Bug 206924] Content blocker: add an option to replace response with static content

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Aug 11 05:11:50 PDT 2021


--- Comment #9 from Sam Sneddon [:gsnedders] <gsnedders at apple.com> ---
(In reply to Michael Catanzaro from comment #8)
> (In reply to Andrey Meshkov from comment #7)
> > That'd be really great. We are ready to contribute, send pull requests, and
> > help to keep it up-to-date.
> Sounds like Apple is OK with this feature? At least it seems pretty
> reasonable for content blockers to be able to inject predefined "empty"
> responses instead of just blocking content outright.
> Sam, if you could confirm that we've reached "patches welcome" state here,
> then that would allow potential contributors (Andrey?) to feel more
> comfortable investing time in trying to implement it. Or we could ask on
> https://lists.webkit.org/pipermail/webkit-dev/.

My understanding is that there's no objection from the Apple WebKit team to this. We do want to be able to vet the substitution files, as I wrote in comment 5, hence we do want some control over them (e.g. by having them as part of WebKit rather than the content blocker). With that restriction, I'm pretty sure patches are welcome!

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210811/e3bea28d/attachment.htm>

More information about the webkit-unassigned mailing list