We want to provide a way for application to specify that they are able to handle files with given mime types or extensions and provide OS integration for opening these files.
This clears the path for applications which read and modify files to be built on the web platform. Some examples:
Image Manipulation Tools
Computer Aided Design Applications
Interoperability and Compatibility
Safari: No signals
Web / Framework developers: Seems to be developer interest.
This API will probably be used in conjunction with ServiceWorkers (e.g. to work out what window to open the file in). This introduces the possibility of some overhead when we start the ServiceWorker before we are able to focus a tab/window and open the file.
This API will likely make use of writable files, and service worker launch events, neither of which have shipped.
Developers should be able to make use of this feature immediately. Polyfilling will not be possible, as it requires OS integration.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Eventually, yes. In the short term, we intend to just add Chrome OS support. More platforms will be added over time (though Android WebView will probably never be supported).
Link to entry on the feature dashboard
Requesting approval to ship?
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/0e019fe9-fc55-4912-b9b6-605187041288%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABc02_LS7wEdGX6LQC56DQdjRLzisYFa2ht6CuiHM%2BUHnXT6jg%40mail.gmail.com.
Given that registerContentHandler didn't pan out, do you think it'd be
a good idea to spell out in the explainer why that ultimately failed
and the differences in the new model? Is it that it's only available
to install web apps?
The interop risk here seems like it might be high if it depends on
other APIs which are also new. Are other vendors on board with the
dependencies here, or what is the risk that this is Chrome-only for a
long time after it's shipped?