Re: [csswg-drafts] [css-view-transitions-2] Clarifications around `view-transition-group` (#10957)

The CSS Working Group just discussed ``[css-view-transitions-2] Clarifications around `view-transition-group` ``.

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> noamr: we resolved in the VT breakout on many things, but there were some unclear or edge cases<br>
&lt;TabAtkins> noamr: small but related<br>
&lt;TabAtkins> noamr: want to clarify the semantics of VT keywords are tree-scoped<br>
&lt;TabAtkins> noamr: We have keywords like 'nearest'<br>
&lt;khush> q+<br>
&lt;TabAtkins> noamr: Want to clarify they're tree-scoped as well, so 'nearest' can't capture things that couldn't be explicitly named<br>
&lt;TabAtkins> noamr: the other one is what happens in a mismatch, the old doc says "VT group X" the new says "VT group Y"<br>
&lt;TabAtkins> noamr: It appears there's no good solution<br>
&lt;TabAtkins> noamr: want to just be consistent with v-t-class and such. the semantic there is "last capture wins", so it'll usually take the VT group from the new doc state, unless it's an exit transition<br>
&lt;TabAtkins> noamr: third thing, not clear when using 'nearest' or a name that it also contains its descendants<br>
&lt;TabAtkins> noamr: if not, it's impossible for an element to contain and be contained at the same time<br>
&lt;TabAtkins> noamr: our proposal is to have it also contains its descendants by default<br>
&lt;TabAtkins> noamr: you can always escape by normal<br>
&lt;khush> q?<br>
&lt;TabAtkins> fantasai: it seems like this is three issues all filed separately, can we take them one by one?<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10957#issuecomment-2377940173 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 26 September 2024 21:07:49 UTC