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 23:55:51 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QlrTb-0004AD-O9@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13333

--- Comment #19 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2011-07-26 23:55:49 UTC ---
(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. 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.

-- 
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 23:55:56 UTC

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