You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-02-24] Web - Chat - Unable to select all text in the composer via CMD+A or double clicking #82465
changed the title [-]Web - Chat - Unable to select all text in the composer via CMD+A or double clicking[/-][+][Due for payment 2026-02-24] Web - Chat - Unable to select all text in the composer via CMD+A or double clicking[/+]on Feb 17, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.20-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@situchan@jliexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Feb 13, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (
External)melvin-bot commentedon Feb 13, 2026
Triggered auto assignment to @jliexpensify (
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.melvin-bot commentedon Feb 13, 2026
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.
melvin-bot commentedon Feb 13, 2026
Triggered auto assignment to @dangrous (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Feb 13, 2026
💬 A slack conversation has been started in #expensify-open-source
18 remaining items
[-]Web - Chat - Unable to select all text in the composer via CMD+A or double clicking[/-][+][Due for payment 2026-02-24] Web - Chat - Unable to select all text in the composer via CMD+A or double clicking[/+]melvin-bot commentedon Feb 17, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Feb 17, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.20-6 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 2026-02-24. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Feb 17, 2026
@situchan @jliexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
jliexpensify commentedon Feb 23, 2026
ANy checklist needed @situchan ?
situchan commentedon Feb 23, 2026
BugZero Checklist:
[Contributor] 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: Fix: "Attachment can't be downloaded" error when downloading receipt #81652 (comment)
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Already exists
https://test-management.browserstack.com/projects/2219752/test-runs/TR-5255/folder/13176681/41236977/1189841643?issue_type=jira
Do we agree 👍 or 👎
jliexpensify commentedon Feb 23, 2026
Upworks job - https://www.upwork.com/jobs/~022025792042868576109
jliexpensify commentedon Feb 23, 2026
Invited you @situchan
jliexpensify commentedon Feb 27, 2026
Paid and job closed!