Feature #497


Add blocklist options to filter by request type

Added by privacybrowser user almost 5 years ago. Updated 6 months ago.

Start date:
Due date:
% Done:


Estimated time:


Grant users ability to manage and filter different types of network requests (XHR,Image,CSS,WS,Script,Inline-Script,Inline Font,Font,Beacon,CORS Manifest,etc...) on a per-subdomain (not only domain) basis with uBlock Origin-style dynamic and static rule system, and allow use cosmetic filtering to e.g. remove unwanted dialogs, etc.

Actions #1

Updated by privacybrowser user almost 5 years ago

The current simple 3rd party requests on/off is great, but a bit blunt. Being able to specify exactly which requests to allow and not to allow would be very useful to be able to do on a per-tab, per (sub)domain basis either temporarily or permanently.

Actions #2

Updated by Soren Stoutner almost 5 years ago

  • Subject changed from uBlock Origin-Style WebRequest and Cosmetic Filtering to Add blocklist options to filter by request type
  • Assignee set to Soren Stoutner
  • Priority changed from 3.x to 4.x and will allow users to create any blocklist they like using the existing functionality described at

Cosmetic filtering is an existing feature request at

Filtering by request type could become possible in the 4.x series. However, it might require more invasive changes to Privacy WebView than I would like to make (because it could significantly increase the complexity of rebasing the modifications every time a new version of Webview is realeased). However, I will leave this feature request open and look at it more closely when we get to that point.

Actions #3

Updated by Soren Stoutner 6 months ago

Filtering by these types is already exposed in Qt WebEngine. As I have become more familiar with the Chromium codebase, I think this would be easier than I initially anticipated, so I would expect to be able to implement it with Privacy WebView in the 4.x series.


Also available in: Atom PDF