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

[HOLD for payment 2023-06-23] [HOLD for payment 2023-06-21] [$1000] mWeb - Chat - Cancel button must be pressed two times #20682

Closed
2 of 6 tasks
kbecciv opened this issue Jun 13, 2023 · 25 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor

Comments

@kbecciv
Copy link

kbecciv commented Jun 13, 2023

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


Issue found when executing PR #20082

Action Performed:

  1. Open http://staging.new.expensify.com/
  2. Log in
  3. Enter the chat with somebody
  4. Edit message and change text
  5. Close keyboard
  6. Click the cancel button

Expected Result:

Cancel button must be pressed one time

Actual Result:

Cancel button must be pressed two times

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

Reproducible in staging?: yes

Reproducible in production?: no

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

Bug6091370_Screen_Recording_20230613_170710_Chrome.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01163231d12c885dff
  • Upwork Job ID: 1668684207716220928
  • Last Price Increase: 2023-06-13
@kbecciv kbecciv added the DeployBlockerCash This issue or pull request should block deployment label Jun 13, 2023
@OSBotify
Copy link
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.

@melvin-bot
Copy link

melvin-bot bot commented Jun 13, 2023

Triggered auto assignment to @thienlnam (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@HezekielT
Copy link
Contributor

HezekielT commented Jun 13, 2023

Proposal

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

Chat’s cancel button must be pressed twice to close it.

What is root cause of that problem?

It was introduced by #20082. The PR removed nativeID for cancel button while migrating the component to pressable feedback.

So when we click on the cancel button, the edit input loses focus and inside onBlur method we have the following condition which fails because the cancel button doesn’t have the native id meaning the onPress event of the cancel button will not be called as shown below.

// Return to prevent re-render when save/cancel button is pressed which cancels the onPress event by re-rendering
if (_.contains([this.saveButtonID, this.cancelButtonID, this.emojiButtonID], relatedTargetId)) {
return;
}

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

Add nativeID={this.cancelButtonID} in PressableWithFeedback of cancel button.

<PressableWithFeedback
onPress={this.deleteDraft}
style={styles.chatItemSubmitButton}

What alternative solutions did you explore? (Optional)

@thienlnam
Copy link
Contributor

Thanks for the proposal @HezekielT - solution looks good to me and tests well. Could you get a PR up?

@thienlnam thienlnam added the External Added to denote the issue can be worked on by a contributor label Jun 13, 2023
@melvin-bot melvin-bot bot changed the title mWeb - Chat - Cancel button must be pressed two times [$1000] mWeb - Chat - Cancel button must be pressed two times Jun 13, 2023
@melvin-bot
Copy link

melvin-bot bot commented Jun 13, 2023

Job added to Upwork: https://www.upwork.com/jobs/~01163231d12c885dff

@melvin-bot
Copy link

melvin-bot bot commented Jun 13, 2023

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

@melvin-bot
Copy link

melvin-bot bot commented Jun 13, 2023

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav (External)

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Jun 13, 2023
@melvin-bot
Copy link

melvin-bot bot commented Jun 13, 2023

Current assignee @thienlnam is eligible for the External assigner, not assigning anyone new.

@melvin-bot melvin-bot bot removed the Help Wanted Apply this label when an issue is open to proposals by contributors label Jun 13, 2023
@melvin-bot

This comment was marked as off-topic.

@HezekielT
Copy link
Contributor

@thienlnam Yes, I will do that now.

@HezekielT
Copy link
Contributor

@thienlnam PR is ready for review.

@thienlnam thienlnam removed the DeployBlockerCash This issue or pull request should block deployment label Jun 13, 2023
@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Daily KSv2 labels Jun 14, 2023
@melvin-bot melvin-bot bot changed the title [$1000] mWeb - Chat - Cancel button must be pressed two times [HOLD for payment 2023-06-21] [$1000] mWeb - Chat - Cancel button must be pressed two times Jun 14, 2023
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Jun 14, 2023
@melvin-bot
Copy link

melvin-bot bot commented Jun 14, 2023

Reviewing label has been removed, please complete the "BugZero Checklist".

@melvin-bot
Copy link

melvin-bot bot commented Jun 14, 2023

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.27-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

If no regressions arise, payment will be issued on 2023-06-21. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

  • External issue reporter
  • Contributor that fixed the issue
  • Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

  • Merged PR within 3 business days of assignment - 50% bonus
  • Merged PR more than 9 business days after assignment - 50% penalty

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Jun 16, 2023
@melvin-bot melvin-bot bot changed the title [HOLD for payment 2023-06-21] [$1000] mWeb - Chat - Cancel button must be pressed two times [HOLD for payment 2023-06-23] [HOLD for payment 2023-06-21] [$1000] mWeb - Chat - Cancel button must be pressed two times Jun 16, 2023
@melvin-bot

This comment was marked as duplicate.

@maddylewis maddylewis added Daily KSv2 and removed Weekly KSv2 labels Jun 20, 2023
@maddylewis
Copy link
Contributor

moving to daily since payment is coming up!

@melvin-bot melvin-bot bot added Daily KSv2 Overdue and removed Daily KSv2 labels Jun 21, 2023
@maddylewis
Copy link
Contributor

apologies for the delay! reviewing this one now.

@melvin-bot melvin-bot bot removed the Overdue label Jun 26, 2023
@maddylewis
Copy link
Contributor

maddylewis commented Jun 26, 2023

Payments:

@maddylewis
Copy link
Contributor

payments sent - is there anything else needed on this one before I close it out?

@HezekielT
Copy link
Contributor

@maddylewis am i not eligible for the timeline bonus?

@allroundexperts
Copy link
Contributor

@maddylewis This was merged the same day so the bonus is applicable here.

@maddylewis
Copy link
Contributor

shoot - i wish you would've mentioned being eligible for a reporting bonus when i listed out the payment amounts here - #20682 (comment)

to clarify, @HezekielT was assigned on June 13 and the PR was merged on June 16, correct?

@HezekielT
Copy link
Contributor

@maddylewis It was merged on June 14.

@maddylewis
Copy link
Contributor

sent bonuses!

@HezekielT
Copy link
Contributor

@maddylewis Thank you!

@maddylewis
Copy link
Contributor

payments sent - i think we're all set here? closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor
Projects
None yet
Development

No branches or pull requests

7 participants