Open Bug 697015 Opened 13 years ago Updated 2 years ago

Download complete notification sent through notification-daemon includes an "Activate" button that does nothing

Categories

(Toolkit :: Downloads API, defect)

x86
Linux
defect

Tracking

()

People

(Reporter: karlt, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: l12y)

Steps to reproduce:

Download a file.


Actual results:

"Download complete" notification appears with an "Activate" button.
Clicking the activate button does nothing.
ed and then persisted in notification-daemon (0.7.1-5). Clearing all the notifications is boring.


Expected results:

Probably no "Activate" button.
Perhaps the "Activate" button might open the download manager, but the strings "Activate" and "All files have finished downloading" are not clear if that is the intended action.


Possibly related to bug 686956.
This is observed under KDE.  I haven't tested other notification systems.
(In reply to Karl Tomlinson (:karlt) from comment #0)
> ed and then persisted in notification-daemon (0.7.1-5). Clearing all the
> notifications is boring.

Oops, please ignore this copy/paste remnant.
It seems the activate button does actually focus the download manager if no focus changes have happened since the download was initiated.

This may be an issue with passing the wrong timestamp in the focus request.
So shall the "Activate" be changed to "Open"? It may be more appropriate when it opens the download manager.
Anyway, the "Activate" button is useful when browser.download.manager.showWhenStarting is false and download manager is hidden by default.
"View" might be better than "Activate" in this particular case, but the nsIAlertsService API does not provide a way to specify the action label.

"Activate" here is not even localizable.  I wonder whether an empty string would be treated consistently.

(In reply to Karl Tomlinson (:karlt) from comment #2)
> It seems the activate button does actually focus the download manager if no
> focus changes have happened since the download was initiated.

If focus changes have happened, then the download window is sometimes marked as demanding attention (but other times I see nothing).

It may not be possible to fix this without a change to the notification spec, because currently callbacks are not given the timestamp of the click to pass to the focus request.  That may all be a bit awkward through dbus.
Keywords: l12y
(In reply to Karl Tomlinson (:karlt) from comment #5)
> If focus changes have happened, then the download window is sometimes marked
> as demanding attention (but other times I see nothing).

I've tested with browser.download.manager.showWhenStarting set to false and the download window is not even opened unless you hit the "Activate" button.
Yes, there's more than one issue here, but it is now clear that the activate button is meant to have an action, and it works in some situations.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.