[css-easing-1] Clarify computed values and serialization
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 24
Description
The CSS Easing spec has a section on serialization, however this section doesn't distinguish between specified and computed values (and seems to be defining the computed value serialization). Should there be any differences between these two? E.g.
- Should specified values of
step-endandstep-startbe serialized as themselves rather than as asteps()function? - Should the
jump-endandendkeywords be kept as distinct specified values?
Relatedly, the spec seems a bit confused about the computed/serialized values for start/end/jump-start/jump-end: the serializations of the “end” values are collapsed to a single serialization, but not the “start” values. I think
jump-start/jump-endshould compute tostart/endor vice versa (unsure which we prefer).- the computed value serialization should fall out from that
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 with the CSS Easing Level 1 serialization section linked in the issue. Compare its treatment of specified values, computed values, and serialization for step-start, step-end, start, end, jump-start, and jump-end. Done means the specification clearly distinguishes these stages and resolves the keyword relationships and serialization behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100