µBlock 0.8.2.7

Closed as fixed:

• Need a stale page store janitor: found entries with no tab counterparts
  • In plain language, fixed potential memory leaks

uBlock.chromium_0.8.2.7.zip:

• MD5: 7b2442bd83f8915c832104b1d06a6003
• SHA1: 7b2990ef8d39dbf2aedfab62185123e24f4b045c

µBlock 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

µBlock 0.8.2.5

Closed as fixed:

• Disappearing Gmail Labels

uBlock.chromium_0.8.2.5.zip:

• MD5: 884f5448e2b3b7d772b9700c0eac44ab
• SHA1: 988a45506e7d4d446703bbabd3bc17db6f717c33

µBlock 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

µBlock 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

µBlock 0.8.2.2

Closed as fixed:

• Weird whitelist issue

µBlock 0.8.2.1

New:

Chinese traditional translation by PeterDaveHello

Closed as fixed:

• Ensure good out-of-box experience when there are network issues
• [Performance] Do not scan page if cosmetic filter count is zero
• Cosmetic filters associated with dynamic filtering of frames still apply after disabling dynamic filtering
• Support built-in external filter lists
• Asset viewer tries to fetch locally external filter lists = blank page
• Restoring mechanism isn't restoring whitelist list

uBlock.chromium_0.8.2.1.zip:

• MD5: db2502ca4a48a7679745640476028837
• SHA1: e2f414daf0f7c156481990940b66e3abe42cf197

µBlock 0.8.2.0

Closed as fixed:

• Element picker popup language inheritance
• How do I "whitelist" a youtube channel?
  • Syntax for whitelist directives has been extended: see wiki
• Element picker text selection inheritance
• Wildcards in whitelist

uBlock.chromium_0.8.2.0.zip:

• MD5: a6f57734afef949f55f36eae84d00425
• SHA1: 867faaa959dd4336b6f59eeb4ac0fc52586f7333

µBlock 0.8.1.2

No change from previous version.

I was forced to bump up the version number due to:

1. Me wanting to submit a new version of uMatrix: 0.8.1.1
2. Being warned by the Chrome store that the description for the pt_PT version was too long
3. Me closing Google Chrome and booting Chromium to address the issue
4. Me fixing as best as I can the too long description and re-packaging uMatrix
5. Me closing Chromium and launching Google Chrome again to re-submit the fixed version (Chromium crashes when opening the Chrome store..)
6. Me realizing that for whatever reason, there is a pending published version of uMatrix as a replacement of uBlock
7. Read carefully: I never ever clicked "Submit" at any time in all this
8. Me panicking, as users of uBlock are about to end up with uMatrix instead
9. Me panicking
10. Me find the unpublish button for uBlock to prevent uMatrix being installed as an update of uBlock
11. It worked, but now there is no longer a uBlock extension in the Chrome store
12. Me resubmitting the new package of uBlock
13. Store refusing, demanding a newer version number
14. Me bumping version number of uBlock to 0.8.1.2 to make Chrome store stop complaining
15. Finally submit works, had to fill in descriptions in all languages all over again, icons, screenshots, etc.
16. Finally it's back in the store, as version 0.8.1.2, all else is same as version 0.7.2.1

µBlock 0.7.2.1

Closed as fixed:

• Element picker button appearance on certain sites
• Gmail stops working properly due to JS issues

uBlock.chromium-0.7.2.1.zip:

• MD5: a8817823183bc41f2ef2a852ff0183eb
• SHA1: bfa10b8a3f604fc29758400fd74ca880b1f61a23