Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(33)

Issue 24085002: Correctly apply per-keyframe timing functions (Closed)

Created:
7 years, 3 months ago by Steve Block
Modified:
7 years ago
Reviewers:
dstockwell
CC:
blink-reviews, shans, rjwright, alancutter (OOO until 2018), Mike Lawther (Google), eae+blinkwatch, dglazkov+blink, dstockwell, Timothy Loh, darktears, Steve Block, dino_apple.com, Eric Willigers
Visibility:
Public.

Description

Correctly apply per-keyframe timing functions Currently, when a per-keyframe timing function is applied to an element which is targeted by multiple animations, the timing function may be applied to the wrong CSSAnimationData object. This causes the per-keyframe timing function to be ignored. This patch fixes the problem by making sure the relevant CSSAnimationData object is always first in the keyframe's RenderStyle. R=dstockwell BUG=288540, 322680 Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=162672

Patch Set 1 #

Patch Set 2 : Fix #

Patch Set 3 : Fix debug build #

Patch Set 4 : #

Patch Set 5 : Add an additional LayoutTest to cover the crash in crbug.com/322680 #

Patch Set 6 : #

Messages

Total messages: 4 (0 generated)
Steve Block
7 years, 1 month ago (2013-11-22 03:23:36 UTC) #1
dstockwell
lgtm
7 years ago (2013-11-26 04:40:38 UTC) #2
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/steveblock@chromium.org/24085002/203001
7 years ago (2013-11-26 05:06:06 UTC) #3
commit-bot: I haz the power
7 years ago (2013-11-26 06:59:55 UTC) #4
Message was sent while issue was closed.
Change committed as 162672

Powered by Google App Engine
This is Rietveld 408576698