Release 2.2.0.0

Some new features were added as well as a bugfix in the detection of formfields.

Changes:

• Bugfix field detection: child input elements were missing from dynamically added forms
• Added configurable Multiline thresholds settings to the Preferences
• Translation added for the age column in the main dialog
• Layout improvements main dialog:
• Use stylish custom scrollbars in main dialog (replaces ugly system scrollbars)
• Removed label from search box, added placeholder
• Hide page control in the main dialog when page-size is set to show all
• Open Help/Release-notes pages in the same window (different tabs)
• Refresh display after a manual cleanup
• Improved Chrome compatibility

Release 2.1.0.1, platform compatibility fix

Just realized that I had not flagged the previous release for being compatible for All platforms (MacOS was left out).
I can not correct this afterwards so I just released version 2.1.0.0 again as version 2.1.0.1 but now compatible for All platforms.

Release 2.1.0.0, many new features

Finally a new release.

In this release:

• Improved field detection
• Automatic Cleanup added
• Disable collecting formhistory for specific sites or fields
  • preferences window:
    • Domain filter: all / blacklist / whitelist
    • Field filter: exclude fieldnames
  • toolbar icon now reflects status enabled/disabled
• Redesign preferences window
• Limit the amount of data (and time) for the popdown dialog (browser limitation issue)
• Show fields current page: color code specific input types
• Update last-used date for autofilled fields
• Blue theme added

There is also a new homepage on github with manuals, release-notes and more!

Getting a blank popup window?

There is an annoying bug in Firefox for Linux users which causes the popup window to come up blank most of the time.

see: https://bugzilla.mozilla.org/show_bug.cgi?id=1425829
and: https://bugzilla.mozilla.org/show_bug.cgi?id=1416505

Workaround is to right-click inside the window or resize it. Hopefully this bug will be fixed soon.

Release 2.0.3.2 Bugfix

Remove prematurely (incomplete) option features.

These additional preferences should not have been released, these extra options do completely nothing.
They were added in preparation for a new feature but got accidentally released.
Apologies for that, it is fixed (removed) in this 2.0.3.2 release.

Release 2.0.3.1 German translation update

A small correction was needed for the German translation. The German datatables.json file which contains locale specific translations for the jQuery datatables plugin was not UTF-8 encoded.

Release 2.0.3.0 Language Update

Thanks to Michael Illgen who volunteered to do the German translation this add-on is now also available in German.

If you also want to participate here are the instructions:

• First download the add-on to a location of your choosing. You can download the latest version here: https://github.com/stephanmahieu/formhistorycontrol-2 and use the green "Clone or Download" button. Either use git (if you have that installed and know how to use it) or download the zipfile and unpack.
• The file you should translate is located in the \_locales\xx\ subdirectory where xx is the language tag of the country, the file should be named messages.json. If the xx directory does not exist yet, you can create it and copy the files from \_locales\en\ into the new xx directory. You can find more on this subject and links to find the correct country tag here: Reference/Global_Objects/Intl
• The messages.json file contains multiple labels with each having a message and a description. You should only translate the message part! The description is only there to give the translator an indication of what the message is used for (see for example the nl version). Please do not add empty lines or break up existing lines into multiple lines.
• The \locales\xx\ subdirectory also contains a datatables.json language file, this file is used by the jquery datatables plugin. For this plugin there are already many translations available.For a complete list see: https://datatables.net/plug-ins/i18n/.
• If you want to test your translation, you can do so in a separate Firefox profile. See support.mozilla.org on how to create an extra profile. Within this profile you can load the add-on version you downloaded in the first step by entering "about:debugging" in the URL bar and then click "Load Temporary Add-on". Next you choose the "manifest.json" file of the add-on you downloaded in the first step. The add-on should now be available in your profile (see mozilla for detailed instructions).
  If you are using an international version of Firefox, it may very well be that you are not seeing the desired translation but the (default) english translation instead. In that case you can switch the default language by entering "about:config" in the URL bar, search for "general.useragent.locale", and set the value to the tag for the desired language, for example "de" for German.
  In some cases switching the locale to does not work for whatever reason but it probably has something to do with not being able to display international characters. I can for example switch between dutch and english, but switching to greek (el) did not work for my FF version. If switching the language does not work, you  may have to download a Language specific version of Firefox.
  If you made changes in the messages.json file, you have to reload the add-on (on the about:debugging page) in order to see the changes
• When you are finished translating you can send the translated file back to me and I will add it to the release. If you are using git you can do a pull request, otherwise you may send the translated messages.json file to me by email.