Re: [csswg-drafts] [css-view-transitions-2] Creating 'classes' of transition groups (#8319)

The CSS Working Group just discussed `[css-view-transitions-2] Creating 'classes' of transition groups`, and agreed to the following:

* `RESOLVED:  Go with option 1 for the syntax in creating view-transition-class`

<details><summary>The full IRC log of that discussion</summary>
&lt;frances_> Alan: next issue is 8319 on classes of transition groups<br>
&lt;frances_> vladimir: have view-transition-name, can be repetitive, introduce view-transition-class to apply to multiple elements, and prevent repeating. Separate list of custom items to name the classes. For the selection, the view-transition pseudo-element can select the class, few options listed in the issue on how to select it such as dots in brackets, dots outside the brackets. No strong preference.<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/8319#issuecomment-1852207709<br>
&lt;frances_> vladimir: the semantics will be the last capture wins. If exit transition, the old capture will win, if an entry transition, class overrides old element.<br>
&lt;frances_> Alan: any objections?<br>
&lt;TabAtkins> q+<br>
&lt;frances_> Alan: any opinions?<br>
&lt;astearns> ack TabAtkins<br>
&lt;khush> q+<br>
&lt;frances_> tab: use case for class sounds great, good idea, for syntax lean towards class selector syntax into pseudo elements, least clumsy, names and classes, syntaxically distinguished<br>
&lt;frances_> Alan: which option is it?<br>
&lt;frances_> vladimir: option 1?<br>
&lt;frances_> Vladimir: option 1.<br>
&lt;astearns> ack khush<br>
&lt;TabAtkins> ::view-transition-group(*.class1.class2)<br>
&lt;frances_> khush: second what tab said, like option 2, if dark-class is a prefix, then will be a subtle difference in class declaration<br>
&lt;frances_> tab: true for hover pseudo class in dom class, for css selector syntax, doesn't allow it, prefer option 1<br>
&lt;TabAtkins> :hover::before and ::before:hover are currently both valid and mean different things in exactly that way<br>
&lt;vmpstr> s/dark-class/dot class/<br>
&lt;khush> ^ I +1'd option 1. :)<br>
&lt;astearns> ack florian<br>
&lt;astearns> ack fantasai<br>
&lt;frances_> fantasai: comment from someone in thread to introduce shorthand for view-transition-name  and view-transition-class, can be reflected in both. Possibly between 1 and 4.<br>
&lt;frances_> Alan: any other opinions?<br>
&lt;fantasai> s/can be reflected in/can choose a syntax that works for/<br>
&lt;fantasai> s/Possibly between/That would likely be option 4. But I like both/<br>
&lt;frances_> Alan: Possibly resolve on option 1<br>
&lt;frances_> vladimir: yes<br>
&lt;frances_> PROPOSAL: Go with option 1 for the syntax in creating view-transition-class<br>
&lt;frances_> Alan: any objections?<br>
&lt;frances_> RESOLVED:  Go with option 1 for the syntax in creating view-transition-class<br>
</details>


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


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

Received on Thursday, 4 January 2024 00:38:48 UTC