| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | Critical |
|---|
| Status | Closed |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2011-10-05T14:42:39.000+0000 |
|---|
| Affected Version/s | Release 1.7.2 |
|---|
| Fix Version/s | Sprint 2011-38, Release 1.8.0 |
|---|
| Components | Android |
|---|
| Labels | merged-v8, parity, scrollableview, stage |
|---|
| Reporter | Opie Cyrus |
|---|
| Assignee | Bill Dawson |
|---|
| Created | 2011-08-29T21:19:09.000+0000 |
|---|
| Updated | 2011-11-01T16:06:23.000+0000 |
|---|
When moving a scrollable view in iOS, the view follows the finger until a threshold is met that triggers the paging mechanism to show the next/previous "page". In Android, the view does not follow the finger up until the threshold. This ticket exists to track the discussion of the parity difference and the fix if one is agreed upon.
UPDATED DESCRIPTION:
I (Bill) changed this ticket to doing the actual implementation of a "follow-the-finger" scrollable view. Original title of this item was "TiAPI: Spec / Tech discussion about ScrollableView".
reviewed. tested. merged.
Reopening for a quick code fix and new Pull request. Not code that broke anything but is horrible.
Tested with 1.8.0.v20111006001414 on Hero 2.1 and Motorola Xoom 3.2