Specs: remove previousSibling/nextSibling arguments to parentChangeCallback() since their purpose is not documented

Review URL: https://codereview.chromium.org/943453004
This commit is contained in:
Hixie 2015-02-19 14:32:31 -08:00
parent a93b70ab08
commit 1ca5d64228

View File

@ -84,7 +84,7 @@ abstract class Node extends EventTarget {
// this is why insertBefore(), append(), et al, are O(N) -- the whole affected subtree is walked
// mutating the element tree from within this is strongly discouraged, since it will result in the
// callbacks being invoked while the element tree is in a different state than implied by the callbacks
external void parentChangeCallback(ParentNode oldParent, ParentNode newParent, Node previousSibling, Node nextSibling); // O(N) in descendants
external void parentChangeCallback(ParentNode oldParent, ParentNode newParent); // O(N) in descendants
// default implementation calls attached/detached
void attachedCallback() { }
void detachedCallback() { }