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 27843 - [MSE] Should the media element load algorithm trigger detaching from a media element?
Summary: [MSE] Should the media element load algorithm trigger detaching from a media ...
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-16 09:22 UTC by Philip Jägenstedt
Modified: 2015-10-13 22:57 UTC (History)
4 users (show)

See Also:


Attachments

Description Philip Jägenstedt 2015-01-16 09:22:38 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."

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.
Comment 1 Matt Wolenetz 2015-10-13 22:57:46 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/17