Closed Bug 424842 Opened 17 years ago Closed 15 years ago

XUL custom view tree breaks upon moving <tree> node to new DOM location

Categories

(Firefox :: General, defect)

3.0 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: ewaters, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 2010-07-30])

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080207 Ubuntu/7.10 (gutsy) Firefox/2.0.0.12 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b4) Gecko/2008030318 Firefox/3.0b4 I use a custom tree view in a XUL project which runs as a FF extension for an inhouse application. The tree is moved from one location to another, with the view being reset after the move to ensure it's visibility in the new location. This worked in 1.5 and 2.0 but no longer works in 3.0 (tried b1 -> b4). The moving is simple: newParent.appendChild(treeElement); treeElement.view = treeView; Reproducible: Always Steps to Reproduce: 1. Run http://demeter.vegcrew.net/~ewaters/tree_bug_ff3.xul with full chrome permissions (I did so by running it in my installed extension). 2. Click the button "Collapse to toolbar". 3. See if the data of the tree remains visible. Actual Results: In 3.0, the tree appears to move but the content doesn't reappear. Expected Results: In 2.0.0.12, it will move the tree with content underneath the label "Below is the hidden toolbar" and back again, keeping the content visible. The test was performed in a relatively empty profile, setup for development purposes.
Tested in 3.0b5 - still doesn't work.
Reporter, are you still seeing this issue with Firefox 3.6.x or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2010-07-30]
Version: unspecified → 3.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.