Since this is an incremental addition to the existing FSA API, my guess is that the positions there sufficient here:
Gecko: https://mozilla.github.io/standards-positions/#native-file-system Webkit: https://lists.webkit.org/pipermail/webkit-dev/2020-August/031362.html These two engines give a Negative signal. I would not expect they would comment further on this incremental addition. On Wed, Jun 15, 2022 at 8:06 AM 'Austin Sullivan' via blink-dev < blink-dev@chromium.org> wrote: > No, I did not realize this was required? showDirectoryPicker() is > currently only implemented for Chromium browsers > > On Wed, Jun 15, 2022 at 7:55 AM Yoav Weiss <yoavwe...@chromium.org> wrote: > >> >> >> On Monday, June 13, 2022 at 1:58:43 PM UTC+2 Austin Sullivan wrote: >> >>> Contact emailsasu...@chromium.org >>> >>> ExplainerNone >>> >>> Specificationhttps://github.com/WICG/file-system-access/pull/300 >>> >>> Summary >>> >>> Allow returning a directory with both read and write permissions in a >>> single prompt for the File System Access API. Currently >>> showDirectoryPicker() always returns a read-only directory (after showing a >>> read access prompt), requiring a second permission prompt to get write >>> access. This double-prompt is a poor user experience and contributes to >>> confusion and permission fatigue among users. >>> >>> >>> Adds an optional "mode" option to DirectoryPickerOptions which can be >>> specified as "read" or "readwrite". >>> >>> >>> Blink componentBlink>Storage>FileSystem >>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EStorage%3EFileSystem> >>> >>> TAG reviewWe did not seek a TAG review given the small scope of this >>> feature. This launch does not add any new capabilities, but merely provides >>> the browser with enough information to combine two permission prompts into >>> one. >>> >> We have filed TAG design review requests for incremental additions to the FSA API (examples: 1 <https://github.com/w3ctag/design-reviews/issues/600>, 2 <https://github.com/w3ctag/design-reviews/issues/598>, 3 <https://github.com/w3ctag/design-reviews/issues/580>) - I think it's worth doing here as well, although I expect support since it's following existing patterns (using an enum value in an options dictionary, with a reasonable/safe default). > >>> TAG review statusN/A >>> >>> Risks >>> >>> >>> Interoperability and Compatibility >>> >>> >>> >>> *Gecko*: No signal >>> >>> *WebKit*: No signal >>> >> >> Have you asked for signals? https://bit.ly/blink-signals >> >> >>> >>> *Web developers*: Strongly positive ( >>> https://github.com/WICG/file-system-access/issues/89) >>> >>> *Other signals*: >>> >>> WebView application risks >>> >>> Does this intent deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>> No >>> >>> >>> >>> Debuggability >>> >>> N/A >>> >>> >>> Will this feature be supported on all six Blink platforms (Windows, Mac, >>> Linux, Chrome OS, Android, and Android WebView)?No - The File System >>> Access API is not supported on Android >>> >>> Is this feature fully tested by web-platform-tests >>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>> ?No >>> >>> Flag name >>> >>> Requires code in //chrome?False >>> >>> Tracking bughttps://crbug.com/1115632 >>> >>> Launch bughttps://crbug.com/1213159 >>> >>> Estimated milestones >>> >>> 105 >>> >>> >>> Anticipated spec changes >>> >>> Open questions about a feature may be a source of future web compat or >>> interop issues. Please list open issues (e.g. links to known github issues >>> in the project for the feature specification) whose resolution may >>> introduce web compat/interop risk (e.g., changing to naming or structure of >>> the API in a non-backward-compatible way). >>> >>> >>> Link to entry on the Chrome Platform Status >>> https://chromestatus.com/feature/6383970247770112 >>> >>> This intent message was generated by Chrome Platform Status >>> <https://chromestatus.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+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADs-7rEsYumZp%3Dd9VuzMixOq5xB7kD0HxrQ2QwYvLM_K%2B7LaLw%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADs-7rEsYumZp%3Dd9VuzMixOq5xB7kD0HxrQ2QwYvLM_K%2B7LaLw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAD649j5j_1PREcHpQVy3YE8MUMxKEe%2B9rNNUVgX271D_WozqSw%40mail.gmail.com.
