w3c / w3c/csswg-drafts

[css-easing-1] Clarify computed values and serialization

Open
#8,723 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

css-easing-1
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-end and step-start be serialized as themselves rather than as a steps() function?
  • Should the jump-end and end keywords 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-end should compute to start/end or vice versa (unsure which we prefer).
  • the computed value serialization should fall out from that

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.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.