[css-view-transitions-2] scoped VT: we should apply content-visibility: hidden for the duration of capture
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
When running a scoped view transition, we need to effectively pause rendering for an element so that it doesn't partially update (the callback is async).
When doing this, the size of the element may change so we have to gutter or overflow the pixels we're displaying here. In order to minimize this, and possibly improve performance, we should apply content-visibility: hidden and contain-intrinsic-size: auto to this element while the capture is happening. We can do this automatically.
@skobes-chromium @chrishtr
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 reading the scoped view transition and capture behavior described in the CSS View Transitions 2 context. Work out how the capture duration should apply content-visibility: hidden and contain-intrinsic-size: auto to the element, including size changes during the asynchronous callback. Done means the behavior is specified consistently and the captured pixels are not partially updated or unnecessarily exposed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100