Re: [csswg-drafts] [css-view-transitions-1] Using pseudo-elements vs shadow DOM syntax (#7928)

The CSS Working Group just discussed `View Transitions: pseudo vs shadow`, and agreed to the following:

* `RESOLVED: Take khushal's proposal to use pseudo-element syntax for view transitions`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> Topic: View Transitions: pseudo vs shadow<br>
&lt;TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/7928<br>
&lt;khush> Proposed Resolution: Use pseudo-element syntax for UA generated DOM in ViewTransitions.<br>
&lt;TabAtkins> khush: This came from a tpac discussion<br>
&lt;TabAtkins> khush: For the exact targeting syntax for the transition generated elements<br>
&lt;TabAtkins> khush: One option is tightly coupled to how pseudo-elements work<br>
&lt;TabAtkins> khush: Another is using ::part(), which tightly couples us to a shadow dom ipml<br>
&lt;TabAtkins> khush: Some are a direct CSS function on the html element<br>
&lt;TabAtkins> khush: would be agnostic for how it's used, pseudo or shadow<br>
&lt;TabAtkins> khush: So this issue is mainly to resolve on if we're okay picking a syntax that is tightly coupled with one or the other, or want a generic one?<br>
&lt;TabAtkins> khush: I propose pseudo-element syntax, primarily becuase a future extension is scoped transitions where these can exist on any element<br>
&lt;TabAtkins> khush: We can say shadow dom is usable on the root right now because authors can't put a shadow on root, but other elements *can* have shadow from authors, so that would complicate things if we used a shadow-based syntax<br>
&lt;astearns> ack fantasai<br>
&lt;TabAtkins> fantasai: I support this proposal, i think it makes sense to pick a sytnax that allows flexibility, and i think pseudo-element can do that<br>
&lt;TabAtkins> fantasai: also feels the most familiar to css authors who aren't as much on the programmatic side, so this works fo rme<br>
&lt;emilio> wfm, though I still think the initial proposal had a _lot_ of pseudos...<br>
&lt;TabAtkins> smfr: I think the concern was that the pseudo-element was unwielding and not user-friendly?<br>
&lt;TabAtkins> khush: A later option is to make that easier, smaller names<br>
&lt;TabAtkins> astearns: Any objections to pseudo-element syntax?<br>
&lt;TabAtkins> RESOLVED: Take khushal's proposal to use pseudo-element syntax for view transitions<br>
</details>


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


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

Received on Wednesday, 26 October 2022 16:20:17 UTC