52028 2011-01-06 15:18:12 -0800 animationTime isn't working on Windows 2011-01-07 13:36:47 -0800 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) PC Windows XP RESOLVED FIXED http://build.webkit.org/results/Windows%20XP%20Debug%20(Tests)/r75196%20(23989)/animations/animation-time-pretty-diff.html InRadar, LayoutTestFailure, PlatformOnly P2 Normal --- 51996 1 aroben webkit-unassigned jamesr simon.fraser oldest_to_newest 330475 0 aroben 2011-01-06 15:18:12 -0800 The animationTime property isn't working on Windows. Presumably it has been this way since it was added in r75169. This is currently causing animations/animation-time.html and fast/dom/Window/window-property-descriptors.html to fail. I've checked in Windows-specific failure results for those tests. 330486 1 jamesr 2011-01-06 15:26:31 -0800 That's very odd. I would not expect window.webkitAnimationTime to return undefined, the logic to return a number for that is all in DOMWindow.idl/cpp. 330496 2 aroben 2011-01-06 15:30:56 -0800 <rdar://problem/8831001> 330501 3 jamesr 2011-01-06 15:34:59 -0800 http://build.webkit.org/builders/Windows%20Debug%20%28Build%29/builds/29208 indicates that the Windows Debug builder didn't actually upload a binary after r75169, so my guess is tester was using a pre-'169 binary to run the tests added '169. Seems like the tester configuration is broken if it's using old binar 330503 4 aroben 2011-01-06 15:36:35 -0800 (In reply to comment #3) > http://build.webkit.org/builders/Windows%20Debug%20%28Build%29/builds/29208 indicates that the Windows Debug builder didn't actually upload a binary after r75169, so my guess is tester was using a pre-'169 binary to run the tests added '169. Seems like the tester configuration is broken if it's using old binar Ah! That's due to bug 51996. 330510 5 aroben 2011-01-06 15:45:24 -0800 Let's keep this bug open to track removing the Windows-specific results I added once bug 51996 is fixed. 330934 6 aroben 2011-01-07 12:45:35 -0800 This got fixed in r75205. 330975 7 aroben 2011-01-07 13:36:47 -0800 (In reply to comment #6) > This got fixed in r75205. I meant r75258.