Re: [csswg-drafts] [css-view-transition-2] Should non-default `view-transition-group` act like `contain`? (#10780)

The CSS Working Group just discussed ``[css-view-transition-2] Should non-default `view-transition-group` act like `contain`?``, and agreed to the following:

* `RESOLVED: all values other than 'normal' implicitly contain`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> astearns: elika was thinking this was alreayd resolved<br>
&lt;TabAtkins> fantasai: when we resolved to adopt the v-t-group, there was a proposal that covered this case, which describes the features exactly as specified here<br>
&lt;TabAtkins> noamr: I thought so, but figured it wasn't clear enough<br>
&lt;TabAtkins> fantasai: i'll drop a link to the proposal we adopted<br>
&lt;khush> q+<br>
&lt;TabAtkins> fantasai: the values in the proposal we resolved defined the values in the way noam is discussing here<br>
&lt;TabAtkins> noamr: yeah this detail was in the conversation, but not explicitly in the resolution<br>
&lt;astearns> ack khush<br>
&lt;TabAtkins> khush: the use-case that was raised in the issue, it wasn't clear how we resolved applied to it, let me understand<br>
&lt;TabAtkins> khush: right now v-t-group does two things, it parents to something, and says your subtree is parented to you<br>
&lt;vmpstr> q+<br>
&lt;fantasai> the proposal as expressed in the issue<br>
&lt;TabAtkins> khush: you can't say both at the same time, so the proposal is to combine them and have them imply both?<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/10334#issuecomment-2165649094<br>
&lt;TabAtkins> noamr: option 2, nearest and custom-ident implicitly mean contain too<br>
&lt;vmpstr> q-<br>
&lt;vmpstr> +1<br>
&lt;TabAtkins> fantasai: yes, that was in the description of the values<br>
&lt;TabAtkins> khush: i'm not a fan of it; i don't see why the nearest keyword has to implly it, rather than just allowing both keywords to be specified together if you want that<br>
&lt;astearns> q+ fantasai<br>
&lt;TabAtkins> khush: i think there are cases where you'd use nearest without implying you want your subtree too<br>
&lt;vmpstr> q+<br>
&lt;astearns> ack fantasai<br>
&lt;TabAtkins> fantasai: you could, but I think it's more likely you want capture.<br>
&lt;vmpstr> q-<br>
&lt;vmpstr> +1<br>
&lt;noamr> +1<br>
&lt;TabAtkins> fantasai: if you want to escape the capture you can use a name on the descendant; it doesn't *trap* them, it just contains by default<br>
&lt;flackr> +1<br>
&lt;TabAtkins> khush: ?<br>
&lt;TabAtkins> fantasai: if you come back with use-cases and decide that by default you don't want to capture, we could revisit, i just think by default it's the right behavior<br>
&lt;TabAtkins> khush: the thing that wasn't clear to me is that you could use a custom-ident on a descendant to escape, ok<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/10334#issuecomment-2165649094<br>
&lt;noamr> nearest and &lt;custom-ident> implicitly also mean contain<br>
&lt;fantasai> PROPOSED: all values other than normal implicitly contain<br>
&lt;TabAtkins> astearns: any objections to this proposal?<br>
&lt;TabAtkins> RESOLVED: all values other than 'normal' implicitly contain<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10780#issuecomment-2377976347 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:32:19 UTC