Opened 11 years ago

Closed 11 years ago

#7444 closed defect (fixed)

BorderContainer: splitters never have their startup() called

Reported by: Sam Foster Owned by: Sam Foster
Priority: high Milestone: 1.2
Component: Dijit Version: 1.1.1
Keywords: Cc: Adam Peller
Blocked By: Blocking:

Description

As the splitter widgets arent registered as children, they do not get their startup method called when the BC's own startup runs.

It's a simple patch, I'll attach...

Attachments (1)

splitter_startup.patch (755 bytes) - added by Sam Foster 11 years ago.
[PATCH] [CLA] fixes BC.startup to call startup on its splitters

Download all attachments as: .zip

Change History (4)

Changed 11 years ago by Sam Foster

Attachment: splitter_startup.patch added

[PATCH] [CLA] fixes BC.startup to call startup on its splitters

comment:1 Changed 11 years ago by bill

Component: GeneralDijit
Owner: changed from anonymous to Adam Peller
Summary: BorderContainer splitters never have their startup() calledBorderContainer: splitters never have their startup() called

comment:2 Changed 11 years ago by bill

Milestone: tbd1.2
Owner: changed from Adam Peller to Sam Foster

Oh, sfoster fixed this in [14857], it just didn't register here.

comment:3 Changed 11 years ago by bill

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.