0.8.6.0

^{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 µBlock (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). The bug is marked "available", which to me translates into "meh". Sigh.}

New:

• Bulgarian translation by antonpenev, avp3000, ecogiko, vladev
  • Found out today that work on this translation had been started since late December and I had missed it: sorry about this
• Korean translation by delightbot
• Latvian translation by 7nolans, spitaligais
• Persian translation by omid3098

Closed as fixed:

Chromium:

• [Chromium] Sometimes web pages may not be cleaned up properly after launch
  • Somehow nobody complained of this regression bug, which probably manifested not that often when µBlock loaded from a selfie
• [Chromium] Chromium bypassing uBlock through behind-the-scene requests
  • [Working on documentation: for now look into request logger drop down list]
  • Behind-the-scene requests can only be filtered if "advanced user" mode is enabled -- though you can examine them in the request logger regardless of mode

Firefox:

• [Firefox] Popup blocker incorrectly closes user clicked window

Safari:

• [Safari] Fix YouTube ClickToPlugin conflict
• [Safari] Big fixes to Safari vAPI stuff
• [Safari] Turning off uBlock for domain doesn't make the site load properly, disabling uBlock does
• [Safari] Safari Extension Gallery

Core:

• [Core] Element picker (nth-child usage)
• [Core] host name not displayed in dynamic filtering frame, when inline-scripting is active..
• [Core] dynamic-net-filtering.js length typos
• [Core] Filters with multiple negated request types
• [Core] Support regular expression-based network filters
  • I just got tired of the suspiciously often-repeated fallacy that uBlock was more efficient because it didn't support regular expression-based filters (only 15 of them in all of EasyList...)
  • µBlock-specific documentation for regex-based filters
• [Core] Romanian list
• [Core] Move µBlock.transposeType() to Chromium's platform-specific code
• [Core] Feature Request: allow µBlock to run on chrome:// urls
  • µBlock is now active regardless of what URL is present in the address bar. For non-HTTP-like URLs, µBlock will create and use a synthetic URL internally, so that these non-standard URLs (about:config, chrome://settings, file:///..., etc.) can be whitelisted and have their own dynamic filtering rules.
  • As far as I can tell this is fully functional for Chromium. There is probably platform-specific code in need of work to have the same feature for Firefox, Safari.

Notes:

• Lots of work from volunteer translators imported from Crowdin