[Bug 18615] New: Define how SourceBuffer.buffered maps to HTMLMediaElement.buffered

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18615

           Summary: Define how SourceBuffer.buffered maps to
                    HTMLMediaElement.buffered
           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: acolwell@chromium.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org


The current spec text does not specify how HTMLMediaElement.buffered is
calculated.

Here is a proposal based on what we currently have implemented in Chrome.

- While readyState is "open" HTMLMediaElement.buffered is the intersection of
the SourceBuffer.buffered ranges for all sources in
MediaSource.activeSourceBuffers.
- While readyState is "ended" HTMLMediaElement.buffered is the intersection
above but the end time of the last range in the intersection is extended to the
highest end time across all SourceBuffer.buffered ranges in
MediaSource.activeSourceBuffers.

The behavior is different based on readyState because in the "open" state a
difference between SourceBuffer.buffered ranges could indicate missing data
that should stall playback. Once there has been a transition to "ended" the
application has signalled that it has appended everything it wants played so a
mismatch in the last ranges simply indicate different stream lengths not
missing data.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 17 August 2012 23:11:18 UTC