Opened 13 years ago
Closed 13 years ago
#5684 closed defect (duplicate)
[dijit] _Widget .destroy() enhancement
Reported by: | dante | Owned by: | dante |
---|---|---|---|
Priority: | high | Milestone: | 1.2 |
Component: | Dijit | Version: | 1.0 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description (last modified by )
It would be nice if you could somehow optionally _not_ delete the srcNodeRef/domNode used by dijit._Widget when calling destroy()
my use case is behavioral widgets you can enable/disable and cleanup effectively, without destroying the content.
eg: var n = new dojox.widget.FishseyeLite?({},"foo"); setTimeout(dojo.hitch(n,"destroy"),10000);
it should fisheye for 10 seconds, and leave the node id="foo" alone (other than having it's this.connect()'s removed, etc)
Change History (3)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
Description: | modified (diff) |
---|---|
Owner: | set to dante |
Status: | new → assigned |
comment:3 Changed 13 years ago by
Resolution: | → duplicate |
---|---|
Status: | assigned → closed |
see #6668 - it's more precise.
Note: See
TracTickets for help on using
tickets.
Agreed. destroyRendering() should probably only remove generated DOM nodes, not the original srcNodeRef. Perhaps just checking if
this.domNode == this.srcNodeRef
(and remove this.domNode only if the condition is false) is enough...