14f10e5d5f51bc54ca2a45ee62d3cfb6debd3af0 |
|
18-Sep-2013 |
Raph Levien <raph@google.com> |
Revert "Revert "Take the input device into account for meta state"" This reverts commit 3954fd9a05232cb6f7fc52aa49a0b34c1539028a, which is equivalent to re-applying 8a1597b39632956cdbcb6b76874ccca786047d4c. The change ("Take the input device into account for meta state") was valid but caused CTS test failures because the test was wrong. The test injected a key event with the meta state missing. This faulty test was masked by the old toggle behavior.
/frameworks/base/core/java/android/text/method/BaseMovementMethod.java
|
3954fd9a05232cb6f7fc52aa49a0b34c1539028a |
|
17-Sep-2013 |
Raph Levien <raph@google.com> |
Revert "Take the input device into account for meta state" This reverts commit 8a1597b39632956cdbcb6b76874ccca786047d4c. That commit broke some of the handling of meta state, which in turn caused CTS test failures, notably bug 10210151 (CTS: android.text.method.cts.BaseKeyListenerTest#testBackspace_withSendKeys is failing on KLP). So this revert fixes those test failures, but leaves bug 8303489 (Pressing shift on the hardware keyboard messes with unrelated keypresses, including virtual ones) still present. We'll plan to address that in a future release. Change-Id: Iea42c643b6d08f33cbd2ed1747e8de3b5f8116a6
/frameworks/base/core/java/android/text/method/BaseMovementMethod.java
|
8a1597b39632956cdbcb6b76874ccca786047d4c |
|
05-Mar-2013 |
Jean Chalard <jchalard@google.com> |
Take the input device into account for meta state Interesting nits about this: - getMetaState(long) and getMetaState(long, int) do not seem to be used anywhere in the framework. Maybe we want to skip adding getMetaState(long, KeyEvent) and getMetaState(long, int, KeyEvent). - getMetaState(CharSequence, int) is used extensively throughout the code. In some places, a KeyEvent is available and should be considered - this change does implement this. In many other cases, there is no relevant KeyEvent for this action (for example, Editor#extractTextInternal). In these cases, the behavior is affected by the current latch state, so it's fine to leave them as is. Bug: 8303489 Change-Id: I4a948c497c49e48f83ba1048520e7fe5bfe84727
/frameworks/base/core/java/android/text/method/BaseMovementMethod.java
|
f76a50ce8fdc6aea22cabc77b2977a1a15a79630 |
|
09-Mar-2012 |
Ken Wakasa <kwakasa@google.com> |
Fix obvious typos under frameworks/base/core Change-Id: Ia5fc3db1bb51824e7523885553be926bcc42d736
/frameworks/base/core/java/android/text/method/BaseMovementMethod.java
|
e982dfc1bae36620f67371efc7b0a0f8adc9450d |
|
22-Mar-2011 |
Jeff Sharkey <jsharkey@android.com> |
Support Ctrl-based EditText movement. EditText now listens for Ctrl+left/right to jump through text at word boundaries. It also listens for Ctrl+home/end to move to start/end of the full text. This emulates behavior found in desktop text editors. Bug: 4081964 Change-Id: I98bd19c0d8707357847db3466648a83fd774dbaf
/frameworks/base/core/java/android/text/method/BaseMovementMethod.java
|
8f34567c71003505456a9b1a0d461a4e62883d70 |
|
26-Feb-2011 |
Jeff Brown <jeffbrown@google.com> |
Add scroll wheel support to TextView. Change-Id: I6e4258c50b0d754dccf07266ff4b2abcbccd733a
/frameworks/base/core/java/android/text/method/BaseMovementMethod.java
|
67b6ab72ae96a9f2be929de2c32c110df5390fdd |
|
18-Dec-2010 |
Jeff Brown <jeffbrown@google.com> |
Add TextView support for Home, End, PageUp, PageDown. Change-Id: If8aa2a63b5fc33528d54eef68e695082a129acce
/frameworks/base/core/java/android/text/method/BaseMovementMethod.java
|