Added by privacybrowser user over 4 years ago. Updated 3 months ago.
0%
Description
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.
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.
https://redmine.stoutner.com/issues/180 and https://redmine.stoutner.com/issues/181 will allow users to create any blocklist they like using the existing functionality described at https://www.stoutner.com/privacy-browser/blocklists/.
Cosmetic filtering is an existing feature request at https://redmine.stoutner.com/issues/442.
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.
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.