Dialog: hide() followed quickly by destroy() throws error

[guest]

Calling dijit.Dialog.hide(), and then immediately calling dijit.Dialog.destroy() or dijit.Dialog.destroyRecursive() on a Dialog will throw an error "this.domNode has no properties". Interestingly, it cannot be caught by wrapping the call in a try/catch.

This is rather annoying since .hide() only hides the dialog, which makes it hard to do "throwaway" dialogs -- something that you create, use once, and destroy.

[guest]

Page that demonstrates the defect.

[bill]

Tried the test, works for me with no errors. I tried on FF2/mac. What browser were you using? See http://dojotoolkit.org/~bill/svn/test_Dialog_bug.html

[guest]

FF 2.0.0.9, WinXP. Also occurs on MSIE7.0, but, strangely, not every time.

[guest]

I tried it through the link you supplied, and... no error. The same file on my local system does produce it. Bizarre, I'll look into it further.

[guest]

I was watching this bug (I entered a similar one, #5141). It works for me with no errors on FF 2.0.0.8/Mac, but if I add "widg.hide();" before "widg.destroyRecursive();" it produces an error.

[tk]

This is a race condition, when calling dlg.hide() you have to allow time for the underLay widget to be destroyed.... I found that adding a 500ms timeout between hide and destroy() works....

[bill]

ah thanks for finding that... updating bug title/description

[bill]

add hide() to test case; otherwise problem doesn't reproduce

[bill]

(In [11525]) Fixes #5118: stop animation before destroying widget, or else will get references to deleted this.domNode