Problem:
Lets say there is a non nullable field "name" in a feature class.
When creating new features using the EditorWiget the FeatureForm prefills these non-nullable fields with a single whitespace.
As a user I definitely expect no prefilling at all, especially no non-visible character.
The Problem is clearly: The user does not see or even recognize that whitespace and just types a name.
By this every new feature in our customers system are getting leading whitespaces in their name.
Background:
Regarding this documentation
https://pro.arcgis.com/en/pro-app/3.3/help/data/feature-classes/defining-feature-class-properties.ht...
ArcGIS adds a single whitespace in textfield values instead of null in case the field is not nullable in GeoDB.
So this may explains where the whitespace comes from, but from my point of view it is no necessary to have that whitespace set on UI side.
Plus I did not find any documentation explaining the necessarity of the behavior in the EditorWidget.
My idea is kinda obvious:
- pretend adding any whitespace in the EditorWidget UI
- add validations if all values are proper defined and give red alerts when trying to persist
Know what? The second part already exists in the EditorWidget.
I can remove the space and try to persist. An error will show me the mandatory field.
One now could argument, that this error would appear directly even the user did not yet start its inputs. And yes, I agree that is no good UI Design as well. But what if we switch the field validation to when clicking the save button instead of directly after focus lost event?
If fot any reason this not suitable, then at least any kind of hint should appear such that the user at least has any chance to even notice that there is a leading invisible whitespace.
As a Workaround we are creating an attribute rule which trims any value.
Btw: The EditorWidget in Arc JS and ExperienceBuilder as well behave the same.
Find a video attached showing the bahavior.
