| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
This returns the wrong string, but since it's used for getting the
previous word for bigrams, it only results in slightly worse
suggestions quality.
Cherry-pick of I6ce5de2f
Bug: 11273655
Change-Id: I17fb6d74f18fb31bd8f8518f80456d74ae30a2c3
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows testing for suggestion freshness in an asynchronous
suggestions world.
Cherry-pick of Ic76cd175
Bug: 11301597
Change-Id: I45a84de0632062475eebe30234b3147f1c680359
|
|/
|
|
|
|
|
| |
Cherry-pick of I62955e36
Bug: 11311002
Change-Id: I5b11cb48e6dd0563fc29566fe0d27864be2beb0a
|
|
|
|
|
|
|
|
| |
- Suggestions form user history can contain invalid words.
- isValidWord always returns false.
Bug: 11139426
Change-Id: I6075b275603332ddb00f4a9284afcaa82d824270
|
|
|
|
|
| |
Bug: 11123691
Change-Id: I36474e12e34af95051129840865015f85595411b
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This bug was leading to corrupted rendering of surrogate pairs in the following
scenario.
1. Type some emojis
2. Move the cursor at the beginning of the text field
3. Hit backspace even though there's nothing to delete
4. Move the cursor after some emoji
5. Hit backspace
The root cause of this issue was the out-of-sync mExpectingUpdateSelection if
handleBackspace() gets called when the cursor reaches at the beginning of the
TextView. In such case, mExpectingUpdateSelection shouldn't be set true because
there's nothing to delete, so there will be no onUpdateSelection() calls associated
with it. Due to this bug, the cache in RichInputConnection could get stale at step 4
described above. Then the following handleBackspace() that should delete a surrogate
pair was not working correctly because of the stale cache.
bug: 11181913
Change-Id: I9c6a948331726a821bd3ccec9c1d02dec2c4703a
|
|
|
|
|
|
|
|
|
| |
Small optimization on generating a String instance from a single code
point too.
bug: 11181913
Change-Id: I0f905e4dc6ec7841092bb4d3d940daf3b2303f5b
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 11163495
Change-Id: I3247b8d1bbd3406b29a30a25aebd932c63431943
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 11163495
Change-Id: I23d12c430125cc2a66a6e00715a4c609bb9e2bb1
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The available space was not computed correctly. This makes the
decision to ellipsize/expand the middle suggestion correct.
Also, the scale was not applied correctly in some cases.
Finally, for some reason ellipsize does not work as we expect.
I'm not sure how to get it to work like we want it to, but
this works around the problem in a simple manner.
Bug: 11158757
Change-Id: I083e7ac56e157f100923733e67b92a6368a526c9
|
|\ \ \
| |/ /
|/| | |
|
| |/
| |
| |
| |
| | |
Bug: 11029983
Change-Id: I5547910c7b5dd7974292fc075af33568940f4e81
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| | |
cherrypick of I8163568a9d7f9d321148001e161c672f78796c96
Bug: 11140087
Change-Id: Ifd28f3017a8cf568a8c4a1045811564a129d85b7
|
|/
|
|
|
|
|
| |
cherrypick of I9ffc457ca44bccfa3eb3bdb0c26535d795215b26
Bug: 11130808
Change-Id: I1a65fd8acc4efe9b4e4786a3dc959498ae63c2f8
|
|
|
|
|
| |
Bug: 10118761
Change-Id: I63501d6c2b5f561d7ab8b7362498665d805d5e1e
|
|
|
|
|
|
| |
Bug: 11136982
Change-Id: I9d022a178c47bad3566be4c0bd8ffbce0b14896d
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I07a3912cb9fef8e28f3605de4e73a201a900e95c
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This adds all those popup keys that were included in commit
b1cb13292f482627e64ccb35be905b7f3154d4ff when the Swedish keyboard was
first added. Many of these definitions were later removed by commit
79b965e04f81ac5c49c84a386566a1aa68752af6 but most likely by mistake, as
that commit log message doesn't mention anything about removing these.
To help making this file more maintainable, this commit also moves a few
definitions around so that all definitions now appear in alphabetical
order.
Change-Id: Iadef9e3dd1dc7b39fe87b2fc75210d0697b24361
|
|\ \ \
| | |/
| |/| |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 10902556
Change-Id: I3c8da35a601de2bfb248292c7b59235fc1120988
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 11107229
Change-Id: I0b36341d60b634a860eb13fafd0dc69fe734bdeb
|
| | |
| | |
| | |
| | |
| | | |
Bug: 10902556
Change-Id: I3a8c1e08d6f953b462d914acd1f411c36f9d80f2
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | | |
bug: 10902556
Change-Id: I313948c73b60cd33c437cf02e8d3fb61c288a240
|
|/ /
| |
| |
| |
| |
| |
| | |
This will help handing correctly the armenian full stop.
Bug: 10082781
Change-Id: Id7bb219ebd89daba203216eab362d1cc26a65a36
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 11105065
Change-Id: I5e90ba55cf708bf7be27d7d101cbc0719ac583c8
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We want to use StringUtils here, but it's full of references to
stuff not accessible host-side like JsonReader and TextUtils
and SettingsValues :/
Bug: 11061476
Change-Id: I3c0194979833ede283b4f9190335dba5376fe6fc
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since loadKeyboard relies on the input connection being
available to give it the auto-caps state, but also can't
be called twice in a row because it needs to save and
restore its state and invalidates it after the restore,
we need to wait until we know we have a valid input
connection to call it.
Bug: 11107229
Change-Id: I1c7baf3215682df6f6ceb357bd37254f9e7418c7
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Bug: 11077905
Change-Id: I9495f13a20edca0e6153cd1a7a0ac6891f707c59
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 11076722
Change-Id: I0de10ab24d33ec31f45664fe92d80d5a7bec9c20
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
14 is the right value.
Bug: 11076722
Change-Id: I95d404b540f7fbe4932d1f8498cde23f1df0314f
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- GC gets failure when the dictionary become empty.
- Useless unigrams are sometimes not removed.
Bug: 10197478
Change-Id: I8d1479c01efba61a81f03bc077da6bcb4797a940
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is not the right way to do it, but it's simple and will kill the
regression. We should investigate why the return values are
wrong in this case.
Bug: 10780091
Change-Id: I808727242c9cb1598df00a7426358dc3a658add4
|
| |/
|/|
| |
| |
| | |
Bug: 11103091
Change-Id: I0c5384e9f148566d1ac1d178a8227eb913d59908
|
| |
| |
| |
| |
| | |
Bug: 11074625
Change-Id: I1ef6b81ef923684b502c24fddb4ced8fe1691733
|