- Aug 13, 2014
-
-
Tadashi G. Takaoka authored
Bug: 13988700 Change-Id: If23f8a14097431e76a303a6d6c24e8d9835fb655 (cherry picked from commit 3659c70f)
-
- Aug 12, 2014
-
-
Tadashi G. Takaoka authored
Bug: 13988700 Change-Id: I215e879ad33b149370c1d0a5fdcf2203c0fc8b4a (cherry picked from commit 34541bfe)
-
Tadashi G. Takaoka authored
Bug: 13988700 Change-Id: I4aeb01bf3571afc97959c213474a6424d7896120 (cherry picked from commit 06514f00)
-
- Aug 08, 2014
-
-
Keisuke Kuroyanagi authored
Bug: 13142176 Bug: 15531638 Change-Id: I89cef5264073eed25ffb5be10fdff731df0a3138
-
- Aug 06, 2014
-
-
Ken Wakasa authored
This reverts commit ef74e737. Apparently, this CL broke several unit tests. Change-Id: I86cf5f1ffb0214707afe99ee97f92ba8c5157f3f
-
Jean Chalard authored
...and prepare for the future Change-Id: Ieed96ab552993fd148e80b9c3355f1b569bd716f
-
Jean Chalard authored
This reverts commit f1accd4f. Bug: 16830599 Change-Id: I4c9367f742b8ee8463920e91263b05c2195f8480
-
Jean Chalard authored
This reverts commit 93b00a31. Bug: 16830599 Change-Id: I955e7da77978c3a495660aa29247e010d489c36b
-
Jean Chalard authored
Change-Id: Ie703e14bff42d34608f11d0c2d7758950b84c88c
-
Jean Chalard authored
Bug: 8152758 Change-Id: Ida05df7d151ceb582886e2ad06c5bdf0b59978ee
-
- Aug 05, 2014
-
-
Jean Chalard authored
Do away with the didAutoCorrect local variables which are unnatural to return out of all these functions. Change-Id: I22024004d2c489de018beff812c2c589bfd8ca32
-
- Aug 04, 2014
-
-
Jean Chalard authored
Bug: 8152758 Change-Id: Ic57d3918b08e775769d4ba5d73ba5c31231e0d6a
-
- Jul 27, 2014
-
-
Tadashi G. Takaoka authored
Formerly "Show correction suggestions" had three options, "always show", "show in portrait mode", and "always hide". The reason behind "show in portrait mode" was that there may not be enough screen estate in landscape mode to show suggestions. Because recent phone devices have relatively large screen, we decide to remove "show in portrait mode" option. Bug: 15780939 Change-Id: I896d737452c3893d43ce20bd88127f10c1eb3d83
-
- Jul 29, 2014
-
-
Tadashi G. Takaoka authored
Bug: 15813742 Change-Id: I8b1feb5c35377e62199e5a909640d9c50f970654
-
- Jul 28, 2014
-
-
Jean Chalard authored
This would wrongly emit a 'timeout' log entry when switching between two instances of the same language. Change-Id: I56e5de121b87f3e762b58f0b2a77e9abc784036e
-
- Jul 20, 2014
-
-
Yohei Yukawa authored
With this CL, InputMethodService#onUpdateCursor and InputMethodService#onUpdateCursorAnchorInfo can be enabled on L when ENABLE_CURSOR_ANCHOR_INFO_CALLBACK and ENABLE_CURSOR_RECT_CALLBACK are specified, respectively. BUG: 16382260 Change-Id: I29924128f6bd2f08cbd91cc4e82c9c4a6ecce3ff
-
- Jul 17, 2014
-
-
Tadashi G. Takaoka authored
Change-Id: I5da2dbf8828fa0e176e7c2496392a5f561ebfe20
-
Tadashi G. Takaoka authored
Bug: 15318007 Change-Id: Ic0268fd12865c9a692a5e7110a9beb76cb8b6d7f
-
- Jul 01, 2014
-
-
Jean Chalard authored
Change-Id: I66ed277751272eb3ae2fd5e55e9f3e413970082f
-
Jean Chalard authored
Change-Id: I5436432c0da86ed1e33b3c9d40204f4ea013ff55
-
Jean Chalard authored
Change-Id: I303ce084a56c6ec709d3eab239a4d9d2274d0dea
-
- Jun 30, 2014
-
-
Jean Chalard authored
...otherwise we can't recompute the composition when we change scripts. This also fixes when we register that we need to take note that the current subtype was used. Luckily this is a good occasion for some cleanup that I've wanted to do for some time: use InputTransaction for onTextInput (with the goal to ultimately remove it entirely) Bug: 15840116 Change-Id: Ie4f4f9157b66b79237eeb3db75535803124d3e19
-
- Jun 27, 2014
-
-
Jean Chalard authored
Bug: 15840116 Change-Id: If2073e76fed74ae6e1cdd7670013e0e985b0e630
-
- Jul 01, 2014
-
-
Jean Chalard authored
When switching languages, we need to wait until the dictionary is loaded to compute suggestions. Change-Id: I7c32a900b297cd6302bfdc020842581315f3007f
-
- Jun 27, 2014
-
-
Jean Chalard authored
...for any given input. This is not necessarily the best fix, but it's simple and it works well enough. Bug: 15869703 Change-Id: I54b262be8bdbec37031dea655c60a5573b3d8ec3
-
- Jun 16, 2014
-
-
Keisuke Kuroyanagi authored
Bug: 14161647 Change-Id: Ic7d53464bd051bffc8c7f8d097325321fe0aaee7
-
Jean Chalard authored
Bug: 15554503 Change-Id: If5e8c0d94ed26d929400ccbb0d45ac23dd98d180
-
- Jun 13, 2014
-
-
Keisuke Kuroyanagi authored
Bug: 14161647 Change-Id: I8106419678d5d26a4debec7bbef43af079c1ab18
-
Keisuke Kuroyanagi authored
Bug: 14161647 Change-Id: I7ab3d701525e9a19bc100aa577527e332bb2ad95
-
- Jun 11, 2014
-
-
Tadashi G. Takaoka authored
Bug: 15531465 Change-Id: Ic7fe5743ad3767cdaed699e5e2d1ebcaa75e22c2
-
- Jun 09, 2014
-
-
Jean Chalard authored
We don't need the optimization of storing the old words now that the RichInputConnection can supply it without IPC. Bug: 13703802 Change-Id: I37ccb8d5fba879fb04b4f23d33571849736d897c
-
Keisuke Kuroyanagi authored
Bug: 13142176 Bug: 15428247 Change-Id: I7ce2c09ebbef6ca8c056807c2a35f2f987fd436e
-
- Jun 06, 2014
-
-
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
-
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
Bug: 2349475 Change-Id: Id4aa5ce56b1a545e4cb88ca1b01cf24642deade2
-
Tadashi G. Takaoka authored
Bug: 15128166 Change-Id: Ie15724c323efa3b102f6aebddc3bda210aad1727
-
Tadashi G. Takaoka authored
Change-Id: I51c5247ac925a158facb79057f704b763b903552
-
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
-
-
Tadashi G. Takaoka authored
Change-Id: I434cf507e68349b9893ac084645986d6b3d7da91
-
- May 29, 2014
-
-
Tadashi G. Takaoka authored
This CL must be checked in together with Ie52007dc5c. Bug: 15318007 Change-Id: Ie665f296e43b5485ae8ba7e949aa262794ee0dcc
-