<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:aitte@gmx.com" title="aitte@gmx.com">aitte@gmx.com</a>
</span> changed
<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>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>aitte@gmx.com
</td>
</tr></table>
<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#c4">Comment # 4</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>Dear Webkit developers, please implement a statistics callback. It would make blocking addons capable of determining what block-rules are the most popular, which in turn lets blocklist authors optimize their lists (to cut out dead rules that never trigger on domains anymore due to site redesigns, etc).
That's the #1 way of handling two problems: Content Blocker only supports 50,000 rules, and the fact that old rules die with time as sites get redesigned. We need statistics to be able to find and delete all dead rules to keep the blocklists up to date.
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.</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>