1.14.20
Changes
The filter list "AAK-Cont Filters For uBlock Origin" has been removed from stock filter lists, it is no longer maintained. See #3241. Note that uBO is equipped to deal with anti-blockers, it's just a matter of users reporting instances to volunteer maintainers. Everybody is welcomed to assist in finding solutions to reported filter issues.
The DOM inspector has been improved a bit to make it more usable (see #407). Some refactoring was necessary to move forward this part, and as a result the DOM inspector is currently not available on legacy Firefox. This will be addressed only as time allow. Note that I still consider the DOM inspector to be work in progress. In case you wonder, the DOM inspector is the best way to visualize the effects of cosmetic filters on a page and to create exception cosmetic filters.
The semantic of the no-csp-reports switch has been changed from "block CSP reports from" to "block CSP reports to". This does not change the behavior of the "Block CSP reports" setting. This change of semantic makes sense, and this also removes an incompatibility with NoScript 10 (see #3260).
Accepted pull requests:
- @ kasper93: improve DOM inspector
- @ gwarser: Update supportURL for POL filters
Closed as fixed:
Firefox
- NoScript WebExtension and its CSP reports
- Use local image in Add-ons Manager
- suspendTabsUntilReady and Violentmonkey compatibility issue
Core
- NSFW not closed popup
- [Regression] Preview of CSS 'style' filters no longer works
- Add Adguard Mobile ads filter to default filter list
- Adguard Mobile Ads filter list will be automatically selected with Firefox for Android (for new installations of uBO).
- A case that a custom RegExp rule doesn't work
- $generichide filter entry appears twice in the Logger on first load
- [Performance] RegExp uses undue amount of memory on Chromium-based browsers
- Reported as a core issue because the fix also benefits Firefox performance-wise.
- uBlock unhides hidden elements when it's updated
- [Regression] :style filters incorrectly shown in logger
- 'Block element' from context menu not working in Firefox, when 0 active filters
- [Accessibility] Screen reader issue, after clicking the toolbar button, the shown up interface is not accessible with screen reader keyboard control
- DOM inspector not sees element