Opened 7 years ago

Closed 6 years ago

#14770 closed defect (invalid)

TabContainer - nesting bug - width property

Reported by: Matej Owned by: Matej
Priority: low Milestone: future
Component: Dijit Version: 1.7.1
Keywords: Cc:
Blocked By: Blocking:

Description

When I use TabContainer? with nested TabContainer?, the nested TabContainer? has width 50431px. If I wrap the nested TabContainer? into the fieldset with fixed width, the fieldset width is overridden. But if I select the Tab 2 second time, the nested TabContainer? width is correct.

Summary: The nested TabContainer? width is for first time incorrect.

Attachments (2)

fieldset.html (1.5 KB) - added by Matej 7 years ago.
Bug example, see Tab 2
bug.jpg (38.0 KB) - added by Matej 7 years ago.
first select incorrect, second select correct

Download all attachments as: .zip

Change History (9)

Changed 7 years ago by Matej

Attachment: fieldset.html added

Bug example, see Tab 2

comment:1 Changed 7 years ago by bill

Sounds like #13411 although maybe not exactly the same.

comment:2 Changed 7 years ago by Matej

The bug appears in Google Chrome.

Changed 7 years ago by Matej

Attachment: bug.jpg added

first select incorrect, second select correct

comment:3 Changed 7 years ago by Matej

Whats new with this bug?

comment:4 Changed 6 years ago by bill

Owner: set to Matej
Status: newpending

Well, the test case isn't valid because the outer TabContainer doesn't have a height/width specified, nor is it doLayout=false. You need one or the other. So please update the test case.

comment:5 Changed 6 years ago by bill

Priority: undecidedlow

comment:6 Changed 6 years ago by bill

Milestone: tbdfuture

comment:7 Changed 6 years ago by trac-o-bot

Resolution: invalid
Status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Note: See TracTickets for help on using tickets.