Opened 14 years ago
Closed 14 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)
Change History (4)
Changed 14 years ago by
| Attachment: | splitter_startup.patch added |
|---|
comment:1 Changed 14 years ago by
| Component: | General → Dijit |
|---|---|
| Owner: | changed from anonymous to Adam Peller |
| Summary: | BorderContainer splitters never have their startup() called → BorderContainer: splitters never have their startup() called |
comment:2 Changed 14 years ago by
| Milestone: | tbd → 1.2 |
|---|---|
| Owner: | changed from Adam Peller to Sam Foster |
Oh, sfoster fixed this in [14857], it just didn't register here.
comment:3 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
[PATCH] [CLA] fixes BC.startup to call startup on its splitters