Project

General

Profile

Feature #497

Add blocklist options to filter by request type

Added by privacybrowser user about 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
4.x
Start date:
09/06/2019
Due date:
% Done:

0%

Estimated time:

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.

https://github.com/gorhill/uBlock

History

#1

Updated by privacybrowser user about 2 months 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.

#2

Updated by Soren Stoutner about 2 months 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

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.

Also available in: Atom PDF