[webkit-help] Feedback and questions regarding Content Blocking Extensions

Romain Jacquinot rjacquinot at me.com
Thu Aug 13 10:27:20 PDT 2015

Forgot one last point:

4) There doesn’t seem to be a way to programmatically enable/disable a previously-enabled content blocker without having to go through the compiler again when re-enabling it. I’ve filed a bug report at bugreport.apple.com <http://bugreport.apple.com/> (#22270848) with an example of use case.

> On Aug 13, 2015, at 6:49 PM, Romain Jacquinot <rjacquinot at me.com> wrote:
> Hi,
> After a few days experimenting with Content Blocking in Safari, I have a few questions / some feedback:
> 1) There are currently no recursive exception rules. It is therefore not possible to whitelist a full website or webpage, i.e. ignoring all rules regardless of where the content comes from. I've filed a bug report at bugreport.apple.com: #22268224. Are there any plans to add this feature before the release of iOS 9.0 and OS X 10.11?
> 2) Enabling content blockers from Safari Settings may be complicated for some non-tech-savvy users. It would be great to be able to open Safari Settings directly (or even better Content Blockers' Settings) from a third-party app using URL-schemes. Bug report: #22217664
> 3) With iOS 9.0 (13A4325c), content blocking doesn’t work on iPad, only in the simulator. I've filed a bug report at bugreport.apple.com: #22217578. Is it a known bug?
> Thanks.
> Romain
> _______________________________________________
> webkit-help mailing list
> webkit-help at lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-help

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-help/attachments/20150813/4d11d170/attachment.html>

More information about the webkit-help mailing list