| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | | |
Bug: 13231889
Change-Id: If64b7422967c3e4107c845072b64a7bb26a35f7e
|
| | |
| | |
| | |
| | |
| | |
| | | |
It may just return null.
Change-Id: I778fb48262ef8af28a4af50b70bb94ace75a488c
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 6867914
Change-Id: Ibc329c8ea03abaa91ba27e7e62fb6d02cc67debe
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | | |
Bug: 13215163
Change-Id: I00099cb4927c96de46e57e14ab906d41c9c2151a
|
|/ /
| |
| |
| |
| |
| |
| | |
This is actually a follow up of I9290974821.
Bug: 13215075
Change-Id: Ib7eef55fd1cfbb05d06aeeb0726bc10c87b07d85
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This CL is a ground work to add keyboard layout labels and more keys
tests.
Bug: 13017434
Change-Id: Ief028e8ab563d79bc0b0f9c06f1fe1d645a6469d
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 13197276
Change-Id: I206cf4e599ca9cdf40d669358a1067a2954d11e3
|
|\| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 13197276
Change-Id: I80311a51d9e98bfeb8c0dd9cd4adde93af366d54
|
|\ \ \ \ |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | | |
Bug: 13197276
Change-Id: I23f453c2c1deea70eab552f8d433fe264adf68b3
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
...and make a method private.
Bug: 8636060
Change-Id: If16f7e8ef3779f77a9db23fb7c54e7c23b043b86
|
|\ \ \ \ \
| |/ / / /
|/| | / /
| | |/ /
| |/| | |
|
| |/ /
| | |
| | |
| | |
| | | |
Bug: 13197276
Change-Id: I6c38a127e1745903594b7bf0ec80ef179e794feb
|
|/ /
| |
| |
| |
| | |
Bug: 13062385
Change-Id: I426545d1fe8fd76bcf4d1dce19e6b571a55c79ae
|
| |
| |
| |
| |
| | |
Bug: 10385162
Change-Id: Icf9471d474a3a8ed8f38c46c7948c66f9131691e
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is more correct. When predictions, the typed word should
always be null unless explicitly passed. The text color should be
that of a valid typed word only if it's actually the typed word.
Bug: 13170509
Change-Id: I769ae100e112c37c6f02064fe9ef2f81372ca9e5
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes the color of the predictions when running
on a theme that has different colors for typed and
suggested words (GB theme).
Also, this is easier to understand and to modify from
now on.
Change-Id: Ifdc6d86a1695e83e16103041b06a2451f8d52cc4
|
| |
| |
| |
| |
| |
| |
| | |
Rename some variables for clarity and use constants
instead of immediates.
Change-Id: Ie07fbfcc3738ac4e67aefddc339fc54259172c39
|
| |
| |
| |
| |
| | |
Bug: 13170509
Change-Id: Ib9f10b8a137fc773ab0e5dc903e577038e29a9e2
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the practice it works because this never tries to access
inside the suggestion strip, and the worst that can happen
is a wrong text color for a suggestion. But since the two
colors that would be swapped are the same, nobody ever
notices -- unless they are using the GingerBread theme.
Change-Id: Ic8c70d8b3cdddf92946dfefbbc6d061572626c7a
|
| |
| |
| |
| |
| | |
Bug: 13017434
Change-Id: I94ff45da3f58b74cc9dd4d38179670fbcf619d92
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 13164518
Change-Id: I8768ad887af8b89ad9f29637f606c3c68629c7ca
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 13082957
Change-Id: I25570ab4da94337ed60330c0869fe47657096626
|
|\| | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Preliminary refactoring to fix
Bug: 13082957
Change-Id: I9f1283c37089bc96140b774b1c559d58031de004
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | | |
Bug: 12115967
Change-Id: I91c567a9577012ec28c08430c55e56e9c2e25b5f
|
|\ \ \
| |/ /
|/| | |
|
| |/
| |
| |
| |
| | |
Bug: 13136079
Change-Id: Ieae6bafbd5339a033f0f342ba9af7dcc4ce209fa
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 194e004e81f74c4124184ad8597d68e3837ea560.
Bug: 10786040
Change-Id: I4c5287d46cabe287abce5cba77635cf26d2cd192
|
|/
|
|
|
| |
Bug: 13138201
Change-Id: Ibaa3c2c22a4fe44ea23e92ce8576141bbad09b12
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The heuristic in RichInputConnection makes little sense
when textLength > mExpectedSelStart but we have
more than 1024 characters of text. If there are that many,
it's about 100% sure that 1024 is not the correct cursor
position. With no good guess, we'll just continue trusting
the app, even though we know it's lying : at least it will
make the problem visible to the app author.
Also, there have been a lot of confusion about initialSelStart
and initialSelEnd. The keyboard should log them so that
it helps us and editor authors debug more easily these
common problems.
Issue #65170 in AOSP and
Bug: 12772035
Change-Id: I6665a16c9f2832d33ee323f033bb38bcc092a3b4
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I812713da5918049c0e504e48bd0693df2f7bf46d
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
File descriptors will be closed in
BinaryDictionary.finalize(); but, this leads to unit test fails.
Bug: 13066902
Change-Id: I2b0d3e54ee91fa844530df54596f86bbbbac81a5
|
|\ \ \
| |_|/
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We already have a mechanism to avoid this crash, but it wasn't
used every time it needed to. It's possible that ending a batch
input and starting a batch input happen while suggestions
are being pulled out, which would result in pointers that have
been reset being passed for trimming.
Just increasing the sequence number should get rid of the
problem.
Bug: 12178124
Change-Id: I36ef3bc8a78679bc09daa39e665f5ce1bab50c2a
|
|\ \ |
|