That doesn't happen unless you're trying to insert the same node into
the document a bunch of times
No, that's not the case - this behaviour is expected (a node can only appear in one place in the DOM).
If you think it's something else, then post a reproducible example.
I am having trouble isolating this, but it now looks like it's a gecko-specific bug which happens when you try to insert new nodes from the window's onload event. In any case, this is not a MochiKit bug, the behaviour is identical when I use plain-vanilla DOM calls. Other browsers behave as expected.
tom
--
http://intellectronica.net/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "MochiKit" group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~----------~----~----~----~------~----~------~--~---
