Closed
Bug 21462
Opened 25 years ago
Closed 25 years ago
[Tree] Shift-click implementation is incomplete
Categories
(Core :: XUL, defect, P3)
Core
XUL
Tracking
()
VERIFIED
FIXED
M14
People
(Reporter: selmer, Assigned: hyatt)
References
Details
(Whiteboard: Fix in hand. Needs review.)
Bug 12288 was closed because the minimal shift+click implementation went in as a
PDT+ fix. This bug picks up where that one left off:
1. Need to honor open/closed state of nodes in trees
2. Need to correctly implement 4.x selection behavior
3. Need to find the remaining performance problems (about 5x improvement is
theoretically possible)
Putterman's comment about using cell selection is invalidated by Hyatt's comment
that cell selection should just die. In any case the implementation using the
nsContentIterator just needs to be refined to handle the remainder of the
features of shift+click.
Reporter | ||
Updated•25 years ago
|
Reporter | ||
Updated•25 years ago
|
Target Milestone: M14
Reporter | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Updated•25 years ago
|
Assignee: selmer → trudelle
Status: ASSIGNED → NEW
Reporter | ||
Comment 1•25 years ago
|
||
Peter, I've got another project that's going to prevent me from helping with
these bugs. I need to send them back to your court. Steve
Updated•25 years ago
|
Assignee: trudelle → hyatt
Comment 2•25 years ago
|
||
back to hyatt
Comment 3•25 years ago
|
||
adding jefft to CC because I think he has a mail bug about this.
Assignee | ||
Comment 4•25 years ago
|
||
I have code in my tree that rewrites shift+click. I would like for individual
bugs to be opened against shift+click as they surface, but I plan to mark this
one fixed once I can check in.
Status: NEW → ASSIGNED
Whiteboard: Fix in hand. Needs review.
Assignee | ||
Comment 5•25 years ago
|
||
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 6•25 years ago
|
||
VERIFIED. shift+click seems to work enough for me with 2000020108 builds.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•