Move CalculateTransitionUpdate for PropertyPass::kCustom
Previously, animated custom properties were part of the base style, and the call to CalculateAnimationUpdate _could_ take place during the base style calculation if custom properties were animated or undergoing a transition. In that world it made sense to compute transitions for custom properties early, since it could affect the base computed style. However, after the introduction of StyleCascade, CalculateAnimationUpdate now always takes place after the base computed style has already been produced. It therefore no longer makes sense to separate kCustom/kStandard transition passes. The two passes can be merged to one, but for now this CL just moves the two passes together. Change-Id: Ibc2b82d4c58af168ceaf2572f98dc09744795702 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2307222 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by:Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#791551}
Showing
Please register or sign in to comment