W3C home > Mailing lists > Public > public-html@w3.org > March 2010

Re: HTML5 Authoring Conformance Study

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Sun, 21 Mar 2010 20:28:12 +0100
To: dbaron@dbaron.org
Cc: Sam Ruby <rubys@intertwingly.net>, Maciej Stachowiak <mjs@apple.com>, HTMLwg WG <public-html@w3.org>
Message-ID: <20100321202812127411.6b194936@xn--mlform-iua.no>
Leif Halvard Silli, Sun, 21 Mar 2010 18:36:38 +0100:
>> youtube.com:
>> What interop issues are solved by disallowing div elements inside of 
>> span elements?
> This is the same question as bug 7056 about flow element inside 
> <caption>: why are they permitted there? And if permitted there, why 
> not also inside <h1>/<h6> elements?
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=7056

Err ... There probably is so many errors in what I say that no one 
bothers to correct me ... But somehow I saw  'h1' when Sam wrote 
'span'. Sorry. 

L. David Baron, Sun, 21 Mar 2010 12:14:36 -0400:
> Blocks inside inlines can, in some cases, cause larger numbers of
> CSS boxes to be present than the author probably expects, which I
> believe in some cases causes performance degradation.  (I've seen
> cases in the past where such performance degradation was
> significant, although those cases may have been fixed in our
> implementation.)
> In many cases, the author intends the outer element to have block
> formatting.  In the other cases, I believe the resulting formatting
> is non-tree-like, which confuses the mental model of the HTML
> element structure representing a tree.

Then <caption> is an inline. So are there not similar problems in 
allowing blocks inside <caption>?
leif halvard silli
Received on Sunday, 21 March 2010 19:28:46 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:13 UTC