>>> If you call setParent(null) the DOM-node is correctly removed. Circular >>> references between widget and DOM are reset in the destructor of Widget.
>>This is not the case in my opinion. The node is only removed after the >>layout queues etc. have been flushed which never happens for widgets >>which are disposed already. Is there any way to know for sure, if a DOM-Node is removed ? I set breakpoints on every 'removeChild'-calls within the _handleDisplayable-method of the Widget-class - Firebug stops at this breakpoints in my simple App. Furthermore watching the DOM in Firebug I can see as well, that the nodes are gone ? That's why I think it is working, but maybe my assumptions are wrong ? PS: tools like 'Drip' or 'Sieve' I used as well - but I trust them no more. GWT-apps which don't leak at all when run without both tools start leaking heavily when started whithin the tool. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
