W3C home > Mailing lists > Public > public-html-media@w3.org > May 2018

[media-source] endOfStream() prior to HAVE_METADATA is not defined well

From: wolenetz via GitHub <sysbot+gh@w3.org>
Date: Mon, 21 May 2018 22:36:57 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-325081699-1526942216-sysbot+gh@w3.org>
wolenetz has just created a new issue for https://github.com/w3c/media-source:

== endOfStream() prior to HAVE_METADATA is not defined well ==
In Chrome, `endOfStream()` (either no parameter, 'network', or 'decode) results with the attached HTMLMediaElement's error attribute becoming populated with a MediaError object:
{code: 4, message: "DEMUXER_ERROR_COULD_NOT_OPEN"}
(4 is MEDIA_ERR_SRC_NOT_SUPPORTED).

This is because Chrome assumes that any attempt to endOfStream() a MediaSource before its attached HTMLMediaElement has reached HAVE_METADATA means that there is not enough metadata to consider any of it renderable, so follows the endOfStream('decode') steps:

> If the HTMLMediaElement.readyState attribute equals HAVE_NOTHING
> Run the "If the media data can be fetched but is found by inspection to be in an unsupported format, or can otherwise not be rendered at all" steps of the resource fetch algorithm's media data processing steps list.

But the endOfStream([no error]) steps for MSE don't consider the media element's readyState like this. Rather, they say to:
> [update duration, then] Notify the media element that it now has all of the media data. [regardless of parent's media element's readyState]

This issue is purely to determine what is the right route forward (does Chrome have a bug, or does the spec, or both?)

Please view or discuss this issue at https://github.com/w3c/media-source/issues/212 using your GitHub account
Received on Monday, 21 May 2018 22:36:59 UTC

This archive was generated by hypermail 2.3.1 : Monday, 21 May 2018 22:36:59 UTC