Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1137 by wanghz: Wrong behavior at Firefox 4b7 with Google Instant
enabled
http://code.google.com/p/ibus/issues/detail?id=1137
What version of the product are you using? On what operating system?
OS (Linux distributions, UNIX or ...): Debian unstable
Architecture (i386, x86_64): i386
IBus version: 1.3.8-1
Input method name and version: ibus-pinyin 1.3.11-1 & ibus-sunpinyin 2.0.2-1
Python version: python 2.6.6
dbus version: 1.2.24-3
dbus-python version: 0.83.1-1
gtk version (if bug is about gtk applications): 2.20.1-2
qt version (if bug is about qt applications):
What steps will reproduce the problem?
1. Open Google.com with Firefox 4 beta7 and make sure Google Instant is
enabled
2. Turn on Chinese input method and make sure Embed preedit text in
application window
3. Input an arbitrary Chinese word, for example "guo jia"
What is the expected output? What do you see instead?
As we all know, Google Instant will immediately response as you type in the
Chinese word's pinyin. The sudden pop-up of the search box of Google will
force the first available candidate corresponding to the pinyin you input
be selected and actually input while the waiting-for-selection status of
the Chinese input method is still there. As a result, when you select the
desired candidate of your pinyin now, there will be two "guo jia" get input
to the search box of Google. Specifically, suppose the first candidate
of "guo jia" is "国家" and the desired one is "郭家". Then what Google
search box actually gets is "国家郭家". With sunpinyin, a different but
still wrong behavior can be observed.
With Google Chrome, the thing changes. With Google Instant enabled, the
pop-up of the search box of Google will just forcely select the Latin
characters of the pinyin, and when you eventually select the desired
candidate of the pinyin the input to the search box will be totally rewrite
with the corresponding Chinese word. So there is no big problem.
Furthermore, if the search box of Google has already pop-up to the top of
the window (the normal status when Google Instant has responded), the
problem reported above does not exist any more. So, it is the pop-up of
the search box that causes the bug.
Please provide any additional information below.
Since Firefox 4 beta is reaching feature frozen, I believe it is a little
bit urgent to fix the problem. Although it seems to me that the bug is due
to Firefox itself, the investigation by ibus community will be more
effective and efficient.
--
You received this message because you are subscribed to the Google
Groups "ibus-devel" group.
iBus project web page: http://code.google.com/p/ibus/
iBus dev group: http://groups.google.com/group/ibus-devel?hl=en
