[quote="EvgenyT"]I reread your first post.
The fact is that when you call node.remove(), it first removes all its child nodes (from DOM hierarchy).
So there's no performance difference in comparison when you just remove all child nodes one by one like in
http://www.9rays.net/forums/viewtopic.php?t=1102&highlight=refresh+node
Actually node.remove() does the same, but also removes itself.
Sorry for being such a pest ... yet, two things:
1.While removing a nodes's every child by iterating takes a tremendously long time (up to the point of IE complaining that the script is slowing down all processes), removing the node itself takes no time at all.
I have no knowledge about the internals of the method .remove(), yet I'd kindly like to ask you to investigate the issue and maybe take a few minutes to test it.
Again, the workaround I described above works like a charm, apart from the newly created node not having an image.
2.As you suggested I had a look at the clone() method. This method does - as the documentation implies - create a deep copy of a node. However, the image of the node itself goes missing (the images the of the cloned node's children are displayed properly).