1 answer
- 10-1
Mario, thanks for your post. We definitely have plans to help with the data forms, with the issues that you have mentioned. We are looking at saving drafts on some of the larger ones (like Animals), and also protection from accidentally moving away from a form and losing data.
I'm actually not sure what we'd want to do about the premature "save" when pressing enter in a text field. I think by changing the ability to press enter in certain fields would hinder regular use of the HTML forms.
We've added these requests to our tracking system, and they are linked below.
Please go to the following page and vote for this issue if you'd like to see us implement it. Also, if you have any comments or suggestions related to the request you can enter them at the page below.
CMTY-161 - Protect from loss of data when pressing the browser's back button Open
Add your comment...
While entering animals, it's unfortunately easy to accidentally hit backspace at the wrong time and exit form entry, losing everything typed so far. I've noticed this happens in particular when editing a cyclic field (like animal color, breed, species, etc), and it's very frustrating!
A similar problem occurs when entering an adoption, after you've entered the new user into the database, you get a popup. If you don't click on "close" but instead on the link to the new person's name (which is the default, since it's earlier in the popup), you reset the entry and lose it!
Obviously, saving your work often would help, but then there's a significant cost in terms of delay involved both in saving the form-in-progress, and in re-opening it for edit.
I should also say that often I get a premature entry because I hit "return" on the wrong field, and it's interpreted as "save the form".