Bug 22546
Summary: | REGRESSION (3.2.1-TOT): Animations misbehave at webkit.org blog on Windows | ||
---|---|---|---|
Product: | WebKit | Reporter: | mitz |
Component: | New Bugs | Assignee: | Chris Marrin <cmarrin> |
Status: | RESOLVED WORKSFORME | ||
Severity: | Normal | CC: | cmarrin, dev+webkit, dino, simon.fraser |
Priority: | P1 | Keywords: | NeedsReduction, PlatformOnly, Regression |
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | Windows XP | ||
URL: | http://webkit.org/blog/138/css-animation/ |
mitz
Steps to reproduce:
1) Go to the URL
2) Click the light blue div that is supposed to spin when clicked
3) Hover over the dark red div that is supposed to get a thicker blue border
Results:
The light blue div does not spin, and while the red div's border animates, it animates inwards instead of outwards, as if the box-sizing mode is wrong.
Regression:
Behaves correctly in Safari 3.2.1 on Windows, behaves correctly in TOT on Mac. Broken in TOT on Windows.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
mitz
My guess is that this might have to do with MSVC's different behavior with enums in bitfields.
Brent Fulgham
For what it's worth, this bug is also present in a ToT build of Windows Cairo. As this is also built with Visual Studio, it probably is due to the same cause.
I thought this might help corroborate the theory that Visual Studio is to blame.
Matt Lilek
If you load the blog post and scroll down without hovering over the first animation example, the third one's blue border grows properly. Also, after you click on the second example, if you force a relayout (NOT just a repaint) by adjusting the window size, the animation "unsticks" and is carried out.
FWIW this seems to work properly in the latest Chrome nightly (6116 - http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/) which, if I've poked around their tree properly, appears to use WebKit r38729 (http://src.chromium.org/svn/trunk/src/WEBKIT_MERGE_REVISION).
Chris Marrin
Works with WebKit commit 38878. Please retry with this version or later.