[Webkit-unassigned] [Bug 92881] New: HTMLMediaElement may fire the seeked event before currentTime reaches the seek time

[bugzilla-daemon at webkit.org]

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

           Summary: HTMLMediaElement may fire the seeked event before
                    currentTime reaches the seek time
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Media Elements
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: vrk at chromium.org
                CC: fischman at chromium.org


This bug was uncovered when trying to make the media/video-seek-past-end-paused.html pass again.
(see reverted CL: https://bugs.webkit.org/show_bug.cgi?id=83505)

Here is the relevant code snippet:

    video.addEventListener('seeked', seeked);
    video.currentTime = 500;
    ...

    function seeked()
    {
      reportExpected(mediaElement.currentTime == mediaElement.duration, "mediaElement.currentTime", "==", "mediaElement.duration", mediaElement.currentTime);
    }

On certain platforms, currentTime is sometimes a number close to zero instead of being equal to the media element's duration. Seems like the problem may be that HTMLMediaElement::mediaPlayerTimeChanged() will consider a pending seek completed when mediaPlayerTimeChanged() is called. It does not check to make sure that the current time does indeed match the seek time. Needs more investigation.

(This bug does not appear to be chromium-specific, but there is a Chrome-side bug here as well: crbug.com/122448)

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