1.5.0

New:

Ability to inject script resource from the resource library directly into a page -- i.e. not through redirection. Can be used to defeat some otherwise hard to defeat ad injection mechanisms on some sites. More specifically, this allows to defeat AdDefend- or Yavli-based ads on many sites (as of writing), which so far were defeated only through inline script tag filtering -- so this means that now Chromium-based browsers can also bypass AdDefend/Yavli (for example, see #1100). Some documentation available here (will eventually create a dedicated page).

Enabling advanced user mode won't cause the tooltips to be disabled anymore. There is now a separate setting for tooltips in the Settings pane: "Disable tooltips". Tooltips are enabled by default.

Closed as fixed:

Chromium:

• uBlock crashes on browser startup if Chromium is compiled without webrtc
  • Solution contributed by @Eloston.

Core:

• [Logger] Cannot reverse find a specific filter
• On a site with 0 connections displayed
• [Efficiency] Make use of String.prototype.startsWith
• no-popups: * true rule blocks opening of a clicked url
• [static filter syntax] separator characters (^) support
• Use case: does an advanced user still need tooltips?

1.4.0

New:

Ability to use Adguard filter lists

You can now directly use Adguard filter lists. Filters which use Adguard-specific filter syntax extension will simply be discarded by uBO. If you want to use an Adguard filter list, you will have to import it as an external filter list.

Popunders

A new filter type is introduced: popunder. This gives uBlock Origin the ability to block popunders. Popunders are when a web page opens new legitimate content in another tab or window, while at the same time loading nuisance content in the current tab. They are essentially the reverse of what is happening with nuisance popups, where the nuisance content is opened in a new tab or window.

Since the popunder option is specific to uBO, any instance of sites using popunders will have to be reported here so that filters can be crafted to address the issue for those sites.

Redirection infrastructure

Consider this still experimental. This adds the option to map blocked network requests to uBO-provided resources. Specifically, this solves issue raised in #949/#1043 -- and more generally consider this yet another tool in uBO's arsenal to enforce users' choices.

The library of resources which are used for redirection is -- and will always be completely under control of uBO, this is not something under the control of any 3rd parties. This ensures only safe resources are used for redirection.

It could be said this feature is vaguely similar to NoScript's surrogates, except that in the case of uBO it's network redirection to plainly map one resource into another one, and it can be used for any kind of resource, not just scripts (anything which can be represented with a data: URI).

Only blocked network requests are candidates for redirection.

To create a redirection filter, just add the redirect=[...] filter option to it, like so:

||example.com/badimage.*$image,redirect=2x2-transparent.png

The [...] is a token identifying the resource to which to redirect: it must be a resource which appears in the resource library. With the example filter above, a web page will not see that the resource was blocked.

For the redirect= filter option to be taken into account, some conditions must be met by the static filter, for efficiency purpose. The static filter ...

• must be hostname-anchored, i.e. starts with ||.
• must have one type specified -- negated types are not valid.
• must have a redirect token which identifies an existing resource in the resource library.

If at least one of the above conditions is not met, no redirection will take place, though the filter will still block matching network requests.

Example of cases solved by the redirect filter option:

• Ads in video: http://www.chip.de/news/Halbvoll-in-2-Minuten-Huawei-zeigt-neue-Superakkus_85752247.html
• Site detects blocker: http://dayt.se/

Closed as fixed:

Firefox

• NoScript Force HTTPS feature interferes with uBlock Origin
• Default browser font does not work well for dynamic filtering panel

Pale Moon / SeaMonkey

• uBlock Origin breaks custom toolbars in Palemoon
  • Possibly related: [SeaMonkey] Filter list is empty after browser restart

Core

• Site disables uBlock Origin's own style tags
• [Pull request] Add YousList as a Korean third party filter
• Element picker: a selected element with width or height of zero should fall back on dimensions of child elements
• End "My filters" list with empty line
• Cosmetic filter fails to hide element
• The white list is invalid
• uBo is causing CPU hog with imdb.com (popup video)
• Support subscribe links
• Block ad videos playing automatically
• Fixed issue arising from Add the I don't care about cookies filter to Regions, languages? (see comment).

1.3.6

Closed as fixed:

Firefox for Android

• uBlock Origin 1.3.4 (and next) broken in Firefox for Android Release (42.0.1) until I disable/enable

1.3.5

Closed as fixed:

Pale Moon, or older versions of Firefox

• 1.3.4 removed all settings & built in 3rd party filters

1.3.4

Closed as fixed:

Firefox

• Inline script tag filtering incompatible with Firefox ESR 38
• Mouse context menu broken
• WebRTC and FF 42.0

Firefox for Mobile

• uBlock Origin 1.1.1 broken in FF-nightly until I disable/enable
  • Thanks to @AlexVallat for having investigated the root cause of the issue.

Core

• /\.js$/ does not work.

1.3.3

Closed as fixed:

Chromium

• vAPI.adminStorage throws an exception in UC Browser.

Firefox

• Cosmetic filters not always reported by logger on Firefox 42 if you refresh the page

Core

• Cosmetic filtering have no effect
• [Performance] Use getElementsByTagName for high-medium generic cosmetic filters

1.3.2

New:

[Chromium] question/suggestion: centralized custom filter/whitelist settings? This needs to be tested by an admin, in a proper environment, I can't test this myself. Will wait for feedback.

Closed as fixed:

Pale Moon/SeaMonkey

• uMatrix icon only available in one browser window when auto-restoring multi-window session
  • Thanks to @DjogaRo for having patiently investigated the root cause of the issue.
• uBlock duplicate icon on Context menu

Core

• Clicking URLs in Chrome Full History bypasses uBlock Origin

1.3.1

Closed as fixed:

Firefox

• AMO reviewer feedback: fix "Security Error: Content at moz-nullprincipal:" warnings in dev console

1.3.0

New

Basic support for Thunderbird, contributed by @M-Reimer.

---

Closed as fixed:

Chromium (v31)

• Buttons don't respond on strict blocking warning pages

Firefox

• uBlock disabled on first unloaded tab on the left
• Missing icon on toolbar not in Customize
  • This is about uBlock Origin's toolbar button in legacy mode: this also applies to:
    • Firefox 28 and less, or Firefox 29+ when forcing the use of the legacy toolbar button (when extensions.ublock0.forceLegacyToolbarButton is true in about:config.
    • Pale Moon
    • SeaMonkey

Core

• Logger shows wrong filter lists when clicked on a filter
• uBlock filters not updating automatically after purge all caches
• Pop unders
  • Making use of the new inline script tag filtering ability takes care of pop-unders for the site mentioned in the issue. Of course, since Chromium does not yet support beforescriptexecute, the fix works only for (recent) Firefox versions.

---

1.2.1

Closed as fixed:

Firefox (Nightly)

• TypeError: LocationChangeListener is not a constructor