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