On 3/25/14 12:14 PM, Si Robertson retromodu...@gmail.com wrote:
When a user decides to save a file that they have been working on in an
application, the file data is typically a temporary serialized version of
the file's state/model. Native
applications will write the data directly to disk using
On Tue, Mar 25, 2014 at 1:10 AM, Si Robertson retromodu...@gmail.com wrote:
Ideally, the File API would provide a way for users to save a file, and I'm
surprised this is still an issue. Writing a file to a user selected location
is no less secure than allowing a user to download a file with an
* Si Robertson wrote:
The problem that this new event would solve is this - when using a
temporary object URL (blob) for the file data, e.g. programmatically
generated content, there is currently no way of knowing when that file data
has been written to disk, therefore there is no reliable way of
On Mon, Mar 24, 2014 at 8:10 PM, Si Robertson retromodu...@gmail.comwrote:
Allowing users to save/download a runtime-generated file with the use of
object URLs and the anchor download attribute is the only viable way of
doing things at the moment. Bouncing the file through a server isn't
* Bjoern Hoehrmann write:
That something has been written to disk does not make destryoing data
safe. It is not unsual, for instance, to expect that data can be saved
more than once, and invalidating such expectations can lead to catas-
trophic data loss. I think
On 3/23/14 5:30 PM, Si Robertson retromodu...@gmail.com wrote:
Hi guys,
This mailing list was suggested to me by one of the Chromium developers,
so I apologize in advance if this mailing list is not appropriate for
this request/proposal.
In a nutshell, I am asking for a download event to be
If a developer creates an object URL, e.g. theFile =
URL.createObjectURL(theData), then it's the developer's responsibility to
revoke that object URL. Assigning theFile to an anchor href so the data can
be downloaded doesn't create a copy of data.
The web browser will definitely know when the
On Mon, Mar 24, 2014 at 2:45 PM, Si Robertson retromodu...@gmail.com
wrote:
If a developer creates an object URL, e.g. theFile =
URL.createObjectURL(theData), then it's the developer's responsibility to
revoke that object URL. Assigning theFile to an anchor href so the data
can be downloaded
On 3/24/14 1:16 PM, Glenn Maynard gl...@zewt.orgmailto:gl...@zewt.org
wrote:
On Mon, Mar 24, 2014 at 2:45 PM, Si Robertson
retromodu...@gmail.commailto:retromodu...@gmail.com wrote:
The web browser will definitely know when the data has been written to disk,
the problem is the developer won't
(Can you turn off the Outlook-style indentation quoting? It makes the
archives unreadable:
http://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0738.html,
and doesn't mix well with regular quoting.)
On Mon, Mar 24, 2014 at 5:24 PM, Brian Matthews (brmatthe)
brmat...@cisco.com wrote:
Allowing users to save/download a runtime-generated file with the use of
object URLs and the anchor download attribute is the only viable way of
doing things at the moment. Bouncing the file through a server isn't
acceptable for web applications that are supposed to act like native apps.
Ideally,
11 matches
Mail list logo
