VerticalScroller fling motion does not match native Android behavior [147493715]

Fixed

Bug

Status Update

No update yet.

Description

ad...@google.com

created issue #1

Jan 10, 2020 06:40PM

Compose UI should match Android's native fling scrolling behavior, delegating to the platform for forward compatibility where possible.

Android's scrolling components, android.widget.Scroller and android.widget.OverScroller internally use the static clock provided by AnimationUtils, making it infeasible to use these components natively in Compose UI without changes.

This work will proceed in several steps:

Extract the sampled spline used by Scroller such that it can be used in a testable, clock-agnostic manner.
Implement a Compose UI DecayAnimation based on this extracted spline.
Make (2) the default behavior of VerticalScroller and similar rather than the exponential decay animation.
Apply the changes from (1) back to AOSP frameworks/base
Refactor (1) to use (4) when running on a new enough Android platform version for forward compatibility with any future Android platform changes

Comments

ap...@google.com <ap...@google.com> #2Jan 22, 2020 12:43AM

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

ad...@google.com <ad...@google.com> Jan 27, 2020 05:59PM

Marked as fixed.

Issue 147493715

Description

Issue summary

Comments

ap...@google.com <ap...@google.com> #2Jan 22, 2020 12:43AM

ad...@google.com <ad...@google.com> Jan 27, 2020 05:59PM

Add comment

Issue metadata