Currently we tick worklet animations with accelerated properties, e.g. opacity, via the compositor and tick the ones with non-accelerated properties, e.g. width, via the main thread.
There may be a way to unify the logic by always updating the time fractions of properties off-main and applying them off-main only if the properties are accelerated, then plumbing the values back to main in both cases.
To achieve this, cc::AnimationHost should be capable of handling / interpreting all kinds of animatable css properties.
Comment 1 by majidvp@chromium.org
, Dec 13