You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if the user has entered "123" the displayed value will be "(123" and if the user thinks they need to type the trailing ")" they won't be able to
Ideally any following mask character(s) would be added, so if the user has entered "123" the displayed value would be "(123) " and the user would know they could continue entering numbers
Alternatively allowing the user to enter the mask characters literally would also solve this problem, though less elegantly in my opinion
The text was updated successfully, but these errors were encountered:
The use of the mask was provided in such a way that the cursor position is set only after the character entered by the user, in your example these are numbers. This
approach is aimed at the unhindered deletion of characters using «backspace».
We will consider the possibility of entering mask characters, thanks for the suggestion.
The preferred solution wouldn't require them entering mask characters, it'd be -
Leading mask character(s) would be automatically added, so if the user has entered "123" the displayed value would be "(123) " and the user would know they could continue entering numbers
If the input contained "(123) " and they hit backspace it would remove all mask characters +1 entered character, ie the input would then contain "(12" as expected
Example, given the mask
<InputMask mask="(___) ___-____" replacement={{ _: /\d/ }} />;
Currently if the user has entered "123" the displayed value will be "(123" and if the user thinks they need to type the trailing ")" they won't be able to
Ideally any following mask character(s) would be added, so if the user has entered "123" the displayed value would be "(123) " and the user would know they could continue entering numbers
Alternatively allowing the user to enter the mask characters literally would also solve this problem, though less elegantly in my opinion
The text was updated successfully, but these errors were encountered: