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
The motivation behind introducing a mask property was to allow entering passwords, and those are usually masked with * or empty string for obvious reasons. I see that in the most places I've seen password inputs, cursor is hidden, so I just rolled with the same behavior :)
For my use-case, I have an input for a masked API token which is one step in a form with a series of different inputs. Some are text inputs, some are select inputs, but in all cases, there's some kind of indicator indicating what the user needs to do (an indicator next to a select option, a cursor in a text input, etc.). The one exception is the masked API token field since showCursor=true doesn't enable the cursor.
Ideally a cursor could be shown to indicate that the input is "focused" and ready to accept text, otherwise there's no visual clues and the user may end up confused about what to do (short of me adding placeholder text, but I'd rather prefer consistency).
I noticed that
showCursor
appears to not work if amask
is set. Seems that functionality was explicitly guarded against:ink-text-input/src/index.js
Line 53 in 6c5b29d
Just curious if there's a specific reason for hiding the cursor in this case? :)
The text was updated successfully, but these errors were encountered: