Closed
Bug 12160
Opened 25 years ago
Closed 25 years ago
Tree does not size intrinsically
Categories
(Core :: XUL, defect, P3)
Core
XUL
Tracking
()
VERIFIED
FIXED
People
(Reporter: slamm, Assigned: hyatt)
References
()
Details
Attachments
(1 file)
1.49 KB,
text/xul
|
Details |
I have a tree in a dialog. I would like to have the tree grow as I resize the window larger (for sidebar customize dialog). I will attach an example.
Reporter | ||
Comment 1•25 years ago
|
||
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Assignee | ||
Comment 2•25 years ago
|
||
Marking invalid. This XUL is buggy. Here's what you've said in your XUL: Inside <window> (a horizontal box), you have placed a flexible object, a box. This object will be stretched horizontally to fill the available area. Inside this box (which you specified as vertical), you placed an INFLEXIBLE object, a horizontal box. Because this object is inflexible, it will only be as tall as it needs to be. It won't consume all the height of your vertical box. The tree is then placed inside this inflexible object, and it isn't even marked as flexible, which means it won't take all of the horizontal space of its parent box. So you end up with a tree that won't stretch in either direction. Marking invalid. Come by my cube if you want a crash course in boxes.
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → REOPENED
Reporter | ||
Comment 3•25 years ago
|
||
chrome://sidebar/customize.xul is in xpfe/components/sidebar/resources
Reporter | ||
Comment 4•25 years ago
|
||
My testcase sucked. Checkout the customize dialog instead.
Assignee | ||
Updated•25 years ago
|
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•25 years ago
|
||
Should be fixed.
Comment 7•25 years ago
|
||
Sorry for spam, re-assigning phillip's QA contact XPToolkit/XPWidget bugs to claudius due to restructure
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 8•25 years ago
|
||
v
You need to log in
before you can comment on or make changes to this bug.
Description
•