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

[whatwg] Tag Soup: Blocks-in-inlines

From: David Hyatt <hyatt@apple.com>
Date: Wed, 25 Jan 2006 23:37:30 -0800
Message-ID: <5BBCC7DA-09AA-4013-A31E-13FDD09D09F0@apple.com>
We used to not reopen the tags.  It was the #1 rendering bug in our  
engine.  We had over 60 unique duplicates of the bug in our internal  
database.  All that would happen if we didn't reopen the tags is that  
people would switch to another browser. :)

dave

On Jan 25, 2006, at 11:31 PM, Blanchard, Todd wrote:

> I have to ask - why reopen the tags?  Why not throw them on the  
> floor?  They're wrong anyhow and cause problems.  If bad code  
> didn't (sort of) work, people would write different code.  That  
> would be good.
>
> IOW:
> <em><p>stuff</em></p> looks like
>
> Body
>   +em
>   +p
>     +stuff
>
>
>
> hyatt at apple.com wrote:
>
> For example, allowing blocks inside inlines minimizes the number of  
> residual style tags that you have to re-open, and deferring the  
> reopening of such tags until a misnested close tag is encountered  
> ensures that well- formed documents don't end up with a bloated  
> DOM.  ...
> Your DOM would grow unacceptably large on real-world pages if you  
> try to restrict blocks from being inside inlines and end up  
> reopening the inlines over and over again inside each block.
>
> On Jan 25, 2006, at 5:41 PM, Ian Hickson wrote:
>
>> On Wed, 25 Jan 2006, Simon Pieters wrote:
>>>
>>> Thus, <em><p>XY</p></em> should be parsed as:
>>>
>>> BODY
>>>   + EM
>>>   + P
>>>     + EM
>>>       + #text: XY
>>>
Received on Wednesday, 25 January 2006 23:37:30 UTC

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