See release notes.


Notes

I will keep bringing in WebAssembly ("wasm") versions of key portions of code where it is found to be beneficial. In this release, a wasm version of the algorithm used to lookup a hostname from a set of hostnames has been created.


Closed as fixed

• When pasting multiple lines into the rules editor they are joined together in a single line
• ##.ad.super from EasyList is causing ##.ad to not be applied
• Fix missing trailing asterisk in filter representation in the logger
• No context menu entry for data:* iframes (banners)
• UI Search field and it's search counter interfere with each other / unreadable
• "Update now" button flashes for 1 second before changing the count numbers
• Improve usability of temporarily disabling strict-blocking
• HTML filter exception doesn't work
• $badfilter does not work on a CSP filter

Commits history since 1.17.2.

No change since 1.17.0: this release is for the benefit of Firefox users, who will be able to take advantage of an up to date resources.txt asset. This new version is published on AMO only.

Commit history since 1.17.0.

See release notes.


New


Per-site JavaScript master switch

A new per-site switch has been added to the popup panel, which acts as a master switch for JavaScript for the current site.

This master switch has precedence over dynamic filtering rules and static filters related to script resources.

Furthermore, when JavaScript is disabled through this master switch, noscript tags will be honoured on a page (as opposed to when just using filters/rules to block script resources).

As with some other per-site switches, the default state of per-site JavaScript master switch can be set in the Settings pane, thus allowing to disable JavaScript everywhere by default, and enable on a per-site basis.

JavaScript master switch rules appear as no-scripting: [hostname] true entries in the My rules pane.


Temporarily toggle per-site switches

From now on, changes to the state of per-site switches will be deemed temporary if and only if the overview panel is visible, regardless of whether "advanced user" mode is enabled.

When the overview panel is not visible, toggling a per-site switch will cause the change to be permanent (i.e. same behavior as before).

However, when the overview panel is visible, toggling a per-site switch will cause the change to be temporary. In such case, there will be an eraser and a padlock icon in the overview pane, which can be used to revert or persist the current state of all the per-site switches.


Cache storage compression

A new advanced setting: cacheStorageCompression, default to true. When true, uBO will lz4-compress data before storing it in its cache storage in supported platforms. Currently, the only supported platform is Firefox/Firefox for Android.

The cache storage is used for storing downloaded filter lists, compiled filter lists, selfies. See https://github.com/uBlockOrigin/uBlock-issues/issues/141 for related discussion.


Closed as fixed


Firefox

• Error loading from the disk cache pages obtained by blocking remote fonts
• "Storage used" in settings tab says "? bytes"
  
  • It's really a workaround, consider the reported figure to be an on-the-low-side estimate
    
• Element picker mode in Firefox CSS failure on denuvo.com

Firefox for Android

• Cannot open Logger. Element picker/zapper does not switch tabs.

Core

• Use +js name for logging
• No reverse-lookup for logged HTML filter
• EasyList Thailand added to stock filter lists
• Various spelling fixes
• “manualUpdateAssetFetchPeriod” setting doesn't save the changes
• False positive detection of popups is broken
• "uBlock — Assets" should be changed to "uBlock₀ — Assets" in its tab
• Minor JS errors in dashboard
• Code exception in contentscript.js (vAPI.setTimeout) when opening Chrome last session tabs that are partly cached
• Element picker mishandles identifiers with backslashes
• Minor usability issue: block all scripts
• Toggle option changes are always permanent
• uBlock Origin doesn’t honor noscript tags when blocking JS

Commits history since 1.16.20.

See release notes.

I decided to create an emergency fix for a bug which was spotted for uMatrix but which also affects uBO:
"My rules tab hangs with cloud storage support"

If using cloud storage, there is a small probability uBO could be stuck in an infinite loop when reading back the data from the cloud storage, something which may occurs when the following conditions are reunited:

• You checked the setting "Enable cloud storage support";
• You saved data into the cloud storage for a given pane;
• The amount (in bytes) of data that was saved into the cloud storage for that given pane is rather high and such that the "chunkification" of that data results in a chunk count which is a multiple of 16;
  
  • Large amount of data is more likely for the "My filters" and "My rules" panes.
  • Sorry for the cryptic explanation, I don't know how else to describe this.
• You open the pane in the dashboard for which the conditions above are true.

If the bug is triggered, uBO could be stuck in an infinite loop in its main process, thus preventing it from doing its job.

This is not a regression, but rather a bug that has been hiding in there since quite a long time.

Commits history since 1.16.16.

See release notes.

I decided to create an emergency fix for a bug which was spotted for uMatrix but which also affects uBO:
"My rules tab hangs with cloud storage support"

If using cloud storage, there is a small probability uBO could be stuck in an infinite loop when reading back the data from the cloud storage, something which may occurs when the following conditions reunited:

• You checked the setting "Enable cloud storage support";
• You saved data into the cloud storage for a given pane;
• The amount (in bytes) of data that was saved into the cloud storage for that given pane is rather high and such that the "chunkification" of that data results in a chunk count which is a multiple of 16;
  
  • Large amount of data is more likely for the "My filters" and "My rules" panes.
  • Sorry for the cryptic explanation, I don't know how else to describe this.
• You open the pane in the dashboard for which the conditions above are true.

If the bug is triggered, uBO could be stuck in an infinite loop in its main process, thus preventing it from doing its job.

This is not a regression, but rather a bug that has been hiding in there since quite a long time.

Commits history since 1.16.16.

See release notes.


New

A new pane has been added in the dashboard for the Firefox version of uBO: Shortcuts. The purpose is to be able to assign keyboard shortcuts to some common operations.


Closed as fixed:

• Settings cannot be reset on Beta and Nightly Firefox
• Add a pane in the dashboard (Firefox only) to assign keyboard shortcuts
  
  • The new pane will be available for Firefox 60+ only.
    
• Element picker cannot be toggled before a site is fully loaded
• Logger: generic hiding rule recorded as active when $generichide in effect
• Filter for dynamically added class is not logged
• Logger: Popup which shows the used filter is empty

Commits history since 1.16.14.

See release notes.

Closed as fixed:

• Race condition at filter lists load time potentially breaking highly-generic cosmetic filters (https://github.com/gorhill/uBlock/commit/dcd98f4efa7876ae5d37bd0588082f6aecd08a30)
• Cursor jumps to next matched item when adding char to search<
• Inifinite update attempts with "AdGuard Experimental filter"
• Odd sorting in popup domains list when domains have same SLD but different TLD
• Cosmetic rules not logged for embedded YouTube videos

Commits history since 1.16.12.

See release notes.

Closed as fixed:

• CSS pseudo element: -webkit-scrollbar
• badfilter + matching duplicate user filter created from picker or logger may rarely cause a js exception

Commits history since 1.16.10.

See release notes.

Closed as fixed:

• HTML filters occasionally lost effectiveness
• Round hour up to nearest day

Commits history since 1.16.8.

See release notes.

No change to uBO itself.

The only change is in uBO's assets and publishing a new version of uBO package is to ensure all users get a new version of the neutered script from googletagservices.com/gpt.js -- see commit 2bc97541b3b9.

Commits history since 1.16.6.

See release notes.

Closed as fixed

• Release versions of uBO will no longer support logger-in-the-sidebar: by design Firefox opens the sidebar with new installation of uBO and this is not a desireable behavior for uBO
  • Dev builds will still support the logger-in-the-sidebar feature.
  • I may bring it back depending on the resolution of bug 1460910
• uBO webext doesn't fill entire panel space
• uBO element picker & Stylus

Commits history since 1.16.4.

See release notes.

Closed as fixed:

• "Ignore generic cosmetic filters" not checked as expected with a new installation [Firefox for Android]
  • Reported by a Reddit user, fixed with this commit
• Pull request from @Rob--W: Clear return value of vapi.js content script [Performance]
• Element picker find twice body on website
• Added a link to uBO's official issue tracker in About pane in the dashboard

Commits history since 1.16.2.

See release notes.

• Text in popup panel tooltip is out of context
• Minor fixes to code (pull request from @anvakl)
• Insufficient escaping in patchScriptlet if streamScriptInjectFilters is enabled
• Can't write any filters on Android
• Firewall pane's save/revert not showing up when scrolled down on small screens
  • Found this myself, fixed without opening a formal issue.
• Firefox 52 ESR + spoofed user agent string fools uBO into thinking cssOrigin is supported [Regression]
• Underscore in domain name breaks whitelist editor
  • Fixed with pull request from @jspenguin2017
• Element picker text area has unreadable text

Commits history since 1.16.0.

See release notes.

New:

Added support for pre-parsing directives to filter list compiler. This allows filter list maintainers to create areas in a filter list which will be compiled only if certain conditions are met (or not met). See detailed documentation.

Changes:

The "3rd-party filters" pane in the dashboard has been renamed "Filter lists", and its look and behavior has been fine tuned.

Work has been done in the dashboard to further improve rendering on small screens.

Closed as fixed:

• Blank pages with stream filtering + content-type header missing
• Cloud synchronization bar fails to load

Commits history since 1.15.24.

See release notes.

The release version of uBO on AMO is not allowed to update its resources.txt asset. This means the version shipped with the extension must be used. However, uBO compile and cache the data in resources.txt, and unless the cache is invalidated, uBO will keep using a potentially out of date version of resources.txt. This has been fixed by unconditionally invalidating the cache when a new version of uBO is detected.

Commits history since 1.15.24.

See release notes.


Regression introduced in version 1.15.12 with the fix to issue #3546: whitelist directives were not taken into account for filterable behind-the-scene network requests. This is now fixed.

Commits history since 1.15.22.

See release notes.

Changes:

From now on, behind-the-scene network requests will be treated and filtered just like any other network requests. The behind-the-scene scope will be un-whitelisted when migrating to 1.15.20+ from an older version.

This will not apply to current installations of the Firefox/legacy version of uBO, as this would cause serious breakage of the browser given that uBO can see all network requests in Firefox/legacy. However for a fresh install of the Firefox/legacy, you will have to manually add the behind-the-scene scope as a whitelist directive in the Whitelist pane.

Keep in mind I plan to drop support for Firefox/legacy once Firefox 60 ESR is released on May 7. This will remove a roadblock for simplifying uBO's code base in many areas.

Miscellaneous:

• Ability to visually filter out rules in the "My rules" pane in the dashboard.
• Firefox for Android: improved compatibility with the CodeMirror editor.
• Responsive design of the dashboard user interface has been improved a bit.

Closed as fixed:

• Loading a .javascript file from a WebExtension's web_accessible_resources messes with macOS file associations
• 2 included filterlists by directive are doubled

Commits history since 1.15.20.

See release notes.

Closed as fixed:

• i don't can paste text with right click

Commits history since 1.15.18.

See release notes.

Closed as fixed:

• "My Rules" tab is not displayed properly in FF RTL

Commits history since 1.15.16.

See release notes.

New

Added a new advanced setting: streamScriptInjectFilters. The purpose is to tell uBO to use stream filtering to inject scriptlets where possible. Default to false. Set to true to bring back scriptlet injection through stream filtering as was the default before 1.15.10. A fix has also been added to resolve https://github.com/uBlockOrigin/uAssets/issues/1492, which was the main reason to disable stream filtering-based scriptlets injection in 1.15.10.

Integration of CodeMirror in uBO's dashboard. Please do not open feature requests related to this.

Changes:

Firefox/webext

From now on, the beta version will be signed and self-hosted here. The stable version and the beta version auto-update independently of each other.

Closed as fixed:

• CSP error notification -> Conflicting with uBlock Origin? [from uMatrix issue tracker]
• Filters starting with * and followed by an uppercase letter are improperly parsed
• HTML Filter with ^ has no effect
• Redirection to neutered scriptlet broken by forbidden redirection to data: urls
• Behind-the-scene websocket's not being filtered by uBO
• Using IPv6 address in dynamic rule
• Normalize all tab id values to integer
• Site CSP's prevent surrogates from being loaded. google-analytics on Twitter for example
• Make Ctrl + S save changes to My Filters

Commits history since 1.15.10.

See release notes.

I rolled back part of the fix for #3069: scriptlets are back to being injected using the delayed path. Using stream filtering to inject the scriptlets raised two distinct issues lately:

• Cause still unknown: https://github.com/gorhill/uBlock/issues/3526
• Cause identified -- but no obvious fix possible: https://github.com/uBlockOrigin/uAssets/issues/1492

HTML filtering is still available, i.e. filters using the ##^ syntax are unaffected.


Commits history since 1.15.10.

See release notes.

Emergency fix:

Fixed a minor memory leak occurring as a result of injecting scriptlets (through ##script:inject(...) filters) using webRequest.filterResponseData.

Commits history since 1.15.8.