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

Taxes - Tax amount input in transaction thread is not auto-focused #39601

Closed
6 tasks done
kbecciv opened this issue Apr 4, 2024 · 10 comments
Closed
6 tasks done

Taxes - Tax amount input in transaction thread is not auto-focused #39601

kbecciv opened this issue Apr 4, 2024 · 10 comments
Assignees
Labels
Engineering Reviewing Has a PR in review Weekly KSv2

Comments

@kbecciv
Copy link

kbecciv commented Apr 4, 2024

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.60-1
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

  • User is an employee of Collect workspace that has taxes.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Start manual request flow.
  4. In confirmation page, click Show more > Tax amount.
  5. Note that Tax amount input is auto focused.
  6. Create the request with tax.
  7. Go to transaction thread.
  8. Click Tax amount.

Expected Result:

Tax amount input in transaction thread will be auto focused.

Actual Result:

Tax amount input in transaction thread is not auto focused.

Workaround:

n/a

Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6437921_1712233909903.tax_amount_focus.mp4

View all open jobs on GitHub

@kbecciv kbecciv added the DeployBlockerCash This issue or pull request should block deployment label Apr 4, 2024
Copy link

melvin-bot bot commented Apr 4, 2024

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

Copy link
Contributor

github-actions bot commented Apr 4, 2024

👋 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.

@kbecciv
Copy link
Author

kbecciv commented Apr 4, 2024

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

@rlinoz
Copy link
Contributor

rlinoz commented Apr 4, 2024

I think this is related to this PR #33927 since it is a new feature.

cc: @alitoshmatov @rezkiy37

@rlinoz
Copy link
Contributor

rlinoz commented Apr 4, 2024

But we don't have to block on this, so removing the label.

@rlinoz rlinoz added Daily KSv2 and removed DeployBlockerCash This issue or pull request should block deployment labels Apr 4, 2024
@ZhenjaHorbach
Copy link
Contributor

ZhenjaHorbach commented Apr 4, 2024

Proposal

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

Taxes - Tax amount input in transaction thread is not auto-focused

What is the root cause of that problem?

The main problem with the issue is that when we pass ref we can't get value from textInput because by default our ref is null

} else if (forwardedRef?.current) {
// eslint-disable-next-line no-param-reassign
forwardedRef.current = ref;
}

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

To fix this issue we can make logic from others' screen and pass like

ref={(e) => (textInput.current = e)}

Or we can update this condition and make null is available value ( or just ignore only undefined )

} else if (forwardedRef?.current) {

What alternative solutions did you explore? (Optional)

NA

@MonilBhavsar
Copy link
Contributor

We'll be fixing this as a regression

@MonilBhavsar MonilBhavsar removed the Hourly KSv2 label Apr 4, 2024
@teneeto
Copy link
Contributor

teneeto commented Apr 4, 2024

Hi, I'm Eto from Callstack - expert contributor group - and I would like to take care of this issue.

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 labels Apr 5, 2024
@MonilBhavsar MonilBhavsar self-assigned this Apr 5, 2024
@MonilBhavsar
Copy link
Contributor

PR is merged!

@rlinoz
Copy link
Contributor

rlinoz commented Apr 12, 2024

Deployed to production: #39675 (comment)

So I am closing this one.

@rlinoz rlinoz closed this as completed Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Engineering Reviewing Has a PR in review Weekly KSv2
Projects
None yet
Development

No branches or pull requests

5 participants