[Webkit-unassigned] [Bug 205720] New: WKUserContentController Block rules introspection

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jan 3 05:42:47 PST 2020


https://bugs.webkit.org/show_bug.cgi?id=205720

            Bug ID: 205720
           Summary: WKUserContentController Block rules introspection
           Product: WebKit
           Version: Safari 13
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit2
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: krzysztof.modras at gmail.com
                CC: am at adguard.com

WKWebView provides no way to introspect what is blocked by the Block Rules. 
This, firstly, makes it more difficult to debug rules, as we cannot be sure if a rule matches the intended url, or if a particular rule is too aggressive and matching too many urls. 
Secondly, most browser using this feature like to include a counter to show how many requests were blocked on a specific page.
Currently, in Firefox and Cliqz, this is implemented by a UserScript that tries to collect urls from the document and re-match against a blocklist in the app (which is both inefficient and imprecise).

Introspection API would be helpful to detect the breakage introduced by blocking rules.

-- 
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/20200103/10d6b3b2/attachment.htm>


More information about the webkit-unassigned mailing list