[css-transitions-2] transition-composition
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
Blending transitions using a subtract operation https://github.com/w3c/csswg-drafts/issues/10646 and CompositeOperation: blend https://github.com/w3c/csswg-drafts/issues/10927.
Keywords replace or blend, default is replace.
Would bypass css-transitions-2 section 3.1 “Faster reversing” and allow multiple transitions to run simultaneously.
With blend, any existing transtions would not get removed when starting a new transition.
After switching from replace to blend, an existing transition would not get removed when starting a new transition.
After switching from blend to replace, all existing transitions would get removed when starting a new transition.
No interest has been shown but I’m implementing proof-of-concept anyway and need something to point to.
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 linked CSSWG issues 10646 and 10927 and CSS Transitions 2 section 3.1, “Faster reversing,” to understand the proposed composition behavior. Compare the replace and blend cases described here; done would require a resolved specification direction and corresponding draft changes, but no implementation file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100