Skip to content

[HOLD FOR PAYMENT 9/26]Expense - Nothing happens when hitting Enter on amount page #49368

Closed

Description

@IuliiaHerets

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: 9.0.37-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+kh010901@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Click + > Submit expense > Manual.
  4. Enter amount.
  5. Hit Enter.

Expected Result:

Enter key will proceed to next step.

Actual Result:

Nothing happens when hitting Enter on amount page.

Workaround:

Unknown

Platforms:

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6607106_1726613695588.743766129871136314420240918_044316.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 18, 2024
  2. melvin-bot commented on Sep 18, 2024

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. melvin-bot commented on Sep 18, 2024

    @melvin-bot

    Triggered auto assignment to @iwiznia (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. github-actions commented on Sep 18, 2024

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. IuliiaHerets commented on Sep 18, 2024

    @IuliiaHerets
    Author

    We think that this bug might be related to #wave-collect - Release 1

  6. luacmartins commented on Sep 18, 2024

    @luacmartins
    Contributor

    Pretty sure it came from this PR #49023 @suneox @alitoshmatov

  7. nkdengineer commented on Sep 18, 2024

    @nkdengineer
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Task title is overlapped by task arrow

    What is the root cause of that problem?

    The input has the role is CONST.ROLE.PRESENTATION and we don't exclude it here. It happens after this PR

    const shouldDisableEnterShortcut = useMemo(() => accessibilityRoles.includes(activeElementRole ?? ''), [activeElementRole]);

    What changes do you think we should make in order to solve the problem?

    We should return shouldDisableEnterShortcut as false if the activeElementRole is CONST.ROLE.PRESENTATION as we did in the past like the diff in this PR

    const shouldDisableEnterShortcut = useMemo(() => accessibilityRoles.includes(activeElementRole ?? '') && activeElementRole !== CONST.ROLE.PRESENTATION, [activeElementRole]);
    

    const shouldDisableEnterShortcut = useMemo(() => accessibilityRoles.includes(activeElementRole ?? ''), [activeElementRole]);

    OPTIONAL: We can exclude other roles if this role is not a pressable element.

    What alternative solutions did you explore? (Optional)

    NA

  8. nkdengineer commented on Sep 18, 2024

    @nkdengineer
    Contributor

    @luacmartins This comes from this #49316.

  9. 7 remaining items

  10. nkdengineer commented on Sep 18, 2024

    @nkdengineer
    Contributor

    @luacmartins The PR is ready.

  11. melvin-bot commented on Sep 18, 2024

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  12. mountiny commented on Sep 19, 2024

    @mountiny
    Contributor

    this was fixed but we forgot to remove the label I believe

  13. CortneyOfstad commented on Sep 23, 2024

    @CortneyOfstad
    Contributor

    PR was deployed to production 4 days ago — updating the title!

  14. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    ReviewingHas a PR in review
    on Sep 23, 2024
  15. changed the title [-]Expense - Nothing happens when hitting Enter on amount page[/-] [+][HOLD FOR PAYMENT 9/26]Expense - Nothing happens when hitting Enter on amount page[/+] on Sep 23, 2024
  16. CortneyOfstad commented on Sep 27, 2024

    @CortneyOfstad
    Contributor

    @nkdengineer — offer sent to you here in Upwork — please let me know once you accept and I'll get that paid ASAP. Thanks!

  17. nkdengineer commented on Sep 30, 2024

    @nkdengineer
    Contributor

    @CortneyOfstad I accepted thanks

  18. CortneyOfstad commented on Oct 1, 2024

    @CortneyOfstad
    Contributor

    Payment Summary

    @nkdengineer — paid $250 via Upwork

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions