| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 11123691
Change-Id: I36474e12e34af95051129840865015f85595411b
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
Change-Id: Ibffaf64a9bda1fb0779a9b53558ca56ed31660d3
|
| |
| |
| |
| | |
Change-Id: I7c2d0d86d85775065a9bcb2b4a8463bb4969579e
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
Change-Id: I976afc5d320bc65835d659bae1d10d2cdc68262b
|
| |
| |
| |
| | |
Change-Id: Ib527a376b693be21aebd4920ac804ee9b161eb96
|
|\ \ |
|
| |/
| |
| |
| | |
Change-Id: Ifda44e6139a4a1bd065468a7f74cd9483b343644
|
|\ \ |
|
| |/
| |
| |
| | |
Change-Id: I9a58e53317654f8a09fbe79044214de3e9c59eb7
|
|/
|
|
| |
Change-Id: I6f990fd84e7f08fd1149198c33d8bbf1cac8e078
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 56402cf10a3a26ca7add62678d7e1ab3064feab7.
I'll submit this on 10/16 after the final cut for Bayo.
Change-Id: I0fe4ab64fd8dfa1e63e29adf00388743fca6a1ed
bug: 11144401
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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: 10920255
Change-Id: I26d2cce3c322a4ff39a614f8615f43fb7bd3baed
|
|\ \ \ \ \ \
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
klp-dev
* commit '3f1c95dbdc18453dc0cd6f847b33e01db1f1d75b':
Fix the suggestion size.
|
| |\ \ \ \ \ |
|
| | | |_|/ /
| | |/| | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | |
| | | | |
Bug: 11073222
Change-Id: I680e4304c6ab701e9aa132e1e140d789097a53ae
|
|\ \ \ \
| |_|/ /
|/| | | |
|
| | |/
| |/|
| | |
| | |
| | | |
Bug: 11029983
Change-Id: I1bec2c3c6b547de68562a818a8d6c9fef83787b7
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In new format, each bigram entry has flags (1 byte), a terminal id (3 byte),
a time-stamp (4 byte), a counter (1 byte) and a level (1 byte).
Bug: 10920255
Bug: 10920165
Change-Id: I0f7fc125a6178e6d25a07e8462afc41a7f57e3e1
|
|/ /
| |
| |
| |
| | |
Bug: 11158604
Change-Id: If8c94ef91ed58bb5028f51be7c8d9beb677436a4
|
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 220ce8f269e8d2507a2a57ec919e48ddb6f496f8.
Sorry, but we are now in the week before the final cut for the next launch. We shouldn't be taking new features like this at this point. Let me revert this change for now. I'll re-revert this after the cut next week.
Change-Id: Ia8b00680c992ec526e6a858945f2380cbcdfdd55
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
There used to be two "Swiss" keyboard layouts, labelled fr_CH and de_QY,
available in LatinIME. They were, however, not actually Swiss layouts
but instead work-arounds to be able to get French or German with qwertz
or qwerty (instead of azerty and qwertz) layouts, respectively. These
were thus removed by commit f6972561fcb45310f18230ce217f0c6bb57e7eee
replacing them with the generic fr-qwertz and de-qwerty layouts instead.
Here, now, is a proper Swiss keyboard layout, following Swiss standards
for people accustomed to typing on Swiss keyboards, with the expected
tailorings for French and German.
Change-Id: I9feed752053ecc694c84db713284f69bc1daf155
|
| |
| |
| |
| |
| | |
Bug: 11130808
Change-Id: I9ffc457ca44bccfa3eb3bdb0c26535d795215b26
|
| |
| |
| |
| |
| | |
Bug: 11140087
Change-Id: I8163568a9d7f9d321148001e161c672f78796c96
|
|\ \ |
|