diff options
| author | guohui@chromium.org <guohui@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-07-18 03:09:52 +0000 |
|---|---|---|
| committer | guohui@chromium.org <guohui@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-07-18 03:09:52 +0000 |
| commit | 25402eb26f2f05b5105523057f06532eaac58764 (patch) | |
| tree | 89b572f0b95925a55a481b871a6065c47417e311 /content/common | |
| parent | 3b67224783df5f125242a411578dbb97a26ed8fd (diff) | |
| download | chromium_src-25402eb26f2f05b5105523057f06532eaac58764.zip chromium_src-25402eb26f2f05b5105523057f06532eaac58764.tar.gz chromium_src-25402eb26f2f05b5105523057f06532eaac58764.tar.bz2 | |
Send the real key code in deleteSurroundingText
On android, when user presses DEL or FORWARD_DEL using IME, Chrome generates key events with 0 keycode. This breaks lots of websites who count on having the real keycode in the key event listeners, especially for the control keys such as DEL and FORWARD_DEL.
This CL fixes the issue for the most common case when a single char is deleted. Instead of triggering deleteSurroudingText path with synthetic key events of key code 0, Chrome sends native key events with real key code.
BUG=118639
Review URL: https://codereview.chromium.org/393933004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283989 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/common')
0 files changed, 0 insertions, 0 deletions