Release 1.3.0.3

A new release with some minor updates.

• Added pt-BR translation.
• Fix: occasional TypeError: can't access dead object
• Resolved some minor warnings showing up in the console logging.

Release 1.2.10.3

Bugfix in Turkish locale preventing the preferences from being opened.

Release 1.2.10.2

Minor change in this release:

- Added locales for ru

Thanks to Vinser for updating the Russian translation.

Release 1.2.10.1

Minor change in this release:

- Description changed in install.rdf for zh-CN locale.

Again many thanks to Techlive Zheng and other translators for their efforts.

Release 1.2.10.0

Minor changes in this release:

- Added locales for tr and zh-CN
- Fix for lengthy (German) translation (Edit Cleanup/Protect criteria)

Release 1.2.9pre3

Changes from 1.2.9pre2:

• Added pt-BR locale
• Fixed clickable browse history view
• Fixed new Mozilla validation warnings

Release 1.2.8.1

Changes in this release:

• Available locales English, Czech, German, Dutch, French, Swedish, Danish, Spanish and Portuguese
• Added option to exclude fieldnames from view
• Added global keybindings for most menu-items in (right-click-)contextmenu
• Added option to Export/Import keybindings (default yes)
• Added menu-option to display (toggle) the fieldname next to each formfield
• Added option to manually save formfields (current field or all fields on page)
• Improved performance places db-lookup (faster startup)
• Set fixed width for the about dialog

Fixes:

• Fixed About dialog not properly displayed in 4.0b8pre
• Fixed Add-on bar right-click menu showing next to popup-menu of FHC itself (Mozilla 4.0)
• Fixed Show icons in regexp menu when invoked from cleanup criteria dialog
• Fixed SeaMonkey bug: undefined Components.classes["@mozilla.org/privatebrowsing;1"]
• Fixed SeaMonkey bug: undefined gBrowser.tabs
• Fixed this.treeBox.view.selection warning in FF4
• Re-use existing formhistory dbconnection from browser
• Possible unresponsive script error: query places db using a background thread

In this release further improvements on the places query (by using a prepared statement). The initial query on my formhistory data takes about 65ms to complete. Looking up additional place data is now reduced from more than 1 second down to 160ms. When Form History Control is opened right after starting the browser, it still might take some 600ms which is probably caused by the fact that the places database is not cached yet.

[Update January 3, 2011]
Additional fixes after Mozilla review:

• Added FHC namespace to element IDs in overlays
• Fixed "leak symbols into global scope" in some event listeners

Plus:

• Added Portuguese locale

[Update January 8, 2011]
Additional fixes after second Mozilla review (new version now 1.2.8.1):

• Using a background thread to query the places database is no longer allowed so I had to fix that. This is related to Mozilla bug 608142 (see also this forum post)

I wish the reviewer had reported this in his first review so I could have fixed this the first time.

Release 1.2.8pre4

In this release I improved the query of places information (the probable url the formfield was used). A user reported an unresponsive script error that was caused by the places query. I now perform the query asynchronous, after the main dialog is displayed. Unfortunately the method I have to use (using a different thread) is deprecated in FF4.0. In the next release I will further improve the performance and efficiency of the query and hope the unresponsive script will no longer occur (an unresponsive script error is triggered when a script takes more than 20(!) seconds to complete).

Changes in this release:

• Added locales Czech, French, Swedish, Danish and Spanish
• Fix possible unresponsive script error (query places db asynchronously)
• Places lookup (url, host, title) temporarily not working in FF4.0b/SM2.1b (Bug 608142)
• Minor technical improvements

Release 1.2.8pre3

This release is intended for translation only and was uploaded to Babelzilla on December 6th.

Release 1.2.7

I have added many new features in this release (see release notes), including the ability to show the page (title, host, url) the formfield was first and/or last used.

The page a formfield originated from is obtained by examining the browse history. So in order for this to work, Firefox's "Remember browsing history" must be turned on. If browse history is available around the time the formfield was first or last used, the originating page can be obtained from the history database (places.sqlite). This however may not always be accurate! When a page is loaded by the browser, it is stored in a database along with the current date and time. The data for a formfield however, is not stored until it is submitted. This will always be some time after the page has been loaded. If the user loads a second page for instance in another tab, submitting a form in the first page will result in formfields being registered right after the second page was loaded. In this scenario Form History Control will link the incorrect page to the formfield.

In order to get a slightly simpler look I decided to get rid of the "Show only matching cleanup criteria" checkbox and replace it with a button under the cleanup tab.

For a complete list of changes, see Release Notes.

[update 23 Oct 2010]
Version 1.2.7 has been reviewed and is publicly available as of 22 Oct.

Release 1.2.4

The Portuguese translation for the latest version became available and is now included in this version.

I tested Form History Control on the nightly build of Firefox (3.7a6pre) to discover that the Extension manager had been replaced by a new Addon manager. This change affected both the About dialog and the information tab in the Preference dialog. Both dialogs display some information about the Extension itself which is obtained from the Extension manager. I had to make some changes in order to make it work with both the old and new manager.

Changed the Firefox maxVersion to 3.7a6pre in install.rdf.

I also tested the new beta version of the Flock browser. Since the new version is based on Google Chrome, the Form History Control Extension will no longer be supported.

Release 1.2.1

Finally, after months of hard work the new version is ready for release. I have added many new features, incorporating most of the feature requests made on this blog (see release notes).

Not all translations were finished, but I did not want to wait any longer releasing this version. The finished translations are Czech, English, Spanish, French and Dutch.
Not finished yet are: bg-BG, de-DE, pt-BR, hu-HU, it-IT, ru-RU, sk-SK, tr-TR and zh-CN. As soon as they become available I will create a new version and upload it to Mozilla.

The review process at AMO should be a lot faster nowadays, I hope the add-on becomes available within the next two weeks.

[update 13 Apr 2010]
Version 1.2.1 has been reviewed and made public as of 13 April.

Release 1.1.4

Corrected some translation errors in locales de-DE, nl-NL, pt-BR and ru-RU. Apparently some translations were not uploaded to Babelzilla in utf-8. My IDE did not create an utf-8 encoded formhistory.properties file for de-DE, nl-NL and pt-BR since all characters fitted the latin character set. The ru-RU translation probably was not in utf-8 either but some other (non latin, non utf-8) code-page.

Anyhow, I have uploaded a new version 1.1.4 with the correct translations. It is now in the sandbox waiting to be reviewed and released. If you can not wait you can download it from here.

[update 19 Dec 2009]
Version 1.1.4 has been reviewed and made public as of 19 December.

Release 1.1.1

Finally the extension has been reviewed by a Mozilla Add-ons editor who approved my extension to become public.

I immediately updated my extension to version 1.1.1 and included the new de-DE, pt-BR, ru-RU, es-ES translations.

New translations

Today new translations were completed at the Babelzilla site. New translations were added for German (de-DE) and Portuguese (pt-BR) and a Russian (ru-RU) translation is also almost finished.

I am waiting with the next release until the extension gets reviewed by Mozilla and can leave the sandbox. For now it is still listed as experimental. I am waiting since June 28th for the review, I hope it will happen any time soon now.