| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Bug: 8152758
Change-Id: Ida05df7d151ceb582886e2ad06c5bdf0b59978ee
|
|
|
|
| |
Change-Id: I4e1e4f101050ebda77c629a61c548d3c8efb330f
|
|
|
|
|
|
|
|
| |
It's probably cleaner to just pass the events rather than read
them from a transaction, especially when a transaction may be
associated with several events in a chain.
Change-Id: I27830f0f3f3f32fe77ea8b9cad505b7ebee648af
|
|
|
|
|
|
|
| |
Do away with the didAutoCorrect local variables which are
unnatural to return out of all these functions.
Change-Id: I22024004d2c489de018beff812c2c589bfd8ca32
|
|
|
|
| |
Change-Id: I503c5403dcaea5db632eba85ae3fae9ba9a1f946
|
|
|
|
| |
Change-Id: I1619f6132f8f71bc1291fd6a5604a5e1e3431ae2
|
|
|
|
| |
Change-Id: Ia866d3f9a5981c687766f8c39979fb6091018e44
|
|
|
|
| |
Change-Id: I5f7932097627766e907764a99a5e9c170f725bc0
|
|
|
|
|
|
| |
The 'processedEvent' variables will ultimately disappear entirely.
Change-Id: I612c5ce7dedc341b64921a86ac028fe91b75359b
|
|
|
|
| |
Change-Id: I18021b7ec1588fc52533c48b7d8774bec7764822
|
|
|
|
|
|
| |
...take 2
Change-Id: I9d13b6d51e13ce2e76ae3febebfb8c310eba509d
|
|
|
|
|
|
|
|
| |
This reverts commit 1db3d860ca0d7380c5a6a3a0f95751565f23043b.
Reverting due to a few critical bugs and unit test failures.
Change-Id: I5e2d02300320438ef9c29577ec5b0860ea91d822
|
|
|
|
|
|
| |
If anyone has better names for those...
Change-Id: Ia2dfc75381816bd688948647e2c50c10657b9e89
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Bug: 15318007
Change-Id: Ic0268fd12865c9a692a5e7110a9beb76cb8b6d7f
|
|
|
|
|
| |
Bug: 15758242
Change-Id: I703dc2703afdf9402c5d2ac27411b74ece993dba
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I66ed277751272eb3ae2fd5e55e9f3e413970082f
|
|\| |
|
| |
| |
| |
| | |
Change-Id: I5436432c0da86ed1e33b3c9d40204f4ea013ff55
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| | |
When switching languages, we need to wait until the dictionary is
loaded to compute suggestions.
Change-Id: I7c32a900b297cd6302bfdc020842581315f3007f
|
|/
|
|
|
|
|
| |
...also implement the check for Hebrew and Arabic.
Bug: 15840116
Change-Id: Ia6433d7d98038ade64c171be4fe4b3f094111fac
|
|
|
|
|
| |
Bug: 15840116
Change-Id: I1123426fbd9d420c1be64ccc917a5f870e70e6fa
|
|
|
|
|
|
|
| |
This reverts commit 1d300239612591879d535c20ade1f2712048170e that broke the build.
Bug: 15840116
Change-Id: I0a5fa7dea2b418d19df24b2b31ed96bf192d45c0
|
|
|
|
|
| |
Bug: 15840116
Change-Id: Ib3380cfc9d343c6f8953bba03af3801142bc3bdb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...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
|
|
|
|
|
| |
Bug: 15840116
Change-Id: If2073e76fed74ae6e1cdd7670013e0e985b0e630
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Bug: 14425059
Change-Id: Ieace636334a9b2a094527341d4fcfc05958296c5
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With hardware events, we do have some events that
have both a keycode and a code point, so we need
a better way of distinguishing between auto-insert
keystrokes and others.
Change-Id: Ia23042989b4dca9d3a7d4a4c06bcebdabe324a7a
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
Bug: 14425059
Change-Id: I2bd6a872904a44b80f638a13d91a97559217cc1a
|
| |
| |
| |
| |
| | |
Bug: 15740318
Change-Id: Idad06cb2c18335a981d5e9dea7eccf5e7ea8f701
|
|/
|
|
|
|
|
|
| |
Also, this double tests for CODE_SPACE in the path going through
maybeDoubleSpacePeriod, but that's temporary.
Bug: 15740318
Change-Id: I0a6ace09cc791f0009157d3017675b9b3eb92145
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Bug: 15555552
Bug: 15552347
Change-Id: Ia4d8c79d079e3ce233d46d4bbad4fff1be5c5c39
|
|/
|
|
|
| |
Bug: 15709298
Change-Id: I1b3fff3152960d85060149727d7a3422fea8a0bd
|
|
|
|
|
|
|
|
| |
We need to update them after separator-space, and also when
the user presses shift and they are displayed.
Bug: 15554503
Change-Id: I5596163d5cd94d3cc5f6af10a1ab2cc74b6d4279
|
|
|
|
|
| |
Bug: 15554503
Change-Id: If5e8c0d94ed26d929400ccbb0d45ac23dd98d180
|
|
|
|
|
|
|
|
| |
This member has outlived its usefulness. It's not clear now that it
makes things really faster, but it does bring a lot of complexity
that we can avoid by removing it.
Change-Id: Ifbc8094a45b56b958fe165b1930f4cc358a97721
|
|
|
|
|
|
|
|
|
| |
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
| |
Change-Id: I434cf507e68349b9893ac084645986d6b3d7da91
|
|
|
|
|
| |
Bug: 13283555
Change-Id: Iab0466425dc44779d110f2cd29d725d22eb04827
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
This fixes PunctuationTests#
testAutoCorrectionWithSingleQuotesAround.
Bug: 14119293
Bug: 15334309
Change-Id: I604c21a21e89a5fc431fd56ab7b6ad03f4736b01
|
|
|
|
|
|
|
| |
At 100k text, it's reasonably fast (less than 1s on latest hardware).
Bug: 12913404
Change-Id: I426b918b2610af24364934a1c37a7314f1142ad0
|