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

Hi TAG reviewers,

We're getting close to launching File Handling and since it's been a while since this review (and our OT has completed), so we're curious if a new review is warranted. The explainer has been brought up to date with this commit [1]. Here is the spec PR (in review) [2].

The only difference I think might warrant consideration is that the file handles passed to the app now have read/write access. The justification is that:

- the confirmation prompt still exists to prevent accidental usage of the API 
- users have an expectation that the file will be writeable (based on the same flow with a native app) 
- having separate confirmation prompts for read (part of FH API) and write (using File System Access API) creates a very high friction experience for the common "open - edit - save" user journey, and ultimately, the two confirmation prompts look pretty much the same to the user. (This was a particular concern for partners.)

The other recent major change from the user's perspective (although not really part of the API) is to the permission prompt.

- the dialog appears *before* the app window is created, which improves the situation where a user blocks the action, as there's no longer an empty app window hanging around.
- the permission is granted to the app, not the origin, which improves user control in situation where multiple apps share a single origin.

[1] https://github.com/WICG/file-handling/commit/612eb739859687e78cc31e42f55967f76c35f349
[2] https://github.com/w3c/manifest/pull/1005

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

Message ID: <w3ctag/design-reviews/issues/371/1022586011@github.com>