Notes

Version 0.9.4.4 submitted to the Chrome store, and I see it has been labeled "Pending Review". Not sure what's happening to the Chrome store lately, publishing new versions used to be straightforward. Probably some new mechanisms to automatically flag an extension when something of importance changes: logo, file added in package, etc. (just speculating).

Version 0.9.4.5 submitted to the Opera store, awaiting reviewer's approval (normal for Opera store).

Minor changes required for the Opera version.

Changes:

• Icons/logo has been reworked a bit more, the last change was done in a hurry in order to restore the extension in the Chrome store. I am rather satisfied with this latest version, so it won't change anymore.
  • The reference icon is located here (Inkscape svg) if you need it.
• Cleanup of filter lists -- please verify that your selected filter lists are still selected:
  • GNU.org's "Block all well known privacy trackers‎" added.
    • Usual warning applies: the more filters one use, the higher the likelihood of web page breakage (for example, this list currently breaks amazon.ca pages) -- your call.
  • Obsolete filter lists have been removed (they were labelled "obsolete, will be removed" since forever).
  • Some filter lists have been relocated to a new server -- issues #14, #75, #844.
  • This will put to work code paths that have not been tested in the pass -- the seamless migration of existing filter lists to a new location, so please ensure that all the filter lists you had selected are still selected with this update.
  • Short term, this will also allow me to reduce the size of the extension package, as from now on I will avoid shipping optional filter lists as part of the extension package.

Closed as fixed:

• Visually identify 3rd party filters that are fetched over insecue http.
• Settings import enables 3rd-party filters not present in backup.
• Consistency between the buttons on the popup UI.

Closed as fixed:

Firefox

• icon bug on firefox nightly

Changes:

• Changed icons/logo as an attempt to resolve "uBlock₀ taken down from Chrome store". Will see.

Just to clear up misunderstanding: I will keep both the Chromium/Firefox working fine. I am not as familiar with the Firefox API as I am with the Chrome API, but nothing which I can't take on in the longer term, the same way I did not know anything about the Chrome API when I started HTTPSB. If anything, uMatrix on Firefox will be a good exercise in dealing with the intricacies of the Firefox API.

Closed as fixed:

Chromium:

• Popup blocker problem? (only on chrome)

Firefox

• this release is totaly junk
  • uBlock and uBlock₀ could not run side-by-side properly because I had missed changing an id in the fork.

^{Reminder: Chromium 41 (or browsers based on) still suffer from that ugly bug which causes a big chunk of memory leak each time a user opens the popup UI of an extension. Therefore, the more you use the popup UI in Chromium, the larger the memory footprint of uBlock (or any extension really) will grow. I've already seen feedback like "doesn't have a µ memory footprint at all for me. >250MB" (for µMatrix). This is important to keep this Chromium memory leak bug in mind if you make use of dynamic filtering, as this feature requires frequent access to the popup UI.}

Important:

If you install uBlock₀ manually:

Because now this version is a fork of the previous repo, I needed to also change name for installation purpose, which means that with this release, uBlock₀ will no longer fetch settings from former uBlock, so it will install as if it was the first time.

Please backup all your settings using a prior release -- if not done yet. You can restore them all with this release. This can be easily done through the Settings pane in uBlock₀'s dashboard: just click the "Restore from file" button.

If you install from the Chrome/Opera store, there is nothing to do.

Related issue: Make this version of uBlock to be installed alongside with gorhill's.

New:

• New per-site switch to toggle cosmetic filtering on/off:
  • 
  • Cosmetic filtering is of course enabled by default, so no change there.
  • The badge on the switch tells the number of DOM elements which have been hidden from view as a result of cosmetic filtering.
  • The switch is useful to create per-site exceptions as to when cosmetic filtering should not apply.
  • See "Popup-user interface: no cosmetic filtering".
  • A good example page to try the switch (given the amount/size of ads on the page): https://www.google.com/search?q=buy+car.
  • An example of that new switch being useful to un-break a web page broken by cosmetic filtering: http://www.infoworld.com/article/2905688/applications/mozillas-rust-based-servo-browser-engine-inches-forward.html (as reported in chrisaljoudi#1192).
• Per-site switches can now be manually edited manually from within the "My rules" panes.
  • So for example, this now allows to do non-recommended things like to disable strict blocking everywhere (no-strict-blocking: * true).
• When a page is blocked because of strict blocking, the user is now given the choice to disable strict blocking for the whole domain.

Fixed:

• uBlock automatically blocks mailing with 'list-manage.com/track'
  • This was one more occurrence where strict blocking appeared overzealous, so I relaxed a bit the heuristic, as per originally suggested in issue #1128 by @harshanvn.
  • This, coupled with the fact that it is now possible to disable strict blocking for a whole domain should make strict blocking less annoying.
• Support font network request type (related: chrisaljoudi#649).
• The display of tooltips in the popup UI.
• Content scripts for cosmetic filtering active despite page being whitelisted
  • This was originally identified as a uMatrix issue but it turns out the problem was in uBlock.
• Refactoring of tab/root document URL binding code -- this takes care of many new and old issues at once. No formal issue, but some are referred to in the code.

The uBlock project's main development responsibilities have been transferred to Chris Aljoudi (chrisaljoudi on GitHub).

This fork is still under my responsibility, and I will keep updating the Chrome and Opera stores. I will ensure the Firefox version keep working fine.

Both projects are expected to diverge over time.

New

• Per-site switches
  • A per-site switch to block all popups for a given site, regardless of filters.
  • A per-site switch to disable strict blocking (new mode, enabled by default)
    • This used to be supported by ABP a long-time ago: "full domain blocking"

Closed as fixed:

Firefox

• Number of items in badge not updated when newtab url is about:blank

Firefox Mobile

• Closing all tabs confuses ublock

Core

• Can't find a way to allow popups
• External script not blocked
  • This was a core issue but problem was manifesting only on Firefox
• Tooltip padding
• CHN: EasyList China will cause the firefox hanging on some website
• 'undefined' shows up in Dynamic filtering pane when popup blocker is enabled and a popup is blocked
• The status of adblock warning removal list won't be stored in the backup file
• Add lists from https://adblockplus.org/en/subscriptions
• Selected domains no longer appears in the popup
• Whitelist wildcard not working when url contains # as wildcard
• Ability to blanket-block popups for a given site
  • See "site-based switches" above
• Show "3rd-party filters list" info when category is collapsed
• Chrome-scheme not showing up in popup
• Unable to block browser take-over scripts in malware/phishing sites, or at least block redirects to such sites
  • See "site-based switches" above
  • Re. Strict Blocking - Should we do Domain blocking based on URL part itself?
• Color for domains with both blocked and unblocked content is too similar
• Problem with “element hiding” filters