µBlock 0.5.1.0

Notes:

• Extension still in "pending mode" status in the Chrome store, so can't update there. Finally. Submitted.
  • Shortly after µBlock's "pending review" status was cleared in the Chrome store, a new version of Google Chrome, version 37, became available. In retrospect, maybe this was the reason for the review? I will likely never know.
• Submitted to the Opera store.

Changes:

• New languages available:
  • Croatian by streger
  • Czech by Baegus
  • Romanian by madalin
• Much translation work by contributors on Crowdin
  • It's hard to keep track of who did what, sorry for when I skip crediting someone.
  • I wish there was a link for a project which list all contributors, like on Github.

Closed as fixed:

• Sometimes whitelisting doesn't work
  • It was a problem where order of load was important, but due to the asynchronous nature of the load operations, the good order was not respected.
• Removed images show broken image images links
• Provide an easy way to disable uBlock for a specific page on a website
  • Related issue #170: "Add option to disable ublock just for a specific page of a website". It was already supported, just not documented.
  • So a better tooltip mechanism is now available so that longer and better formatted text can be used as tooltip.
  • Thus the text for the "power" button has now moved from the popup itself into a tooltip when hovering the power button, and it does inform about how to whitelist a single web page.
• Better icons (SVG) (fix by Baegus)
• Blocks video plugin loading instead of just blocking the ad
  • Another case of some of the hosts file blocking something useful. An appropriate exception filter has been added.
• Settings in Hebrew language are displayed from ltr instead of rtl
  • Work by and support from Mikey1993 in order to ensure right-to-left languages are properly supported. One minor kink left to fix (#179).

Closed as answered:

• Add option to disable ublock just for a specific page of a website
• Style injection?

Other changes

• Some infrastructure work:
  • to address some concerns expressed in #148. I do not really plan to not ship most of the lists in there as part of the µBlock package, but I do agree that maybe some built-in lists could maybe not be part of the package. Whenever I come to a decision as to which lists are candidate, if any, the µBlock's infrastructure will support it.
  • to implement a saner way to manage he remote URLs of built-in assets.

µBlock 0.5.0.1

Changes:

• Translation work from volunteers on Crowdin:
  • Turkish description now available (required by Opera for the Turkish locale of the extension to be accepted)
  • More work on Hebrew translation
    • There are still issues pending for left-to-right languages, any dev help on this would be nice.

Notes:

• Every once in a while, someone asks me what filter lists I use. Which lists someone uses depend on their tolerance to site breakage, so don't consider my setup a strong advice on how to use µBlock. I am pleasantly surprised however at how little my selection of lists breaks web pages (given how much it blocks). Here it is: "Filter lists: gorhill"

µBlock 0.5.0.0

Closed as fixed:

• Disable silent subscriptions update
  • New setting: "Auto-update filter lists"
  • Available at the top of "3rd-party filters" tab
  • Enabled by default
  • Now only the filter lists which are in use will be fetched from remote servers (if auto-update is enabled)
    • Before 0.5, all filters lists deemed obsolete were pulled whether or not they were in use
  • If auto-update is disabled, user can force update with the Update button which will be present if µBlock sees there are lists which are, or may be out of date.
  • µBlock currently considers a filter list is out of date if:
    • The checksum of the local version (cached or install) is different than the version on the Github repository -- labeled "new version available"; or
    • The local version is older than 3.141592654 days (most ABP filter lists are deemed expired after 4 days) -- labeled "maybe obsolete"
  • The update UI in the About tab is gone, no need for it anymore
  • Note that this more efficient way of updating filter lists may mitigate the problem of µBlock not properly filtering ads when launching Chromium (or derived). By design, there is no guarantee an extension will be all set and ready before tab loads with Chromium-based browsers. So the fix here will cause µBlock to launch faster, and this will very likely help to mitigate the problem.
• Elements with style attribute containing display: none !important won't hide
  • See bug description for test case
  • A more reliable way is now used to hide element: an inline CSS attribute display: none !important; is added to every element which need to be hidden
  • Notice test case fails also with Chromium-based browser version Adblock Plus (and AdBlock), but works fine with Firefox version of Adblock Plus.

µBlock 0.4.0.1

Closed as fixed:

• with v0.4 uBlock fails to collapse the elements some times..
  • Some pages load so fast (especially when no javascript is executed before a page displays) that by the time µBlock's content script is injected, the embedded resources have been already loaded, and thus won't fire a load or error event.
  • While testing for the fix for this bug, I found that the mentioned web site, http://watchseries.lt/Watch was a good test case to show how µBlock loads web page more efficiently than ABP. Try the web page with only µBlock and then only ABP and see for yourself.

µBlock 0.4.0.0

Closed as fixed:

• Element hiding performance
  • Of interest: Cosmetic filtering in µBlock: version 0.4.0.0 update

µBlock 0.3.2.3

Closed as fixed:

• EasyList China in uBlock blocks Gmail contents

µBlock 0.3.2.2

Changes:

• Imported translation work from Crowdin
• New language partially supported: Finnish.

Closed as fixed:

• Could not support certain ABP rules
  • Highly generic cosmetic exception filters were not properly supported
  • I took the opportunity to re-factor some of the cosmetic filters code, including further performance improvements for processing highly generic cosmetic filters, and for processing post-load changes in web pages
• Whitelisted element may not display as intended

µBlock 0.3.2.1

Changes:

• Imported translation work from Crowdin

Closed as fixed:

• Performance improvement opportunities for hostname-based cosmetic filters
• uBlock's third-party filter option does not follow strictly ABP's semantic
• "Error in response handler for browserAction.setIcon: No tab with id: 21"

µBlock 0.3.2.0

Changes:

• Imported translation work from https://crowdin.net/project/ublock
  • Thanks to all contributors

Closed as fixed:

• Extension Content Verification flag in Chrome dev breaks uBlock
  • Problem was caused because of zero-length files in the extension: https://code.google.com/p/chromium/issues/detail?id=399251
• Localize fully popup menu
  • Added tooltips as suggested by bearbin
• Exception filter @@||yoursite.com^$document doesn't seem to work
  • Well, the fix which I chose is to allow people to be able to enter a URL in the Whitelist tab
  • So before, for purpose of whitelisting, one could only enter something like:
    • www.example.com: whitelist any page which hostname ends with www.example.com
  • Whereas now, these are valid whitelist directives:
    • www.example.com (as before)
    • https://www.example.com/ublock/: whitelist the web page which URL address matches exactly https://www.example.com/ublock/
    • https://www.example.com/ublock/*: whitelist web pages which URL address starts exactly with https://www.example.com/ublock/
  • There is no new UI for this new feature, except that if you hold the Ctrl key while clicking the power switch _{(I need to figure a less confusing icon)}, a URL-based whitelist directive will be created instead of a hostname-based one (default)

µBlock 0.3.1.3

Closed as fixed:

• Tab being closed automatically
  • Another case of false positive for the popup blocker.
  • Filters with a negated (~) request type would result in the popup type to be set for these filters, leading to false positives
  • Fix is: the popup type can never be implicit, only explicit
  • I found 74 filters in EasyList+EasyPrivacy which could lead to such false positives. In the reported bug, it was specifically /webtracking/*$~subdocument causing the false positive