Nested visibility animations do not start simultaneously |
|||
Issue descriptionWhen updating bindings, we recur if a subtree will be visible. However, when updating animations, we recur when an element was visible during the frame. This means that if a parent and child both animate to visible, since the parent's animation starts at opacity 0, the child won't get ticked until the next frame. This can cause small delays to animation start times.
,
May 14 2018
,
May 15 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, May 14 2018