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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13333

--- Comment #2 from Glenn Adams <glenn@skynav.com> 2011-07-23 04:39:55 UTC ---
(In reply to comment #1)
> Such params are always just useful for a particular website because of the way
> they have been set up. Your examples confirm this. Thus, IMO the data-*
> attributes seem completely sufficient to satisfy these needs.

I disagree. Use of these parameters are definitely *not* specific to a
particular website, and, in fact, may require specific semantics in a UA. At
present, HTML5 3.2.3.8 states "User agents must not derive any implementation
behavior from these attributes or values. Specifications intended for user
agents must not define these attributes to have any meaningful values." In
contrast, the intended use of param is precisely to define meaningful values
for which UAs derive implementation behavior.

The fact that param is defined on object, and made use of regularly in the
manner I describe, and since it is the intent that audio and video elements
supplant the use of object, it is necessary to retain this usage or provide an
equivalent.

> Also not that swf or sliverlight files are much more than just audio or video
> resources and can thus not be used in audio and video elements. So, those
> examples are not really valid.

Oh? Why not? There is nothing in the definition of audio or video that preclude
its use. There are no restrictions placed by HTML5 on the media type referenced
by these elements. Since swf and silverlight can represent audio and video
content, why shouldn't they be reasonable examples. In any case, the problem
described here is independent of the examples, and stands on its own without
requiring use of these particular formats.

G.

-- 
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 Saturday, 23 July 2011 04:40:01 UTC