Bug: cjk words are composed in an incorrect way on iOS devices
See original GitHub issueLexical version: 0.3.9
Steps To Reproduce
- Visit playground.lexical.dev from iOS device.
- Enter something in Korean or any other cjk character.
Link to code example:
The current behavior
- It composes a Korean word in an incorrect way.
- For example, when you type
ㅇ
and thenㅣ
, it should be이
, but it becomesㅇ이
. - In addition, if there is a character following it, the character is deleted.
- For example, when you type
The expected behavior
- It composes a word in a correct way.
- It doesn’t delete a character following it.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looking into this more, it actually has nothing to do with composition. It’s because we aren’t handling the
deleteContentBackward
event properly here with Safari. I’ll have a fix up later today.Not at all, I’ll take a deep dive into this issue when I’m back from parental leave. 😃