4 ms·
You're looking for https://fs.spec.whatwg.org/ https://fs.spec.whatwg.org/ https://mozilla.github.io/standards-positions/ https://mozilla.github.io/standards-p
by magicalist 4y ago
You're looking for https://fs.spec.whatwg.org/ https://fs.spec.whatwg.org/
https://mozilla.github.io/standards-positions/ https://mozilla.github.io/standards-positions/ is positive on it
and implementation is well underway: https://bugzilla.mozilla.org/show_bug.cgi?id=1748667 https://bugzilla.mozilla.org/show_bug.cgi?id=1748667
- sgbeal 4y ago> https://mozilla.github.io/standards-positions/ https://mozilla.github.io/standards-positions/ is positive on it To hopefully add a bit of clarity: indeed, that page has OPFS flagged as positive under the label "File System." Further down the page is a "File System Access" entry which is flagged negative.
- whimsicalism 4y agoYou're wrong for the API discussed in GP.
- dmitriid 4y agoThat's why I wrote this: "in true Google fashion Chrome team implemented and released at least three different APIs all having something to do with files." :) I didn't want to dig through all of them on mobile when I was responding. Both Safari and Mozilla are open (and implement/have implemented) to Origin Private File System. Because it gives web sites an access to a file system without a chance of escaping and damaging user data. Can't remember which spec introduced it, and it doesn't really matter at this point. For the more general part of File System Access Mozilla's and Safari's positions are: nope. https://github.com/mozilla/standards-positions/issues/154 https://github.com/mozilla/standards-positions/issues/154 There was also Storage Foundation API but it was thankfully never shipped (it was like a third way of handling files or something),and also received negative responses: https://chromestatus.com/feature/5670244905385984 https://chromestatus.com/feature/5670244905385984