> Phaedra, how are you identifying the number of leaked nodes? I'm using sieve 0.08. I take note of the used nodes in the home page, then, i open a dialog (jquery), again take note of the nodes. After closing it they are always there, removed in the dom but always there in memory. These nodes are free fom events.
Same in the two examples, a blank page with a button with a onclick event. I can accept that the clock example was not well formed, but this was intentionally, apart of caching the selector. Changing the html inside the div call the "empty" function of jquery, that does nothing about memory leaks. So, i agree that .text() was better, but my example was about memory leaks, not performance. When ie7 number of used nodes grow, it slow down, making the spa too slow.
