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: Wed, 27 Jul 2011 15:47:36 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qm6Ke-0000tE-3Y@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13333

--- Comment #29 from Bob Lund <b.lund@cablelabs.com> 2011-07-27 15:47:33 UTC ---
(In reply to comment #21)
> (In reply to comment #20)
> > (In reply to comment #19)
> > > (In reply to comment #18)
> > > > 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
> > > 
> > > Since browsers don't support DRM, you will need to provide a browser plugin to
> > > interpret the DRM parameters, no matter in which way you put them into the HTML
> > > page.
> > 
> > I guess you're referring to some of the current more popular browsers. In fact,
> > there is an activity underway defining requirements for an HTML5 user agent
> > that supports a specific DRM in a widespread, but specialized application. In
> > this case, the need to pass DRM related info exists. Aside from this specific
> > requirement to be able to convey DRM specific information acted on by the user
> > agent the video element can be used as is.
> 
> 
> I am talking about User Agents that implement the HTML5 specification in a
> cross-UA-compatible way as defined by the W3C. Are you are talking about an
> application that supports the HTML5 specification and other extra
> specifications?

Yes, I am talking about a user agent that implements the HTML5 specification
and other media format specifications which are defined independent of
HTML5.Today, popular user agents support different audio and video codecs.
Support for media types is orthogonal to conformance to the HTML5
specification.


> That then goes beyond being a HTML5 UA and would not be
> compatible with HTML5 UAs for that extra functionality (unless used with
> plugins).

I disagree. HTML5 does not specify any audio/media formats.

> This is be a move towards proprietary extensions that only work in
> specific browsers

I fail to see how this goes beyond the situation as it exists today. I can
author Web content that attempts to play a video of a media type supported by
HTML5 UA implementation 'A' and not supported in 'B'. This page only works in
specific browsers but no one is claiming this is a proprietary extension.

I think what this bug is proposing, and what I see a need for, is an HTML5
specified way to pass arbitrary media specific information to a UA
implementation of the video element.

> and thus doesn't help to retain the Web as an interoperable
> platform. Why not add such specifications directly to HTML5 and bring it to the
> whole Web?

-- 
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 Wednesday, 27 July 2011 15:47:40 UTC

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