- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Oct 2022 23:31:12 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-shared-element-transitions-1] Renaming and brevity`, and agreed to the following: * `RESOLVED: Prop: Use css-view-transitions as the shortname` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-shared-element-transitions-1] Renaming and brevity<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/7788<br> <dael> vmpstr: I can intro. We want to rename structure to something more meaningful<br> <dael> vmpstr: I would hope can resolve on feature name so can move to FPWD with a URL that's fixed<br> <dael> vmpstr: JakeA proposed view-transition prefix to most things.<br> <dael> vmpstr: Has been activity today discussing details<br> <dael> astearns: Note we can pick a fixed URL and then change syntax. We've done it before. Shouldn't look at shurt URL as unchangable thing.<br> <dael> fantasai: But shared-element-transitions is not the name we want. Do we use view-transitions or css-view-transitions as the URL short name?<br> <khush> +1 for css-view-transitions<br> <dael> florian: Seems reasonable. might want ot change later, but not clear we will.<br> <dael> astearns: Anyone argue against view-transitions?<br> <dael> astearns: Could resolve on css-view-transitions as the short spec name. Can also resolve to change all draft syntax.<br> <TabAtkins> Find with the shortname. Still not particularly happy with the syntax options, yeah<br> <dael> fantasai: Can we do shortname first before we dive to everything else?<br> <dael> astearns: Prop: Use css-view-transitions as the shortname<br> <dael> astearns: Obj?<br> <dael> RESOLVED: Prop: Use css-view-transitions as the shortname<br> <dael> khush: Limit discussion to spec name or also touch on names for pseudo elements? Got a good bunch of options there<br> <dael> astearns: Are you looking to have the discussion on call or continue on issue when there has been a little more async discussion?<br> <dael> vmpstr: If we can timebox discussion? Want a sense of uncertainty. I think JakeA prop names are pretty reasonable. I feel like close to resolution<br> <dael> astearns: Let's spend 10 min<br> <vmpstr> https://github.com/w3c/csswg-drafts/issues/7788#issuecomment-1266772511<br> <dael> vmpstr: In Jake's prop ^<br> <dael> vmpstr: All the pseudo elements have view-transition prefix. The property to tag elements with an id is view-transition-name. Pseudos are view-transition-root. Images old and new are subpseudo elements.<br> <TabAtkins> I prefer -images fwiw. The "set" doesn't mean anything afaict<br> <dael> vmpstr: fantasai prop view-transition-set whic makes sense. Also prop to drop root from view-transition-root but that got pushback<br> <dael> astearns: images vs set. Let's discuss<br> <dael> astearns: fantasai can you say why good to change to set?<br> <khush> i'm ok with set. it's smaller. :)<br> <dael> fantasai: It's kind represent 2 images that correspond. It's not a selector that represents each image but represents the set that correspond. Captures it's a container<br> <TabAtkins> q+<br> <dael> astearns: If this is just [missed]. If you can duplicate on old and new and get same result why set?<br> <dael> fantasai: Theres a wrapper for ar eason. If we were being really verbose with image-wrapper we could, but I think I prefer succinct. I like using transition-set on the wraper for 2 images<br> <astearns> ack TabAtkins<br> <dael> vmpstr: It's (image) also singular which makes it weird so set is good<br> <dael> TabAtkins: I like images, the plural makes it clear that it's a set. I find set ot be so content-less I have no clue what it means. This structure can be various levels. Don't know why call one a set. I vote images<br> <vmpstr> we also discussed -image-group<br> <dael> fantasai: Other thing about images is we're getting into, I don't know, the fact that it is an image we should knwo that but what we're representing is a snapshot of older and newer version<br> <dael> fantasai: Feels different than an image that is a replaced element<br> <dael> TabAtkins: The fact that it's an image in browser is important<br> <dael> fantasai: Images pseudo-element is not an image, it's a wrapper around 2. Since old and new doesn't have work 'image' having 'image' in wrapper is confusing<br> <dael> astearns: Agree set is vague and images isn't great since it's a plural. Can someone describe what this is used for?<br> <dael> vmpstr: It's a wrapper that sets up isolation for blending of 2 images. Not a replaced element, but container of 2 images being blended together.<br> <dael> astearns: What are you going to use this pseudo element for?<br> <dael> vmpstr: Not sure I understand. The opacity and blend modes of images will interact in it without effecting other things b/c it's isolated<br> <dael> fantasai: I think astearns is asking how an author is likely to use this pseudo element<br> <iank_> its similar to various cross-fade effects<br> <dael> vmpstr: I see. I don't think there's a particularly good guidance on how to use. Typically dev wants to customize container above this, the parent of wrapper, or the opacity blend of images.<br> <dael> vmpstr: Are some use cases where dev would want to shift container up or down. It moves left to right and container rises from below<br> <iank_> effect-group?<br> <dael> khush: Saw a demo where someone added a small animation to give a pop effect. Not what we anticipated for usage. We did it for cross fade, but that's a way we've seen devs using it.<br> <dael> astearns: Given this is something that we don't have explicit use cases but we know people will use it. not crucial, though. Could go a longer name like view-transition-effect-group or -image-set<br> <dael> fantasai: If you're going for long view-transition-old-new-set. I think it's good to not use image b/c not really an image<br> <TabAtkins> (it is really an image)<br> <fantasai> sorry, I meant conceptually<br> <fantasai> it is implemented as an image<br> <TabAtkins> I mean conceptually too<br> <dael> khush: one of the earlier sugegstions was view-transition-group. Is that a good compromise? Maybe view is better than set.<br> <dael> astearns: TabAtkins bjeciton to group?<br> <dael> TabAtkins: It's jsut as generic and non-meaninful. If it's not high use I would say make it longer with a name for its purpose.<br> <dael> TabAtkins: Where we expect style have shorter names like old new<br> <dael> astearns: I suggest we take this back to the issue. Let's continue with this open and come back after a bit more discussion.<br> <dael> astearns: I was going to suggest breaking it out, but there's good discussion so continue there<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7788#issuecomment-1269104296 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 October 2022 23:31:14 UTC