This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html Multipage: http://www.whatwg.org/C#found-another-audio-track Complete: http://www.whatwg.org/c#found-another-audio-track Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Can new audio/video tracks be added before/after loadedmetadata? Posted from: 83.218.67.123 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 OPR/21.0.1432.48 (Edition Next)
These are separate steps in the resource fetch algorithm: "If the media resource is found to have an audio track" "If the media resource is found to have a video track" "Once enough of the media data has been fetched ..." Does this mean that audio/video tracks can be added at any time, even after playback has begun? I think that can happen when using Media Source Extensions, so probably yes. However, the only point where tracks are enabled/selected is in the last step: "If either the media resource or the address of the current media resource indicate a particular set of audio or video tracks to enable ..." What should happen when the media resource itself indicates that a track should be enabled/selected, but there are already enabled/selected tracks?
I think this got resolved in response to one of the other bugs; is there anything still unclear about this?
Yes, by moving the "If either the media resource or the address of the current media resource indicate a particular set of audio/video tracks to enable" steps into "If the media resource is found to have an audio/video track" the problem has been solved. Thanks!