-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[lexical-rich-text][lexical-plain-text] workaround for Korean IME issue on iOS #6819
[lexical-rich-text][lexical-plain-text] workaround for Korean IME issue on iOS #6819
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
size-limit report 📦
|
Co-authored-by: wnhlee <[email protected]>
33ba318
to
e317974
Compare
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.
This seems pretty low risk given the isolation to just iOS+Korean, I don't have any experience with IMEs so I can't really provide any guidance for what a proper fix would be and I am not even sure I could test it very easily (I couldn't get the korean IME to work in the iOS simulator, it never combines characters for me, and on my phone I don't think it would be very easy for me to have navigator.langauge set to korean)
Co-authored-by: Bob Ippolito <[email protected]>
The only failing tests is a very flaky one (that is improved in #6759) so I'm going to merge |
Description
related to #5841, #3305.
based on #4814,
isCollapsed
handling.while we don't have
e2e-ios
tests, I checked the fix withoutif (navigator.language === 'ko-KR' && IS_IOS)
passed tests on my local.please include @DeadIntegral as a co-author since it contains his work.
Closes #4814
Test plan
Before
ScreenRecording_11-13-2024.00-51-43_1.mov
After
ScreenRecording_11-13-2024.00-48-57_1.MOV