What should the ProgressEvent attributes be in the case of an error/abort?

Open
#14 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
html
Domain
api

Research direction

Review the ProgressEvent attribute definitions in the File API specification and trace how error and abort cases are described. Resolve whether length, total, and current values are computable or must be false and zero, then document the agreed behavior in the relevant specification text.

Written by the indexing model from the issue text.

Description

normative change

Is the length computable, is there a total and a current length, or are the values all supposed to be false and zero?

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 Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.