hidden="true" on tree item hides subsequent items

RESOLVED FIXED in Future

Status

()

Core
XUL
P3
normal
RESOLVED FIXED
18 years ago
10 years ago

People

(Reporter: myk, Assigned: David Hyatt)

Tracking

Trunk
Future
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

18 years ago
Overview Description:

Setting hidden="true" on a tree item incorrectly hides subsequent items in the
tree that are not hidden.

Steps to Reproduce:

1) Load test case which contains tree with five items, the third of which is hidden.
2) Notice that items four and five do not appear.
3) Check test case code to verify that those items are not hidden.

Actual Results:

Items four and five do not appear.

Expected Results:

Items four and five appear.

Build Date & Platform Bug Found:

2000072608 Linux

Additional Builds and Platforms Tested On:

None

Additional Information:

None
(Reporter)

Comment 1

18 years ago
Created attachment 12159 [details]
test case
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → Future

Comment 2

18 years ago
->moz0.9
Target Milestone: Future → mozilla0.9

Comment 3

18 years ago
FYI: This was working Mozilla M18 but it's broke again in Mozilla 0.7

Comment 4

18 years ago
->future
Target Milestone: mozilla0.9 → Future

Comment 5

18 years ago
The following code which toggles the hidden state of a treeitem got broken
sometime between build IDs 20001024 and 20001104:

  var treeitem = document.getElementById('foo');
  if (treeitem.getAttribute('hidden') == 'true')
    treeitem.setAttribute('hidden','false');
  else treeitem.setAttribute('hidden','true');

Using the latter build, all of the treeitems following the one explicitly hidden
are also removed.

Comment 6

16 years ago
content view handles this correctly.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED

Updated

10 years ago
Component: XP Toolkit/Widgets: Trees → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.