24347 2014-01-21 23:06:55 +0000 Use consistant criteria for transitioning to HAVE_FUTURE_DATA. 2014-03-03 23:46:27 +0000 1 1 1 Unclassified HTML WG Media Source Extensions unspecified PC Linux RESOLVED FIXED P2 normal --- 1 acolwell adrianba cyril.concolato mike public-html-media public-html-bugzilla oldest_to_newest 98853 0 acolwell 2014-01-21 23:06:55 +0000 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. 101799 1 acolwell 2014-03-03 23:46:27 +0000 Change committed https://dvcs.w3.org/hg/html-media/rev/cad94fce3b90