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.

Release 2.0.2.5, improved bugfix

The previous bugfix regarding not showing content proved to be not effective enough in all cases.
Opening windows from the dropdown-popup still behaved different from opening a window from a regular popup window, so opening a new window is now being handled by the background script.
Also in some cases (Linux/slow pc's) the html content in a newly created window was still showing blank, so I increased the no of attempts to 3 to refresh the window by varying the height one pixel.

Changes in this release:

• Bugfix 2 for not showing content in popup windows on some OS's and slow pc's (multiple attempts to restore content)
• Bugfix missing first letter of About window title

Bugfix release 2.0.2.4, fixing display issues

On some OS's, like Ubuntu with FF 57 content in popup windows were almost always hidden. Only after resizing did the content reveal itself.
This is probably caused by a weird bug in FF in relation to Linux ans possibly also MacOS.
The only fix I could come up with is displaying the popup window first and sending a width update next increasing the width 1 pixel.
Also the handling of sending and receiving messages behaved a little different, causing the close button for the preferences window not always showing up.
Hopefully this fixes all display issues.

Minor bugfix release 2.0.2.3

After a short break it is time to pickup the pace again. First some minor but annoying bugfixes.

Changed in this release:

• Display an error message when there is a problem with the database permission
• Hide URL column from small popup dialog to prevent messed up layout (URL remains searchable)

Formhistory not saved and/or empty database?

Data not stored?

If you experience problems regarding form history not being saved, please check if you have cookies enabled.
This add-on uses IndexedDB to store its information and according to this issue (see bugzilla) disabling cookies will prevent data being stored. So please check the Privacy and Security preferences of the browser and make sure that cookies are accepted or Form History Control will not be able to store your data.

Empty database?

This add-on now uses the new mandatory WebExtensions API which no longer offers access to Firefox's built-in formhistory database. To overcome this limitation this add-on will create and maintain its own private formhistory database which initially will be empty.

There are two ways to get the formhistory data from the old version back into the new version:

1. If you have an export file from the old version, you can simply import that file into the new version. The exportfile is compatible with the new version.
2. If you have no importfile, you can use a standalone Java application that can export the formhistory data from the old version. You can find this program plus Instructions on my Githib page: https://github.com/stephanmahieu/formhistory-export

Still not working?

Despite rigorous testing on many websites and being a heavy user myself, it is very likely some issues have been overlooked or slipped through. So if you think this add-on is not saving the text you type on a particular website despite the fact you have cookies enabled let me know!
I will gladly investigate any problem you experience and try to figure out what the problem is so I can fix it and improve this add-on. By providing me with feedback you not only help yourself, it will also benefit other users who might run into the same problem.