- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Aug 2024 09:51:52 +0000
- To: public-css-archive@w3.org
Copying from #9406 for the purpose of the CSSWG breakout. There are 3 use-cases that can benefit from changing the way we capture in certain scenarios: 1. Groups that have nested descendant with `view-transition-group`: they need to capture opacity, filters, 3D, and sometimes borders, backgrounds & shadows in order to display in a way that doesn't look buggy. 2. Sometimes, regardless of nesting, animating border and `box-shadow` can have a nicer effect than flattening them into the snapshot. 3. When an element comes from far away from the viewport, or if we're moving elements around without changing their content, we could benefit from an optimization of not capturing the old content into a snapshot at all. I see this as 3 styles of transition, with an `auto` that generates default behavior: - Crossfade between the old and new element snapshots, like today (`crossfade`?) - Crossfade the contents and animate the box decorations individually (`morph`?) - Display the new content only and morph only the box decorations (`shapeshift`?) `auto` could mean: - Use `morph` when the group contains other groups - Use `shapeshift` when animating from very far from the viewport (100vw, 100vh?) - Otherwise, use `crossfade` -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10585#issuecomment-2296151653 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 August 2024 09:51:53 UTC