1265328 - [meta] Remove DownloadLegacy

Status: RESOLVED INACTIVE

(Toolkit :: Downloads API, task, P3)

Description

[:Paolo Amadini]

This is a meta-bug for the long-term work needed to re-architect the handling of downloads made by nsExternalHelperAppService.cpp and remove the DownloadLegacy component from the JavaScript API for downloads.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:Paolo, maybe it's time to close this bug?

Comment 2

[:Paolo Amadini]

It doesn't look like this robot is doing useful work, most of these are meta-bugs for past projects missing a breakdown, but they're still valid, as much as any similar bug without the "meta" keyword.

Comment 3

[Sylvestre Ledru [:Sylvestre]]

Thanks for your input. We will evaluate the impact of this nag.

Comment 4

[Marco Bonardo [:mak]]

This is still important to simplify management and to cover all of those bugs where the download fails unexpectedly (full disk) or the user is surprised by us storing something before he actually picked a destination.

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

The meta keyword is there, the bug doesn't depend on other bugs and there is no activity for 12 months.
:mak, maybe it's time to close this bug?

Comment 6

[Marco Bonardo [:mak]]

I think there's no trivial path to remove DownloadLegacy, as for various reasons the download will start in network and reach us later. It may still be a good idea to rename it, as it's not really Legacy, is more like DownloadAdopted, though that'd be a different bug.
Rearchitecting nsExternalHelperAppService may be a good idea, but without a plan and a team is not very useful to track it.
If we want to do it, we should have a more complete plan of how to attack the problem.