Skip to main content
User Experience

Return to Answer

added 1 character in body
Source Link
SW4
SW4
  • 501
  • 2
  • 7

I would tend to be of the opinion that a user who enters 0015 would not be surprised if the input automatically changes it to 15.

They will likely also not be tootoo surprised to see 15 be changed to 15.00. That said, they may then be aware the required number can be input to 2dp after the fact, which isnt best practice in the strictest sense.

Although users are also likely to realise when rounding is happening, such a change to the underlying value (and not just the format) should be accompanied with a clear explanation this is going to happen, before any rule is applied.

With this in mind, wherever there is an input format requirement it is generally a good idea to either provide the input field with an initial place-holder value in this format, or a note next to the field to inform users what the format is, or both.

I would tend to be of the opinion that a user who enters 0015 would not be surprised if the input automatically changes it to 15.

They will likely also not be too surprised to see 15 be changed to 15.00. That said, they may then be aware the required number can be input to 2dp after the fact, which isnt best practice in the strictest sense.

Although users are also likely to realise when rounding is happening, such a change to the underlying value (and not just the format) should be accompanied with a clear explanation this is going to happen, before any rule is applied.

With this in mind, wherever there is an input format requirement it is generally a good idea to either provide the input field with an initial place-holder value in this format, or a note next to the field to inform users what the format is, or both.

I would tend to be of the opinion that a user who enters 0015 would not be surprised if the input automatically changes it to 15.

They will likely also not be too surprised to see 15 be changed to 15.00. That said, they may then be aware the required number can be input to 2dp after the fact, which isnt best practice in the strictest sense.

Although users are also likely to realise when rounding is happening, such a change to the underlying value (and not just the format) should be accompanied with a clear explanation this is going to happen, before any rule is applied.

With this in mind, wherever there is an input format requirement it is generally a good idea to either provide the input field with an initial place-holder value in this format, or a note next to the field to inform users what the format is, or both.

Source Link
SW4
SW4
  • 501
  • 2
  • 7

I would tend to be of the opinion that a user who enters 0015 would not be surprised if the input automatically changes it to 15.

They will likely also not be too surprised to see 15 be changed to 15.00. That said, they may then be aware the required number can be input to 2dp after the fact, which isnt best practice in the strictest sense.

Although users are also likely to realise when rounding is happening, such a change to the underlying value (and not just the format) should be accompanied with a clear explanation this is going to happen, before any rule is applied.

With this in mind, wherever there is an input format requirement it is generally a good idea to either provide the input field with an initial place-holder value in this format, or a note next to the field to inform users what the format is, or both.