Opened 4 years ago

Closed 4 years ago

#18668 closed defect (invalid)

dijit/layout/tabcontainer lost first contentpane's content

Reported by: cidylong Owned by: bill
Priority: undecided Milestone: tbd
Component: Dijit Version: 1.10.4
Keywords: Cc:
Blocked By: Blocking:

Description

dojo 1.10.4, sitemesh 2.4.2

I am trying to use dojo 1.10.4 in my project to work with sitemesh 2.4.2, spring framework 4.1. When I try to put a tabcontainer in my content section (header, content and footer style defined by sitemesh).

I never get my tabcontainer's first contentpane's content shows up, it is alway dis-appear.

test code as:

<div style="width: 350px; height: 300px">

<div data-dojo-type="dijit/layout/TabContainer" style="width: 100%; height: 100%;">

<div data-dojo-type="dijit/layout/ContentPane" title="My first tab" data-dojo-props="selected:true">

Lorem ipsum and all around...

</div> <div data-dojo-type="dijit/layout/ContentPane" title="My second tab">

Lorem ipsum and all around - second...

</div> <div data-dojo-type="dijit/layout/ContentPane" title="My last tab" data-dojo-props="closable:true">

Lorem ipsum and all around - last...

</div>

</div>

</div>

javascript as:

<script type="text/javascript"> require(["dojo/parser", "dojo/aspect", "dijit/layout/TabContainer", "dijit/layout/ContentPane","dojo/domReady!"], function(parser, aspect) {

parser.parse();

}); </script> The result as:

other tabbed contentpane display properly.

As I can't upload image here, I had uploaded image to stack overflow website. please refer:

http://stackoverflow.com/questions/32064838/dojo-1-10-4-dijit-layout-tabcontainer-not-rendering-first-contentpanes-content

Attachments (1)

dojo-contentpane-missed.jpg (23.5 KB) - added by cidylong 4 years ago.
first contentpane's content not rendering in tabcontainer.

Download all attachments as: .zip

Change History (2)

Changed 4 years ago by cidylong

Attachment: dojo-contentpane-missed.jpg added

first contentpane's content not rendering in tabcontainer.

comment:1 Changed 4 years ago by bill

Resolution: invalid
Status: newclosed

Solved on stack overflow. Apparently page was being parsed twice, due to user error.

Note: See TracTickets for help on using tickets.