-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Writable Files #110
Comments
Given the drafty nature of this, I think that the only sensible response is "defer". Once things mature a little, we can reconsider that position. It seems like some of the thinking here is headed in the right direction, some not. The details matter, but they are still very much in flux. |
I merged the "defer" position... but I'm wondering if maybe we should leave this issue open? |
I think that it would be appropriate to reopen, or open a new issue, when someone believes that there is sufficient new information such that reassessment is warranted. |
…Native File System (mozilla#154).
Request for Mozilla Position on an Emerging Web Specification
Other information
The Writable Files specification seems to be getting some attention lately, so it seems like it may be useful to have a position on it. See the repository, the WICG Discourse discussion, and the Google Developers blog post.
Also see the relationship to the old File System API proposal (caniuse).
The text was updated successfully, but these errors were encountered: