Opened 10 years ago

Last modified 10 years ago

#12246 closed defect

TabContainer not working when set as href or content — at Version 1

Reported by: Pete Smith Owned by:
Priority: high Milestone: tbd
Component: Dijit Version: 1.6.0b1
Keywords: Cc:
Blocked By: Blocking:

Description (last modified by bill)

I have a parent ContentPane where I set the href on it. The contents of that request have dijit.layout.TabContainer in them, and in 1.5.0 they widgetize and work just fine.

In 1.6.0b2, this does not work. There are no tabs in the tablist, even though each subcontainer has a title="foo" on it. I whipped up this test just by setting the content of the pane, and it fails as well. Although the regression I think I have uncovered is, setting the href or content of panes has some problem when it comes to widgetizing and parsing.

Change History (2)

Changed 10 years ago by Pete Smith

A simple test case showing the setting of content on a pane does not create working tabs .

comment:1 Changed 10 years ago by bill

Component: GeneralDijit
Description: modified (diff)
Owner: anonymous deleted

Thanks for the test case, but I don't understand what it's trying to do. You have:

<div dojotype="dijit.layout.TabController">
  <div dojotype="dijit.layout.ContentPane" title="edit">blah</div>
</div>

Strange things are:

  • Why are you creating a TabController directly?
  • Why does your TabController contain ContentPanes rather than TabButtons?

Also, the test has some other apparently spurious things:

  • The makeTab() method isn't ever executed, nor is testClose(). Actually, everything in the <script> tag besides a few dojo.require()'s seem unnecessary for the test.
  • Custom styling in script tag also seems unnecessary, does the problem still happen without that?
Note: See TracTickets for help on using tickets.