[Webkit-unassigned] [Bug 42517] New: Incorrect behaviour calling Range setStart or setEnd with boundary in different document

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=42517

           Summary: Incorrect behaviour calling Range setStart or setEnd
                    with boundary in different document
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: HTML DOM
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: timdown at gmail.com


Created an attachment (id=61903)
 --> (https://bugs.webkit.org/attachment.cgi?id=61903)
Test case

According to the DOM Range spec, setting a Range boundary to a position within a document other than the one in which the Range currently exists should collapse the Range to the new boundary (in the new document). This works correctly in Firefox. In WebKit, we get a WRONG_DOCUMENT_ERR.

This may also affect other Range methods that move the range's boundaries, such as selectNode and selectNodeContents.

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