Hi, On Thu, Oct 30, 2008 at 5:02 PM, T.J. Crowder <[EMAIL PROTECTED]> wrote: > FWIW, I don't think this is a bug in Prototype. Prototype keeps track > of the event handlers it hooks up so it can unhook them on page unload > to work around memory leaks in IE. (This also lets it provide the new > stopObserving functionality in release 1.6 where you don't have to > specify the handler to unhook things.) This means that it has to use > a small bit of memory to track the handlers. That's not a *leak*, I > wouldn't say, but a *use* of memory.
As noted from the thread I quoted above, prototype 1.6 does not "unhook them on page unload" anymore, it just do cache[id][eventName] = null. prototype 1.5 does "unblock them on page unload" using stopObserving while iterating over each of the handlers. Cheers, Phuah Yee Keat --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
