661384 - In Download Manager, the Clear List button has a bug if the file list is more than one screen

Status: RESOLVED WORKSFORME

(SeaMonkey :: Download & File Handling, defect)

Description

[Steve Dunn]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14

If the list of files showing in Download Manager is more than can be displayed on one screen (i.e. a scroll bar is needed to scroll up and down the list), pressing Clear List causes Download Manager to stop displaying further downloads.

Reproducible: Always

Steps to Reproduce:
1.  Save/download enough files to exceed the number of lines that Download Manager can display in whatever size window you've given it.
2.  Press the Clear List button.
3.  Save/download something else.
4.  Close Download Manager.
5.  Save/download something else.

Actual Results:  
After clearing the long list, Download Manager will not display your subsequent downloads.  It will flash and the notification that downloads are complete will appear as usual, but the Download Manager window will be empty.

After closing and re-opening Download Manager, it works correctly again.

Expected Results:  
After clearing the list, new downloads should appear in the list without having to close Download Manager first.

If you clear the list *before* the list grows too big to display in the window, everything works as you'd expect.  As far as I can tell, this problem only occurs if the list has grown to be too large for the window.

Comment 1

[therube]

If you maximize the Download Manager window, do your downloads then "appear"?

I'm not able to duplicate your steps in 2.0.15 nor 2.2, but I suspect it is some variation of these:

Bug 519623 - Download Manager, Search, Returns No Results
Bug 519612 - Download Manager, Search Results Blank Out (Dup'd to 519623)

With Bug 519623 resolved not to be fixed in 2.0.x, & WFM in 2.2.

So check to see if you can duplicate this in 2.2 & if not, suspect this will be resolved the same.

Comment 2

[Steve Dunn]

(In reply to comment #1)
> If you maximize the Download Manager window, do your downloads then "appear"?

I haven't tried to see if the same problem occurs if I leave Download Manager maximized from the start - I'll try that next and see if it makes any difference.  If I cause the problem to occur with the window not maximized, maximizing the window does not fix it (nor does restoring it after maximizing it).

> I'm not able to duplicate your steps in 2.0.15 nor 2.2

Interestingly enough, the first time I tried to test this today in 2.0.14 (by letting the list grow beyond what fits in the window, clearing it, and then downloading/saving again), it worked properly.  But the *second* time in the same session that I overflowed one window's worth of downloads and then cleared it, the problem showed up.  I don't recall the same prerequisite before; I'll test it again some time to see if this is consistent and report back.

> So check to see if you can duplicate this in 2.2 & if not, suspect this will
> be resolved the same.

I don't even use version *.0 as my primary browser, let alone a beta, so I'm afraid this isn't something I can test in 2.2 at this point.

Comment 3

[Steve Dunn]

(In reply to comment #2)
> I haven't tried to see if the same problem occurs if I leave Download
> Manager maximized from the start - I'll try that next and see if it makes
> any difference.

Having Download Manager maximized doesn't change its behaviour.  As with yesterday's comment, the first time it overflowed the number of downloads that could be shown in the window, clearing the list worked properly, but the second time it overflowed, subsequent downloads did not appear until I closed and restarted Download Manager.  (As before, this is in 2.0.14.)

Comment 4

[Steve Dunn]

(In reply to therube from comment #1)
> So check to see if you can duplicate this in 2.2 & if not, suspect this will
> be resolved the same.

I have been unable to duplicate this in 2.2.  I'm fairly confident (though not 100% certain) that, given the same usage I've done with 2.2, it would have shown up by now in 2.0.14.  So I suspect this issue went away somewhere between 2.0.14 and 2.2.

I will continue to try to duplicate it and will post an update if anything changes (or if I can duplicate it in something later than 2.2).

Comment 5

[Phoenix]

Is this still actual?

Comment 6

[Steve Dunn]

I have not seen it in subsequent versions, so I think whatever was causing it in 2.0.x has gone away.