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: http://www.whatwg.org/C#the-video-element Complete: http://www.whatwg.org/c#the-video-element Referrer: Comment: Shouldn't <video> allow intermixed script-supporting elements? Posted from: 2a00:801:e0:30:d9c4:c34f:b530:6023 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)
I assume you mean before and between <source> and <track>? What's the benefit?
Maybe you want to stamp out <source>s or <track>s from a <template>, or you want to run a script that sets a capturing listener for "error" for the <video> before the <source>s are parsed instead of putting onerror="" on each <source>.
I'm finding it hard to come up with a plausible scenario where a template is the easiest way to stamp out some <track> or <source> elements...
Simon, want to spec or WONTFIX this?
I'd like to fix this and the other template content model bugs.
Let’s re-raise this in the GitHub issue tracker if necessary.