16638 2012-04-05 06:33:22 +0000 Define who owns what with MutationObserver 2012-11-09 18:59:57 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC Linux RESOLVED FIXED P2 normal --- 1 bugs annevk adamk jonas mike rafaelw rniwa www-dom public-webapps-bugzilla oldest_to_newest 66428 0 bugs 2012-04-05 06:33:22 +0000 Should MutationObserver own the nodes it is observing? I think not. If JS doesn't have a pointer to the node, it can't modify it. But if the original observe target is deleted, what should happen to the transient observers? I think they should still work (until the end of the microtask). That way GC/CC behavior isn't visible to the API user. Then MutationObserver object itself... I think the only way to hide GC/CC behavior is to keep MutationObserver object alive as long as the node(s) it is observing is/are alive. 66429 1 rniwa 2012-04-05 06:37:45 +0000 Yes, that makes sense. 66448 2 annevk 2012-04-05 16:46:08 +0000 So MutationObserver has weak references to its nodes? 66469 3 bugs 2012-04-06 08:07:54 +0000 Yes, and nodes have strong references to the MutationObservers which are observing them 78117 4 annevk 2012-11-09 15:10:49 +0000 Is http://dom.spec.whatwg.org/#garbage-collection correct? 78118 5 annevk 2012-11-09 15:11:14 +0000 https://github.com/whatwg/dom/tree/eb59b065b161846cd3c35899a926ba7a426e837e 78119 6 adamk 2012-11-09 15:13:19 +0000 Sounds right to me 78143 7 bugs 2012-11-09 18:59:57 +0000 Yup, looks ok.