correlr/roam
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

updates

Browse source
This commit is contained in:
Correl Roush 2021-11-04 20:13:12 -04:00
parent 457de828f7
commit 9feb79a954
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
20211104164651-input_data_properties.org
View file

@ -16,3 +16,18 @@ data?
Is there a good language for describing these categories of data, can we better Is there a good language for describing these categories of data, can we better
understand what differentiates them, and use that knowledge to build more understand what differentiates them, and use that knowledge to build more
consistent guidelines for UX and input handling? consistent guidelines for UX and input handling?
* Trimmable
#+begin_notes
Taken from https://experience.sap.com/fiori-design-web/leading-trailing-blank-removal/
#+end_notes
** Use field trimming if:
- The leading or trailing white space is not needed for the business process.
- The input fields have uniquely identifying business objects.
- The input fields have a fixed field length.
** Do not use field trimming if:
- The use case explicitly requires leading/trailing white space. For example,
for formatted text such as chats, comments, descriptions, source code, or for
file names (according to the supported OS behavior).
- For text areas where users would expect leading white space as a formatting
tool.