-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Input: A method for obscuring sensitive data by default with user reveal method #4098
Comments
Similar patterns might be...
Can you get design to take a look at this @inforandy ? |
@tmcconechy Any ETA on this? |
Going to slot it in for next sprint and see if some designers can be wrangled. I think its a quick design question? I think we should just put an icon in the field at the far left (right on RTL) that you press down to show the password. Problem is we do not have a suitable icon i can think of (reveal/show?). What about a text/hide show button. Thinking something like this... What do you think @kevinwhitedesign @inforandy ? |
Lets implement this as:
|
Is your feature request related to a problem or use case? Please describe.
Per our internal security department, sensitive PII data should be obscured rather than openly display on web pages. Some examples of this date are social security numbers, bank account numbers, drivers license numbers. etc.
Describe the solution you'd like
The recommendation is displaying these with a * similar to password type and allow a way for the user to view the data,,, either by hovering the mouse over the field, an icon for temp reveal, or clicking an icon for permanent reveal while the page is still loaded.
This should ideally support both inputs and display areas like spans/etc.
Describe alternatives you've considered
Implementing this field by field is possible. But, a feature built-into the framework would prevent duplication.
Additional context
Add any other context or screenshots about the feature request here.
And what application do you work on? [e.g. {Infor XYZ}]
The text was updated successfully, but these errors were encountered: