[Bug 24347] New: Use consistant criteria for transitioning to HAVE_FUTURE_DATA.

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

            Bug ID: 24347
           Summary: Use consistant criteria for transitioning to
                    HAVE_FUTURE_DATA.
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Source Extensions
          Assignee: adrianba@microsoft.com
          Reporter: acolwell@google.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org

The "SourceBuffer monitoring" algorithm in Section 2.4.4 and the "Coded frame
processing" algorithm in Section 3.5.8 don't use the same criteria for
transitioning the HTMLMediaElement.readyState to HAVE_FUTURE_DATA.

SourceBuffer monitoring text:
"If buffered for at least one object in activeSourceBuffers contains a
TimeRange that includes the current playback position but not enough data to
ensure uninterrupted playback:"

Coded frame processing algorithm text:
"If the HTMLMediaElement.readyState attribute is HAVE_CURRENT_DATA and the new
coded frames cause all objects in activeSourceBuffers to have media data beyond
the current playback position, then run the following steps:"


I propose that the SourceBuffer monitoring text be updated to the following:
"If buffered for all objects in activeSourceBuffers contains a TimeRange that
includes the current playback position and some time beyond the current
playback position, but not enough data to ensure uninterrupted playback:"

I believe this will bring the 2 algorithms into sync and avoid potential
readyState oscillations caused by different criteria being used.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 21 January 2014 23:06:57 UTC