Closed
Bug 8335
Opened 25 years ago
Closed 25 years ago
tree widget selection problem
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
VERIFIED
FIXED
M10
People
(Reporter: selmer, Assigned: hyatt)
References
Details
(Whiteboard: [DOGFOOD] Mailnews needs this for Dogfood)
Build 1999061611: setting the selected attribute of a treeitem to true causes
that item to remain selected even after the user clicks on another treeitem. It
stays selected until you click on it and then click somewhere else. Visually,
this causes me to have 2 items appearing selected even though no meta keys were
used at any point.
Is there some magic I can do to avoid this or is it just a bug?
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M8
Assignee | ||
Comment 1•25 years ago
|
||
Are you explicitly setting the selected attribute on a node? e.g.,
setAttribute("selected", "true")
is being done in your JavaScript somewhere?
Reporter | ||
Comment 2•25 years ago
|
||
Yup, exactly.
Moving all Widget Set bugs, past and present, to new HTML Form Controls
component per request from karnaze. Widget Set component will be retired
shortly.
Assignee | ||
Updated•25 years ago
|
Target Milestone: M8 → M9
Updated•25 years ago
|
Whiteboard: [DOGFOOD] Mailnews needs this for Dogfood
Comment 4•25 years ago
|
||
changed status. Assuming this is the correct bug, we need this for 10658 to do
work like Next Unread Message or opening to the Inbox on startup which are part
of mailnews dogfood. M9 would be great, but I could live with early M10.
Assignee | ||
Comment 5•25 years ago
|
||
Moving to M10.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•25 years ago
|
||
This bug is now fixed. Yay! See the XPFE newsgroup post I made tonight
regarding the new selection APIs on the tree element. They should come in
handy.
code level fix, marking verified. steve, reopen if i'm wrong here...
You need to log in
before you can comment on or make changes to this bug.
Description
•