Comment 71 for bug 151162
Revision history for this message
|
|
#71 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Per comment #46, in the backend if it receives the filepromise flavours it can still convert the data to the text/uri-list and do its thing.
In windows the x-moz-url flavor creates a link file of 'internet shortcut' type. If this is correct other o/s should do the same.
If we use the x-moz-file type then the front ends need to do the work outputting to a temp file and passing data as nsIFile per spec. That would facilitate drag and drop to other apps which can receive temp files but not streamed data. The temp file can still be deleted and the other app notes it and gives its user the option to save it.
Ideally, we should use the best of both worlds. This is data not a file and should use filepromise but in backend the data should be offered as both and either streamed or a file made as requested by the target.