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 26764 - Behavior not specified for MediaController when one of the media elements is media fragment URI with start position > 0
Summary: Behavior not specified for MediaController when one of the media elements is ...
Status: RESOLVED DUPLICATE of bug 26768
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-09 13:42 UTC by Amogh Bihani
Modified: 2014-09-10 09:29 UTC (History)
5 users (show)

See Also:

Attachments

Description Amogh Bihani 2014-09-09 13:42:03 UTC 
If a media fragment URI with a start position greater than 0 is attached to media controller and a new media element is added to the media controller, then it is not specified how the new element should be seeked. If the ready state is HAVE_NOTHING, then the seeking is aborted and the media element has to be seeked when it is played.
I guess we should set something like default playback start position for that media element and seek it after the state is > HAVE_NOTHING.
Otherwise we would be buffering some data which won't be played and skipped as soon as media controller is played.
Comment 1 Philip Jägenstedt 2014-09-10 09:29:14 UTC 

*** This bug has been marked as a duplicate of bug 26768 ***