-
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
iOS - Status - Cursor jumps behind the minutes after entering hour #40930
Comments
Triggered auto assignment to @muttmuure ( |
We think that this bug might be related to #vip-vsb |
@muttmuure FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributor. |
ProposalPlease re-state the problem that we are trying to solve in this issue.iOS - Status - Cursor jumps behind the minutes after entering hour What is the root cause of that problem?The selection is correctly set to the start but when the we focus on the input the caret is placed at the end, I think that this is the default behaviour in iOS devices. I also tested on other inputs and the behaviour is the same, no matter what is the current selection position, on initial focus the caret will be placed at the end. What changes do you think we should make in order to solve the problem?To resolve this issue, we can set the selection to any value when the hour input is focused. This will resolve the issue because if we focus on the minute input after the hour input, the selection will be Optionally we can hide the care when the selection is What alternative solutions did you explore? (Optional)N/A Before fixbefore_fix.mp4After fixafter_fix.mp4 |
@muttmuure Huh... This is 4 days overdue. Who can take care of this? |
Not a priority |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.65-0
Reproducible in staging?: y
Reproducible in production?: y
Issue found when executing PR: #40390
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The digit will jump to the next value.
Actual Result:
The digit jumps to the end of minutes.
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6460120_1713956450728.RPReplay_Final1713956117.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: