This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24347 - Use consistant criteria for transitioning to HAVE_FUTURE_DATA.
Summary: Use consistant criteria for transitioning to HAVE_FUTURE_DATA.
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Adrian Bateman [MSFT]
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-21 23:06 UTC by Aaron Colwell
Modified: 2014-03-03 23:46 UTC (History)
3 users (show)

See Also:


Attachments

Description Aaron Colwell 2014-01-21 23:06:55 UTC
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.
Comment 1 Aaron Colwell 2014-03-03 23:46:27 UTC
Change committed
https://dvcs.w3.org/hg/html-media/rev/cad94fce3b90