-
Notifications
You must be signed in to change notification settings - Fork 67
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
Weird autocorrect behavior: #28
Comments
Interestingly this doesn't happen on new documents. |
Yeah, I'm not sure how to reproduce this. I booted up a simulator and when I typed "I", "m" and space, it autocorrected to I would recommend:
If none of that works, please provide:
|
@kyle-n this is on a simulator: https://youtu.be/lOoK9TifNKo our app is targeting everything, but the bug is only experienced on ios / ipados -- where autocorrection is enabled. I used the text of my bug report. I said before that this doesn't happen on new documents, I think this is incorrect, I think this doesn't happen at the edges of a document, but happen in the middle of a new document as well. |
Awesome, that video did the trick. I can reproduce in the UIKit editor with these steps:
The editor handles autocorrect correctly when typing at the end of the editor's current content, but not when typing anywhere else. I will investigate and try to figure out what's happening here. 👍 |
I'm not sure what change did it, but I can no longer reproduce this bug using the the steps to reproduce I laid out. @Parth are you still seeing this? If not, I'll close this Sunday. |
Describe the bug
On my phone, typing
Im
into aTextEditor
will highlight the text and suggest the wordI'm
as an autocorrect replacement. If I tap spacebar it'll accept the suggestion, and put my cursor overI'm |
<-- here.In this library if I tap
Im
it will auto correct toI'|m
after which tapping the spacebar (the normal behavior) I'll be in this state:I' m
. For my use case turningautocorrectionType(.off)
would be a disappointment.I can try to capture a video if you have trouble reproducing this.
The text was updated successfully, but these errors were encountered: