Is it acceptable to normalize the contents of a text field when it loses focus?

I got requirements that require normalizing the contents of the text field when the user changes focus to another control in the same data entry form. Normalization example:

  • spaces at the beginning and end of input are trimmed
  • If the text field was empty and this is not allowed, replace the contents of the text field with the default value

I have a feeling that this does not correspond to a good graphic design. I read the UX Guide for text fields , but I did not immediately find the appropriate rules.

Is normalizing the contents of the text field in this way acceptable?

+2
source share
6 answers

I definitely saw this before (examples are eluding me right now), but I personally don't like it when the user interface changes my input. If the user interface is smart enough to change my input to me, it should take it as it is and change the value when it needs to process it.

When the input changes automatically, you are now forcing the user to stop and ask yourself why he changed, and if they did something wrong or if the application has an error. Do not make the user think!

+5
source

, , . , . , , , . , , , .

:

  • . , (, , ), , , . , .

  • . , . , , "9-8-09" "8 2009" ( "9 2009 " ), , .

  • , . - (, , , ) , . , , - , .

  • , . , , theres . "i" .

, , , , , , , . , 15:30, 15:30, . , ( ) , 3:30 ( , ).

, , . , ( ) , . , , 0 , == none == , , , , . (, 0 " " ), , , .

, , , , - , - , .

+4

, , . . , . ( 0 0).

+2

, . , .

+1

, Microsoft Office, - "pt". , . Microsoft .

+1

. , , , , . " - ". , .

+1

Source: https://habr.com/ru/post/1735922/


All Articles