> The change was pulled off (perhaps it was considered too obtrusive or > there was no time to test it thoroughly).
I was talking about the (apparent) change between 1.5 and 1.6. > I think we should at least > provide some kind of `purgeObservers` method Yeah, something that accepts an element and clears observers from it and all of its descendants, like the OP's select("*") or ideally something more efficient using the cache internal to prototype. Then in situations where you know some things are hooked, you can do: $('container').purgeObservers().update(newcontent); -- T.J. Crowder tj / crowder software / com On Oct 30, 4:53 pm, kangax <[EMAIL PROTECTED]> wrote: > On Oct 30, 11:07 am, "T.J. Crowder" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > 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. > > > I'll be interested in hearing what someone from Core has to say about > > that change; I thought maybe they'd realized that that was all that > > The change was pulled off (perhaps it was considered too obtrusive or > there was no time to test it thoroughly). I think we should at least > provide some kind of `purgeObservers` method and educate people about > what happens when you update document and leave observers hanging in > memory. > > [snip] > > -- > kangax --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to email@example.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 -~----------~----~----~----~------~----~------~--~---