[css-view-transitions-1][css-view-transitions-2] Soft-freeze view-transitions L1 and merge into L2
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
While view transitions L1 is pretty stable (a minor bug fix/clarification now and then), L2 is getting a bit complex in terms of being a delta spec, with more and more hooks into internal parts of L1.
Proposing that this is the right time to merge L1 into L2, and soft-freeze L1 (meaning, we generally don't change it but can backport if necessary).
/cc @nt1m @emilio @fantasai @vmpstr
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 by reviewing the CSS View Transitions Level 1 and Level 2 editor drafts and the relationship between them. Determine the scope of merging Level 1 into Level 2 and soft-freezing Level 1; the work is done when the specifications reflect that merged structure and freeze policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend, web-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100