Anonymous content is smoking trees

NEW
Assigned to

Status

()

Core
XUL
15 years ago
10 years ago

People

(Reporter: WeirdAl, Assigned: janv)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
I came up with the idea that if I have a tree in anonymous content, and its 
treeitems non-anonymous, I should be able to just append treeitem elements to 
the appropriate bound element:

<foo:tree>
  <xul:treeitem>
    <xul:treerow>
      <xul:treecell label="Hi mom!"/>
    </xul:treerow>
  </xul:treeitem>
</foo:tree>

This assumes the foo:tree element has a properly formatted tree in its 
anonymous content:

<binding id="foo:tree">
  <content>
    <xul:tree style="height:200px; width:300px;">
      <xul:treecols>
        <xul:treecol id="primary" primary="true" label="Messages"/>
      </xul:treecols>
      <xul:treechildren>
        <children/>
      </xul:treechildren>
    </xul:tree>
  </content>
</binding>

Unfortunately, it doesn't work.  Similarly, moving the treechildren element out 
of the binding and into the mainstream content is ineffective.

Basically, the tree's default view just doesn't consider the anonymity that XBL 
makes possible in all the relevant combinations.

Cc'ing hyatt, bz.  I'm wondering if I'm just asking way too much of the tree 
view code, to call for anonymous and non-anonymous code to sit side-by-side 
happily ever after.  (Please don't assign this bug to me; I haven't the 
foggiest idea how to fix this...)

Comment 1

14 years ago
The similar thing has a place when I try insert non-anonymous menuitems into
anonymous menulist. In this case it can be fixed by changing menulist binding.

Updated

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