Closed
Bug 70858
Opened 24 years ago
Closed 23 years ago
[XUL Syntax] Implement <listbox>
Categories
(Core :: XUL, defect, P3)
Core
XUL
Tracking
()
RESOLVED
FIXED
mozilla0.9.8
People
(Reporter: hyatt, Assigned: hewitt)
References
Details
(Whiteboard: [xul1.0-widgets-listbox])
Attachments
(2 files)
148.08 KB,
patch
|
Details | Diff | Splinter Review | |
9.72 KB,
application/vnd.mozilla.xul+xml
|
Details |
The <tree> tags should all be replaced with list equivalents. When this bug is fixed, all uses of <tree> tags will be eliminated from the XUL. <tree> --> <listbox> <treehead> --> <listhead> <treecolgroup> --> <listcols> <treecol> --> <listcol> <treerows> --> <listrows> <treerow> --> <listrow> <treecell> --> <listcell> <treechildren> --> <listchildren> The new list should support several simplified forms of syntax. <listbox> <listitem value="1" label="One"/> <listitem value="2" label="Two"/> </listbox> up to the full-blown multi-column scrolling list. This is a very very large bug that I will probably have to tackle. It might make sense to continue to support <tree> so that all XUL files need not be updated initially.
Reporter | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Whiteboard: [XUL1.0]
Target Milestone: --- → mozilla1.0
Comment 1•24 years ago
|
||
If you need any gruntwork help, let me know.
Comment 2•24 years ago
|
||
I had bug 61436 relating to the .treecell-text class resolved as wontfix because of these changes. Should some form of the .treecell-text class be retained then believe this bug would become relavent.
Reporter | ||
Updated•23 years ago
|
Summary: [XUL Syntax] Replace <tree> with <listbox> → [XUL Syntax] Implement <listbox>
Whiteboard: [XUL1.0] → [xul1.0-widgets-listbox]
Assignee | ||
Comment 3•23 years ago
|
||
taking
Assignee: hyatt → hewitt
Status: ASSIGNED → NEW
OS: Windows 2000 → All
Priority: -- → P3
Hardware: PC → All
Target Milestone: mozilla1.0 → mozilla0.9.7
Assignee | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.7 → mozilla0.9.6
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.6 → mozilla0.9.7
Assignee | ||
Comment 4•23 years ago
|
||
This patch includes the new frames, layout manager, xbl, and css for listbox. My original strategy was to just use the old tree frames, but since we are going to ditch tree, I decided to rewrite these frames for listbox and remove all the hierarchical stuff that will no longer be used. This makes the listbox code much much simpler than the tree code.
Comment 5•23 years ago
|
||
r=evaughan
Comment 6•23 years ago
|
||
Am I crazy or should there be some xbl changes in this patch? Will tree.xml stay the same, or will there be a new listbox binding? Will the current listitem.xml stay as it is?
Comment 7•23 years ago
|
||
Never mind ...
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Assignee | ||
Comment 9•23 years ago
|
||
fixed
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 10•23 years ago
|
||
Does this mean that <tree> and associated tags are now officially deprecated, or will be very soon?
Comment 11•23 years ago
|
||
<method name="_selectTimeoutHandler"> <parameter name="me"/> <body> <![CDATA[ me._fireOnSelect(); this._selectTimeout = null; ]]> </body> </method> Shouldn't that be me._selectTimeout = null? I would like to see a currentIndex property and also more keys as per bug 97434, is it worth my while filing a separate bug?
Comment 12•23 years ago
|
||
Oh, and has <listbox rows="N"> been tested with an empty listbox? IIRC this didn't work very well with trees.
Assignee | ||
Comment 13•23 years ago
|
||
Yes, <listbox rows="N"> works. The current tree implementation has been deprecated, and it will be removed fully during the next milestone, as the tree tags come to be used for outliner, and the outliner tags go away completely.
Assignee | ||
Comment 14•23 years ago
|
||
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•