Advise on shipping existing API on a new platform

[Ajay Rahatekar]

Hello API Owners,

The Chrome Storage team is planning on shipping the File System Access API in Android and Android Webview. The API had previously shipped on WIndows, Mac, Linux and ChromeOS. The scope of shipping spans 2 intents, https://groups.google.com/a/chromium.org/g/blink-dev/c/9Fcpl2KVfbk and  https://groups.google.com/a/chromium.org/g/blink-dev/c/OR0poFdzEpo

Everything in  https://github.com/whatwg/fs/ will be exposed on Android and Android Webview. What will not be shipping is show*Picker methods.

Can you please advise if we can ping one or both original intents to inform about this shipping or would a new I2S/PSA be more appropriate in this case?

Thanks in advance.

--

Ajay Rahatekar | Technical Program Manager | ajayra...@google.com | 650-797-1279

[Chris Harrelson]

Hi,

I think it makes sense to send a new intent with a new chromestatus entry, but reuse the existing documentation (e.g. link to the previous reviews for most details), TAG review and so on. That way the new parts will clearly highlight the milestone when it shipped on the new platforms, so developers will be well-informed.

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAHB%2BDAikmmWso%3DD_%3DHknmRuHXX_tCaCBoakPecLeRwEziEsejA%40mail.gmail.com.

[Ajay Rahatekar]

Ty very much for the guidance.

-Ajay

[Thomas Steiner]

This is great news, but sad that the `show*Picker()` methods won't be included. The related bug https://bugs.chromium.org/p/chromium/issues/detail?id=1011535 has 74 stars, so it's definitely something where there's developer demand for. Is there a potential future where we ship the picker methods as well?

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/CAHB%2BDAiXYqM2AaPR3u2x4wrPz3CjxXSAy%2BWsRayn3yow52pJWw%40mail.gmail.com.

--

Thomas Steiner, PhD—Developer Relations Engineer (https://blog.tomayac.com, https://twitter.com/tomayac)

Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany
Geschäftsführer: Paul Manicle, Liana Sebastian
Registergericht und -nummer: Hamburg, HRB 86891

----- BEGIN PGP SIGNATURE -----

Version: GnuPG v2.3.4 (GNU/Linux)

iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.hTtPs://xKcd.cOm/1181/

----- END PGP SIGNATURE -----

[Austin Sullivan]

As things currently stand, there are a lot of technical challenges around exposing the show*Picker() methods (Android's inconsistent support for directories, using content URIs, playing nicely with a much more restrictive OS-level file system permissioning model, etc...) and the value prop is less clear. Some of the use cases mentioned in https://crbug.com/1011535 will be satisfied by this launch, along with many others, such as supporting SQLite-over-WASM-over-OPFS as a replacement for WebSQL.

My hope is that as the Android ecosystem evolves, the need for the show*Picker() methods will become more pressing and we can justify tackling all those challenges mentioned above. But for now let's not let perfect be the enemy of good :)