diff options
author | alancutter <alancutter@chromium.org> | 2015-10-15 22:58:26 -0700 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2015-10-16 05:59:23 +0000 |
commit | 1737f9e86e74990aad0e9693ebf247c8ffbb86f9 (patch) | |
tree | a2e61a9a0e9c44febf2410e4a55276d44dcab9a9 /extensions/utility | |
parent | eb7f57c9808ff03e537d1f79fb0cc57ebb19d34f (diff) | |
download | chromium_src-1737f9e86e74990aad0e9693ebf247c8ffbb86f9.zip chromium_src-1737f9e86e74990aad0e9693ebf247c8ffbb86f9.tar.gz chromium_src-1737f9e86e74990aad0e9693ebf247c8ffbb86f9.tar.bz2 |
Preserve running CSS Animations across changes to animation styles according to same name index
We currently only keep track of the last animation that used
a given @keyframes name. If multiple animations use the same
@keyframes rule we fail to update their timing input correctly
as animation styles are updated.
This change makes us track animation-name references to running
animations based on name and name index (nth occurrence of name)
rather than just name.
This behaviour does not conform to any spec text as the
specification does not dictate what to do in this scenario:
"Need to specify better handling of dynamic changes of animation-name"
https://drafts.csswg.org/css-animations-1/#other-open-issues
The behaviour introduced in this patch is arbitrary though
better than the existing behaviour of ignoring running
animations and crashing debug on timing updates.
BUG=487092
Review URL: https://codereview.chromium.org/1402143004
Cr-Commit-Position: refs/heads/master@{#354457}
Diffstat (limited to 'extensions/utility')
0 files changed, 0 insertions, 0 deletions