Skip to content

Releases: gorhill/uBlock

0.8.8.3

11 Oct 15:05
Compare
Choose a tag to compare

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.8.3]

Closed as fixed

0.8.8.2

11 Oct 15:07
Compare
Choose a tag to compare

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.8.2]

New

Changes

Dynamic filtering pane:

  • You can now collapse/expand the all subdomains: click on the all cell.

Safari

Closed as fixed

0.8.8.1

11 Oct 15:08
Compare
Choose a tag to compare

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.8.1]

Emergency fix:

0.8.8.0

11 Oct 15:10
Compare
Choose a tag to compare

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.8.0]

Changes & enhancements

Safari

Important (though minor) improvements in request capturing(gorhill/uBlock@d2cc20e)

  • Bonus: out-of-the-box support for HTML5 twitch.tv (some users may need to disable Flash to get the HTML5 player)

Core

All dynamic rules are temporary by default: Click the padlock if you want to persist the ruleset for a specific web site.

  • The padlock will be visible if and only if there is at least one temporary rule in the pane
  • This is really the optimal way to use dynamic filtering, as using this feature is often a matter of trial and error
  • This prevents ruleset pollution: your ruleset will be only those which you will have explicitly persisted
  • If you Ctrl-click to set/unset a rule, it will be immediately persisted (command ⌘-click on Mac)

µBlock's power button's color is now 450nm-blue-LED: green could lead to confusion given that in the dynamic filtering pane, green is used to denote that network requests won't be blocked.

The assets auto-updater has been rewritten, to work in a more gentle and discrete way

  • Assets which need to be updated will be fetch one by one in the background, with a good delay between each fetch (this prevents large peak in memory and network bandwidth usage)
  • Once all assets have been updated, they will then all be reloaded using their locally cached copies
  • The optimal way to update assets in µBlock is to let auto-update do the job: it is more gentle on resources locally and also more gentle to remote servers

Closed as fixed

Firefox

Safari

Core

0.8.7.0

11 Oct 15:13
Compare
Choose a tag to compare

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.7.0]

Closed as fixed:

Firefox:

Safari:

Core:

0.8.6.0

11 Oct 15:16
Compare
Choose a tag to compare

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.6.0]

New:

Closed as fixed:

Chromium:

Firefox:

Safari:

Core:

Notes:

  • Lots of work from volunteer translators imported from Crowdin

0.8.5.7

11 Oct 15:19
Compare
Choose a tag to compare

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.5.7]

Changes:

Local mirroring[1] has been taken out for the time being. Too many issues which requires non-trivial fixes, while for now I prefer more to spend time on polishing, performance and overall stability.

[1] Available when "Experimental features" was enabled.

Closed as fixed:

0.8.5.6

11 Oct 15:21
Compare
Choose a tag to compare

0.8.5.5

0.8.5.4-beta.0

11 Oct 15:23
Compare
Choose a tag to compare

[Release notes salvaged from https://github.com/uBlock-LLC/uBlock/releases/tag/0.8.5.4-beta.0]

New:

Firefox version.

@Deathamns' notes concerning the Firefox version:

Notes for an official release / things that aren't working well:

For many resources the Firefox version will report double hits on the badge of the toolbar button or in the network log. This is a Firefox thing, and probably this issue is related.

The badge doesn't look good on different systems (OS X for example, see above).
It should look okay for those who use Firefox 36+, but even there moving the toolbar button to the menu-panel may mess it up (both the badge and the menu-panel).

The badge number disappears when navigating through bfcache.

If the current extension ID will not be changed, and custom update URL won't be specified for the pre-release, then once the extension will be sent to AMO, everyone will be automatically updated to that version.

Pop-up blocking is not thoroughly tested. I basically made a few random examples for myself, and only tested those.

I removed my ports/xpi branch, since the code has been pushed to the main project. If you had install scripts, then update their URLs.


Closed as fixed: