Statically defined tree doesn't draw opened children

RESOLVED FIXED in Future

Status

()

Core
XUL
P5
normal
RESOLVED FIXED
19 years ago
18 years ago

People

(Reporter: selmer (gone), Assigned: David Hyatt)

Tracking

Trunk
Future
x86
Other
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

19 years ago
I just checked in a new version of treeTest1.xul that conforms to current tree
syntax.  I have built it to include 2 levels of treechildren.

In the 12/14 build, go to this page and double click on either of the items that
are displayed.  Notice that nothing appears to happen.  Double click in the
windows title bar to expand the window to full screen (other operations may work
but this one is consistent.)  Notice that the children are now drawn.

This is probably related to the fact that the tree contents are populated
directly from the xul file.  This appears to now be the only test like that in
the source tree.
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 1

19 years ago
Prefs is a straight XUL tree.  Is it broken?
(Reporter)

Comment 2

19 years ago
Nope.  Prefs tree works fine.  Here are some differences between them:

prefs uses container=true attribute
prefs tree has twisties (because container=true?)
prefs tree uses name= and value= attributes of treecells
prefs tree used opne=true attribute on every single treeitem
pref tree is in an iframe that's contained within a box

test tree uses div to put text into treecells
(Assignee)

Updated

19 years ago
Target Milestone: M18
(Assignee)

Comment 3

19 years ago
Static trees are fixed.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED

Comment 4

19 years ago
the tree test referenced above fails with the 2000020308 Mac OS 8.5.1 comm opt build. REOPENING. It also does not work with 
with the 2000020108 build on WinNT.

The tree still fails to draw opened children unti lyou resize. Moreover, the content of each child is somewhat munged
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 5

19 years ago
This test has never been right.  It should be deleted with extreme prejudice.  
Please just look at the prefs tree, which is static.  It works.
Status: REOPENED → RESOLVED
Last Resolved: 19 years ago19 years ago
Resolution: --- → FIXED

Comment 6

19 years ago
According to the comments above the prefs tree was never broken. That is to say that during this bug's lifetime the prefs tree 
never exhibited the bug. So verifying that indeed the prefs tree still does not show this bug now that it's 'fixed' has no logical 
consequence.
All that being said if there is no bug to be found, and you promise this is fixed, there's not much else for me to do.
marking VERIFIED.
Status: RESOLVED → VERIFIED
(Reporter)

Comment 7

19 years ago
Not so fast!

David, you and I sat together and corrected this test to current syntax and 
requirements and then I checked it in.  If this test is failing, please point 
out what is now wrong with the source for this test.

Steve
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
(Assignee)

Updated

19 years ago
Status: REOPENED → ASSIGNED
Priority: P3 → P5
Target Milestone: M18 → M20

Comment 8

19 years ago
Mass move of all M20 bugs to M30.

Comment 9

19 years ago
Mass move of M20 bugs to M30
Target Milestone: M20 → M30

Comment 10

18 years ago
Mass-moving all M20-M30 XPToolkit bugs to Future
Target Milestone: M30 → Future
(Assignee)

Comment 11

18 years ago
fixed, although the syntax for the test needs to be updated again.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago18 years ago
Resolution: --- → FIXED

Updated

18 years ago
QA Contact: claudius → jrgm
You need to log in before you can comment on or make changes to this bug.