[Webkit-unassigned] [Bug 87153] New: [chromium] Forcibly sync running animations in the waiting state when synchronized start times are needed.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=87153

           Summary: [chromium] Forcibly sync running animations in the
                    waiting state when synchronized start times are
                    needed.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: vollick at chromium.org
                CC: enne at google.com


Currently, when we force a sync of the animations, we blindly copy them to the impl thread. This is a problem if the main thread is waiting for a synchronized start time and the animation has already started on the main thread. In this case, we would copy the running animation over to the impl thread, where it would happily tick, but would never send an 'animation started' notification to the main thread. If the main thread animation requires this notification, we must copy the animation over in a 'waiting' state.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.