Bug 84592 - [EFL][DRT] Unclear timing behavior of LayoutTestController suspendAnimations() / resumeAnimations()
Summary: [EFL][DRT] Unclear timing behavior of LayoutTestController suspendAnimations(...
Status: RESOLVED DUPLICATE of bug 49182
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit EFL (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Dominik Röttsches (drott)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-23 06:33 PDT by Dominik Röttsches (drott)
Modified: 2012-10-30 05:53 PDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik Röttsches (drott) 2012-04-23 06:33:13 PDT 
animations/stop-animation-on-suspend.html needs more investigation - currently fails with position values too far off.
Comment 1 Jussi Kukkonen (jku) 2012-10-09 08:58:07 PDT 
From the date I'm guessing you're not currently working on this. I'll take a look.
Comment 2 Jussi Kukkonen (jku) 2012-10-09 12:45:15 PDT 
I believe the "webkitAnimationStart" event on document and the one on iframe happen at different times, but the test starts a single timer (on documents event) and of course the the iframe animation isn't synced.

That sounds like quite an assumption in the test, but maybe that's how it is supposed to happen?
Comment 3 Jussi Kukkonen (jku) 2012-10-09 12:47:15 PDT 
Oh, and this is not just EFL. Happens on most (all?) ports.
Comment 4 Jussi Kukkonen (jku) 2012-10-10 04:50:42 PDT 
(In reply to comment #2)
> I believe the "webkitAnimationStart" event on document and the one on iframe happen at different times, but the test starts a single timer (on documents event) and of course the the iframe animation isn't synced.

Rephrasing this: "When animationStart happens, the "iframe-box" element does not even exist in the DOM yet".
Comment 5 Dominik Röttsches (drott) 2012-10-30 05:53:12 PDT 

*** This bug has been marked as a duplicate of bug 49182 ***