https://github.com/whatwg/fs/pull/53/commits/618b663ebdc0f9842d7db3091baed5f75aa87534
Updates the asynchronous methods (`flush()`, `getSize()`, `truncate()`) in `FileSystemSyncAccessHandle` in the File System Access API to synchronous methods. `FileSystemSyncAccessHandle` currently has a mix of sync and async methods, hindering the performance and the usability, especially for applications porting C/C++ to Wasm. This update will bring consistency in the API usage and improve the performance for Wasm-based libraries.
https://github.com/w3ctag/design-reviews/issues/772
Pending
Compatibility:
Changing a return type from Promise to value can break, only if Promise methods are directly used rather than `await`. However, we expect minimal breakage due to very low usage (~0.00002% page loads; zero usage queried via HttpArchive). The original API was shipped in M102 and targeted for partner usage, to which the changes may be communicated. In addition, all code snippets and examples in public documents use `await`, which does not cause any breakage.
Interoperability:
There are no interoperability risks expected. The design change was initially proposed and assessed from vendor feedback. https://github.com/whatwg/fs/issues/7
Gecko: Positive (https://github.com/whatwg/fs/issues/7#issuecomment-1226562961)
WebKit: No signal
Web developers: Strongly positive (https://github.com/whatwg/fs/issues/7)
Other signals:
Low ergonomics risks are expected. In fact, the goal of this change is to improve the ergonomics of the API by making all methods to return synchronously and make it easier to use on Wasm-ported applications.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
Basic tooling: Autocomplete works as described in "New WebIDL/DOM interfaces and attributes".
No
Desktop only now. Origin Private File System (including `FileSystemSyncAccessHandle`) is planned to be shipped on Android in the near future.
Yes
sync-access-handle-all-sync-surface
False
https://bugs.chromium.org/p/chromium/issues/detail?id=1338340
https://github.com/whatwg/fs/pull/53/commits/618b663ebdc0f9842d7db3091baed5f75aa87534
https://chromestatus.com/feature/5149644305203200
This intent message was generated by Chrome Platform Status.
Contact emails
Specification
https://github.com/whatwg/fs/pull/53/commits/618b663ebdc0f9842d7db3091baed5f75aa87534
Summary
Updates the asynchronous methods (`flush()`, `getSize()`, `truncate()`) in `FileSystemSyncAccessHandle` in the File System Access API to synchronous methods. `FileSystemSyncAccessHandle` currently has a mix of sync and async methods, hindering the performance and the usability, especially for applications porting C/C++ to Wasm. This update will bring consistency in the API usage and improve the performance for Wasm-based libraries.
Blink component
TAG review
https://github.com/w3ctag/design-reviews/issues/772
TAG review status
Pending
Risks
Interoperability and Compatibility
Compatibility:
Changing a return type from Promise to value can break, only if Promise methods are directly used rather than `await`. However, we expect minimal breakage due to very low usage (~0.00002% page loads; zero usage queried via HttpArchive).
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPscNz4GPefX650W7y-z2-kDVpwChCWur1UJb2490ySm03jy2A%40mail.gmail.com.
On Thu, Sep 22, 2022 at 8:06 PM 'Daseul Lee' via blink-dev <blin...@chromium.org> wrote:Contact emails
Specification
https://github.com/whatwg/fs/pull/53/commits/618b663ebdc0f9842d7db3091baed5f75aa87534
Summary
Updates the asynchronous methods (`flush()`, `getSize()`, `truncate()`) in `FileSystemSyncAccessHandle` in the File System Access API to synchronous methods. `FileSystemSyncAccessHandle` currently has a mix of sync and async methods, hindering the performance and the usability, especially for applications porting C/C++ to Wasm. This update will bring consistency in the API usage and improve the performance for Wasm-based libraries.
Blink component
TAG review
https://github.com/w3ctag/design-reviews/issues/772
TAG review status
Pending
Risks
Interoperability and Compatibility
Compatibility:
Changing a return type from Promise to value can break, only if Promise methods are directly used rather than `await`. However, we expect minimal breakage due to very low usage (~0.00002% page loads; zero usage queried via HttpArchive).
Do I understand correctly that this usage is a loose upper bound of users of the API, and not necessarily sites that are not using `await`?
Does it include all the APIs that are planned to stop returning Promises?Also, can you link the use counter?
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPscNz4GPefX650W7y-z2-kDVpwChCWur1UJb2490ySm03jy2A%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/165251ea-912f-480d-bc37-1758d5bede6en%40chromium.org.