313134 - Tree doesn't show column selector

Status: RESOLVED WORKSFORME

(Toolkit Graveyard :: XULRunner, defect)

Description

[Tom Germeau]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8b5) Gecko/20051006 Firefox/1.4.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8b5) Gecko/20051006 Firefox/1.4.1

Console::[JavaScript Error: "element has no properties" {file: "chrome://global/
content/bindings/tree.xml" line: 989}]

there should be an extra check

Reproducible: Always

Comment 1

[Nickolay_Ponomarev]

Please write more detailed descriptions. In what cases does this happen? Can you attach a testcase?

Comment 2

[Brian Kardell]

Attachment: Numerous Table Problems with DOMParse

This code illustrates numerous problems with parsing a string of XUL and inserting it into the DOM vs normal rendering.  Set this as your toolkit.defaultChromeURI and run the app.

The first table will parse properly and load up with column draggability, resizing and the column selector.  Almost identical XUL inserted from string using DOMParser renders the tree, but loses all of these pieces of functionality.  I realize that DOMParser does not do everything that loading the application in the browser does, but is this a bug or is it 'as designed'?  If it is 'as designed' - is there a way to 'initialize' the tree?   Curiously enough - it works 'better' (assuming that this isn't by design) with the runner off the trunk.

Comment 3

[Brian Kardell]

Attachment: Slightly better version

This one also adds an onclick to the first column that should output whether or not the tree element has the 'enableColumnDrag' attribute set on it.  The parsed version does not.

Comment 4

[Brian Kardell]

My comments I believe are actually a seperate bug, newly opened as Bug #338159 

Comment 5

[Tom Germeau]

I can not reproduce this bug.