Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#6777 closed defect (fixed)

BorderContainer programmatic wrong splitters

Reported by: [email protected] Owned by: Adam Peller
Priority: high Milestone: 1.2
Component: Dijit Version: 1.1.0
Keywords: Cc:
Blocked By: Blocking:


I think that there is a bug in the way BorderContainer? manage splitters. The problem happens when you create BorderContainer? programmatically and you call the startup method AFTER the creation of the children. In this case if one pane has a splitter you get 2 splitters and in the wrong place.

I attach a test that shows the problem. It must be placed in the same folder of other BordrContainer? test.

In the test you can see the wrong behaviour when the 'doPatch' variable is false.

Then I found a patch that seems able to fix the problem and you should be able to see that it works setting doPatch to true.

Please let me know if the bug is confirmed and if my patch is ok. I really have to use BorderContainer? and this bug is a show stopper for me.

Thank you

Giovanni Porcari

[email protected]

Attachments (1)

test_BorderContainer_progr.html (3.3 KB) - added by guest 14 years ago.

Download all attachments as: .zip

Change History (5)

Changed 14 years ago by guest

comment:1 Changed 14 years ago by bill

Owner: set to Adam Peller
Reporter: changed from guest to [email protected]

Thanks for the test file, they are always appreciated.

comment:2 Changed 14 years ago by Adam Peller

Milestone: 1.2

comment:3 Changed 14 years ago by Adam Peller

Resolution: fixed
Status: newclosed

(In [13760]) Fix programmatic test case with splitters. Thanks, genro. Fixes #6777 !strict

comment:4 Changed 14 years ago by Adam Peller

(In [13767]) Redo patch for proper instantiation of splitters. !strict Fixes #6777, #6782

Note: See TracTickets for help on using tickets.