24653 2014-02-13 12:30:58 +0000 Planning on changing mutation hooks 2014-09-12 18:23:21 +0000 1 1 1 Unclassified WHATWG HTML unspecified PC All RESOLVED FIXED P2 normal Unsorted 23268 1 annevk ian ian mike www-dom contributor oldest_to_newest 100517 0 annevk 2014-02-13 12:30:58 +0000 HTML loosely uses "nodes are inserted" and "nodes are removed" for two elements or so and does not even bother with attribute callbacks. I'm planning on slightly revamping them in order to fix a bug in NodeIterator. Is there a way I can write them that will make you use these callbacks throughout HTML? For the removed callback I plan to provide /removedNode/, /oldParent/, /oldPreviousSibling/ as arguments. For the inserted callback only /insertedNode/ seems needed. Similar for attribute changes on an element. However, I suspect that over time there may be more churn coming to these callbacks due to custom elements and how we envision everything to evolve. So this bug is both a question whether you mind if I change the current callbacks to suit my needs and what your thoughts on the matter are. 100633 1 ian 2014-02-14 21:52:25 +0000 I don't have any particular thoughts. If there's cases where the HTML spec is too loose about something Web-detectable, I'm happy to tighten it up. I'm in no rush to do it if it's going to churn. 101277 2 ian 2014-02-24 22:12:46 +0000 Do you need anything else from me here? 110184 3 annevk 2014-08-14 14:56:36 +0000 The hooks are now named "insertion steps" and "removing steps" to be consistent with "cloning steps" and "adopting steps". Sorry for the churn, will try to keep these as is. They are also passed arguments now that can be used. 111454 4 contributor 2014-09-12 18:23:21 +0000 Checked in as WHATWG revision r8769. Check-in comment: Integrate with DOM for 'removing steps' and 'insertion steps'. http://html5.org/tools/web-apps-tracker?from=8768&to=8769