For future reference, I posted another suggestion to the public-webapps
list. Instead of specifying a download URL, you could specify a URL on a
type as the source of the data:
dataTransfer.setRemoteData(mimeType, url);
That could allow for both file downloads and/or lazy loading of data
On Mon, 17 Aug 2009, Jian Li wrote:
The HTML 5 spec defines the event-based drag-and-drop mechanism that
could cross the browser boundary. If a draggable element contains a URL,
dragging it out of the browser will only copy the URL value. However, in
some scenarios, we really want to
Sounds interesting!
You only mention a singular file, what do you think about multiple files?
Also, would it be possible to hook browser-produced data into this model, so
client-generated data (f ex text, html, pdf) could be dragged out as a
virtual file to the desktop?
Best regards
Mike
Also, would it be possible to hook browser-produced data into this model,
so client-generated data (f ex text, html, pdf) could be dragged out as a
virtual file to the desktop?
You could also extend the File API to allow for user created instances of
FileData objects. This would be comparable
