This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16373 - replacing a child creates extra mutationrecord
Summary: replacing a child creates extra mutationrecord
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-14 16:39 UTC by Olli Pettay
Modified: 2012-03-20 17:32 UTC (History)
3 users (show)

See Also:

Attachments

Description Olli Pettay 2012-03-14 16:39:41 UTC 
Replacing a child should create just one record, which has
the old child in the removedNodes, and new node in the addedNodes.
Currently the spec creates separate records.
Comment 1 Olli Pettay 2012-03-20 12:35:41 UTC 
This can't be done in general
Comment 2 Olli Pettay 2012-03-20 12:37:14 UTC 
Or maybe I'm wrong :)
Comment 3 Anne 2012-03-20 14:30:29 UTC 
I think I fixed this. Review welcome.
Comment 5 Adam Klein 2012-03-20 16:30:46 UTC 
Looks good to me, thanks! Just one nit: step 12 of "replace" says "Insert ... with the suppress observers flag." instead of "...with the suppress observers flag set." Seems like that should be consistent throughout this section.