W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2006

[whatwg] Tag Soup: Blocks-in-inlines

From: Billy Wong <billyswong@gmail.com>
Date: Thu, 26 Jan 2006 10:22:16 +0800
Message-ID: <500602e30601251822i478335d2u4a3820e8ab8803be@mail.gmail.com>
On 1/26/06, Henri Sivonen <hsivonen at iki.fi> wrote:
> On Jan 25, 2006, at 17:17, Billy Wong wrote:
>
> > Sorry.  I don't notice that this is invaild.  I am new here.  What
> > makes inline-level element not feasible to contain block-level
> > elements??
>
> The HTML 4.01 Transitional DTD. Gecko and WebCore try to force the
> document tree to be a sane Transitional document tree.
>
But I am still not clever enough to grasp it.  For
"<span><div></div><div></div></span>", what is pratically preventing
it from being a sane document tree, so that it has to be defined
invalid in HTML 4.01?  The key word is "infeasible".  So far, I can
only explain to myself that mixing the order of close-tag will make
DOM not a tree and therefore, wrong.

> > I should change my line to "break things that are not well-formed
> > instead of those well-formed"
>
> I think it is perfectly OK for residual style to kick in when there
> are block elements inside inline elements in text/html even if the
> document was well-formed when parsed as XML.
>
> > First, my idea would not, and should not, break the whole web.  If it
> > is really deployed, it would only break webpage that are not
> > well-formed in this particular way.
>
> That's a large chunk of the Web.
>
> --
> Henri Sivonen
> hsivonen at iki.fi
> http://hsivonen.iki.fi/
>
>
>
Received on Wednesday, 25 January 2006 18:22:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:25 UTC