227145 - no confirmation that a new download has begun, if the download manager window is open in the background

Status: RESOLVED DUPLICATE of bug 230768

(Toolkit :: Downloads API, defect, P2)

Description

[Az]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031128 Firebird/0.7+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031128 Firebird/0.7+

When a new file is added to the download manager it does not come to the front
so the user receives no notification that it is successfuly going ahead.

Reproducible: Always

Steps to Reproduce:
1. Begin download 1.
2. Move focus to main FB window
3. Begin new download (2)

Actual Results:  
File starts to download but download manager does not come to the front.  No
notification is provided.

Expected Results:  
Download manager should focus front.

Alternatively a little popup notification should be shown (just like when dls
are complete).

Comment 1

[Ben Goodger (use ben at mozilla dot org for email)]

Currently we don't focus the window because by and large that'd be annoying. 

You can make the window focus when a new download starts however by using
about:config to set this pref:

browser.download.manager.focusWhenStarting

to "true"

I'm leaving this bug open however for discussion. 

Comment 2

[scratch]

i like the current behavior.

Comment 3

[Az]

after spending more time with the new dl manager i must say i agree that if it
kept coming into focus then it would be annoying, however i do still think that
some kind of confirmation would be nice.  Maybe a small box (just like when dls
are complete) which doesnt actually need to be 'OKed' would be more appropriate.

Comment 4

[Ben Goodger (use ben at mozilla dot org for email)]

Resummarizing. This *is* annoying. If the window is open in the background, you
click a link and nothing happens. I'm going to try and see if I can make the
window flash a few times in the taskbar. 

Comment 5

[José Jeria]

Duping, this has been implemented. Comment 4 is almost identical to bug 230768,
comment 0

*** This bug has been marked as a duplicate of 230768 ***