W3C home > Mailing lists > Public > public-html-media@w3.org > August 2012

[Bug 18666] New: Define what HTMLMediaElement.seekable returns

From: <bugzilla@jessica.w3.org>
Date: Thu, 23 Aug 2012 15:15:38 +0000
To: public-html-media@w3.org
Message-ID: <bug-18666-5436@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18666

           Summary: Define what HTMLMediaElement.seekable returns
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Source Extensions
        AssignedTo: adrianba@microsoft.com
        ReportedBy: philipj@opera.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org


http://dev.w3.org/html5/spec/media-elements.html#dom-media-seekable
http://dev.w3.org/html5/spec/media-elements.html#dom-media-seek

The HTMLMediaElement seek algorithm clamps the requested position to the
closest seekable range, so anything outside the reported seekable ranges is
impossible to seek to.

It's not defined in MSE how to report the seekable attribute and it's not clear
that there's a good answer, since the browser isn't in a good position guess
what ranges the application will be able to provide.

Possible solutions:

1. Expose [0, duration]. This is still broken because it's a complete lie for
Infinite duration, and for implicit duration it makes it impossible to seek
beyond the already appended data.

2. Expose no seekable ranges at all, and say that the clamping step of the
seeking algorithm should be skipped for MSE. That works, but isn't exactly
elegant.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 23 August 2012 15:15:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:48:25 UTC