On 12/22/2014 5:01 PM, Ehsan Akhgari wrote: > There are numerous add-ons that depend on nsIDownloadManager, > unfortunately: Do we have a plan for them?
From the add-ons point of view, the mere removal of nsIDownloadManager from mozilla-central is a bookkeeping operation. With regard to add-ons that only support Firefox for Desktop, the removal of the nsIDownloadManager interface would be only a minor change, because the only functions that are still operational in the component are those to get the path of the download directories, and there are already Downloads.jsm alternatives available. If an add-on supports Firefox for Desktop plus Thunderbird or SeaMonkey, the answer depends on the migration path chosen by those applications. If they migrate to Downloads.jsm as well, add-on authors could simplify their code instead of having to support both back-ends. If they don't, the current compatibility situation would not change. Actually, I'm led to believe that most add-on code showing up on MXR for nsIDownloadManager today is for abandoned add-ons, unused code paths, or add-ons that still want to be compatible with older application versions, for which the legacy code paths would not change. Unfortunately we can't filter that list by add-on status. Cheers, Paolo _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
