On Mar 12, 11:54 am, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote: > On Monday 12 March 2007 18:14, Beau Hartshorne wrote: > > > The Signal, native, and YUI APIs should be independent, though I've > > never made time to testing this. Problems might bubble around > > "onunload" because of MK and YUI's efforts to plug IE memory leaks. > > That made me think.. .I do use both toolkits, and so far I was pretty > convinced I was spared the signal-related mem-leaks because of MK taking care > of releasing signals in onunload. Yet still I have mem-leaks under IE which > could be related to that.
What are you using to detect those memory leaks? I'd love to have a simple but effective Javascript debugger/handler under IE but I use Windows rarely: typically over a remote desktop connection, and usually to see how things are behaving in IE. I am using YUI with MochiKit, but I'm only using YUI in a couple of places right now. I haven't noticed any odd behavior, but I haven't looked too close. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~----------~----~----~----~------~----~------~--~---
