Skip to content
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

Input rendering is deferred after auto-correction in Safari 17.2.1 #1119

Closed
packagethief opened this issue Jan 12, 2024 · 0 comments · Fixed by #1129
Closed

Input rendering is deferred after auto-correction in Safari 17.2.1 #1119

packagethief opened this issue Jan 12, 2024 · 0 comments · Fixed by #1129

Comments

@packagethief
Copy link
Member

In the latest version of Safari (17.2.1), input rendering can be deferred until the next input after Safari has performed an auto-correction of entered text.

Steps to Reproduce

  1. Using Safari 17.2.1, visit https://trix-editor.org and clear all existing text from the editor.
  2. Ensure that Safari's auto-correct option is enabled (Edit > Spelling & Grammar > Correct Spelling Automatically).
  3. In the editor, press Return once to insert a new blank line.
  4. On the next line, enter some text that will be auto-corrected, like the lowercase letter "i", then press Return. Observe that "i" is auto-corrected to the capital "I".
  5. On the new line, enter any single character. Observe that the character is not rendered.
  6. Enter another single character. Observe that both characters are now rendered.

Demo

trix-safari-input.mov

Details

  • Browser name and version: Safari 17.2.1
  • Operating system: macOS 14.2.1 (23C71)
afcapel added a commit that referenced this issue Feb 1, 2024
The insertReplacementText text comes from an autocorrected word. If we
don't request a render, the cursor will be in the wrong place and the
document doesn't update until the user types another character.

Fixes #1119
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant