269498 - XML viewer doesn't handle expansion/hiding properly

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[matthew.booth]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When using the XML viewer, certain nodes are not handled correctly when
hiding/expanding. I have seen 2 bugged behaviours which I suspect are caused by
the same bug:

1. Hiding a node (click -) causes the node to be hidden, but the nodes
underneath it are not moved up, leaving a white space on the page.

2. Expanding a node (click +) causes the node to be expanded, but the nodes
underneath it are not moved down, causing overlapping text.

This does not happen for all nodes, however it does happen in one of the nodes
in an XML document I will attach in a comment below.

1 is really simple to reproduce, simply contract the <nav:url> tag in my
example. This is 100% reliable on this browser.

2 is harder to reproduce because it only happens for the <nav:url> node, which
doesn't move the text below it up in normal circumstances. By clicking on random
stuff I have managed to reproduce this (only takes a few seconds of random
clicking), but I haven't worked out a reliable path to it.

Note that this works fine on Mozilla 1.7.2.

Reproducible: Always
Steps to Reproduce:
1. Open example.xml, which I will attach below.
2. Hide the nav:url node

Actual Results:  
The node was contracted, but nodes below it did not move up to fill the space.

Expected Results:  
The node should contract and nodes around it should adjust properly.

Look in a comment for example.xml

Comment 1

[matthew.booth]

Attachment: An example xml file which demonstrates the bugged behaviour

Only the <nav:url> node displays the bugged behaviour.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.