W3C home > Mailing lists > Public > public-html-media@w3.org > January 2015

[Bug 27854] New: [MSE] Should fetch algorithm failure trigger detaching from a media element?

From: <bugzilla@jessica.w3.org>
Date: Mon, 19 Jan 2015 12:25:43 +0000
To: public-html-media@w3.org
Message-ID: <bug-27854-5436@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27854

            Bug ID: 27854
           Summary: [MSE] Should fetch algorithm failure trigger detaching
                    from a media element?
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Source Extensions
          Assignee: adrianba@microsoft.com
          Reporter: philipj@opera.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org

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."

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 19 January 2015 12:25:45 UTC

This archive was generated by hypermail 2.3.1 : Monday, 19 January 2015 12:25:46 UTC