Unwanted field changes in results compilation

[nathanshammah]

When adding or editing a new / existing result, many fields get a unwanted change while one fills out the form. I believe the reason is because the mouse is still "engaged" with the change, even if one has made the selection. For example, I insert 2000 as number of shots, then scroll down, to the next field, but this changes the number to 2003. One needs to click outside the form field to deselect the edit mode. Similarly this happens to single-select options. In this case, once the "edit view" drop down menu is closed and the choice is selected, the edit mode of that field should exit and not be susceptible to mouse movements.

[WrathfulSpatula]

These are the default HTML key press actions for underlying input types. I'm not saying there's no "mitigation" for this in terms of our forms, but overriding basic HTML input defaults might be advised against. I am thinking about this, and I'll return to the issue to address the concern. We might suppress these default input actions, but this is potentially a challenge to hypothetical users who use assistive technology like digital screen readers. (The correct "forward button" for cycling through form fields, by the way, I believe to be "TAB" button, according to HTML itself.)