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: Fri, 29 Jul 2011 16:57:21 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QmqNF-0007za-Ta@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13333

--- Comment #42 from Henri Sivonen <hsivonen@iki.fi> 2011-07-29 16:57:21 UTC ---
(In reply to comment #41)
> (1) the resolution fails to address the bug, which is that video/audio elements
> do not support param children (while object does); the issue of whether source
> should also support param children is incidental as noted in the original
> submission;

<embed> uses attributes. <object> only uses <param>, because it wasn't possible
to make arbitrary attributes allowed in a DTD. We aren't using DTDs anymore, so
the only reason for the <param> design to continue to exist is that object
already uses <param>.

> (2) the resolution is based in part on the invalid claim that a technical
> change that affects parsing is not permissible because "it is treated as a void
> [empty] element in shipped versions of all the major general-purpose browsers";
> this is entirely irrelevant, and probably not true either

It is true and the truth is easily experimentally verifiable. (I experimentally
verified it today.)

> (3) the resolution assumes the bug is intended to be used "to mint
> vendor-proprietary attributes", which is not the case;

It's intended to mint vendor-proprietary name-value pair parameters, AFAICT.

-- 
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 Friday, 29 July 2011 16:57:26 UTC

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