-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Fix suggestion list cursor bug #67720
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
Merged
chiragsalian
merged 13 commits into
Expensify:main
from
LorenzoBloedow:suggestion-list-fix
Nov 10, 2025
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
51392fa
Fix suggestion list selection not moving cursor to the end
LorenzoBloedow 993ee29
Remove outdated comment
LorenzoBloedow 2499af2
Merge branch 'main' of https://github.com/Expensify/App into suggesti…
LorenzoBloedow e826fe2
Merge branch 'main' of https://github.com/Expensify/App into suggesti…
LorenzoBloedow bf9b9f6
Merge branch 'main' of https://github.com/Expensify/App into suggesti…
LorenzoBloedow aee0e6c
Merge branch 'main' of https://github.com/Expensify/App into suggesti…
LorenzoBloedow 0b90afb
Revert "Remove outdated comment"
LorenzoBloedow b941385
Revert "Fix suggestion list selection not moving cursor to the end"
LorenzoBloedow bddb177
Override current cursor position on suggestion selection
LorenzoBloedow 7c12234
Merge branch 'main' of https://github.com/Expensify/App into suggesti…
LorenzoBloedow 42df889
Merge branch 'main' of https://github.com/Expensify/App into suggesti…
LorenzoBloedow ff7fe0e
Merge branch 'main' of https://github.com/Expensify/App into suggesti…
LorenzoBloedow 5f63341
Fix crash due to null textInputRef being called when selecting from s…
LorenzoBloedow File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you clarify why do we have these changes? this might cause regressions on ios Native
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's because setting the cursor imperatively is what's causing the bug and, in general, declarative is how you should use these props. As you mentioned here the bug that made us use imperative handling in the first place doesn't seem to be present anymore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry but i didn't interpret this from you proposal, i thought we were just going to pass selection prop in and tested that only while checking proposal surprisingly that only seems to working, but since we are removing this also I'll test this more and get back ASAP!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you talking about the changes regarding removing the imperative handling? If so, I think that was my mistake actually, I forgot to mention we should also remove it, sorry about that. I think removing the imperative handling is better since we don't need it anymore, but we can try just passing the prop and not removing the other code, I'm pretty sure both ways work at the moment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so i noticed a bug when randomly putting cursor it adds random spaces in between
Screen.Recording.2025-09-01.at.12.15.57.AM.mov
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok so i checked that this is reproducible on main as well, and only reproducible on Hybrid app so i guess not related to the PR, will continue testing
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@LorenzoBloedow i have founce another bug while testing this on IOS it seems when adding a emoji from keyboard there is no space added at end while it did add on main
main:
Screen.Recording.2025-09-28.at.1.24.01.AM.mov
this branch:
Screen.Recording.2025-09-28.at.1.26.11.AM.mov
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also it would be very much appreciate if we can track blame history and list all issue for which this imperative handling is added or modified and test each one to make sure its not reproducible anymore, Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any updates? @LorenzoBloedow
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm testing without removing the imperative handling.