-
Notifications
You must be signed in to change notification settings - Fork 233
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
Selection glitch in SuperTextField when IME is used #905
Comments
@miguelcmedeiros Could you enable the |
@angelosilvestre
This is only a small portion of the log. It seems that super_editor is sending |
@miguelcmedeiros Could you also attach |
@miguelcmedeiros I'll investigate those logs tonight. Don't worry about it. |
I'm starting to investigate this. One thing I'm noticing is that, on my end, placing the caret in What does trigger the problem is a rapid selection across characters. I'm wondering if the problem might be due to frame scheduling on our end. We run various things, like selection changes, in post-frame callbacks. I'll continue digging. |
Experimentally, I found that #876 seems to fix the After taking inventory of #876 the following seem like possible candidates for why it fixed this problem:
|
… TextEditingValue to the IME (Resolves #905)
The root cause of the issue in |
… TextEditingValue to the IME (Resolves #905)
@matthew-carroll, when using the latest commit from In the demo app (SuperTextField demo), it also show the same issue if the implementation is changed to use Screen.Recording.2023-01-10.at.11.47.16.movThis infinite-caret-jumping now happens when the content changes. |
…superlistapp#905)" This reverts commit 0a6c784.
…superlistapp#905)" This reverts commit 0a6c784.
…superlistapp#905)" This reverts commit 0a6c784.
… TextEditingValue to the IME (Resolves superlistapp#905) (superlistapp#910)
The selection in
SuperTextField
jumps between old and current selection as shown in this recording:Screen.Recording.2023-01-02.at.13.07.27.mov
This is reproducible in demo app ("SuperTextField" -> "Interactive demo"). If
TextInputSource.keyboard
is used instead, then the issue is not reproducible.The text was updated successfully, but these errors were encountered: