Last modified: 2014-03-11 10:07:34 UTC
When editing a Snak value which uses server-side backend parser/validation (e.g. Quantities), the "save" button will be disabled until the request returns and says the value is valid. Originally, we designed the system to always allow hitting "save" independently of backend validation - only immediate frontend parsing failure would immediately disable the save button after a value change and prevent any parse/validation request to the backend for the current value. If the backend had a problem with the value, the user would be notified and the edit mode would switch back on (with the save button disabled until the value changes again?). Allowing to hit the save button before backend validation is done allows better use of keyboard only usage. E.g. I enter a quantity and hit enter. With the current implementation the enter might be ignored depending on how fast after entering the number I hit enter and how fast the connection works.
