[Webkit-unassigned] [Bug 11997] New: Ranges are not fixed after mutation

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=11997

           Summary: Ranges are not fixed after mutation
           Product: WebKit
           Version: 420+ (nightly)
          Platform: Macintosh
        OS/Version: Mac OS X 10.4
            Status: NEW
          Severity: Major
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: rvamerongen at xs4all.nl


When using the supplied code as sample
1. USING: 
>node2.appendChild(rangeAnd2.extractContents());
>rangeAnd2.insertNode(node2);

 you will see that the andRange and the janeDoeRange are damaged and not fixed.
Because of Drosera isn't really helpfull yet with this, I can't realy check
what is going on, but it looks like janeRange is pointing to "john"'s content
and the visual reference is gone ( whatever that is ).

2. USING: 
>rangeAnd2.surroundContents(node2);

 you will see that the  janeDoeRange is damaged and not fixed.
But also here it looks like janeRange is pointing to "john"'s content ( but in
another test it did point to somewhere else ).

See about fixing
:http://www.w3.org/TR/DOM-Level-2-Traversal-Range/ranges.html#Level-2-Range-Mutation
About identical results expected see:
http://developer.mozilla.org/en/docs/DOM:range.surroundContents

Because some pages are using this, they let safari crash at a later stadium.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.