Pages which create a Canvas instance (new Canvas()) can be seen to have an increase in memory (at least in FF/Mac) which is proportional to the size of the created Canvas.

I first observed this when working with the Spacetree. The behavior can be seen on the example page but is small (~2MB) because of the size of the Canvas. Altering the example to use a 1000px X 1000px canvas will show a more dramatic (~25-50 MB) increase.

Seeking to isolate the cause and symptoms, I created these 3 pages:
http://jfsiii.org/testpages/tagcanvas.html - 4000px X 4000px Canvas using only the canvas tag http://jfsiii.org/testpages/classcanvas.html - 4000px X 4000px Canvas using new Canvas() * http://jfsiii.org/testpages/classcanvasgc.html - 4000px X 4000px Canvas using new Canvas() and deleting the variable when the page unloads

The treemap changes the order of the children elements in the tree.
This is really a minor issue but should be considered to be fixed because it is not replicable from outside what the treemap object does.
One of my implementations relied on the order of those children elements, so this behavior was really a mess. I had the clone the whole tree over and over again. And I don't think this is necessary.

Hi there!

On the documentation page http://thejit.org/tutorials/hypertree/ I found some dead links like http://localhost:8888/docs/files/Canvas-js.html
But besides that you have a great documentation, thanks :)

Phil

adding and removing trees works fine for the SpaceTree, but the generic op methods won't work because you need to ignore nodes having ignore=true as value when traversing the tree.