Also Christoph explained it here a bit: https://mootools.lighthouseapp.com/projects/2706/tickets/1193#ticket-1193-4 <https://mootools.lighthouseapp.com/projects/2706/tickets/1193#ticket-1193-4>And 1.3 is apparently a bit different than 1.2 which is now fixed in the docs as well: https://github.com/cpojer/mootools-core/commit/832c0a244
On Thu, Mar 10, 2011 at 6:40 PM, Aaron Newton <[email protected]> wrote: > 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 >
