- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Aug 2024 14:15:29 +0000
- To: public-css-archive@w3.org
Summary from internal sync, we concluded that we'd defer the no-content-change to later. There are 3 options on the table: 1. Change the capture mode by default. Capture box-decorations and tree effects as style, and cross-fade only the contents. This asserts that morphing rather than cross-fading is mostly superior. However, it might make some of today's view transition animate differently, e.g. a different background image between the old and new state would animate discretely. 2. Make this an opt-in with a new property (`view-transition-style` or `view-transition-capture-mode`), one option is like today, and the other one captures box-decorations & tree effects as style. 3. Add a new property, but give it an `auto` value. The capture-mode will be the same as today, unless the element is a containing group (has nested group descendants). This asserts that flat capturing doesn't make sense at all for a nested group tree, and it allows us to change that without breaking existing content. Note that (1) would become much stronger once we can automatically animate backgrounds/border-image/masks/clip-path by creating an automatic cross-fade. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10585#issuecomment-2298972930 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 August 2024 14:15:30 UTC