Updating the user value when there is a validation error can be confusing

[jgou]

The Control.setValue function always ends with writing the user value. However when the control state is invalid, this can be confusing for the end user.

A good example is with integer fields. When the user types 5.3 in an integer input control, the isInt validator will mark the control as invalid. Writing the user value however will cause the displayed value to be 5, so you get an input field with value 5 with a validation error "not a valid integer" next to it.
And even worse, if you then want to input 5, you first have to clear it (or type in another value) because the validation error remains otherwise.

[freya]

(In [1605]) fixes #347 : only remove the trailing zeros, and not everything behind the decimal separator