-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Passcode input misbehaving #3342
Comments
Some device/vendor dependency here. I tested with: Pixel2 Android11 and not reproducible. In any case, the custom view implementation could be productive and interesting. |
I tested again, I can reproduce this on any device. |
Now reproduced correctly with all devices. Touches must not be allowed in the passcode gaps. |
Maybe we should talk about redesigning the whole passcode activity in general. @michaelstingl what do you think? |
Why? Currently it's not an urgency? Let's check Monday morning… |
For the moment, I will fix this by making the fields not selectable. A redesign of this activity could be addressed in another issue. |
Actual behaviour
Pin code input behaves janki when one of the EditText fields is selected and its Value gets deleted.
Expected behaviour
EditText field should not be select at all. They should only indicate how much of the pin code was entered so far. The delete button should only delete the last entered digit.
Steps to reproduce
Additional information
pincode_fail.mp4
Proposed fix
Maybe it is useful if we wrote our own custom view for the pin input. It should not be hard as no input must be processed by it.

Here a possible mock up:
TASKS
The text was updated successfully, but these errors were encountered: