15544 2012-01-13 15:54:51 +0000 Wrong node used for range adjustment in the remove mutation 2012-01-17 16:34:43 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified All All RESOLVED FIXED http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-node-remove P2 normal --- 1 stighal ayg ayg mike www-dom public-webapps-bugzilla oldest_to_newest 62663 0 stighal 2012-01-13 15:54:51 +0000 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 62812 1 ayg 2012-01-17 16:34:43 +0000 Thanks! I've fixed it: http://dvcs.w3.org/hg/domcore/rev/8fd99dd0579b