| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Bug: 8839763
Bug: 8862327
Change-Id: I5d49c86edcbc0fc1b2b147856437cfbadd678377
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
RichInputConnection#getWordRangeAtCursor may now returning
either a SpannableString or a String. We can't test that with
String#equals(), but TextUtils#equals() does the job for us.
Change-Id: I59ebe54207e92f4d90b49476b64f1e12fd4929cb
|
|
|
|
| |
Change-Id: I32700c434b296bb3fd39e040c2dda1fe90667daf
|
|
|
|
|
| |
Bug: 8131968
Change-Id: Ibca5a0d63a492134b8af401a62ca3a5748e003cf
|
|
|
|
| |
Change-Id: I6e7c3aba2b40ecefa483c9680978bc806368e96e
|
|
|
|
|
| |
Bug: 6766059
Change-Id: I378f9d35c4904c4f373260bda5863235d833eb31
|
|
Change-Id: I9982ff325bef56694402caef28a77683c52ccd71
|