[Webkit-unassigned] [Bug 213775] [Feature Request] Implement the File System Access API (née Native File System API)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 15 12:03:55 PST 2022


https://bugs.webkit.org/show_bug.cgi?id=213775

jdscheff at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jdscheff at gmail.com

--- Comment #5 from jdscheff at gmail.com ---
For https://basketball-gm.com/ (video game with tens of thousands of active users) I store a ton of data in IndexedDB. If users want to export it, the File System Access API and showSaveFilePicker is the only good way to stream client side data to a file. Otherwise, I need to either read it all into memory first (not feasible for large data) or use a complicated workaround like https://github.com/jimmywarting/StreamSaver.js

So currently it is possible to create files client side, if you read the data into memory first. And it is possible to create arbitrarily large files from streaming data, as long as you use a complicated workaround. showSaveFilePicker lets you accomplish the same thing with no complicated workaround.

I understand showSaveFilePicker enables more functionality than just streaming data to a new file... but I am not aware of any alternative proposal that would allow easily streaming data to a new file. So I hope browsers besides Chrome can either support showSaveFilePicker or come up with some feasible alternative.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220215/914eb9e1/attachment.htm>


More information about the webkit-unassigned mailing list