W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2012

[Bug 15544] New: Wrong node used for range adjustment in the remove mutation

From: <bugzilla@jessica.w3.org>
Date: Fri, 13 Jan 2012 15:54:52 +0000
To: www-dom@w3.org
Message-ID: <bug-15544-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15544

           Summary: Wrong node used for range adjustment in the remove
                    mutation
           Product: WebAppsWG
           Version: unspecified
          Platform: All
               URL: http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.ht
                    ml#concept-node-remove
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM
        AssignedTo: annevk@opera.com
        ReportedBy: stighal@opera.com
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, www-dom@w3.org


In step 2 and 3 in the description of the remove mutation in DOMCore [1], the
spec states that:

 "For each range whose start/end node is a descendant of _parent_, set its
start/end to (parent, index)."

That doesn't seem to be what browsers do.

What browsers do seems to be more like:

 "For each range whose start/end node is a descendant of _child_, set its
start/end to (parent, index)."

Which makes more sense, since child is being removed here and boundary points
under child will be gone after the mutation, and so setting them to an offset
of the parent seems appropriate.

[1]
http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-node-remove

-- 
Configure bugmail: https://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 Friday, 13 January 2012 15:59:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:09 GMT