#7123 closed defect (fixed)
BorderContainer: Tab container in nested BorderContainer default sizing issue
| Reported by: | nonken | Owned by: | bill |
|---|---|---|---|
| Priority: | high | Milestone: | 1.2 |
| Component: | Dijit - LnF | Version: | 1.1.1 |
| Keywords: | TabContainer, nested, resizing | Cc: | bill, nonken |
| Blocked By: | Blocking: |
Description
When having tabs within BC within BC their initial sizing seems to be taking some padding or so into account. After resize of browser window it adjusts correctly
Attachments (1)
Change History (4)
Changed 13 years ago by
| Attachment: | sizingtabs.png added |
|---|
comment:1 Changed 13 years ago by
| Milestone: | tbd → 1.2 |
|---|---|
| Owner: | set to bill |
| Status: | new → assigned |
| Summary: | Tab container in nested BorderContainer default sizing issue → BorderContainer: Tab container in nested BorderContainer default sizing issue |
comment:2 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
(In [14348]) Fix sizing problem when BorderContainer?.resize(size) was called (w/a size argument) on content-box sizing browsers (i.e., everything but IE). Need to do padding hack before _LayoutWidget.resize(size) is called, because it affects the value we pass to dojo.marginBox() to set the size of the widget. Fixes #7123 !strict.
comment:3 Changed 13 years ago by
oops, checkin comment was inaccurate... should have said that we need to modify the widget's padding before we set the margin-box size (in _LayoutWidget.resize())... otherwise when changing the padding inadvertently changes the margin-box size.
Note: See
TracTickets for help on using
tickets.
Actually the problem is with a BorderContainer inside a TabContainer.