Skip to content

[HOLD for payment 2024-04-09] [$500] Composer defocuses when editing parent message in thread #38878

Closed

Description

@kbecciv

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.56-0
Reproducible in staging?: y
Reproducible in production?: n
Issue found when executing PR: #37566
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com.
  2. Go to any chat.
  3. Send a message containing inline image markdown. Example:
    An inline image and some text off
  4. Right click on the message > Edit comment.
  5. Focus the cursor anywhere in the editor.
  6. Note that the composer will not defocus.
  7. Right click on the message > Reply in thread.
  8. Right click on the parent message > Edit comment.
  9. Focus the cursor anywhere in the editor.

Expected Result:

The composer will not defocus.

Actual Result:

The composer defocuses when editing message with inline image mark down in thread.

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

Bug6424058_1711173003900.20240323_134637.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~012dd2062cbe841507
  • Upwork Job ID: 1772340169085984768
  • Last Price Increase: 2024-03-25
  • Automatic offers:
    • jjcoffee | Reviewer | 0
    • bernhardoj | Contributor | 0

Activity

  1. github-actions commented on Mar 23, 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.
  2. melvin-bot commented on Mar 23, 2024

    @melvin-bot

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

  3. kbecciv commented on Mar 23, 2024

    @kbecciv
    Author

    We think that this bug might be related to #vip-bills

  4. amyevans commented on Mar 25, 2024

    @amyevans
    Contributor

    This is related to a new feature and also pretty minor so not worth considering a blocker.

    @kidroca do you have bandwidth to take this on and fix as polish? If not I can open it up to external proposals. cc @situchan @marcaaron

  5. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Mar 25, 2024
  6. amyevans commented on Mar 25, 2024

    @amyevans
    Contributor

    Hmm actually I'm going to walk back my comment that it's related to the Image Markdown PR, I think it was just incidental that it was discovered during QA there. I can reproduce the bug on main with that PR reverted, and I can also reproduce on a comment that does not include image markdown.

    Will continue to investigate...

  7. situchan commented on Mar 25, 2024

    @situchan
    Contributor

    Agree, I am not convinced why composer focus behavior is related to image MD.

  8. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Mar 25, 2024
  9. changed the title [-]Image MD - Composer defocuses when editing message with inline image mark down in thread[/-] [+][$500] Image MD - Composer defocuses when editing message with inline image mark down in thread[/+] on Mar 25, 2024
  10. 29 remaining items

  11. changed the title [-][$500] Composer defocuses when editing parent message in thread[/-] [+][HOLD for payment 2024-04-09] [$500] Composer defocuses when editing parent message in thread[/+] on Apr 2, 2024
  12. melvin-bot commented on Apr 2, 2024

    @melvin-bot

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

  13. melvin-bot commented on Apr 2, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.58-8 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 2024-04-09. 🎊

    For reference, here are some details about the assignees on this issue:

  14. melvin-bot commented on Apr 2, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@jjcoffee] The PR that introduced the bug has been identified. Link to the PR:
    • [@jjcoffee] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@jjcoffee] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@jjcoffee] Determine if we should create a regression test for this bug.
    • [@jjcoffee] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@isabelastisser] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  15. isabelastisser commented on Apr 9, 2024

    @isabelastisser
    Contributor

    @jjcoffee please complete the list above. Thanks!

  16. isabelastisser commented on Apr 9, 2024

    @isabelastisser
    Contributor

    The payments were processed in Upwork.

    Waiting for @jjcoffee to complete the BZ list before this can be closed.

  17. jjcoffee commented on Apr 10, 2024

    @jjcoffee
    Contributor

    Regression Test Proposal

    1. Send a message to any chat
    2. Right-click and reply in thread to the message
    3. Right-click and edit the thread parent message
    4. Tap anywhere in the message
    5. Verify that the focus on the composer isn't lost

    Do we agree 👍 or 👎

  18. isabelastisser commented on Apr 10, 2024

    @isabelastisser
    Contributor

    Hi @amyevans, do you agree that we should create the regression test with the steps above? Thanks!

  19. amyevans commented on Apr 10, 2024

    @amyevans
    Contributor

    @isabelastisser I think since the bug was caught during normal regression testing by Applause, it means that adding an explicit test case for this would be unnecessary. However if you want to be safe you can always open a GH for it and let Isabella make that call!

  20. isabelastisser commented on Apr 10, 2024

    @isabelastisser
    Contributor

    Thanks for the context, Amy! I agree and will close it then.

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions