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 00:28:52 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QlrzY-0005di-Lp@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13333

--- Comment #20 from Bob Lund <b.lund@cablelabs.com> 2011-07-27 00:28:50 UTC ---
(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.

>Browser plugins are used in HTML through the object and embed tags, which
> have a param attribute, so that should solve it. If a particular Web page needs
> to communicate something from the plugin with the video element, then the
> data-* attributes would make sense. Even if there was a recommendation
> ("standard") to use a particular plugin with particular params and a particular
> JavaScript library to do this communication.

To reiterate, there is no plugin. The user agent will be expected to support a
media format that includes a DRM. It is desired the HTML5 video element and all
of the related features be available to Web content that runs on this browser.
I think that as media delivery using new media formats become more widespread
on the Web there may be other new browser implementations that will support
certain aspects of these formats and there may be a need to pass information
across the video element API.

-- 
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 00:28:58 UTC

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