New issue
Advanced search Search tips

Issue 812652 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 3
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Refactor logic in cc::Animation so that the control flow matches blink

Project Member Reported by yigu@chromium.org, Feb 15 2018

Issue description

RunState of cc::Animation is supposed to be managed/accessed at a higher level. e.g. the counterpart of blink::Animation, which is AnimationPlayer.
 
Status: WontFix (was: Assigned)
The run_state of the lower level concept keyframe model (formerly known as animation) was exposed to clients and they have been directly talked to the keyframe models ever since. It makes operating animations easier for the clients as they have more controls on the lower level components. However, this makes the cc side animation harder to maintain. e.g. exposing two kinds of APIs. Eventually we'd like to refactor all the clients to use the high level APIs and keep the low level concepts as internal implementation details.

However, this bug was filed against animation worklet which we now have a workaround (by setting RunState::PAUSE to all of its keyframe models). Therefore closing the bug as wont fix. The refactor work mentioned above should be tracked in a separate bug when time comes.

Sign in to add a comment