Issue metadata
Sign in to add a comment
|
The data property in compositionupdate event should contain all the marked text
Reported by
siul...@gmail.com,
Dec 9 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36 Steps to reproduce the problem: 1. Type Japanese or Simplified Chinese pinyin in the text box. What is the expected behavior? The "compositionupdate data" should always be the entire marked text. What went wrong? The "compositionupdate data" is the last character typed. Say if you type "t" and then "e", it shows just "e". Did this work before? Yes M54 Does this work in other browsers? Yes Also reproducible with Chrome version: 55.0.2883.75 Channel: stable OS Version: OS X 10.12.0 Flash Version: Shockwave Flash 23.0 r0
,
Dec 12 2016
,
Dec 13 2016
Tested this issue on Mac OS 10.12 using chrome latest stable M55-55.0.2883.87 by following steps mentioned below. 1. Changed system language and keyboard language to Japanese 2. Navigated to compositionupdate.html 3. Typed 't' and then 'e' in the text box 4. Observed the text got converted to 'て' siulung@ - Could you please confirm is the above mentioned steps is the right way to reproduce this issue? If yes, observed similar behavior on firefox as well. Could you please provide the screen-shot of actual and expected behavior of this issue for better understanding. Attaching scree-cast for reference, please have a look on it and let us know if anything missing from our end. Thanks!
,
Dec 13 2016
Ah sorry, I should have mentioned that if you are using Japanese, you need to type two separate hiragana characters, say "a" "i". In this case, we should get "compositionupdate data: あい" but got only "compositionupdate data: い".
,
Dec 15 2016
Are you able to look at this?
,
Dec 15 2016
Thanks for the report! This issue was introduced in M55 and fixed in M57 (e.g. Current Canary). Also see https://crbug.com/620549#c22
,
Jan 6 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by kkaluri@chromium.org
, Dec 12 2016