20063 2012-11-23 15:27:56 +0000 Unclear whether a <track> element's load event should fired if appended to a <video> with no "src" attribute 2016-04-21 15:39:49 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC All RESOLVED FIXED whatwg-resolved P2 normal --- 1 graouts silviapfeiffer1 erika.doyle mike philipj public-html-admin public-html-wg-issue-tracking silviapfeiffer1 travil zcorpan public-html-bugzilla oldest_to_newest 78702 0 graouts 2012-11-23 15:27:56 +0000 It's unclear to me whether a <track> element that is a child of a <video> element, where the <video> element has no "src" attribute set, should ever fire its "load" event. In this situation, Opera 12.11 fires a "load" event but a WebKit nightly doesn't. For reference, see the final test in http://w3c-test.org/html/tests/submission/Opera/media/interfaces/TextTrack/addCue.html. 78706 1 zcorpan 2012-11-23 15:52:50 +0000 http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#start-the-track-processing-model "If the text track's track element does not have a media element as a parent, abort these steps." It does not matter if the parent has a src attribute (or <source> children). AFAICT, the spec is clear, and WebKit nightly has a bug. 78707 2 zcorpan 2012-11-23 15:55:47 +0000 (Oops, I didn't notice this was a HTML WG bug.) 78708 3 graouts 2012-11-23 16:01:19 +0000 Thanks for noticing this Simon, I think you're correct. 78793 4 silviapfeiffer1 2012-11-26 01:54:15 +0000 There is no "load" event for media elements, only a "loadstart", "loadedmetadata" or "loadeddata". Neither does the track element have a "load" event - it only have a readiness state of "loaded". Are you referring to the "load" event of the page? 78816 5 zcorpan 2012-11-26 07:30:33 +0000 track has a load event. "If the file was successfully processed, fire a simple event named load at the track element." http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#sourcing-out-of-band-text-tracks 78822 6 silviapfeiffer1 2012-11-26 11:54:36 +0000 Ah right! We should add an event list for track at the end, cause that totally slipped by me - somewhere near: * http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#cue-events * http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#mediaevents As for the bug as recorded: I agree with comment #1. Antoine: you should register a bug on WebKit. 78836 7 graouts 2012-11-26 16:19:50 +0000 Here's the WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=103258. 124405 8 zcorpan 2015-12-10 10:58:08 +0000 (In reply to Silvia Pfeiffer from comment #6) > Ah right! We should add an event list for track at the end, cause that > totally slipped by me - somewhere near: > > * > http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video- > element.html#cue-events No, there's a common section for events on all HTML elements. > * > http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video- > element.html#mediaevents Yes. https://github.com/whatwg/html/issues/392 125993 9 travil 2016-04-21 15:39:49 +0000 HTML5.1 Bugzilla Bug Triage: Fixed The fix from WHATWG PR: https://github.com/whatwg/html/pull/419/files has been included into the W3C HTML spec. I believe this resolves the bug. If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!