27843 2015-01-16 09:22:38 +0000 [MSE] Should the media element load algorithm trigger detaching from a media element? 2015-10-13 22:57:46 +0000 1 1 1 Unclassified HTML WG Media Source Extensions unspecified PC Linux RESOLVED MOVED P2 normal CR 1 philipj adrianba acolwell mike public-html-media wolenetz public-html-bugzilla oldest_to_newest 117272 0 philipj 2015-01-16 09:22:38 +0000 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. 123690 1 wolenetz 2015-10-13 22:57:46 +0000 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