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
Applying a mask to a password type input field confuses the user
Use case:
We're trying to apply a mask to field that accepts a PIN number. The PIN number should be hidden from onlookers as the user types, so we use a password type input field. We want to limit the user to entering exactly 6 digit and only digits. The mask is perfect for this (paired with a validation).
Bug
Feature request
Code refactor
Continuous Integration (CI) improvement
Changes in documentation (docs)
Other (describe)
What is the current behavior?
Applying a mask to a password type input field initially displays the field populated dots. These dots erroneously indicate to the user that something has been entered in the field.
What is the expected behavior?
A password type input field should initially display the underscores representing each digit in the mask.
The text was updated successfully, but these errors were encountered:
Applying a mask to a password type input field confuses the user
Use case:
We're trying to apply a mask to field that accepts a PIN number. The PIN number should be hidden from onlookers as the user types, so we use a password type input field. We want to limit the user to entering exactly 6 digit and only digits. The mask is perfect for this (paired with a validation).
What is the current behavior?
Applying a mask to a password type input field initially displays the field populated dots. These dots erroneously indicate to the user that something has been entered in the field.
What is the expected behavior?
A password type input field should initially display the underscores representing each digit in the mask.
The text was updated successfully, but these errors were encountered: