Last Comment Bug 825588 - (jsdownloads) Asynchronous JavaScript API for downloads
(jsdownloads)
: Asynchronous JavaScript API for downloads
Status: NEW
: meta
Product: Toolkit
Classification: Components
Component: Downloads API (show other bugs)
: Trunk
: All All
: -- normal with 11 votes (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
: :Paolo Amadini
Mentors:
https://wiki.mozilla.org/User:P.A./Do...
: asyncDownloadMgr 830757 (view as bug list)
Depends on: 588314 836445 841348 847184 851471 907764 918188 921052 921054 924091 928972 929391 937740 941009 1163424 1258192 1265328 1265329 1265334 1265391 1297728 825591 831708 835803 835872 835875 835876 835880 836439 836483 836487 847191 847863 851461 851774 852478 852581 852957 865364 899013 901017 905123 905508 907047 907062 907082 908260 908448 911474 915036 915214 916433 917217 919100 928947 929067 941063 941317 1009465 1113736 1254100
Blocks: 890702 932266 asyncDownloadMgr 732924
  Show dependency treegraph
 
Reported: 2012-12-31 04:47 PST by :Paolo Amadini
Modified: 2016-11-04 01:32 PDT (History)
40 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description :Paolo Amadini 2012-12-31 04:47:41 PST
This meta-bug tracks the implementation of an asynchronous JavaScript API for
downloads, according to the draft specification linked by this bug's URL field.
Comment 1 Vladan Djeric (:vladan) 2013-01-15 07:26:31 PST
*** Bug 830757 has been marked as a duplicate of this bug. ***
Comment 2 David E. Ross 2013-08-04 12:08:38 PDT
How will users do downloads if they have been advised to disable JavaScript because of a security vulnerability?  It might be necessary to download a patch or new version of a Mozilla application to eliminate that vulnerability.
Comment 3 Robert Kaiser 2013-08-04 13:18:49 PDT
(In reply to David E. Ross from comment #2)
> How will users do downloads if they have been advised to disable JavaScript
> because of a security vulnerability?  It might be necessary to download a
> patch or new version of a Mozilla application to eliminate that
> vulnerability.

This has nothing to do with JavaScript on websites, this is about JavaScript as used by the user interface. Firefox, Thunderbird and SeaMonkey UI is based on XUL and JavaScript, you can't turn it off there anyhow. And websites don't have access to this API.
Comment 4 :Paolo Amadini 2014-02-24 03:31:46 PST
*** Bug 699854 has been marked as a duplicate of this bug. ***
Comment 5 David E. Ross 2016-04-29 17:26:21 PDT
(In reply to Robert Kaiser (don't count on reactions on anything) from comment #3)
> 
> This has nothing to do with JavaScript on websites, this is about JavaScript
> as used by the user interface. Firefox, Thunderbird and SeaMonkey UI is
> based on XUL and JavaScript, you can't turn it off there anyhow. And
> websites don't have access to this API.

Today, I encountered an extension that is compatible with Firefox, Thunderbird, and SeaMonkey.  That extension uses JavaScript.  If a user disables JavaScript, that extension is broken.  Can extensions use the API to avoid that problem?  If so, how is that documented for extension developers?  

Yes, this is likely off-topic.  However, this seems to be the only venue where this question can be asked of knowledgeable persons.

Note You need to log in before you can comment on or make changes to this bug.