This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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
Thanks! I've fixed it: http://dvcs.w3.org/hg/domcore/rev/8fd99dd0579b