Open
Bug 825588
(jsdownloads)
Opened 12 years ago
Updated 1 year ago
[meta] Asynchronous JavaScript API for downloads
Categories
(Toolkit :: Downloads API, enhancement)
Toolkit
Downloads API
Tracking
()
NEW
People
(Reporter: Paolo, Unassigned)
References
(Depends on 13 open bugs, Blocks 1 open bug, )
Details
(Keywords: meta)
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.
Reporter | ||
Updated•12 years ago
|
Blocks: asyncDownloadMgr
Reporter | ||
Updated•12 years ago
|
Whiteboard: [Async]
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Comment 2•11 years ago
|
||
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•11 years ago
|
||
(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.
Updated•11 years ago
|
Flags: sec-review?(mgoodwin)
Reporter | ||
Updated•11 years ago
|
Whiteboard: [Async]
Comment 5•9 years ago
|
||
(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.
Updated•8 years ago
|
Flags: sec-review?(mgoodwin)
Updated•6 years ago
|
Summary: Asynchronous JavaScript API for downloads → [meta] Asynchronous JavaScript API for downloads
Updated•6 years ago
|
Type: defect → enhancement
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•