Opened 9 years ago

Closed 9 years ago

#11780 closed defect (invalid)

Detached splitters in a ContentPane when attached to a BorderContainer

Reported by: spidey2099 Owned by:
Priority: high Milestone: tbd
Component: Dijit Version: 1.5
Keywords: Cc:
Blocked By: Blocking:


Context: My application extends the content pane. I do this so that I can add behaviors that my app needs without impacting the basic functionality of the content pane.I have used the recommended dojo pattern for doing this and - until dojo 1.4.2- the class was instantiated and was working as expected: It attached to the border container, splitters could be added and removed, and so on.

Starting with 1.5 and using this same class (without a line of code being changed) the results are quite different: When this class is attached (with splitters enabled) to a border container, it results in the splitter being detached from the pane. Basically the splitter moves but the pane does not. Obviously something has gone wrong in construction. I have checked the rendered objects by using inspect element in Firebug. Sure enough - splitters are not attached to the pane.

I notice that the BorderContainer? has gone through some significant changes in 1.5. I am wondering - what has changed to cause this behavior?

I have not attached the test which demonstrates this functionality but I will do that in the next day or so. It is repeatable and consistent. Stay tuned.

Change History (3)

comment:1 Changed 9 years ago by spidey2099

Here is what I found. I was over-riding the ContentPane?'s resize method to do some inner work on the page layout. In 1.4.2, calling this.inherited(arguments) from my resize method would not resize the page layout correctly. So I removed it.

However, in 1.5 not calling this.inherited(arguments) has the effect of a content pane being detached from it's splitter. And this seems to be the only effect resulting from not calling this.inherited(arguments) from my resize method. There may be others, but I haven't found them yet.

BTW - I had to create my own ContentContainer? which extends dojo's ContentPane? because - at the time - it was against dojo's policy to attach other layouts (tabs, accordions, etc to a content pane). Now that the policy is relaxed my code has had to change accordingly.

Otherwise - its looking good.

comment:2 Changed 9 years ago by bill

Component: GeneralDijit
Owner: anonymous deleted
Priority: highestnormal
severity: blockernormal

I don't know what you mean by "attach other layouts (tabs, accordions, etc to a content pane)" or "resize the page layout". In any case, looking forward to seeing your test case if you are still having an issue.

comment:3 Changed 9 years ago by bill

Resolution: invalid
Status: newclosed

OK, looks like this is working for you now by calling this.inherited().

Note: See TracTickets for help on using tickets.