1.11.0
Changes
Asset managements was refactored: details.
The user interface of the "3rd-party filters" pane has been revisited:
- To render better in devices with smaller screen.
- Clicking "Update now" is no longer a blocking operation.
- The home icon is a link to the support site for a given filter list.
- The clock icon replaces the "purge cache" label.
- Click to mark a filter list as out-of-date.
- The custom filter lists input field has been repurposed to import external filter lists, as opposed to declare external filter lists as was the case before.
- An imported filter list will have an X icon aside its name, to be used to remove the custom filter list.
- You can now hide unused filter lists by clicking the global filter count at the top.
Procedural cosmetic filters can now be chained and recursive (something which was planned) .
New procedural cosmetic filter operators:
:has-text(argument)
: to filter elements according to whether they have a specific text string found in them. Use/.../
to match a literal regular expression instead of plain text.:if()
/:if-not(argument)
: use to implement recursion,argument
is itself a valid procedural cosmetic filter, but can also be a plain CSS selector.
The cost of parsing procedural cosmetic filters has been moved from content script-time to filter list compile-time, i.e. done only once when a filter list is updated.
Documentation about procedural cosmetic filters has been updated.
The element picker supports all procedural cosmetic filters, i.e. it will also provide visual feedback as you enter manually such filters in the input field. Invalid filters, procedural or not, will be labelled with a bright red E
.
Closed as fixed
Firefox
Firefox for Android
Core
- Please enable RU Adlist filter for ex-USSR/CIS locales
- Assets management refactored
- Logger timestamps are incorrect when system time zone is not on hour boundary
- Not blocked websockets (worker)
- Want to create a regex to whitelist all google but no luck
- Ads are not blocked on bing.com web searches (issue filed for Edge, but also present on other platforms, those not supporting user styles or shadow DOM).
- The fix needs to be tested/confirmed for the Edge version.
- For Chromium-based browsers, use of shadow DOM has been removed in an attempt to simplify/unify generic implementation of the concept of user styles. (can be brought back if feedback shows it's needed).
- Most reliable and low overhead cosmetic filtering is on modern Firefox (38+), all other platforms (Chromium, Edge, legacy Firefox, Safari) not providing proper "user styles" API rely on same generic implementation.
- Duplicate filter lists