- From: <bugzilla@jessica.w3.org>
- Date: Mon, 20 Aug 2012 13:51:51 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18624 Summary: endOfStream("network") issues Product: HTML WG Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Media Source Extensions AssignedTo: adrianba@microsoft.com ReportedBy: philipj@opera.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-media@w3.org 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. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 20 August 2012 13:51:52 UTC