0.8.2.6

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.2.6]

Closed as fixed:

• Disappearing Gmail Labels
  • This was actually really a different bug than the one reported before -- though it exhibited the same symptoms here
  • I consider the bug fixed here to be worst:
  • Generally uBlock loads fast enough so that web pages are properly filtered when the browser is launched
  • However, since it loads fast enough, this meant that content scripts were injected twice into already opened web pages when launching Chromium
    • Content scripts are injected manually once uBlock has launched, because many users didn't like already opened web pages to have ads right after launching the browser
  • So not only this affected launch performance, but this also caused some bad side effects into web page already opened at launch time
  • Now uBlock's content scripts detect whether they are already injected, and bail out immediately if so

uBlock.chromium_0.8.2.6.zip:

• MD5: 2237d7407f1d394aa248482da4a35a2e
• SHA1: 5ff470d7e5bab63fde7e16cd8ae55f5459e530d1

0.8.2.5

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.2.5]

Closed as fixed:

• Disappearing Gmail Labels

uBlock.chromium_0.8.2.5.zip:

• MD5: 884f5448e2b3b7d772b9700c0eac44ab
• SHA1: 988a45506e7d4d446703bbabd3bc17db6f717c33

0.8.2.4

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.2.4]

Will release to the stores later today when I am confident there is no regression.

Closed as fixed:

• Github Issue
  • 563 cosmetic filters in EasyList and 194 cosmetic filters in "Fanboy's Social Blocking List" were potentially affected by this bug: some DOM elements could unduly disappear from a page
  • It appears that the filters found in "Fanboy's Social Blocking List" were the ones most likely to be affected by the bug (see #456)
• Cosmetic filter cache: convert watermark-based pruning trigger to time-based pruning trigger
  • Concretely, this will make uBlock use memory in a more savvy way with regard to cosmetic filtering cache. It's a code area I had not revisited since the first commit.

Other changes:

• Improved performance of MD5 hash function
  • JsPerf: MD5 Shootout
  • The MD5 hash function is used when pulling resource from Github repo, to ensure integrity; and for local mirroring, to ensure mirror-able resources are cached only once.

uBlock.chromium_0.8.2.4.zip:

• MD5: 83ac9dc95b28fee768bd319cb8cb5aac
• SHA1: c47f5ab43bfa993cd0bb45f3da8f547509273d8f

0.8.2.3

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.2.3]

Changes:

• Put back nb as a target locale (along with no).

uBlock.chromium_0.8.2.3.zip:

• MD5: 7e0b2737c251d0c12699c4a228fbd1ec
• SHA1: f12685754b6f4f846790aa8d47d55f82b01b0ad0

0.8.2.2

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.2.2]

Closed as fixed:

• Weird whitelist issue

0.5.5.0

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.5.5.0]

Closed as fixed:

• Exception in onBeforeRequest on sodaplay.com/creators/soda/items/constructor
  • This bug could in rare instances prevent net request filters from being blocked (or allowed in case of net request exception filters) for some net request URLs.
• Element picker overlay not covering the whole document for some web pages
• "Your Filters" should take precedence over 3rd-party filters
  • New filter option: important, which means exception filters will be ignored
  • The important option applies only to block filters
  • Example: ||google-analytics.com^$important = block Google Analytics, ignore all exceptions that could cancel this rule
  • The important option does not apply to exception filters, this ensures that nothing can override an important block rules: this guarantees that no external filter lists will have the ability to override your custom block rules marked as important.

0.1.0.2

This is the first version of uBlock Origin (formerly known as "µBlock") published in the Chrome Web Store on June 23rd, 2014.

It loads fine and still works (as far as I can tell) in contemporary Chromium.