HistoryBlock 1.4.0.5 - Changelog

What's new in HistoryBlock 1.4.0.5:

November 21st, 2011

· A stylistic and simple rewrite of HistoryBlock to make future features easier to implement and augment as modules.

What's new in HistoryBlock 1.4.0.4:

November 21st, 2011

· Fixed a bug that would result in tons of errors to the console.

What's new in HistoryBlock 1.4.0.3:

November 21st, 2011

· Minor clean-up for FF5.

What's new in HistoryBlock 1.4.0.2:

November 21st, 2011

· Just an update for FF5.

What's new in HistoryBlock 1.4.0.1:

November 21st, 2011

· Release for Firefox 4.
· Many speed improvements.

What's new in HistoryBlock 1.3.5:

November 21st, 2011

· Refactored the code a lot to centralize the blocking process (should speed things up even more)
· Refactored the cookie aspect of closing a blacklisted tab; there exists a bug in FF3.6 that could cause certain cookies to fail to get added back due to their expiry value being set greater than JS's capability for Max-Int (workaround in place, bug fix slated for next small patch of FF).
· Cleaned up domain'ing, should be MUCH more straight forward now (www.google.com different than mail.google.com; google.com captures both).

What's new in HistoryBlock 1.3.4.5:

November 21st, 2011

· Completed the subdomain overhaul. Unfortunately, this MAY lead to some older blacklisted domains to act more aggressively than in previous builds. Specifically, before entries were saved as hostnames only (i.e. 'google.com'), and the default action was on every page with a 'google.com' hostname, blacklisting was used (maps.google.com, mail.google.com, www.google.com, etc). NOW, google.com has the same meaning, but blacklisting 'www.google.com' will be treated as a subdomain, only blocking www.google.com (i.e., NOT blocking maps.google.com, etc; maps.google.com can be blocked individually as well, or the hostname can be blocked for complete coverage).

What's new in HistoryBlock 1.3.4.4:

February 2nd, 2010

· Fixed a bug that would cause the meta "refresh" tag to fail every time.

What's new in HistoryBlock 1.3.4.2:

February 2nd, 2010

· Fixed an issue which would occasionally cause downloads to add an additional history item to the history drop-down.

What's new in HistoryBlock 1.3.4.1:

February 2nd, 2010

· Changed when History entries are purged (now gets called on page-load completion, and only once. Keep the speed increase, and do it the way I wanted it done to begin with!)
· Took out the redundant history-wipe call in Tab-Close events.

What's new in HistoryBlock 1.3.4.0:

February 2nd, 2010

· Moved a LOT of code around to GREATLY increase speed of opening blacklisted pages.
· Moved process of removing blacklisted pages ENTIRELY to the "close tab" event. History will have blacklisted information in it UNTIL the blacklisted tab is closed.

What's new in HistoryBlock 1.3.3.5:

February 2nd, 2010

· Compatibility update for FF3.6

What's new in HistoryBlock 1.3.3.4:

September 22nd, 2009

· fixed a bug concerning remembering cookies after closing a tab (should remember by default now so closing one tab won't wipe the cookie values of another on the same blacklisted domain)

What's new in HistoryBlock 1.3.3.3:

September 1st, 2009

· Added a power-user option for site-wide blocking (extensions.historyblock.blocksitewide). This option is for whether a user wants example.com to block all subdomain hits, so sub1.example.com and sub2.example.com. By default, it is set to true, so sub1.example.com would be blocked by the entry example.com. Setting it to false will make it so that a user can block sub2.example.com and NOT sub1.example.com or example.com from the history pages.

· Fixed some annoying bugs regarding hostname detection. The regular expression which had previous tried to grab the hostname would sometimes get confused with area extensions (example.californiadmv.com would block 'example.ca' for instance).

What's new in HistoryBlock 1.3.2:

September 1st, 2009

· added option in "about:config" allowing the user to specify to block cookies on tab close. By default, cookies/sessions are again saved upon closing tabs with locations are blacklisted domains (old functionality). This can be changed by going to "about:config" and changing the preference "extension.historyblock.blockcookies" to true.

What's new in HistoryBlock 1.3.1:

July 6th, 2009

· Fixed a bug in adding domains to be blacklisted.

What's new in HistoryBlock 1.3.0:

June 27th, 2009

Updated the code quite a bit to be more security-minded. Firefox3.5 introduced a new privacy manager to more specifically allow the things that HistoryBlock attempts to do, so a rewrite was in order. HistoryBlock now successfully blocks the following:

· History
· Recently Closed Tabs
· Cookies
· Downloads
· Cached entries

What's new in HistoryBlock 1.2.10:

December 19th, 2008

· Added the ability to UNblock domain addresses.