It's not that it takes it out of memory but rather that it removes any references from it to JS land (things like DOM event listeners) which allows browsers to garbage collect it. If it didn't do this, some browsers (IE, Firefox) would leak memory (if you refreshed the page the memory footprint of the program would grow and grow indefinitely).
Aaron Sorry for any typos. Tiny buttons, big thumbs... On Mar 10, 2011, at 12:02 PM, SamGoody <[email protected]> wrote: > As you can see in the demo, it doesn't work. > Thought perhaps Mootools had another concept for the same word. > > Ticket opened. > > On Mar 8, 11:08 pm, DJGosnell <[email protected]> wrote: >> When an element is removed disposed (Element.dispose) it is removed from the >> DOM, but remains an active element that can be used and injected into the >> DOM again. The destroy method takes it completely out of the memory and you >> can not inject it or reference it any more. >> >> For >> referencehttp://mootorial.com/wiki/mootorial/04-element/00-elementhttp://en.wikipedia.org/wiki/Garbage_collection_%28computer_science%29
