- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 8 Jan 2009 11:35:03 +0000 (UTC)
- To: Henri Sivonen <hsivonen@iki.fi>
- Cc: Martin Atkins <mart@degeneration.co.uk>, public-html@w3.org
On Thu, 8 Jan 2009, Henri Sivonen wrote: > On Jan 8, 2009, at 04:03, Ian Hickson wrote: > > > > However, my concern isn't making the void elements actually do > > > something, but rather the cascading failure that happens as soon as > > > you use an unknown void element. > > > > > > The entire page shouldn't break just because one element is not > > > supported by the parser. > > > > Could you elaborate on this? I'm not aware of any cascading failure > > that comes from using any of the void elements proposed in a UA that > > doesn't parse it as expected. > > s/cascading/selector/ The only case new in HTML5 where you can't wrap the offending element in <span> is <source>, and for those it's easy to work around the resulting DOM in the selectors if that is actually needed. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 8 January 2009 11:35:39 UTC