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#dom-TrackList-getKind-categories Complete: http://www.whatwg.org/c#dom-TrackList-getKind-categories Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Use the media element task source for audio/video tracks Posted from: 113.23.85.58 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 Safari/537.36 OPR/20.0.1387.59 (Edition Next)
Maybe we discussed this and I suck at search my bugs/mail, but: Using the media element task source for the change/addtrack/removetrack events fired at audio and video track lists seems like a very good idea, so that those events aren't fired after a new load() when they could be confused for event related to the new resource.
I can't work out why this didn't use the media element event source. Let me know if I missed something important.
Checked in as WHATWG revision r8600. Check-in comment: Made 'addtrack' and other events fire on the media element task source. http://html5.org/tools/web-apps-tracker?from=8599&to=8600
Thanks, that was a small diff but seems to be all that's needed!