Closed
Bug 11102
Opened 26 years ago
Closed 26 years ago
[Tree] treewidget won't layout tables nested >1 level deep
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
FIXED
M13
People
(Reporter: waterson, Assigned: hyatt)
References
(
URL
)
Details
Attachments
(1 file)
|
5.08 KB,
text/xul
|
Details |
Open the attached test case using viewer. (A simple tree specified using XUL
tags.)
Expected to see:
Bookmarks
XUL Child #1 (Beetle)
XUL Child #1.1
XUL Child #1.2
XUL Child #2
Actually see:
Bookmarks
XUL Child #1 (Beetle)
XUL Child #2
Double clicking "XUL Child #1 (Beetle)" will open the node and present two
blank lines.
I've verified that the content is in fact being built (by setting
NSPR_LOG_MODULES=nsRDFXULBuilder:5 and watching the output), so this looks like
a bug on your end.
| Reporter | ||
Comment 1•26 years ago
|
||
| Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M9
| Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 2•26 years ago
|
||
I'm assuming you got bitten by Paul Hangas' checkin to xul.css (he forgot to
close a rule, and this blew away the tree widget rules). Marking fixed.
| Reporter | ||
Updated•26 years ago
|
URL: resource:/res/rdf/dom-test-8.xul
Status: RESOLVED → REOPENED
| Reporter | ||
Comment 3•26 years ago
|
||
Hyatt, I've updated xul.css, and I still see this as busted. I've checked it in
as resource:/res/rdf/dom-test-8.xul -- could you re-pull that file and tell me
if I'm just on crack?
| Assignee | ||
Updated•26 years ago
|
Target Milestone: M9 → M10
| Assignee | ||
Comment 5•26 years ago
|
||
Moving to M10.
Updated•26 years ago
|
Target Milestone: M10 → M11
Comment 6•26 years ago
|
||
mass targetting m11
| Assignee | ||
Comment 7•26 years ago
|
||
My hands have deteriorated to the point where I can no longer type. I need
help. If you think you can fix this bug on your own, please take it away from
me. If you'd like to volunteer to be my hands for a specific bug, then I'll be
happy to come up to your cube and sit with you and fix the bug (assuming you
have the patience for that).
Comment 8•26 years ago
|
||
trying to help out hyatt:
I'm updating dom-test-8.xul to enclose a tree in a div (bitrot, trees need to be
in divs now)
The behavior still occurs on linux.
| Assignee | ||
Updated•26 years ago
|
Assignee: hyatt → alecf
Status: REOPENED → NEW
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M11 → M12
Comment 9•26 years ago
|
||
I doubt I'd get to this in M11. Moving to M12
Updated•26 years ago
|
Summary: [tree] treewidget won't layout tables nested >1 level deep → [Tree] treewidget won't layout tables nested >1 level deep
Updated•26 years ago
|
Target Milestone: M12 → M13
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
Comment 10•26 years ago
|
||
This seems fixed now -- nested folders in the folder pane look fine now.
| Reporter | ||
Updated•26 years ago
|
Status: RESOLVED → REOPENED
| Reporter | ||
Comment 11•26 years ago
|
||
alecf: you need to test resource:/res/rdf/dom-test-8.xul (see URL and bug
description). This has to do with hard-coded XUL, not RDF-generated XUL. N.B.
that I've just updated the test case (it had bit-rotted). The test case is
checked into the tree.
Comment 12•26 years ago
|
||
Clearing FIXED resolution due to reopen.
Updated•26 years ago
|
Assignee: alecf → hyatt
Status: REOPENED → NEW
Comment 13•26 years ago
|
||
reassigning tree bugs back to hyatt. this bug may even already be fixed. It
would be great if the QA contact here could verify this bug is still broken.
| Assignee | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 14•26 years ago
|
||
This was fixed some time ago. Take a look at prefs for a demonstration.
Note that the attached test case is no longer valid. Just verify by looking at
prefs.
Comment 15•26 years ago
|
||
Marking verified fixed in the Feb 01 build (20000020108).
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•