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 27854 - [MSE] Should fetch algorithm failure trigger detaching from a media element?
Summary: [MSE] Should fetch algorithm failure trigger detaching from a media element?
Status: RESOLVED MOVED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: CR
Assignee: Adrian Bateman [MSFT]
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-19 12:25 UTC by Philip Jägenstedt
Modified: 2015-10-13 23:00 UTC (History)
4 users (show)

See Also:


Attachments

Description Philip Jägenstedt 2015-01-19 12:25:43 UTC
https://w3c.github.io/media-source/#mediasource-detach

"The following steps are run in any case where the media element is going to transition to NETWORK_EMPTY and queue a task to fire a simple event named emptied at the media element. These steps must be run right before the transition."

Blink also detaches in the fetch algorithm failure steps, when networkState reaches NETWORK_NO_SOURCE. Should this be part of the spec? I'm not sure it matters much, but things may be easier to understand/explain if the resource selection algorithm is the only thing that invokes "detaching from a media element."
Comment 1 Matt Wolenetz 2015-10-13 23:00:25 UTC
This bug has been migrated to the GitHub issue tracker. Please follow/update progress using the GitHub issue:
https://github.com/w3c/media-source/issues/18