Related: https://developers.google.com/web/updates/2011/08/Saving-generated-files-on-the-client-side So I think the correct behaviour for a PUT to a "file:" URL is this: 1. Serialise to an internal structure 2. Present it to the user as a "download", as in the text example in that article, with the filename initially filled in according to the PUT URL. 3. Let the user decided if it is to be downloaded at all (a [cancel] would generate a submit-error), and if so to which actual file. Similarly, a GET from a file: which would be equivalent to an upload dialogue, with the URL filled in, allowing the user to cancel, or change the location. Steven Steven On Wed, 13 Mar 2019 22:35:36 +0100, Erik Bruchez <ebruchez@orbeon.com> wrote: > Related, I just read this today (although the post dates back to > November): > > https://developers.google.com/web/updates/2018/11/writable-files > > -Erik > > On Tue, Mar 12, 2019 at 1:42 PM Steven Pemberton > <steven.pemberton@cwi.nl> wrote: >> Part 1. >> >> File write. Here is a (working) example: >> >> https://eligrey.com/demos/FileSaver.js/ >> >> >> From this blog: >> >> https://eligrey.com/blog/saving-generated-files-on-the-client-side/ >> >> >> Steven >> >> On Wed, 30 Jan 2019 15:19:02 +0100, XForms Users Community Group Issue >> Tracker <sysbot+tracker@w3.org> wrote: >> >>> ACTION-2217: Spec up file/read and write (and provide links) >>> >>> https://www.w3.org/2005/06/tracker/xforms/actions/2217 >>> >>> Assigned to: Steven Pemberton >>> >>> >>> >>> >>> >>>
Received on Wednesday, 8 April 2020 10:48:13 UTC