New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 635607 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
inactive
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Use the frame time from Choreographer for computeScroll animation time

Project Member Reported by hush@chromium.org, Aug 8 2016

Issue description

AwContents#computeScroll uses the AnimationUtils.getCurrentFrameTimeMillis() as the animation timestamp, which is read from SystemClock. This is different from the frame time in Choreographer. As a result, this has caused tiny 'sleeps' during fling animation.

This is a problem for L+. Android will fix AnimationUtils.getCurrentFrameTimeMillis to be backed by Choreographer.
But in order for Android WebView to work properly on L+, we need to stop using AnimationUtils.getCurrentFrameTimeMillis and instead read from Choreographer's frame time directly.

See internal bug b/30674719 for more details.

 

Comment 1 by hush@chromium.org, Aug 23 2016

Status: WontFix (was: Assigned)

Comment 2 by hush@chromium.org, Aug 23 2016

We can't do it without breaking existing apps (https://codereview.chromium.org/2222073002/#msg17)


Sign in to add a comment