^{Reminder: Chromium (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.}

Notes

There is a version 0.9.2.2, not released here, because I feel it's not worth the storage space. The only difference with this version is this commit. This commit made it into the Opera store version as v 0.9.2.2.

Closed as fixed

Safari

• UI is shrunk with latest update

Core

• µBlock -> uBlock.
  • In case you wonder: yes, I've decided to drop the µ in favor of u, because I have seen too much arguing about how it should be pronounced, etc.
• 0.9.2.0 is now resizing each time you open it.

Other changes

Chromium

• Various small changes to ensure Chromium passes all popup tests.
  • Due to limitations to the chrome API...
    • There is just no guarantee case 6, 7 will always work. The fix was to increase as much as possible the likelihood Chromium will succeed.
    • The only way I can make case 12 succeed on Chromium is by enabling uBlock for the behind-the-scene scope.

Core

• Various small issues with element picker related to the new feature in 0.9.2.0.