Also thanks to the beta testers who tested the pre-releases published in the beta channel over the last couple of days. They gave me the confidence that this version was ready enough to go into production.
Coincidence or not, it took exacltly200 commits to get to this state. It was a tremendous amount of work and I still have plenty of work left on my todo list.
What is new or noteworthy in this almost completely redesigned version:
- The new API no longer offers access to the internal formhistory. This is both a bad and a good thing. The built-in formhistory only stores basic textinput fields and only when submitted in a standard way. I have taken a different approach which hopefully will catch more user-input.
Each text-input field is stored the moment the field loses focus.Editor fields, which may contain multiple lines of text are captured while you type.
Since both type of fields are now under my full control, I have chosen to store everything in the same table and also present them to the user in one table. - The user interface is very different, the new API offers no widgets of any kind, so everything has to be designed from the ground up. For the table display I now use a jquery plugin to do all the hard work.
- Because this plugin now maintains a complete separate registration of captured text-fields, it made sense to also add a custom auto-complete system that is based on the formhistory maintained by this plugin. Since this new auto-complete system may not be to anyone's liking, it can be disabled through the preferences of this add-on.
The new add-on now uses the new mandatory API which no longer offers access to Firefox's built-in formhistory database. To get your old formhistory data into the new add-on you must first export the data using the previous versionof this add-on (1.4.0.6 or earlier) so you can import it into the new version.
Within the next few days I will provide a standalone app that can export the formhistory data from Firefox's database if you have already migrated to the new version.
6 comments:
UserStyles did a better job upgrading their extension as they gave detailed instructions on how to migrate the old data over.
As the new extension only imports XML. You need to let users know how to convert their old formhistory.sqlite to XML
congrats :)
Good job! Thank you. If you plan to translate your extension let us know. We will help.
Good job. Any pointers on getting some of the functionality back?
What functionality are you missing and would you like to get back?
Still todo and on top of my priority list is being to able to exclude sites and/or fields from collecting formhistory.
How do I make money out of sports betting? - WorkToms
A sports bettor is paid a 메리트 카지노 쿠폰 $3,000 payout on หาเงินออนไลน์ the sports bet in which they place the first wager on the game. If the game is played with 바카라사이트 a tie,
Post a Comment