| Issue 343: | Chinese Sogou input method lose first initial letter | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Product Version : 0.2.149.27 (1583)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 3: OK
Firefox 3: OK
IE 7: OK
What steps will reproduce the problem?
1. launch Sogou Pinyin Chinese Input Method
2. Type some pinyin, especially right after some existing English letters
to get a Chinese character
What is the expected result?
After each letter is typed, the input method pad will show some Chinese
letters to choose from.
What happens instead?
The first letter will show on the screen instantly and the pinyin sequence
starts from the second letter and therefore produce a wrong Chinese
character. It seems the browser kill the input method pad right after the
first letter is typed. But it does not kill the input method pad for the
second or third letter.
Please provide any additional information below. Attach a screenshot if
possible.
|
||||||||||||||||||||
,
Sep 03, 2008
Thank you for your bug report. Even though I assume this issue is caused by Chrome that it accidentially receives an input-focus change after you type the first character, I cannot reproduce this issue on my PC with sogou IME. Is it possible to give me more detailed information about your environment so that I can reproduce this issue? For example, Windows message logs captured with spy++, the version number of sogou IME and Windows, etc. Sorry for your inconvenience. |
|||||||||||||||||||||
,
Sep 04, 2008
I tried Sougo IME 3.1, MSIME 2007, Unispim IME 6.1 and Google IME, can't reproduce this issue. But I do hear from someone saying that he met this issue also, he installed both English and Chinese IME on his computer, after switch from English to Chinese using "Shift + Alt" very quickly, this issue happened. However, I still can't reproduce it.
Cc: js...@chromium.org hb...@chromium.org xly...@chromium.org
|
|||||||||||||||||||||
,
Sep 29, 2008
(No comment was entered for this change.)
Labels: -area-unknown Area-Misc
|
|||||||||||||||||||||
,
Nov 11, 2008
(No comment was entered for this change.)
Cc: thatan...@google.com tak...@google.com
Labels: I18N I18N-jp |
|||||||||||||||||||||
,
Nov 11, 2008
<b/1109582> |
|||||||||||||||||||||
,
Nov 12, 2008
Thank you for your updates and sorry for my lazy responses. Our testing person noticed we could reproduce this problem with GMail as listed below. What steps will reproduce the problem? 1. Make sure your default keyboard is Chinese, Japanese, or Korean. 2. Close all Chrome instances. 3. Open Chrome. 4. Open GMail and log it in. 5. Open an existing mail. 6. Click [Reply]. -> The caret is moved to the reply input box. If it is not RICH-TEXT mode but plain text mode, switch it to RICH-TEXT and start over from step #1. 7. Type some characters. To investigate this problem, it seems to be caused by our IME code which does not filter out false focus events raised by IME functions of WebKit. (The WebCore::setComposition() function may raise a false focus event.) I have written a workaround that ignores such false events and been testing on my PC. When I confirm this change does not cause any regressions, I'm going to send a review request and submitted to trunk. Sorry again for your inconvenience.
Status: Started
Owner: hb...@chromium.org |
|||||||||||||||||||||
,
Nov 14, 2008
http://codereview.chromium.org/10827/show will fix this bug. Hironori, I think it's good to have this in for 1.0. Although 1.0 code freeze was last weekend, your fix seems simple and safe enough. What do you think? If you agree, will you ask Mark to merge your patch to the branch after it's landed in the trunk and baked there for a while.
Cc: m...@chromium.org
|
|||||||||||||||||||||
,
Nov 17, 2008
Thank you for your suggestion. I have submitted the workaround (r5556) to trunk. I wish it fixes this issue. Also, I have sent a merge request for this workaround.
Status: Fixed
|
|||||||||||||||||||||
,
Dec 03, 2008
Verified on build 0.4.154.31 (Official Build 6264), fixed.
Status: Verified
|
|||||||||||||||||||||
,
Dec 04, 2008
Also verified on 0.4.154.31 with ATOK2008 on XP SP2. |
|||||||||||||||||||||
| ► Sign in to add a comment | |||||||||||||||||||||
