SplitContainer, destroyRecursive after moving sizer, errors or leaves sizers displayed

[guest]

destroyRecursive() for a SplitContainer? w/o first moving a sizer, in both FF2 and IE7, appears to work cleanly.

destroyRecursive() for a SplitContainer? after moving a sizer, in IE7, in the script debugging window of Web Development Helper, displays error messages, seemingly related to marginBox and currentStyle, but possibly related to a SplitContainer? node that has been removed.

destroyRecursive() for a SplitContainer? after moving a sizer, in FF2, leaves the moved sizer(s) displayed, and, depending on the contents of the SplitContainer?, when closing the window, may log this message in Firebug if another FF2 window/tab is open:

second argument to Function.prototype.apply must be an array

This is the test file used:

​nightly SplitContainer test file

and this JS statement:

dijit.byId('holderNode').destroyRecursive();

after moving, or not, the sizer in the bottom SplitContainer? (Programmatic Example:).

[Adam Peller]

likely a wontfix

[Frank Fortson]

Original poster: This must have been corrected in another fix. No longer seems to be a problem. Closing.