[Bug 27843] New: [MSE] Should the media element load algorithm trigger detaching from a media element?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27843

            Bug ID: 27843
           Summary: [MSE] Should the media element load algorithm 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."

Per a literal reading of the MSE spec, the media element load algorithm in the
HTML spec does not qualify, as there is no transition to NETWORK_EMPTY. In
Blink the "If a fetching process is in progress for the media element, the user
agent should stop it." step is "implemented" by setting networkState to
NETWORK_EMPTY, but per spec that doesn't happen and doesn't matter since the
resource selection algorithm set it to NETWORK_NO_SOURCE.

A review of exactly which bits of the HTML spec should trigger the detaching
from a media element may be in order. The "These steps must be run right before
the transition." also make it such that the event order depends on the order in
which HTML queues the task to fire the event and sets networkState.

If an explicit hook in HTML would help, let's ask Hixie for one.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Friday, 16 January 2015 09:22:40 UTC