Skip to content
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

Closed
4 of 7 tasks
theScrabi opened this issue Aug 10, 2021 · 7 comments · Fixed by #3365
Closed
4 of 7 tasks

Passcode input misbehaving #3342

theScrabi opened this issue Aug 10, 2021 · 7 comments · Fixed by #3365

Comments

@theScrabi
Copy link
Contributor

theScrabi commented Aug 10, 2021

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

  1. enable Pin code
  2. open Pin Code Acitivity
  3. enter half of the pin code
  4. select one of the input fields
  5. hit the delete button

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:
Screenshot_1628587277

TASKS

  • Create branch fix/select_passcode_fields
  • Development tasks
    • Make passcode fields not selectable
  • Code review and apply changes requested
  • Design test plan
  • QA
  • Merge branch fix/select_passcode_fields into master
@jesmrec
Copy link
Collaborator

jesmrec commented Aug 11, 2021

Some device/vendor dependency here. I tested with:

Pixel2 Android11
Huawei P20 Android9
Nexus6P Android7

and not reproducible. In any case, the custom view implementation could be productive and interesting.

@theScrabi
Copy link
Contributor Author

I tested again, I can reproduce this on any device.

@jesmrec
Copy link
Collaborator

jesmrec commented Aug 11, 2021

Now reproduced correctly with all devices. Touches must not be allowed in the passcode gaps.

@michaelstingl michaelstingl added this to the backlog milestone Aug 17, 2021
@michaelstingl michaelstingl added the p4-low Low priority label Aug 17, 2021
@michaelstingl michaelstingl modified the milestones: backlog, 2.20-next Aug 17, 2021
@theScrabi
Copy link
Contributor Author

Maybe we should talk about redesigning the whole passcode activity in general. @michaelstingl what do you think?

@michaelstingl
Copy link
Contributor

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…

@JuancaG05
Copy link
Collaborator

For the moment, I will fix this by making the fields not selectable. A redesign of this activity could be addressed in another issue.

@JuancaG05 JuancaG05 self-assigned this Aug 31, 2021
@JuancaG05 JuancaG05 changed the title Pincode input missbehaving Passcode input misbehaving Aug 31, 2021
@JuancaG05 JuancaG05 linked a pull request Aug 31, 2021 that will close this issue
1 task
@abelgardep
Copy link
Contributor

Already merged into #3361 so it will be tested as part of #3354 PR

@jesmrec jesmrec modified the milestones: 2.20-next, 2.19-current Sep 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants