- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 17 Dec 2025 17:25:16 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-animations-2][web-animation-2] Rename exit range to active range`, and agreed to the following: * `RESOLVED: Use timeline-trigger-entry-range and timeline-trigger-active-range` <details><summary>The full IRC log of that discussion</summary> <fantasai> flackr: animation-trigger has two ranges. one is when you get into that range, you activate the trigger (plays animation or whatever)<br> <fantasai> flackr: and while trigger is active, can have a different range which can be larger<br> <fantasai> flackr: currently called exit range, proposing to call it the active range<br> <fantasai> flackr: mostly agreed on this, other than what to call the first range<br> <fantasai> flackr: two questions: 1) does it need to have a name?<br> <fantasai> flackr: in spec describe it as entry range or whatever<br> <fantasai> flackr: or 2) have an explicit name for this like "enter" or "entry" or "activation"<br> <bramus> q+<br> <fantasai> flackr: I don't think I'd oppose any of the proposals, so maybe just straw poll?<br> <fantasai> flackr: so questions are do we give that property a distinct name or do we just leave out the extra description<br> <astearns> ack bramus<br> <fantasai> flackr: and if naming it, what are these called<br> <bramus> https://codepen.io/bramus/full/bNpzXrV<br> <TabAtkins> Small sample, but the emoji reactions lean heavily toward `trigger-range` and `trigger-active-range` for the property names<br> <fantasai> [bramus shows a demo]<br> <fantasai> activation range is the middle half of the screen<br> <fantasai> but the active range is until the item starts to leave the viewport (a wider rane)<br> <fantasai> s/rane/range/<br> <fantasai> flackr: The active range is an analogy of "while hovered, you have to move your mouse to [missed]"<br> <fantasai> flackr: whie active, you have a larger range to no longer be active<br> <Rossen3> q?<br> <ydaniv> q+<br> <astearns> ack fantasai<br> <kbabbitt> scribe+ kbabbitt<br> <kbabbitt> fantasai: talking about 2 different properties, one trigger [missed] and one trigger active range<br> <kbabbitt> ... maybe we want a shorthand now or maybe in the future, don't want one longhand to be a shorter version of another<br> <kbabbitt> ... active and activation are too close together and that would be confusing<br> <kbabbitt> ... between enter and entry I think entry is a bit more natural<br> <bramus> q+<br> <astearns> ack ydaniv<br> <fantasai> s/[missed]/entry range/<br> <fantasai> ... so I would pick (e)<br> <fantasai> ydaniv: I agree with fantasai<br> <fantasai> ydaniv: Also I'm concerned that "active" also sounds like an entry.<br> <fantasai> ydaniv: Also I'm concerned by the demo, I think we require the active range to be larger than the entry range<br> <fantasai> bramus: it was larger<br> <fantasai> flackr: already required per spec<br> <astearns> ack bramus<br> <fantasai> bramus: Entry might also confuse authors because you're specifying a range from a view timeline<br> <fantasai> bramus: so you could say, oh, entry range is entry 100% and ... then you have "entry" twice, one is from the timeline range<br> <fantasai> bramus: so that can be confusing when talking about it<br> <TabAtkins> I'm fine with a poll<br> <fantasai> flackr: Having presented both arguments, would everyone be happy with a poll? I just want to choose a property name<br> <fantasai> flackr: I think we're polling between entry and activation. I think fantasai presented a good argument for not having nothing<br> <astearns> ack fantasai<br> <kbabbitt> fantasai: one point, what if you confuse active and entry range ... in the past we were thinking of entry range as primary thing you set<br> <kbabbitt> ... exit range is derivative, might want to set differently<br> <kbabbitt> ... primary thing author wants to set is active range, don't want to set an entry rannge, then entry range is a narrowing of the primary thing they're setting<br> <kbabbitt> ... rather than having exit range be an extension of primary range<br> <ydaniv> q+<br> <kbabbitt> ... in that case I don't think the pairing is that confusing<br> <astearns> ack ydaniv<br> <flackr> +1 that sounds like a good way to think about it<br> <fantasai> ydaniv: exit or active range, behaves more like a hold range or maintain range, so I think the naming should go along this line of terminology<br> <fantasai> ydaniv: so something like "active range" and "hold range", then each one is more clear<br> <miriam> those sound the same to me<br> <fantasai> astearns: Not sure I get "hold" as the term.<br> <fantasai> astearns: I think we should be open to refining the names if we find something that works better<br> <miriam> +1 fantasai's proposal<br> <fantasai> flackr: I'm happy with what fantasai proposed. Just want something we can all agree to.<br> <kbabbitt> +1 to having a term in both properties<br> <fantasai> astearns: So consensus for adding term to both properties to distinguish<br> <fantasai> astearns: Seems like (c) and (e) are the top choices<br> <fantasai> astearns: Should we have a poll between those two?<br> <fantasai> c) timeline-trigger-activation-range and timeline-trigger-active-range<br> <fantasai> e) timeline-trigger-entry-range and timeline-trigger-active-range<br> <TabAtkins> E<br> <bramus> C<br> <fantasai> e<br> <kbabbitt> E<br> <flackr> e<br> <JoshT> E<br> <astearns> e<br> <DavidA> e<br> <jfkthame> c<br> <miriam> e<br> <ydaniv> E<br> <jbreiland> E<br> <vmpstr> c<br> <Rossen3> e<br> <dbaron> e<br> <jensimmons> e<br> <emeyer> e<br> <fantasai> astearns: So we'll go with (e) for now<br> <kbabbitt> fantasai: since bramus was taking about confusion with entry keyword, we could use the word start<br> <kbabbitt> ... timeline-trigger-start-range and timeline-trigger-active-range<br> <kbabbitt> ... either of those are fine with me, just don't like activation<br> <fantasai> astearns: Let's go with this, and we can continue bikeshedding later<br> <fantasai> astearns: any objections?<br> <fantasai> RESOLVED: Use timeline-trigger-entry-range and timeline-trigger-active-range<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13174#issuecomment-3666401670 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 December 2025 17:25:17 UTC