[Webkit-unassigned] [Bug 28697] WebKit crash on WebCore::Node::nodeIndex()
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Nov 25 21:40:16 PST 2009
https://bugs.webkit.org/show_bug.cgi?id=28697
--- Comment #19 from Eric Seidel <eric at webkit.org> 2009-11-25 21:40:16 PST ---
The "easy" solution would be to get rid of removeChildren() all together.
Since the model of removing lots of children at once does not fit with the:
document->nodeWillBeRemoved(child);
model. nodeWillBeRemoved assumes that the node in question is the *only* node
about to be removed, and that all siblings and parents are going to stay
around.
We could have a separate callback in this case which is
nodesChildrenWillBeRemoved? That would fix the Range case. Really not sure.
Going to sleep on it. I'm still curious what Darin's opinion here is.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list