-
Notifications
You must be signed in to change notification settings - Fork 3k
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 2024-10-24] [$250] Forward delete moves cursor location after deleting a character #48797
Comments
Triggered auto assignment to @jliexpensify ( |
Triggered auto assignment to @youssef-lr ( |
Can this issue be assigned to me ? Looks like something i can contribute to |
📣 @BreakTos! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
In the video shared, the Delete key is erasing characters to the right of the cursor, which I also tested and found to be true. I believe this is the expected behavior. |
The video is recorded on Windows, not MacOS. |
I'm not sure we've established that this is unexpected behavior here |
The bug description is incorrect. It is not deleting the character before the cursor, which would be unexpected for forward delete. It is deleting the character after (expected), but then advancing the cursor one position to the left (unexpected). The expected behavior is that the cursor remains where it is after the character to the right is deleted. Reported here for macOS too. |
Happy to take over this issue @youssef-lr, I will be joining the NewDot Quality and ECM chores very soon. |
@tgolen, @youssef-lr, @jliexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Sounds good, thanks Matt |
@rafecolton, @jliexpensify, @QichenZhu, @ishpaul777 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
Not overdue. PR was recently merged, waiting for this change to be deployed. |
Hi @rafecolton - just a heads up I'm OOO from 3rd to 14th, so I will prep a Payment Summary. If needed, feel free to reassign to another BZ for payment.
|
@jliexpensify you can assign to me for payment, if needed. When you post payment summaries, can you use the below format? For auditing purposes we need to know where someone is being paid (Upwork vs NewDot) and also if they're due/owed funds are 'paid'. Thx |
Will do in the future, thanks @mallenexpensify! |
unfortunately, E/react-native-live-markdown version bump was reverted because of unrelated changes to our issue, we have new PR #50047 for second try 🤞 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.49-2 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-10-24. 🎊 For reference, here are some details about the assignees on this issue:
|
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:
|
whoohooo... it's fixed!! Thx |
Hi @ishpaul777 - do we need a checklist here? |
i could not find PR that introduce this bug, But i think we need regression tests for this. Regression Test Proposal:
Do we agree 👍 or 👎 |
Sounds great, thank you! Definitely agree we need one - while we were waiting for the fix to get merged, the issue actually got worse somehow |
Payment Summary
New Upworks Job - the other one closed automatically so please accept my offers here, thanks! |
Paid and job closed! |
@rafecolton @mallenexpensify @jliexpensify Be sure to fill out the Contact List! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.31-0
Reproducible in staging?: Y
Reproducible in production?: Y
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
Expensify/Expensify Issue URL:
Issue reported by: @tgolen
Slack conversation: https://expensify.slack.com/archives/C05LX9D6E07/p1725900088874679
Action Performed:
Delete
button on the keyboardExpected Result:
Pressing the delete key should delete characters after the cursor, then the cursor should remain in its current opsition.
Actual Result:
Pressing the delete key is deleting characters before the cursorAfter deleting the character after the cursor (expected), the cursor advances one character to the left (unexpected).Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Recording.528.mp4
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mallenexpensify / @jliexpensifyThe text was updated successfully, but these errors were encountered: