1.12.0
Changes
New static network filter option: badfilter. Using this option will prevent another filter to be loaded in memory. See uBlockOrigin/uAssets#192 for rationale for having such a filter option.
Chromium/Firefox WebExtension
Ability to support more request types from webRequest API: csp-report, font, media, websocket, and actually whatever is part of webRequest.ResourceType. This means uBO will be able to natively filter websocket connection attempts starting with Chromium 58.
Firefox
The webext version for Firefox has been converted into a hybrid version, to allow seamless migration of uBO's settings/data from a legacy extension to webext extension. I consider this webext version of uBO to be fit to release to AMO if the current stable Firefox version (52) supported all the proper WebExtensions API required by uBO. All the blocking issues have been resolved, but the fixes will be available in a future stable version of Firefox.
Update: due to auto-update snafu, the webext version of uBO has been given a different id than the official one, this will guarantee that auto-update won't cause issue (you will have to update manually if using the webext version).
Important: If you install the webext version of uBO (you need the most recent build of Nightly), this is what will happen:
When you launch uBO/webext for the first time, it will read all your settings/data from the old storage and migrate them to the new webext storage. This happens only if uBO/webext can find a file named ublock0.sqlite. This will happens only once, the first time you install uBO/webext. Depending of how much data there is to migrate, this may cause your browser to work hard during that first launch and delay readiness.
Once the data from the uBO/legacy has been migrated to uBO/webext, each version of uBO will only see its own data, meaning no change in settings in one version will be seen by the other version. If you remove uBO/webext, this also removes the storage associated to it, meaning re-installing uBO/webext following removal will cause the storage migration code to kick in again.
Closed as fixed:
Chromium
- Use the strictest setting for preventing the leakage of private IP addresses through WebRTC. It turns out the use of the strictest setting has (currently) the unforeseen virtuous side-effect of preventing WebRTC-delivered ads on some sites. See uBlockOrigin/uAssets#333 (comment).
Edge
Firefox
- uBO broken on Firefox mozilla-central tip (fixed by @gijsk through pull request #2493)
- jpm sign fails (fixed by @andreicristianpetcu through pull request #2434)
Firefox/Webextension
Core
- Autogenerated filter breaks a web page
- Cosmetic filters containing pseudo-elements like ::before and ::after are ignored
- Unable to remove/modify dynamic filter when using wildcard
- Dynamic URL Filtering fails to take precedence over Dynamic Filtering for worker requests
- Enable users to create their own custom scriptlets