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 26768 - 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 INVALID
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
: 26764 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-09-10 03:14 UTC by Amogh Bihani
Modified: 2014-09-12 14:07 UTC (History)
2 users (show)

See Also:

Attachments

Description Amogh Bihani 2014-09-10 03:14: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 seeking of the new element should be handled. If the ready state is HAVE_NOTHING, then the seeking is aborted and the media element has to be seeked when media controller 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 
*** Bug 26764 has been marked as a duplicate of this bug. ***
Comment 2 Philip Jägenstedt 2014-09-12 14:07:40 UTC 
This bug was the result of a Chromium code review, but when we looked closer the spec did handle this case. (https://codereview.chromium.org/539103002/)