| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
InputConnection#finishComposingText() should not change the position of the cursor,
so neither should it change its internal expectation of the cursor's position.
Change-Id: Ib3d39a5743cd1e8e356f438b04a5c30279430b2a
|
|
|
|
|
| |
Bug: 8911898
Change-Id: Ifb4bb63c14dc960d0a53f1511908830093cca012
|
|
|
|
| |
Change-Id: I4d36a23567415c3a293a588b51b46006256c148f
|
|
|
|
|
| |
Bug: 8864306
Change-Id: Ic8eecd64eff6a1150a90b9f5ec9ebbc5f1d2a6a9
|
|
|
|
|
| |
Bug: 8864306
Change-Id: Ia146f711f1de4336d7e3363208ab92eba856f5e1
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This reverts commit f712dc9a4f17ee4a6916b0f477e89d1bc34a4d70.
It turns out this refactoring is not useful after all.
Change-Id: I0145c907b3cc5ac9a30a59abcd719cb546c9bd3a
|
|\| |
|
| |
| |
| |
| |
| | |
Bug: 8864306
Change-Id: I5c9b118cb6a8eb59efc52d5534b10fcab93182d6
|
|/
|
|
|
| |
Bug: 9429906
Change-Id: I576a91643bdaf5017cc826ac2e07a74a9a275d60
|
|
|
|
| |
Change-Id: Id170dbfe2dcfc93130b7be4a84615940403ec37f
|
|
|
|
|
|
|
|
| |
This change also eliminates a reference of
AudioAndHapticFeedbackManager from KeyboardSwitcher and MainKeyboard.
Bug: 6522943
Change-Id: Iac42ec8ff00c66deb76a660ffc07477923a58959
|
|
|
|
|
|
| |
Range has grown a bit too big to stay an internal class.
Change-Id: Ic3fbc48a5d10776eedd7559c4d696e5926b88288
|
|
|
|
|
|
| |
Bug: 8839763
Bug: 8862327
Change-Id: I5d49c86edcbc0fc1b2b147856437cfbadd678377
|
|
|
|
|
|
|
|
|
|
| |
I548d899b introduced a new method to fix a sync miss between
the cursor position and the cached cursor position, but did not
take into account that it should also update the cached text
before and after the cursor in this case and that there was
already a method for doing this.
Change-Id: I31bd741893207c822827304e77791b1159774e1a
|
|
|
|
| |
Change-Id: If2f7bd1346cc5085bf57645830f0faac44d017e4
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The documentation for setComposingRegion states explicitly
that it does not move the cursor. This is just a bug.
This does not have any ill effects right now, but it will have
in later changes if not fixed.
As for the selection handling, the specific test that this code
removes used to serve a purpose, but it does not any more because
the code using the value has been much sanitized. Now the variable
can just take the obvious value, and become so self-explanatory
that the comments are unnecessary.
Change-Id: I548d899b38776bd3ab5f5361aab0d89d98f12e73
|
|\ \ |
|
| |/
| |
| |
| | |
Change-Id: I1c5b27c8edf231680edb8d96f63b9d04cfc6a6fa
|
|/
|
|
|
|
|
|
|
| |
This changes how the Range class stores its data, but not its
functionality. It also improves encapsulation a bit.
Bug: 8839763
Bug: 8862327
Change-Id: I5bd583b3fc96a99b93a2632882d8fd587c03ab76
|
|
|
|
|
|
|
|
|
|
|
| |
- Don't call finishComposingText when useless.
- Add safeguards against calling setComposingRegion when the
data returned by the editor is inconsistent.
- Cancel pending recorrection messages when new messages arrive.
Bug: 8842941
Bug: 8845001
Change-Id: I939701033cf5c2bbd85871ecf83e329021ddeb91
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is about as ad-hoc as it gets, but then again, what we want
is probably as ad-hoc as it gets.
All URL boxes I know of double as search bars, and not adding
automatic spaces there sucks (e.g. in Chrome URL bar).
And in other boxes actually you don't want to add a space if
it looks like a URL. QSB isn't even a search box, and it behaves
like this.
So I think this is actually the right answer to the problem.
Bug: 7062925
Change-Id: Ib09472b34644fd5bf2dc84bb97cedeeba28bcd02
|
|
|
|
|
|
|
|
|
|
| |
Upon pressing Shift, if there is currently a selected string, have
Latin IME change its capitalization.
This does not yet have the keyboard mode follow the mode - the change
is complicated enough as is.
Bug: 7657025
Change-Id: I54fe8485f44e04efd72c71ac9feee5ce21ba06f2
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This uses the old suggestions. It does not try to recompute
new suggestions if there are no old suggestions yet: this is
coming in a later change.
If there are no suggestions, this shows the word itself
as a suggestion.
Bug: 8084810
Change-Id: I4c2e25df0ff3673be1825f57a0c19a9d23d47a48
|
|/
|
|
|
| |
Bug: 8561056
Change-Id: I91fb0ac76dabfc841bafc0e2c0ea9f63e6f604f9
|
|
|
|
|
|
|
|
| |
Also remove an unused method and make 2 private variables
final.
Bug: 8461093
Change-Id: I676d93fda28e82eb5a6978f2e7ad5a0add2cbecf
|
|
|
|
|
| |
bug: 8393568
Change-Id: Ie5edf44a3627aca9416145aff56bf05bbf2a05f3
|
|
|
|
| |
Change-Id: I32700c434b296bb3fd39e040c2dda1fe90667daf
|
|
|
|
| |
Change-Id: Ic56167f952a7f4449da366e1e81610e72c966086
|
|
|
|
|
|
| |
Bug: 7889078
Bug: 7268000
Change-Id: I6c77b8c9e60ef69f02526b407124d2f5d02818ee
|
|
|
|
|
|
| |
multi-project commit with Ia4ec213e8356897807cb6a278fccdbaa945732f0
Change-Id: Ib3fe886dc889954a31586ab81d00a21d8d55efd2
|
|\ |
|
| |
| |
| |
| |
| |
| | |
multi-project commit with I684ba5fed8c653777942e6b0366113ca40dfa37c
Change-Id: Id3804e6cfa97b4cdde212b8eebc413f76fa4772c
|
| |
| |
| |
| |
| |
| | |
Multi-project commit with I249d5fbe
Change-Id: Ia28c4e970992aa1299a30e604eaa5d096655c3a5
|
| |
| |
| |
| | |
Change-Id: Ib0de800599ae7f12c86270a627616d5b52366414
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this test, it's impossible that start < 0 so the test is useless.
I'm not sure what the cursor test was for, but it's very old code, and
it seems the assumption was either misled or doesn't hold any more:
testing for the absolute cursor position against the length of the
word against the cursor makes no sense.
The net result of this was that when the cursor index got large
enough, resuming suggestion would not work any more.
Bug: 7586467
Change-Id: I3462082374fe9579bec7698f4d424de6ff5f2ded
|
|
|
|
|
|
| |
multi project commit with I5847d4aba97a7224ae170a7153811c5a11816449
Change-Id: Ie6fbf6f19f0193451fe6f3ddf9d4ef1637a35db1
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
multi-space logging should look like single-space logging, missing a few minor log statements
(SuggestionUpdates, SetComposingText)
multi-project commit with I2af842348c2f2b8f7271ac5b63def245e83df24d
Change-Id: Icd3187c0d0377255f82787afffea657c14345803
|
| |
| |
| |
| | |
Change-Id: I7defaf1f577fd67e678cac83ff935e8181dd0a48
|
|\ \
| |/
|/|
| | |
Change-Id: I21141956135debe737453dba87617671b1716d0a
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When the user edits a word before adding it to the user
dictionary, the keyboard should replace whatever was
committed before with the amended version.
Bug: 7725834
Change-Id: I1a417be6c5a86d6a96bc2c76aca314ad8f1202a9
|
| |
| |
| |
| | |
Change-Id: I0c29c5d2abcbf80759b996d34b534deb083cd7d3
|
|\|
| |
| |
| |
| |
| |
| | |
fields" into jb-mr1.1-dev
* commit '8c470f16db291e257ac538bd0ac2a9354d34010c':
Fix a bug with some text fields
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Not sure when this happens exactly, but it is possible that
InputConnection#getTextBeforeCursor returns null. This
happens for example upon rotating the screen with the
composing field empty in Gmail.
In this case, StringBuilder#append will convert the null
pointer into the string "null", which is sure better than a
crash, but can have a number of bad side-effects, like
auto-caps not working.
Bug: 7533034
Change-Id: Ia1cfab432c13a12ff1c2f013c59bac05a587f553
|
| |
| |
| |
| | |
Change-Id: Iee01d4d2b916d0b584531104ac865ae6e6370a3d
|
|/
|
|
| |
Change-Id: Idc478f901185ee1b4912acc82d0cbc54fee4e991
|
|
|
|
|
|
|
| |
Bug: 7359291
Bug: 7357758
Bug: 7197651
Change-Id: Ia805a87e922739ae0a06978a3bf00d91c94b6c51
|