Refactor read operation algorithm

Open
#208 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
html
Domain
documentation, web-dev

Research direction

Start with the linked File API read operation algorithm, then read the Streams specification's readablestreamdefaultreader-read-all-bytes definition and Fetch's body-fully-read example. Compare their handling of the read operation and event-loop wording; done means the File API algorithm is simplified consistently with those references.

Written by the indexing model from the issue text.

Description

The read operation algorithm uses the inappropriate "in parallel" concept(see event-loop-for-spec-authors), and instead of rewording this, it could be simplified through the use ofreadablestreamdefaultreader-read-all-bytes.

Here is an example from Fetch.

Dominant language
HTML
Stars
118
Forks
52
Avg merge
9d 16h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from w3c/FileAPI

All issues in w3c/FileAPI

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.