> It's sort of charitable to say that there's "no signal" from either Safari or Firefox on File System APIs I agree the phrase "no signal" does not accurately

> It's sort of charitable to say that there's "no signal" from either Safari or Firefox on File System APIs I agree the phrase "no signal" does not accurately communicate other browser vendors' position. Mozilla's current position on File System API is "defer". > The ability to read and write from the filesystem is potentially very dangerous. We will need to carefully consider any solution in light of the security and privacy implications. > We recognize that the spec authors take this issue seriously, but we are concerned that any solution will increase the risk of security incidents more than we are willing to tolerate. Right now, there isn't enough detail in the specification to make an assessment of these risks, so we will defer our decision until we have more information. https://mozilla.github.io/standards-positions/#native-file-system https://mozilla.github.io/standards-positions/#native-file-s... ..And Safari's position: > Apple's WebKit team does not support this feature due to the security / safety concerns. https://lists.webkit.org/pipermail/webkit-dev/2020-August/031362.html https://lists.webkit.org/pipermail/webkit-dev/2020-August/03...