Definitions related to image loading are not precise
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 61
- Forks
- 19
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 1
Description
In 3.7 step 1.2, "fully decoded" should probably be fully decodable
There are also references to "completely available" which may fire earlier than we would like - when the image dimensions are known, rather than when it's fully decoded.
@npm1 - thoughts?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read section 3.7, step 1.2, and the linked HTML definition of “fully decodable” first. Review the specification’s uses of “fully decoded” and “completely available”; done means the terminology and timing expectations are precise and consistent with the referenced HTML behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100