- From: <bugzilla@jessica.w3.org>
- Date: Thu, 31 Oct 2013 20:50:49 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23450 --- Comment #3 from Arun <arun@mozilla.com> --- Just to clarify Comment 2, I meant that user agents return headers of the sort Content-Disposition: inline; filename="file.name" Where "file.name" is the filename from the File object. UAs would do this specially for File objects retrieved with blob: URLs. The API wouldn't allow header-based configuration of "Save As" behavior by allowing web developers to add "attachment" as an option for the header (since this would mean an additional property on Blob, and an additional member to the configuration/invocation dictionary for constructor calls). The alternative is to add another attribute on Blob, and to allow it to be set in the constructor. Is it worth allowing programmatic manipulation of "Save As" through a header? I'm inclined to not allow it. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 31 October 2013 20:50:50 UTC