4bd02c0fb6
[mv3] Inject specific cosmetic filters through scriptlet injection
...
This solves the following remaining issues regarding specific cosmetic
filtering:
- High rate of false positives in last build
- High number of generated content css files in the package
2022-09-19 08:55:45 -04:00
89566bc397
[mv3] Further reduce the number of distinct generated scriptlets
2022-09-18 17:07:02 -04:00
154a71c658
Import translation work from https://crowdin.com/project/ublock
2022-09-18 09:36:13 -04:00
5ddd3aaac6
[mv3] More work toward improving declarative css/js injection
2022-09-18 09:31:44 -04:00
9058c3524e
[mv3] Fix improper usage of scripting.unregisterContentScripts()
...
THis was causing all registered css/scripts to be removed when revoking
permission for a single site.
2022-09-17 11:22:25 -04:00
10406f5f74
Import translation work from https://crowdin.com/project/ublock
2022-09-17 08:35:54 -04:00
e1b54514cc
[mv3] Add badge reflecting number of injectable content on current site
...
Additonally, general code review.
2022-09-17 08:26:41 -04:00
46c461c568
Import translation work from https://crowdin.com/project/ublock
2022-09-16 16:06:32 -04:00
232c44eeb2
[mv3] Add scriptlet support; improve reliability of cosmetic filtering
...
First iteration of adding scriptlet support. As with cosmetic
filtering, scriptlet niijection occurs only on sites for which
uBO Lite was granted extended permissions.
At the moment, only three scriptlets are supported:
- abort-current-script
- json-prune
- set-constant
More will be added in the future.
2022-09-16 15:56:35 -04:00
34aab95107
[mv3] Add support for specific cosmetic filtering
...
Specific plain CSS cosmetic filters are now supported.
Cosmetic filtering will occur only after the user explicitly
grant uBO extended permissions for a given site, so that it
can inject CSS on the site.
A new button in the popup panel allows a user to grant/revoke
extended permissions to/from uBO Lite for the current site.
More capabilities will be carefully added for when extended
permissions are granted on a site, so specific cosmetic
filtering through plain CSS is the first implemented capability.
Generic and procedural cosmetic filtering is not implemented.
The current implementation for plain CSS cosmetic filters is
through declarative content injection, which does not require
the service worker to be alive, the browser takes care to
inject the cosmetic filters.
However declarative CSS injection does not support user
styles, so the injected cosmetic filters are "weak". I consider
this is a browser issue, since user styles are supported by
Chromium, there is just no way in the API to specify user
styles for the injected content.
Also:
- Fixed dark theme issues
- Added Steven Black's hosts file
Keep in mind all this is very experimental and implementation
details in this release may (will) greatly change in the future.
2022-09-15 13:14:08 -04:00
b343cdc374
Import translation work from https://crowdin.com/project/ublock
2022-09-15 12:53:56 -04:00
43a20f08a8
Import translation work from https://crowdin.com/project/ublock
2022-09-15 12:19:31 -04:00
be4537ef44
Use translated strings in manifest
2022-09-14 09:32:59 -04:00
76835ebcac
Reword description
2022-09-14 09:31:58 -04:00
6098f96a5d
Import translation work from https://crowdin.com/project/ublock
2022-09-13 18:00:25 -04:00
5de156a0ed
Add missing translatable strings
2022-09-13 17:58:48 -04:00
3435e9886e
Import translation work from https://crowdin.com/project/ublock
2022-09-13 17:58:12 -04:00
e31637af78
[mv3] Add ability to enable/disable filter lists
2022-09-13 17:44:24 -04:00
93e5133783
Rename to less controversial name
2022-09-11 17:41:24 -04:00
1258414f37
Report ruleset stats in popup panel
2022-09-08 10:04:08 -04:00
41d66a78ba
Report per-ruleset stats for filters-to-rules conversion
2022-09-07 13:45:55 -04:00
224410a6f5
Add per-site on/off switch to mv3 experimental version
2022-09-07 10:15:36 -04:00
a559f5f271
Add experimental mv3 version
...
This create a separate Chromium extension, named
"uBO Minus (MV3)".
This experimental mv3 version supports only the blocking of
network requests through the declarativeNetRequest API, so as
to abide by the stated MV3 philosophy of not requiring broad
"read/modify data" permission. Accordingly, the extension
should not trigger the warning at installation time:
Read and change all your data on all websites
The consequences of being permission-less are the following:
- No cosmetic filtering (##)
- No scriptlet injection (##+js)
- No redirect= filters
- No csp= filters
- No removeparam= filters
At this point there is no popup panel or options pages.
The default filterset correspond to the default filterset of
uBO proper:
Listset for 'default':
https://ublockorigin.github.io/uAssets/filters/badware.txt
https://ublockorigin.github.io/uAssets/filters/filters.txt
https://ublockorigin.github.io/uAssets/filters/filters-2020.txt
https://ublockorigin.github.io/uAssets/filters/filters-2021.txt
https://ublockorigin.github.io/uAssets/filters/filters-2022.txt
https://ublockorigin.github.io/uAssets/filters/privacy.txt
https://ublockorigin.github.io/uAssets/filters/quick-fixes.txt
https://ublockorigin.github.io/uAssets/filters/resource-abuse.txt
https://ublockorigin.github.io/uAssets/filters/unbreak.txt
https://easylist.to/easylist/easylist.txt
https://easylist.to/easylist/easyprivacy.txt
https://malware-filter.gitlab.io/malware-filter/urlhaus-filter-online.txt
https://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=1&mimetype=plaintext
The result of the conversion of the filters in all these
filter lists is as follow:
Ruleset size for 'default': 22245
Good: 21408
Maybe good (regexes): 127
redirect-rule= (discarded): 458
csp= (discarded): 85
removeparams= (discarded): 22
Unsupported: 145
The fact that the number of DNR rules are far lower than the
number of network filters reported in uBO comes from the fact
that lists-to-rulesets converter does its best to coallesce
filters into minimal set of rules. Notably, the DNR's
requestDomains condition property allows to create a single
DNR rule out of all pure hostname-based filters.
Regex-based rules are dynamically added at launch time since
they must be validated as valid DNR regexes through
isRegexSupported() API call.
At this point I consider being permission-less the limiting
factor: if broad "read/modify data" permission is to be used,
than there is not much point for an MV3 version over MV2, just
use the MV2 version if you want to benefit all the features
which can't be implemented without broad "read/modify data"
permission.
To locally build the MV3 extension:
make mv3
Then load the resulting extension directory in the browser
using the "Load unpacked" button.
From now on there will be a uBlock0.mv3.zip package available
in each release.
2022-09-06 13:47:52 -04:00
Raymond Hill