- From: <bugzilla@jessica.w3.org>
- Date: Tue, 09 Sep 2014 13:42:03 +0000
- To: public-html-admin@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26764
Bug ID: 26764
Summary: Behavior not specified for MediaController when one of
the media elements is media fragment URI with start
position > 0
Product: HTML WG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec
Assignee: dave.null@w3.org
Reporter: amogh.bihani@samsung.com
QA Contact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-admin@w3.org,
public-html-wg-issue-tracking@w3.org
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 9 September 2014 13:42:06 UTC