Opened 12 years ago

Closed 12 years ago

#5355 closed defect (worksforme)

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

Reported by: guest Owned by: Adam Peller
Priority: high Milestone:
Component: Dijit Version: 1.0
Keywords: bordercontainer splitcontainer move sizer destroy Cc: frank.fortson@…
Blocked By: Blocking:

Description

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:).

Change History (5)

comment:1 Changed 12 years ago by Adam Peller

Milestone: 1.0.21.1

comment:2 Changed 12 years ago by bill

Owner: set to Adam Peller

comment:3 Changed 12 years ago by Adam Peller

Keywords: bordercontainer added

comment:4 Changed 12 years ago by Adam Peller

Milestone: 1.1

likely a wontfix

comment:5 Changed 12 years ago by Frank Fortson

Resolution: worksforme
Status: newclosed

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

Note: See TracTickets for help on using tickets.