Bug 605475 - Can't type word in chrome after backspace
Can't type word in chrome after backspace
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: ibus-pinyin (Show other bugs)
12
All Linux
low Severity high
: ---
: ---
Assigned To: Peng Wu
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-18 01:09 EDT by Caspar Zhang
Modified: 2013-07-03 03:24 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-22 22:24:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Caspar Zhang 2010-06-18 01:09:44 EDT
Description of problem:
In Chrome, after I pressed backspace or up/down/left/right key, I can't type any words
in text field, unless I press "shift" to turn ibus-pinyin to English mode or turn off the 
IME then switch on again. This problem appears only in Google Chrome, I haven't
seen it in other applications.

Version-Release number of selected component (if applicable):
ibus-devel-1.3.3-1.fc12.i686
ibus-libs-1.3.3-1.fc12.i686
ibus-pinyin-db-open-phrase-1.3.6-1.fc12.noarch
ibus-gtk-1.3.3-1.fc12.i686
ibus-pinyin-1.3.6-1.fc12.i686

How reproducible:
100%

Steps to Reproduce:
1. Open Google Chrome and a website(such as google.com), turn on ibus-pinyin, type some words in text field.
2. press "backspace" or left key
3. try to type a word again.
 
Actual results:
Can't type words

Expected results:
It should be able to type words normally.

Additional info:
Comment 1 Peng Huang 2010-06-18 03:57:59 EDT
This problem has been fixed in upstream. I will build it soon.
BTW, the beta chrome browser does not have this problem.
Comment 2 Peng Wu 2010-07-22 22:24:48 EDT
ibus 1.3.9 is released for Fedora 12/13, please upgrade ibus-pinyin and ibus.
This issue seems fixed.
Close bug.

Note You need to log in before you can comment on or make changes to this bug.