| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 11328842
Change-Id: I7c22e951fef9bc4443c6b64625e25f632f876ab1
|
|
|
|
|
|
|
|
| |
This allows testing for suggestion freshness in an asynchronous
suggestions world.
Bug: 11301597
Change-Id: Ic76cd17568598d8534aec81e037f9e37f52eb6b4
|
|
|
|
| |
Change-Id: I44ac89edaba2e57bd1b7e091ff74b77a5e598f2f
|
|
|
|
|
|
|
|
|
|
|
| |
The only use of mDeleteCount is to implement delete
acceleration. It's reset at each non-delete code point, and
is guarded by a timer.
Plus, ultimately we want to remove this completely :
acceleration should be implemented by actually deleting
stuff faster, not by deleting several code points at a time.
Change-Id: Ia3144860b3aa2499034f2a2a7c81f32087af9598
|
|
|
|
|
| |
Bug: 11226045
Change-Id: I043f90ba92989bd8307c978eb32630439f63a0b9
|
|
|
|
|
|
|
|
|
|
| |
We don't support LOG_FULL_TEXTVIEW_CONTENTS any more, nor do
we have any plans to support it again in the future.
This also is a prelude to removing mIsExpectingUpdateSelection.
Bug: 11226045
Change-Id: Ib68c6daf52993b87225a7ea9e71a414caaecfdb7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
cherripick of I9c6a948331726a821bd3ccec9c1d02dec2c4703a
(forward cherrypicking this because the automerger is stuck now.)
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: I1cbf444d8d105416e7de75c16d80b3797f470495
|
|\
| |
| |
| |
| |
| |
| | |
sendKeyCodePoint()
* commit '3a3bbf4a38870ecc42b7f6fbd3a7cae20fe020a7':
Fix wrong commitText parameter in sendKeyCodePoint()
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Small optimization on generating a String instance from a single code
point too.
bug: 11181913
Change-Id: I0f905e4dc6ec7841092bb4d3d940daf3b2303f5b
|
|\|
| |
| |
| |
| |
| |
| | |
klp-dev
* commit '60fb58654e33448651fea191ba22cfdc87e37466':
Make emoji separators
|
| |\ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 11163495
Change-Id: I3247b8d1bbd3406b29a30a25aebd932c63431943
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | | |
remove the suggestion strip." into klp-dev
* commit '405062733cfe066c4b9af719bfc36a9a516c9dd3':
Fix a bug where emojis would remove the suggestion strip.
|
| |/
| |
| |
| |
| | |
Bug: 11163495
Change-Id: I23d12c430125cc2a66a6e00715a4c609bb9e2bb1
|
| |
| |
| |
| |
| | |
Bug: 11158604
Change-Id: If8c94ef91ed58bb5028f51be7c8d9beb677436a4
|
| |
| |
| |
| |
| |
| |
| | |
Workaround for framework bug:
Bug: 10792236
Change-Id: I3706b9eed5223889791840e30660f8d17625cb70
|
|/
|
|
|
|
|
|
|
|
| |
This is not useful because we're going to call setSelection again
with different values on the connection right away.
Also a preliminary change for
Bug: 10792236
Change-Id: I46c6ef1fbb3624086099bf81afddb0ef5ae85661
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 10902556
Change-Id: I3c8da35a601de2bfb248292c7b59235fc1120988
|
|/
|
|
|
| |
Bug: 11107229
Change-Id: I0b36341d60b634a860eb13fafd0dc69fe734bdeb
|
|
|
|
|
|
|
| |
This will help handing correctly the armenian full stop.
Bug: 10082781
Change-Id: Id7bb219ebd89daba203216eab362d1cc26a65a36
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Bug: 6669677
Change-Id: Ib465fa7e1a7f289a07843535ba89d0dd5259e803
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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: 8669376
Change-Id: Id71b2c2835daa7a8c9d6c92c57a7e302551c289d
|
|\ \ |
|
| |/
| |
| |
| |
| |
| | |
Bug: 6669677
Change-Id: I2462777eaa07600f1c774226adfc4f351882f523
|
|/
|
|
|
|
|
|
| |
This is not enough to really fix behavior with TYPE_NULL,
but it does make things a bit better.
Bug: 10949594
Change-Id: Ia359f781cdd76a2e2c5a4c9f166025d81b931174
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
...and do a best effort to fix it.
Bug: 10323080
Bug: 10252066
Change-Id: Icb3c9fe85005406bdfce0b7bb143ba0a910a0ddb
|
|/
|
|
|
| |
Bug: 10848621
Change-Id: If5ff7f001e69af005a5ff9ab3e9f630b88a0a858
|
|
|
|
|
| |
Bug: 10814472
Change-Id: I3a150124baf7a9b7889b033089a859ff9c11e206
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 10704936
Change-Id: I30fdaea648605ef7e7fea6c093581ed5c6de03f3
|
|/
|
|
|
| |
Bug: 10780016
Change-Id: I94fad06e4c71eddc96bdda1765925f98bed160f3
|
|
|
|
|
|
|
| |
...for phrase gesture.
Bug: 9059617
Change-Id: Ic5c0616f28af4ba45ca72a5721d1926029adc1c5
|
|
|
|
|
| |
Bug: 9059617
Change-Id: I7e5d89a9037b9181a0a6456c12043b4bfda8fe4b
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 9059617
Change-Id: I7a47b0675446fc4f39628c60d16de9aea90d1b4d
|
| |
| |
| |
| |
| | |
Bug: 10541453
Change-Id: I16dd72c8c55cb5d21ad61a3307c0f3c5f16f460c
|
|/
|
|
|
| |
Bug: 10115839
Change-Id: I1f1025c9f28adfb6f5a63d5ba86e359f30c0963e
|
|
|
|
|
|
|
|
|
| |
This code is now useless.
I thought it affected 9902905, but it seems it actually does not.
Still, it's dead code.
Bug: 9902905
Change-Id: Id9c90fbf88f015af47b2368b90d173c481647093
|
|
|
|
| |
Change-Id: I2ddb250d5a473ea955a5171656974de7288a13f7
|
|
|
|
| |
Change-Id: Icfa685bcda2f5c74f5649f09098d00b4bd321c5a
|