This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The section on “Seeking” 2.4.3 in the 12 March 2013 Editors Draft contains the following text (“Seeking“ is 3.4.3 in the first public working draft and the text is the same). The media element feeds data from the media segments into the decoders until the new playback position is reached. “feeds data from the media segments” can be interpreted in many different ways. What does this actually mean in terms of what the user sees? At least in the following scenarios; - The new playback position is a RAP but not the start of a DASH segment - The new playback position is not a RAP How much is implementation dependent?
(In reply to comment #0) > The section on “Seeking” 2.4.3 in the 12 March 2013 Editors Draft contains > the following text (“Seeking“ is 3.4.3 in the first public working draft and > the text is the same). > > The media element feeds data from the media segments into the decoders until > the new playback position is reached. > > “feeds data from the media segments” can be interpreted in many different > ways. > > What does this actually mean in terms of what the user sees? At least in the > following scenarios; > - The new playback position is a RAP but not the start of a DASH segment > - The new playback position is not a RAP > > How much is implementation dependent? This is a pretty old part of the spec. I'll update it to something along the lines of "The media element feeds coded frames from the active track buffers starting with the closest random access points that are before the new playback position." I'll also add a definition for "active track buffers" that indicates that these are the track buffers that are associated with the selected tracks. This is a subset of the tracks in the SourceBuffer objects that are in MediaSource.activeSourceBuffers.
Change committed. https://dvcs.w3.org/hg/html-media/rev/f7f2b7226543