Arrow next to year is not working properly

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Open your profile.
2. Click on "Personal Details".
3. Click on " Date of Birth ".
4. Click on the " Calender " field.
5. Click on the arrow next to year.
6. Both arrow and year is selected.
7. Notice normally clicking on the arrow next to the month increases or decreases the month value. However, when the arrow next to the year is clicked, options appear instead of jumping to the next year.

Expected Result

Clicking on the arrow next to the year should increase the year value by jumping to the next year by pressing the ">" button.

Actual Result

Instead of jumping to the next year, options appear to select a year.

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.2.91-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Recording.92.mp4

20230329_205758.mp4

Expensify/Expensify Issue URL:
Issue reported by: Posted in slack
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1680105522998849

View all open jobs on GitHub

[MelvinBot]

Triggered auto assignment to @maddylewis (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[kavimuru]

Seems it's by design #15343. Closing this issue.

[MelvinBot]

@maddylewis Eep! 4 days overdue now. Issues have feelings too...

[maddylewis]

#16712 (comment)

closing