Korean character break-up issue on a third party search engine on the search bar shortcut.
Reported by
wschd...@gmail.com,
Jan 17
(6 days ago)
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome (new page or new tab). 2. Type 'naver.com' or 'daum.net' on the search bar. 3. Then press Tab button to convert the default search to third party search engine. 4. Type in any Korean word longer than 1 syllable. 5. Issue occurs on the first character / syllable. What is the expected behavior? Complete characters for words. What went wrong? The issue occurs when a user searches on a third party's search engine other than the Google's via search bar shortcut. The phenomenon is the breakup of the first combination of vowels and consonants (which makes it a character). This only happens in the first character of the vowel-consonant combination; the next characters form just okay. In my opinion, this issue occurs due to the difference in space; one Korean character takes up 2 bytes while one English alphabet takes up 1 byte. Did this work before? No Chrome version: 71.0.3578.98 Channel: stable OS Version: 10.0 Flash Version:
,
Jan 18
(4 days ago)
Tried testing the issue on reported chrome version #71.0.3578.98 using Windows 10 by following below steps. Steps: ===== 1.Launched chrome. 2.Navigated to 'naver.com'. 3.Clicked Tab button, observed "naver.com" did not become default browser. 4.Navigated to "chrome://settings". 5.Under manage search engines added "naver.com". 6.Tried making it as default browser, observed that there is no option to make it as default. Note: Tried same with "daum.net", observed same results as above. Attached screencast for reference. @reporter: Could you please review attached screencast and let us know if anything is missed from our end. If possible requesting you to provide screencast of the issue so that it would be really helpful for further triaging of the issue. Thanks.!
,
Jan 19
(3 days ago)
Yes. I also added the video about the occuring issue. The Korean character should not breakup when the combination of vowels and consonants exist in the first character. So it means that the word in the video 'ㅇㅏㄴ녕하세요?' should be typed like '안녕하세요?' and of course the first character here should be '안' not 'ㅇㅏㄴ'.
,
Jan 19
(3 days ago)
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by vamshi.kommuri@chromium.org
, Jan 17 (5 days ago)