Chromium Code Reviews| Index: content/public/android/java/src/org/chromium/content/browser/input/ImeAdapter.java |
| diff --git a/content/public/android/java/src/org/chromium/content/browser/input/ImeAdapter.java b/content/public/android/java/src/org/chromium/content/browser/input/ImeAdapter.java |
| index c27a60f74288dd191dd1ba43228c7840c143e1b4..7d25e13aad60d5d020b4fe73ba5290f60e161575 100644 |
| --- a/content/public/android/java/src/org/chromium/content/browser/input/ImeAdapter.java |
| +++ b/content/public/android/java/src/org/chromium/content/browser/input/ImeAdapter.java |
| @@ -433,12 +433,9 @@ public class ImeAdapter { |
| KeyEvent.changeAction(keyEvent, KeyEvent.ACTION_UP), 0); |
| } |
| - // If we do not have autocomplete=off, then always send compose events rather than a |
| - // guessed keyCode. This addresses http://crbug.com/422685 . |
| - if ((mTextInputFlags & WebTextInputFlags.AutocompleteOff) == 0) { |
| - keyCode = COMPOSITION_KEY_CODE; |
| - modifiers = 0; |
| - } |
| + // Always send compose events. This is a quick fix for http://crbug.com/476497. |
| + keyCode = COMPOSITION_KEY_CODE; |
| + modifiers = 0; |
|
jdduke (slow)
2015/07/14 16:42:32
Are there any plans to fix this? Are we OK always
huangs
2015/07/14 16:57:44
This is the debate between two view points:
A: Th
|
| // When typing, there is no issue sending KeyDown and KeyUp events around the |
| // composition event because those key events do nothing (other than call JS |