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

[whatwg] Tag Soup: Blocks-in-inlines

From: Henri Sivonen <hsivonen@iki.fi>
Date: Sun, 29 Jan 2006 11:10:07 +0200
Message-ID: <CE899B88-5D8B-479A-86E1-1C79885B9782@iki.fi>
On Jan 27, 2006, at 09:16, Ian Hickson wrote:

> In that case I don't understand your proposal.
>
> We need something that, given this:
>
>    <em><p>X
>
> ...results in this DOM:
>
>    BODY
>      EM
>        P
>
> ...and given this:
>
>    <em><p>X</em></p>
>
> ...results in this DOM:
>
>    BODY
>      EM
>      P
>        EM
>
> Given that "X" can be arbitrarily long, how do you generate the  
> above DOMs
> using your system without sacrificing incremental rendering?
>
> I understood your system to be:
>
>    [TOKENISER] --> [PREPROCESSOR] --> [PARSER]
>
> ...where the preprocessor rearranges tokens, and the parser creates  
> the
> DOM. How does your system handle the cases above without blocking  
> in the
> preprocessor stage to wait for the end of X?

By producing the second DOM in both cases.

Based on Hyatt's comments, I take it that this would make the DOM too  
heavy and would not work.

-- 
Henri Sivonen
hsivonen at iki.fi
http://hsivonen.iki.fi/
Received on Sunday, 29 January 2006 01:10:07 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:44 UTC