[Webkit-unassigned] [Bug 152598] Feature request: a callback when request is blocked by the Content Blocker

[bugzilla-daemon at webkit.org]

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

--- Comment #13 from Andrey Meshkov <am at adguard.com> ---
> For the use case of debugging content blocker extensions, maybe we could provide something better via Web Inspector or safaridriver?

Yep, this will be even better.

Currently, requests blocked by content blockers simply disappear from the "Network" tab of the Web inspector.

Instead of this, you could mark them as "blocked", and provide additional metadata:
1. What content blocker has blocked (or upgraded, or blocked cookies) this or that request
2. What exact rule was triggered

For the main document and frames, we'd like to see how many `css-display-none` rules were injected.

If there is a rule with `action: ignore-previous-rules` that was triggered on a request, we'd like to see this information as well.

-- 
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/20200219/34c8b93a/attachment.htm>