> Given the stack of options for saving, why is the > HTML5DownloadFileSave last? What I mean is, what is the disadvantage > compared to the others? > Should it perhaps be first?
The existing direct file I/O functions are synchronous, and return true/false if they actually succeed/fail to save the file. However, the new HTML5 download handling is asynchronous. It simply sets up a link and triggers it to start a browser-controlled interaction. Unfortuately, there's NO events or callback handling we can hook into to know if that process succeeds or fails, so we just have to trigger the link and hope for the best. HTML5DownloadFileSave() returns true if the HTML5 download attribute is supported... regardless of whether or not the file is actually saved. Another, more subtle difference: due to the asynch handling, saving multiple files (i.e., main document, backup file, XML (RSS feed), and empty.html) is problematic. The interaction varies from browser to browser: in Chrome, it pops up a dialog for the first download (main doc), and then it gives you a *modal* warning message "this page is attempting to download multiple files... allow/deny", and waits for a response before popping up as many as 3 more download dialogs, all stacked on top of each other. In contrast, FireFox does not handle more than one asynch link at a time... it only processes the *last* download invoked and ignores the others entirely. -e -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
