[Bug 14035] New: Range + splitText handling is inconsistent

http://www.w3.org/Bugs/Public/show_bug.cgi?id=14035

           Summary: Range + splitText handling is inconsistent
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM Core
        AssignedTo: annevk@opera.com
        ReportedBy: Olli.Pettay@gmail.com
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, www-dom@w3.org


The behavior depends on whether the textnode has parent or not.
If there is parent, boundary point's node can be changed, 
but if not, range is possibly just collapsed to the end of the
original text node.

I would expect that if the range is fully after the split point, the
range's node would be updated.

Also, it should be specified clearly what should happen in the case when
textnode doesn't have parent and splittext happens between the range's
boundary points. In this case the end point should probably point to the
end of the original (modified) node.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Monday, 5 September 2011 18:08:37 UTC