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 18624 - endOfStream("network") issues
Summary: endOfStream("network") issues
Status: VERIFIED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Adrian Bateman [MSFT]
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-20 13:51 UTC by Philip Jägenstedt
Modified: 2012-09-14 12:31 UTC (History)
3 users (show)

See Also:


Attachments

Description Philip Jägenstedt 2012-08-20 13:51:51 UTC
http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html#dom-endofstream

MSE maps endOfStream("network") to "If the connection is interrupted, causing the user agent to give up trying to fetch the resource" but HTML has no such section, it is called "If the connection is interrupted after some media data has been received, causing the user agent to give up trying to fetch the resource."

The "after some media data has been received" difference is relevant, because at least in Opera, this step of the algorithm can only be run when HTMLMediaElement.readyState > HAVE_NOTHING. Network errors reported when readyState is HAVE_NOTHING are treated as "If the media data cannot be fetched at all, due to network errors, causing the user agent to give up trying to fetch the resource".

For consistency with HTTP and other resources, I think the handling should be different "after some media data has been received", i.e. depending on readyState.
Comment 1 Aaron Colwell (c) 2012-09-14 01:02:29 UTC
Changes committed.
http://dvcs.w3.org/hg/html-media/rev/349559debcc3