Re: [w3ctag/design-reviews] File Handling (#371)

> So, I think this is out of scope of file handlers. What we're trying to build is specifically a way for websites to get the functionality of native apps opening real local files on disk: that is, being able to:

At the same time, I think this might provide the functionality I was talking about for free.

Say, for example, https://calendar.google.com/ uses the File Handling API to say that it supports handing `.ics` files (`text/calendar`) so that a user choosing an ICS file in the OS's file browser will load Google Calendar's ICS importer.  However, then, if a user browsing the web clicks on an ICS file... typically what the browser does in that case is show a dialog that offers to use whatever the OS handler for ICS files is... which in this case is the browser running Google Calendar mediated by this File Handling API.  So maybe it just works. (Or if it doesn't work, maybe Firefox will load Google Calendar in Chrome, and Chrome will load Google Calendar in Firefox, providing both browsers an incentive to do it right!)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/371#issuecomment-594222271