0.9.8.3

Notes

Most of the work for this version are for Firefox, but I will publish this version only in the Chrome store, as the new setting:

[ ] Disable pre-fetching (to prevent any connection for blocked network requests)

... is only functional for the Chromium version. I need to read more to hook it properly for Firefox. That new setting is checked by default. It is suggested you read Chrome Help's Make webpages load faster:

If you turn this setting on in Chrome, websites (and any of their embedded resources) that are prerendered or prefetched may set and read their own cookies as if you had visited them before -- even if you don’t visit the prerendered or prefetched pages after all.

Note that pre-fetching is more of a crutch to speed up page load, using a blocker in the first place is what really improve page load time, without sacrificing privacy like pre-fetching does. Aside the privacy implication of pre-fetching, it certainly does not come for free either resource-wise (bandwidth, memory, cpu). In any case, your choice, so long as you can make an informed one (that pre-fetching setting, enabled be default, and its negative implication privacy-wise are not exactly disclosed upfront).

Closed as fixed:

Firefox:

• Performance issues in Firefox 39 beta.
  • Need someone to test, I do not have a test case readily available (100s of tabs).
  • Maybe will also fix #252?
• Tab selector list error?

Chromium:

• Allow advanced users to turn prefetching back on
  • The new setting is in the Settings pane. Pre-fetching is disabled by default. It is suggested you leave it disabled. I am skeptical of the advertised benefits when using a blocker.