[css-cascade] Instruction in example 11 is confusing
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
Spec link: https://drafts.csswg.org/css-cascade/#computed
In the Computed Values section, the theme of Example 11 is “Computing a relative value generally absolutizes it”. The example then ends with the sentence “See examples (f), (g) and (h) in the table below.”
However, only example (f) is an example of this theme. Why does Example 11 mention examples (g) and (h) when nothing happens to their values between the Specified value and Computed value steps? These two examples are examples for what is mentioned in the subsequent Used Values section, where it says that some values are absolutized late because knowledge about the layout is needed.
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
Start at the CSS Cascade specification's Computed Values section and inspect Example 11, the referenced examples (f), (g), and (h), and the following Used Values section. Confirm which examples match each section's explanation, then update the confusing instruction so the references are accurate and verify the surrounding text remains consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100