Repository navigation
[Due for payment 2025-02-13] [$250] Pasting data in chat puts the cursor in the wrong position #40025
Description
Reported here https://expensify.slack.com/archives/C049HHMV9SM/p1712763627228909
Happening on staging but not on prod.
Steps:
- Copy some text
- Paste it in the chat box
- Cursor is at the beginning of the line, but it should be at the end
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~0166be7baac5afe84f
- Upwork Job ID: 1780997931107999744
- Last Price Increase: 2025-01-14
- Automatic offers:
- QichenZhu | Contributor | 105706923
Issue Owner
Current Issue Owner: @RachCHopkinsMetadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
melvin-bot commentedon Apr 10, 2024
Triggered auto assignment to @rlinoz (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Apr 10, 2024
Triggered auto assignment to @miljakljajic (
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.github-actions commentedon Apr 10, 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:
iwiznia commentedon Apr 10, 2024
Seems I can't reproduce it anymore 🤷
Julesssss commentedon Apr 10, 2024
Thank fuck for that
lanitochka17 commentedon Apr 18, 2024
Issue is still reproducible on the latest build 1.4.63-0
mWeb/Chrome
cursorled.mp4
100 remaining items
[-][$250] Pasting data in chat puts the cursor in the wrong position[/-][+][Due for payment 2025-02-13] [$250] Pasting data in chat puts the cursor in the wrong position[/+]melvin-bot commentedon Feb 6, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Feb 6, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.94-25 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 2025-02-13. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Feb 6, 2025
@jjcoffee @RachCHopkins @jjcoffee 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]
jjcoffee commentedon Feb 13, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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: https://github.com/Expensify/react-native-live-markdown/pull/450/files#r1954219567
[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
Precondition:
Test:
Do we agree 👍 or 👎
RachCHopkins commentedon Feb 14, 2025
Payment Summary:
Upwork job here
RachCHopkins commentedon Feb 14, 2025
Contributor has been paid, the contract has been completed, and the Upwork post has been closed.
garrettmknight commentedon Feb 19, 2025
$250 approved for @jjcoffee