W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

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

From: <bugzilla@jessica.w3.org>
Date: Wed, 03 Aug 2011 20:10:48 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QohmC-0002gD-Po@jessica.w3.org>

John Foliot <jfoliot@stanford.edu> changed:

           What    |Removed                     |Added
           Keywords|                            |TrackerIssue

--- Comment #49 from John Foliot <jfoliot@stanford.edu> 2011-08-03 20:10:48 UTC ---
(In reply to comment #40)
> EDITOR'S RESPONSE: This is an Editor's Response to your comment. 
> Status: Rejected
> Change Description: no spec change
> Rationale: This bug report requests the HTML spec to provide <param name=foo
> value=bar> children for <source> as a mechanism for special-purpose browsers to
> attach name-value parameters to the <source> element.
> <source> element is
> treated as a void element in shipped versions of all the five major
> general-purpose browsers. Void elements can't have children, so this bug report
> is asking for an HTML parser change.

Actually, the bug stated that <audio>, <video> *and* <source> should be able to
take <param> attributes. While it may be that at this time <source> cannot take
a <param>, technically both <audio> and <video> could. 

In Comment 48 Glenn also notes:
"Finally, I would note that it may be acceptable to add param only to video and
audio, and not require its support with param." (Did he mean source instead of
param here?)

> Therefore, the general
> problem of attaching proprietary name-value pairs to the <source> element is

Actually, this now appears incorrect - data-* will not work here.

> and the specific solution of introducing <param> children to
> <source> is WONTFIX.

It is clear that this is an issue that is more complex than what some
participants think. Given that there has been continued dialog on this topic
subsequent to Henri seeking to close this bug, (and the noted possibility of
negative impacts on accessibility concerns - Comment 30) I will ask that this
become a Tracked Issue at the Task Force. I expect that at least one formal
Change Proposal will emerge.

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, 3 August 2011 20:10:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:59 UTC