W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2007

[whatwg] overlap and Browser DOMs

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 02 Feb 2007 20:04:07 +0100
Message-ID: <op.tm4xw5g264w2qv@id-c0020>
On Fri, 02 Feb 2007 19:57:21 +0100, Elliotte Harold  
<elharo at metalab.unc.edu> wrote:
>> Only if there's non-whitespace content as far as I can tell.
>
> In my tests taking out the whitespace did not change the results, though  
> one might have expected it to.

I tested in Firefox 2 fwiw.


>>> What does Opera do? I haven't been able to coax it into giving me an  
>>> answer yet.
>>  "magic"
>
> Could you perhaps elaborate? Does Opera show a single node which is a  
> child of both p elements? If so, which is its parent?

Oh sure. For <p><strong></p><p></strong> the _DOM_ tree becomes:

   html
     body
       p
         strong
           p

(Also for variants with text nodes in between.)

It should be noted that this is quite different from the actual rendering  
you get. This is this way mostly for performance reasons and works quite  
fine.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Friday, 2 February 2007 11:04:07 UTC

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