- From: Ian Hickson <ian@hixie.ch>
- Date: Fri, 23 Oct 2009 03:22:24 +0000 (UTC)
- To: Joe D Williams <joedwil@earthlink.net>
- Cc: HTMLWG WG <public-html@w3.org>
On Thu, 22 Oct 2009, Joe D Williams wrote:
>
> " ... are only short-term workarounds, and the same applies to, e.g.,
> <source> in <video>, or <command>, ... "
>
> this quote was in another topic but it caught my eye because I'm not
> sure how <source> constitutes a workaround; what is the problem allowing
> multiple <source > elements is not solving?
What I meant was that the same problem that affected <itemref> in legacy
browsers would also affect <source> in legacy browsers.
e.g.
<video>
<source>
<div></div>
</video>
...gets parsed as (modulo whitespace):
<video>
<source>
<div></div>
</source>
</video>
...in legacy UAs.
My point was that that wasn't a big deal and would not be a kiler problem
for <itemref>.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 23 October 2009 03:09:41 UTC