Open Bug 537669 Opened 16 years ago Updated 3 years ago

Avoid several confirmation dialogs on multiple file download via multipart response

Categories

(Firefox :: File Handling, enhancement)

x86
All
enhancement

Tracking

()

People

(Reporter: jose.fandos, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2b5) Gecko/20091204 Firefox/3.6b5 Build Identifier: FF allows to upload several files at a time, but it's missing functionality to allow several files download. Most websites that need this type of solution resort to Java, Flash or others, while some offer the multiple files as a single zip files. Reproducible: Always
An improved description would be to avoid showing multiple dialogs to confirm file download when a multiple file download is done via a multipart response with the files as parts, each part having "Content-Disposition: attachment" Updated bug title to reflect this
Summary: Allow multiple file download from a link on website or form (file selector) submittal (not FTP) → Avoid several confirmation dialogs on multiple file download via multipart response
You haven't provided examples of sites doing this. Please provide 5 distinct real world sites including the steps to reach their download and a description of the content they're downloading. Your description should include a characterization of the content and provider as well as the general size of the components. Please note that networking:file relates to the file: protocol, whereas you're much more concerned with the http: protocol, so the fact that your bug stands unconfirmed should not be blamed on us. Misplacing a bug is hardly a reasonable baseline for expecting confirmation. As this bug is actually mostly a UI bug, I'm going to move it to file handling instead of networking:http.
Component: Networking: File → File Handling
QA Contact: networking.file → file-handling
timeless, there's absolutely no need for 5 sites doing this or any such garbage. The linked-to thread has all the necessary information. I also have no idea where your second paragraph is coming from; there was no "expecting confirmation" that I see. Confirming the enhancement request. We probably need both back end code for this (to allow the front end to do something sane) and front-end code. I'd be interested in knowing what sort of API front-end would want here.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Product: Core → Firefox
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.