| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Bug: 10118761
Change-Id: I63501d6c2b5f561d7ab8b7362498665d805d5e1e
|
|
|
|
|
|
| |
Bug: 11136982
Change-Id: I9d022a178c47bad3566be4c0bd8ffbce0b14896d
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 10902556
Change-Id: I3c8da35a601de2bfb248292c7b59235fc1120988
|
|/
|
|
|
| |
Bug: 11107229
Change-Id: I0b36341d60b634a860eb13fafd0dc69fe734bdeb
|
|
|
|
|
|
|
| |
This will help handing correctly the armenian full stop.
Bug: 10082781
Change-Id: Id7bb219ebd89daba203216eab362d1cc26a65a36
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This is a very rare corner case.
Bug: 11072132
Change-Id: Iad2aa69511f7dc99105284a049c63f2f997b8ef0
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
This also includes a fix that allows this code to read surrogate
pairs in this processing.
Bug: 11070482
Change-Id: If5ef8d6863938252f09128b7e99ea07ece6e7019
|
|\ \ |
|
| |/
| |
| |
| | |
Change-Id: I5f85a7a0f94ea9ecbe0c4a8caebcf551fa9c9669
|
| |
| |
| |
| | |
Change-Id: I986ab26faf535fc4bc98443053f534eced9d048f
|
|/
|
|
| |
Change-Id: I2208378b33038771b460abb33f9a690872e998e2
|
|
|
|
| |
Change-Id: Ie69d84e090f69dc3ea1f5de73ad8c954ecd2c6a7
|
|
|
|
|
| |
Bug: 10920165
Change-Id: I340759eadbde7fb64cb3b9a3c619ee3a768cedf8
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Bug: 6669677
Bug: 10667710
Change-Id: I6cdc6a6c9cacc7f276fda3a26ec31e3eb928471c
|
| |
| |
| |
| |
| | |
Bug: 10920165
Change-Id: I6372492e97297baad4c5aeeb3fb36dcccd7a944b
|
| |
| |
| |
| | |
Change-Id: Ic586e46e5a9f59de53d53e59886d635345940974
|
|/
|
|
|
| |
Bug: 11032428
Change-Id: I5d422f1c15a582015770ef9a652348ca6eb8ab85
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Bug: 6669677
Change-Id: Ib465fa7e1a7f289a07843535ba89d0dd5259e803
|
| |
| |
| |
| | |
Change-Id: Iaf1556fec194d17cb4318f2bdcc837f8d79449ef
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 10920165
Change-Id: Ie9008452ee292fb0b1fec66e2ffed228c4af6c3e
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
What's happening here is, setAlphabetKeyboard sets the
keyboard to AUTOMATIC_SHIFTED and updates the keyboard, then
restoring the keyboard old state sets it back to UNSHIFTED without
updating it. When we finally know what the correct value is,
we try to set it to UNSHIFTED, but since that's already the currently
recorded state, it skips updating the keyboard forever.
The solution is to avoid setting the shift state without updating the
keyboard.
Bug: 10948582
Change-Id: Ic8670401e378f8284e851281f91a9ad93eac8e90
|
| |/ /
|/| |
| | |
| | |
| | | |
Bug: 10118761
Change-Id: Ia7d1c6c526dae849f447c26387e96a4fb4d6042f
|