Open
Bug 405373
Opened 18 years ago
Updated 3 years ago
Phantom/non-functional context menu still appears after doing a Clear List
Categories
(Toolkit :: Downloads API, defect)
Toolkit
Downloads API
Tracking
()
NEW
People
(Reporter: adelfino, Unassigned)
References
(Depends on 1 open bug)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2pre) Gecko/2007112505 Minefield/3.0b2pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2pre) Gecko/2007112505 Minefield/3.0b2pre
When doing right click on empty space of Downloads, while there's a download going on, no options should appear.
Since there is no selected download.
Reproducible: Always
Reporter | ||
Updated•18 years ago
|
Version: unspecified → Trunk
Comment 1•18 years ago
|
||
from what i see here, there is always a selected download...
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b2pre) Gecko/2007112605 Minefield/3.0b2pre
![]() |
||
Comment 2•18 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9b2pre) Gecko/2007120304 Minefield/3.0b2pre
If I choose Clear List, the menu with all those items still appears until I reopen the dialog.
Comment 3•18 years ago
|
||
Yup, I see this too. Confirming the bug -> NEW
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•18 years ago
|
||
Are we not flushing the rich listbox's tree (or whatever that is) after doing a "Clear List"?
Summary: Confusing options when doing right click on empty space in Downloads → Phantom/non-functional context menu still appears after doing a Clear List
![]() |
||
Updated•18 years ago
|
OS: Windows XP → All
Comment 5•18 years ago
|
||
This looks like a richlistbox bug, actually. We remove the elements from the richlistbox, but its selectedItems array isn't updated, so its selectedItem getter still returns the previously selected element. Could fix this on the DM side by explicitly setting selectedItem to null, or using a richlistbox method to do the removals, I guess, but I wonder whether the listbox-base binding should handle this case better.
Comment 6•18 years ago
|
||
If that's the reason, then it would be fixed by bug 331513 presumably.
Comment 7•18 years ago
|
||
Seems likely. I tried testing the patch but it doesn't apply to current trunk.
Depends on: 331513
Reporter | ||
Updated•18 years ago
|
Hardware: PC → All
Comment 8•18 years ago
|
||
The current behavior is that the context menu that appears corresponds to the selected download, even if you right-click on the empty space of the Download Manager window. This is completely wrong, because clicking on the empty space should bring up a context menu suitable for the empty space (possibly containing only generic options such as "Clear List".
Maybe the context menu issues fit in Bug 397655 ?
Reporter | ||
Comment 9•18 years ago
|
||
(In reply to comment #8)
> The current behavior is that the context menu that appears corresponds to the
> selected download, even if you right-click on the empty space of the Download
> Manager window. This is completely wrong, because clicking on the empty space
> should bring up a context menu suitable for the empty space (possibly
> containing only generic options such as "Clear List".
>
> Maybe the context menu issues fit in Bug 397655 ?
>
I'd think so if the mock ups of that bug would deal with context menu of empty space.
Comment 10•17 years ago
|
||
This seems to work more or less correctly in latest nightlies of Firefox 3:
- In a clear list, no context menu appears
- If I deselect the selected item by Ctrl+click, so that no item is selected, then right-click on the empty space does not bring up a context menu.
However, if there is a selected item, clicking on the empty space does bring up the context menu relevant to the selected item, which is still wrong, since the correct behavior when right-clicking on the empty space would be to deselect any previously selected item and bring up a context menu suitable for the empty space.
Assignee | ||
Updated•17 years ago
|
Product: Firefox → Toolkit
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•