[w3ctag/design-reviews] Support seeking past the end of a file in the File System Access API (#600)

HIQaH! QaH! TAG!

I'm requesting a TAG review of seeking past the end of a file in the File System Access API.

Rather than rejecting when trying to write past the end of a file this
changes the File System Access spec to require extending a file with 0 bytes
instead.

  - Explainer¹ (minimally containing user needs and example code): https://github.com/WICG/file-system-access/pull/266

  - Specification URL: https://pr-preview.s3.amazonaws.com/WICG/file-system-access/266/65e990d...882219a.html#write-a-chunk

  - Tests: tests in https://wpt.fyi/results/native-file-system will be updated
  - Security and Privacy self-review²: https://github.com/WICG/file-system-access/blob/main/security-privacy-questionnaire.md (no changes for this API change)
  - GitHub repo (if you prefer feedback filed there): https://github.com/WICG/file-system-access/

  - Primary contacts (and their relationship to the specification):
      - Marijn Kruisselbrink (@mkruisselbrink), Google, Spec Editor
  - Organization(s)/project(s) driving the specification: Google/Chromiuim
  - Key pieces of existing multi-stakeholder review or discussion of this specification: https://github.com/WICG/file-system-access/issues/262

  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): 

Further details:

  - [X] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)
  - Relevant time constraints or deadlines: We hope to ship this change in Chrome 90, branching at the end of February
  - The group where the work on this specification is currently being done: WICG
  - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): unknown
  - Major unresolved issues with or opposition to this specification:
  - This work is being funded by: Google

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  💬 leave review feedback as a **comment in this issue** and @-notify @mkruisselbrink


-- 
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/600