Korean(non-English) characters are input weirdly on Firefox browser or Edge.
See original GitHub issueHi, this is Terry Lee.
My application is objected for Korean.
For your information, single Korean character is composited of each partial character. (that is not friendly to the non-Korean)
I tested typing Korean characters on your official example site on Firefox (v63.0 62bit), but there is strange thing on input text : when I typed next character, it seems that input occurs twice (unwanted appending).
For other browsers : So does edge browser. Chrome broswer is working well.
If I use AutosizeInput
component in 'react-select` individually, there’s no problem.
Does anyone guess what problem is?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
I have problems in displaying Korean characters. | Firefox ...
My Mozilla used to show Korean characters till last week, but now it displays them in shape of squares with tiny numbers.
Read more >javascript - Regular expression to match non-ASCII characters?
I would like to match all words individually in an input string, but the language may not be English, so I will need...
Read more >Korean or Japanese IME composition may not work correctly ...
When you input Korean (Hangul) characters on a contentEditable element by using Korean IME, a composition string may be committed unexpectedly. When you...
Read more >Display Problems - Unicode
If you are unable to read some Unicode characters in your browser, it may be because your system is not properly configured.
Read more >internet explorer chan characters
A page for describing Characters: I Made A Comic About Internet Explorer. ... We say you will this kind of Microsoft Edge Chan...
Read more >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
Should be fixed by #3442 (not released yet, will be soon)
Thanks for raising this issue @starrybleu . This is resolved as part of #3563 which has since been merged and published. Please update to the latest version react-select to see this in effect.