Current XULSortService implementation is hard-coded to only deal with trees. Can we extend to deal with any kind of template-generated content?
Add shaver to cc list; I know he wanted this for a calendar demo.
The sorting code is tight fairly tightly to trees... for example, it has intimate knowledge of the DOM layout of trees, needs the tree's column nodes to determine what to sort on, etc. Nisheeth is helping complete work on getting XSL in. That might be a better answer for Shaver, depending on what he's doing, if/when XSL lands, and the phase of the moon.
Assigning to originator per new organizational structure.
Changing QA Contact back to firstname.lastname@example.org
The XULSortService can now sort any content, not just trees, so I'm changing this from WONTFIX to FIXED.
Robert, is there a specific test case for this?
Chris, my friend, just for you: I've attached a simple test case which will put all the non-container nodes in your personal toolbar into a HTML:SELECT widget and impose a descending sort on it.
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL component will be deleted.
Massive QA Contact update.
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.