- Jun 10, 2014
-
-
Keisuke Kuroyanagi authored
Change-Id: Ib0150b3306bb2db8aff443d1158fecc8464cbbdb
-
- Jun 06, 2014
-
-
Tadashi G. Takaoka authored
-
Keisuke Kuroyanagi authored
-
Tadashi G. Takaoka authored
The logic to determine when the suggestions strip (a.k.a. the contextual strip) should be shown is already complex. In addition to that the voice input key get shown on the strip as well. There are a several factors to be considered and a few things to control. - The password input field shouldn't have the strip. - Show voice input key on the strip or not. - User preference settings "Show Voice Input Key". - A voice IME exists and is enabled. - The input field may have a private IME option to prevent the voice input key from being displayed. - Application can specify auto completions. - Full screen mode or not. - User preference settings "Show correction suggestions". - Always show, Show in portrait mode, Always hide. - The input field may have flags to prevent showing suggestions or auto corrections. - Suggestions is empty or not. - An important notice may be shown. Bug: 14981852 Bug: 15436479 Change-Id: I3050fd53ee6271fc64a8f17b6b12d9581d37b750
-
Keisuke Kuroyanagi authored
Bug: 13142176 Bug: 15428247 Change-Id: I5c23fbea2851f891f76f19d9da2cb70ae964569b
-
Keisuke Kuroyanagi authored
-
Keisuke Kuroyanagi authored
Bug: 13142176 Bug: 15428247 Change-Id: I5be6d683be95505412615ca7c88260de1ea05f54
-
Tadashi G. Takaoka authored
Bug: 15310025 Change-Id: I2fa267e5c448e28435f4737666a03b40f1f4a4d5 (cherry picked from commit 0621dd1d)
-
Jean Chalard authored
-
Tadashi G. Takaoka authored
-
Jean Chalard authored
This change also includes a fix that has suggestions re-computed when the typed word is included but no prior suggestions were found in spans. Bug: 2349475 Change-Id: Ic06e6ac492507126ffc1e96a5f396c971b567272
-
Jean Chalard authored
-
Jean Chalard authored
Bug: 2349475 Change-Id: Id4aa5ce56b1a545e4cb88ca1b01cf24642deade2
-
Tadashi G. Takaoka authored
Bug: 15128166 Change-Id: Ie15724c323efa3b102f6aebddc3bda210aad1727
-
Tadashi G. Takaoka authored
Change-Id: I51c5247ac925a158facb79057f704b763b903552
-
Tadashi G. Takaoka authored
-
Tadashi G. Takaoka authored
Change-Id: I849cec7deb5607e8ce8fb25c1f903f15328fb611
-
Jean Chalard authored
-
Jean Chalard authored
The symptom : when text is selected and the device is rotated, sometimes the keyboard sets the word as being composed around the start of the selection. Upon the next rotation this ends up with the keyboard committing some text in place of the selection. The cause : another bug in the framework with rotation >.> The keyboard receives a call to startInput with a wrong cursor position, namely one that does not represent a selection. The keyboard sets a composition according to this wrong data. When the keyboard is rotated again, it commits the text, which takes the place of the selection. The solution : actually when restarting input the keyboard realizes that the cursor position is wrong. We cancel composition at that time. For robustness, this change also implements two other defensive changes : upon call to onUpdateSelection, we actually realize that the previous values were wrong, so we also fix it at that time, and in addition, when rotating, we finishComposingText() instead of commitText() which is less dangerous. Implementing this later change also allows us to let less internal variables from InputLogic escape to LatinIME, so it's also a good change for design. Bug: 14140799 Change-Id: Ib10de18e53e376ac1bbc8487e13d969828483346
-
- Jun 05, 2014
-
-
Keisuke Kuroyanagi authored
-
Keisuke Kuroyanagi authored
Bug: 13142176 Bug: 15428247 Change-Id: I93b44ef40cafb6b811c68fa79f3a4971fc3916a5
-
Tadashi G. Takaoka authored
-
Tadashi G. Takaoka authored
-
Tadashi G. Takaoka authored
Change-Id: I434cf507e68349b9893ac084645986d6b3d7da91
-
Keisuke Kuroyanagi authored
Bug: 13142176 Bug: 15428247 Change-Id: I2ae25090b67ad0c6df97dec7712e2f7e0bb08c40
-
Tadashi G. Takaoka authored
Change-Id: I4f13e85a3db1ba4adf36c596cb23827bdcf93ae7
-
- Jun 04, 2014
-
-
Jean Chalard authored
-
Tadashi G. Takaoka authored
Bug: 12491371 Change-Id: Ib01452b6a2a53faa591b05e62014f356e0511308
-
Tadashi G. Takaoka authored
-
Tadashi G. Takaoka authored
Bug: 12491371 Change-Id: Ib1fc8affbccfbaca3424ecdc2812f47047106aa2
-
Jean Chalard authored
Bug: 13869301 Change-Id: Icd77a308f85cc16dccffe65a532471c738d6fbc5
-
Tadashi G. Takaoka authored
-
Tadashi G. Takaoka authored
Bug: 12491371 Change-Id: I8c5b1e91f41146a023edcc405e6120c0bf33f49b
-
Jean Chalard authored
-
Jean Chalard authored
-
Jean Chalard authored
Bug: 13283555 Change-Id: Iab0466425dc44779d110f2cd29d725d22eb04827
-
Jean Chalard authored
Rename `initialize' to `start' and `deactivate' to `stop' for ease of understanding. It's completely bizarre that you can "deactivate" a recapitalization and that will just restart a new one the next time you press shift. Start and stop are easier to understand. Change-Id: I455175aebfcfe11198c6c61bf2c6b19efc3f82df
-
Tadashi G. Takaoka authored
-
Tadashi G. Takaoka authored
It turns out passing hover event to accessibility key handling methods isn't necessary. This parically reverts I1f7feef707. Bug: 12491371 Change-Id: I9d71cd29723344433427795e44cb22ac41faace6
-
Yohei Yukawa authored
-