Opened 14 years ago

Closed 12 years ago

#563 closed enhancement (wontfix)

LayoutPane cannot size itself based on it's content

Reported by: anonymous Owned by: koranteng
Priority: high Milestone: 1.0
Component: Dijit Version: 0.2
Keywords: Cc:
Blocked By: Blocking:

Description

In the http://archive.dojotoolkit.org/nightly/tests/widget/test_Layout.html example, changing the text sizes does not cause the layout pane to resize itself. In fact, when loading content in dynamically, if the new content is much larger than the previous content, the results will be clipped. This behaviour can be seen in both FF and IE by: choosing the smallest text size refresh the browser to ask the LayoutPane? to resize itself choose the largest text size

You can notice that splitpane bar position never moves. This isn't so much of a problem in the test harness, but this behaviour is wrong for applications with liquid layouts.

Change History (5)

comment:1 Changed 14 years ago by bill

Summary: ContentPane does not resize itself in layout when content changes (or when text size changes)LayoutPane cannot size itself based on it's content
Type: defectenhancement

You can specify style="overflow: auto" on the content pane so you get a scrollbar.

But, you have to specify an explicit size for LayoutPane? (and SplitPane? and TabPane?, etc.). It's a design limitation.

Changing this to an enhancement request. Not sure if it's possible though (since the LayoutPane? doesn't have anyway of knowing when the font size has changed).

comment:2 Changed 13 years ago by dylan

Component: GeneralWidgets
Milestone: 0.9
Owner: changed from anonymous to bill

setting a far in teh future milestone in case inspiration strikes.

comment:3 Changed 13 years ago by dylan

Milestone: 0.90.6

comment:4 Changed 12 years ago by Adam Peller

Component: WidgetsDijit
Owner: changed from bill to koranteng

comment:5 Changed 12 years ago by bill

Resolution: wontfix
Status: newclosed

Layout widgets aren't supposed to do this. If you want dynamic sizing use a plain <div>. Sorry, closing this.

Note: See TracTickets for help on using tickets.