Actions
Feature #442
openUse the blocklists to modify page elements
Start date:
05/15/2019
Due date:
% Done:
0%
Estimated time:
Description
This would allow the removal of those annoying popups that explain cookie or GDPR policies.
Actions
Added by Soren Stoutner over 5 years ago. Updated about 1 year ago.
0%
Description
This would allow the removal of those annoying popups that explain cookie or GDPR policies.
This would also allow the removal of empty ad elements. Note that this does require significantly more CPU processing than is currently used for the blocklists, so it may not be desirable even when it is possible with Privacy WebView.
As extension support stripped out from the default out of the box android webview, is it possible to integrate CSS based filtering inside a non-standalone browser like PB, lightning, FOSS browser, etc ?
Is Cosmetic Filtering possible with existing Android Webview ? Does the default webview allow page modifications ?
I really support the removal of page elements and pop-ups. Empty ad banners & warnings pop-ups are annoying as hell.
Soren Stoutner wrote in #note-1:
Note that this does require significantly more CPU processing than is currently used for the blocklists,
I think it's worth giving up little bit processing power for this. Although, I believe chrome's Raw Draw feature reduces the rendering workload by offsetting the texture allocation. Also uses less memory for each tile.
Currently, the only way to do cosmetic filtering in WebView it to inject JavaScript into the page. Which requires that the page have JavaScript enabled.
Interesting. Injecting in the sense inspecting the source, modifying the elements and zapping them ?
Injecting in the sense that you add an extra JavaScript file to a website which uses JavaScript commands to delete things you don't want on the website.
Many, many moons ago this was how Privacy Browser used to create dark website themes.