Fix unexpected behavior on TextField showing error when errorText is empty #3855
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When the page is refreshed, the input field is incorrectly marked as an error if
errorText
is set previosly. This happens because_set_attr_internal
prevents theerrorText
attribute from being set toNone
, resulting in it being set as an empty string, which causes the error border to appear.Type of change
Checklist:
Screenshots (if applicable):
after page refresh:
Summary by Sourcery
Fix the input field error display issue by setting errorText to null when it is empty, preventing unnecessary error borders.
Bug Fixes: