57f4e5bcf56752053815a755fee4867e722ce2b8
Previous CL https://android-git.corp.google.com/g/55138 was submitted before the suggested change was uploaded. setSelection() was called twice by onTouchEvent, once to the previous position, and then to the new position (unless the IME got displayed, so that in that case the cursor is not moved). The second call was actually triggering a call for a scroll of 0 since the view is already displaying the cursor. This scroll is filtered out by a shortcut in ScrollView. The first setSelection's scroll does not have the same issue (since the previous cursor's position is out of screen and requires a scroll) and it is then applied, effectively moving the cursor to a new position but scrolling to the previous position. The fix is to call setSelection only once, after the IME has been asked to display. The cursor is moved to the old/new position depending on the resultCode in onReceiveResult in CommitSelectionReceiver. Bug: http://b/issue?id=2778954 Change-Id: I157d7ae451574e8a6fffb894eb1d6880acfe01d1
am
0b16e6a0: am 7f0a1f62: am 5f11e95f: docs: small edits to catchup to edits made in html pushed live
am
dde1ae84: am 45378f07: am 6b22d81a: As Donut (API=4) devices and earlier do not have a Bluetooth API, .apk files that have minSdkLevel (or targetSdkLevel) set to 4 or lower should not be presumed to require Bluetooth just because they take the permission.
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%