<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Feature request: a callback when request is blocked by the Content Blocker"
href="https://bugs.webkit.org/show_bug.cgi?id=152598#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Feature request: a callback when request is blocked by the Content Blocker"
href="https://bugs.webkit.org/show_bug.cgi?id=152598">bug 152598</a>
from <span class="vcard"><a class="email" href="mailto:aitte@gmx.com" title="aitte@gmx.com">aitte@gmx.com</a>
</span></b>
<pre>I misspoke earlier. I said "I think there should be a single callback function with an array of blocked resources, at the end of the page loading. That sounds like a resource-efficient way of handling blocking-statistics."
What I meant, and think would be even better, is:
I think there should be a single callback function with an array of the IDs of triggered blockrules AND triggered whitelist rules, at the end of the page loading.
Such an array would be easy to build and lightweight to process. It would tell us what rules are active, and what unblock/whitelist rules are active. From that, we can detect which rules never trigger on a domain anymore, as well as which triggers the most. Then we can build optimized blocklists that cut out all the years-old, long-dead rules (about 80% of the blocklist contents are dead rules by now, and we need statistics to find those).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>