uBlock Origin Ad-Blocker - Versionsinfo

Boersenfeger

Die neue Beta-Version uBlock Origin 1.14.23b2 ist erschienen!

Änderungen

New

Ability for filter list maintainers to force uBO to load extra filter lists from within a filter list, using an !#include directive. Example:

!#include adblock_ublock.txt

When uBO encounters the above directive inside a filter list, it tells uBO to load the extra filter list and append it to the current one. The main purpose of such directive is to allow filter list maintainers to be able to make use of uBO's extended filter syntax, without forfeiting the ABP-compatibility of their main filter list: ABP will ignore such directive since it will be seen as a mere comment.

All the details of the new directives syntax is being fleshed out at AdguardTeam/AdguardBrowserExtension#917. At this point only !#include is implemented by uBO, because it solves immediately a current issue by simplifying the work of filter list maintainers who want to make use of uBO's extended filter syntax.

Important: uBO forbids cross-origin requests for embedded filter lists: an embedded filter list must have the same origin as the embedding list (i.e. be on the same server). If it's not the case, the embedded filter list is rejected. Typically, filter list maintainers will just use a single file name, as seen in the example above, in which case same-origin is implicit.

Closed as fixed:

Scriplet injections are Not Logged

Die neuesten Versionen und Informationen gibt es immer hier:
https://github.com/gorhill/uBlock/releases

Direktdownload vom Entwickler

Direktdownload von AMO

[b]Diskussionen und Fragen zu ublock Origin bitte nur im
uBlock Origin Ad-Blocker - Diskussionsthread posten.

Vielen Dank!

Boersenfeger

Die neue Beta-Version uBlock Origin 1.14.23b6 ist erschienen!

Änderungen

New

HTML filtering

Ability to remove DOM elements from a source document before it is parsed by the browser. The platform must support an extension API to modify the response body on the fly. Currently only Firefox 57+ allows this.

The filter syntax is similar to cosmetic filtering, except that the character ^ is used before a valid selector to denote that the filter is to be applied to the source data. Contrary to cosmetic filtering, with HTML filtering the elements matching a selector are removed from the source. Example:

twitter.com##^meta[http-equiv="refresh"]
www:google.ca##^#hplogo
boards.4chan.org##^script:has-text(7c9e3a5d51cdacfc)

Note that procedural operators are supported. Procedural operators which are senseless to use on source data will be ignored. For example, it makes no sense to use procedural operator such :matches-css(...) for HTML filtering.

Note that HTML filtering essentially brings back support for inline script tag filtering. I plan on deprecating the syntax ##script:contains(...) in favor of ##^script:has-text(...). For the time being, uBO will conveniently convert the old syntax to the new, more generic one.

Given that HTML filters are to be applied to the source data of a document, the best way to create such filters is to view-source: the document and from there analyze what should be removed. Thus the element picker won't be extended as a tool to create HTML filters.

This is a first release of the feature, and I do know there is code review needed and TODOs to work on before this makes uBO ready for a release (for example, exceptions are not supported yet).
Sub-filter lists