W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2011

[Bug 13333] audio, video (and source) elements require param children or equivalent

From: <bugzilla@jessica.w3.org>
Date: Tue, 26 Jul 2011 14:54:45 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qlj1x-0004ov-Lv@jessica.w3.org>

--- Comment #18 from Bob Lund <b.lund@cablelabs.com> 2011-07-26 14:54:44 UTC ---
(In reply to comment #17)
> (In reply to comment #15)
> > If an eventual standardisation is envisaged of such parameters, and a browser
> > is intending to experiment with a new "parameter", they will just pick an
> > attribute that has not been used yet by the standards and other browsers and
> > propose that in preparation for standardisation. For JavaScript developers, the
> > data-* attributes are sufficient for experimentation and demonstration of a use
> > case prior to proposing it for standardisation.
> > 
> > BTW: you seem to believe that <object> is deprecated. That is not the case, I
> > just wanted to make that clear. You can continue to use <object> with a browser
> > plugin, even for any needs where you have special audio and video requirements.
> (1) it is not appropriate for other standards organizations, e.g., those
> writing profiles on HTML5, to define attributes on video/audio elements; such
> practice is considered poor form
> (2) i have stated it a number of times in this thread, but the use of param I
> am describing here is *NOT* intended to be interpreted by JavaScript; while
> that is possible, and I do not preclude it, it is beside the point for the
> purpose of this bug report; this bug report is addressing the need for the
> content author to specify one or more parameters to be interpreted by the UA
> for the purpose of configuring the transport, decoding, playback, rendering, or
> other usage of video/audio content when specified with the video/audio element
> types, and where such parameters are not yet standardized as content attributes
> by HTML5;
> (3) saying "please use <object>" is not a sufficient answer unless you redefine
> HTMLObjectElement as HTMLVideoElement or HTMLAudioElement (according to the
> media type) and additionally add all the new equipment defined for use with
> video/audio to the object element;
> So, to reiterate:
> (1) using non-standard attributes on video/audio in the HTML syntax of HTML5
> won't work for other defining (external) standards/specifications;
> (2) using data-* won't work because that is based on JS interpretation only;
> (3) using <object/> will not work because it does not implement
> HTML{Video,Audio}Element nor does it have the other new mechanisms of
> video/audio, e.g., <source> children, <track> children, etc.
> G.

I would like to point out that there is an existing need to pass DRM parameters
to a user agent that supports that DRM. This in no way extends the
functionality of the video API but instead conveys information to the user
agent that it needs to fetch and decode the media. <param> would provide a way
to do this. data- would also work if the restriction that Glenn cited were
removed; is that a possible path.

Bob Lund

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 26 July 2011 14:54:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:14 UTC