[css-view-transitions-2] [scoped] Force tag containment for active transitions
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
On #13123 it was resolved to add the UA stylesheet rule :active-view-transition { view-transition-scope: all }, presumably with the intention of achieving the behavior described in the explainer as follows:
"If the scope does not have view-transition-scope: all, it acquires the behavior of view-transition-scope: all while the transition is running."
However, the proposed UA stylesheet rule would still allow the developer to override the behavior by setting view-transition-scope: none explicitly. We should decide between the following options:
- Allow the developer to override the behavior.
- Add
!importantto the UA stylesheet rule. - Specify the behavior without relying on the UA stylesheet.
I think Option 3 is closest to what Chrome is doing today since we implemented this in StyleAdjuster.
@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 with the scoped-transitions explainer section on tag containment and the resolution in issue #13123. Review the three listed options, including the current StyleAdjuster behavior mentioned here, and determine which behavior should be specified for active transitions. Done means the working group agrees on one option and the specification states that behavior unambiguously.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100