- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Mar 2023 15:38:12 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[scroll-animations-1] Allow optional `<percentage>` in `animation-range-*` ``, and agreed to the following: * `RESOLVED: Make <percentage> optional in animation-range-start/end, defaulting to 0%/100%` * `RESOLVED: When specifying "animation-range: foo X%", set the -range-end to "foo 100%" (staying in same phase, just setting to end)` <details><summary>The full IRC log of that discussion</summary> <fantasai> -> https://github.com/w3c/csswg-drafts/issues/8438#issuecomment-1464672747<br> <TabAtkins> fantasai: there was discussion about %s in teh syntax of animation-range<br> <TabAtkins> fantasai: Can specify the shorthand to a name, but the longhands currently require a %<br> <TabAtkins> fantasai: One proposal is to make that optional - if omitted it defaults to 0%/100% depending on prop<br> <TabAtkins> flackr: sounds fine to me<br> <bramus> +1<br> <TabAtkins> TabAtkins: +1<br> <TabAtkins> astearns: proposed resolution is to make % optional in animation-range-start/end, defaulting to 0%/100%<br> <fantasai> PROPOSAL: Make <percentage> optional in animation-range-start/end, defaulting to 0%/100%<br> <TabAtkins> RESOLVED: Make <percentage> optional in animation-range-start/end, defaulting to 0%/100%<br> <fantasai> animation-range: name x%<br> <TabAtkins> fantasai: if yous pecify `animation-range: name %`, currently it sets animation-range-start to that, and leaves -end as normal<br> <fantasai> animation-range-start: name x%; animation-range-end: normal<br> <fantasai> animation-range-start: name x%; animation-range-end: name (100 - x)%<br> <TabAtkins> fantasai: The alternative is to expand it to this ^^<br> <TabAtkins> fantasai: so if you say "contain 5%", it'll set them to "contain 5%" and "contain 95%", so you're insetting from either end<br> <TabAtkins> flackr: I put this forward bc it felt odd to take the specified % from the start, but ending in a potentially totally different animation range<br> <ydaniv> q+<br> <TabAtkins> flackr: felt consistent with margin/padding that get spammed to the other side of the block.<br> <astearns> ack ydaniv<br> <TabAtkins> ydaniv: q is do we want to change the range as well - if start is "entry" do we use "exit" in the end?<br> <TabAtkins> fantasai: Seems maybe too magical? Don't you want contain/cover?<br> <TabAtkins> YehonatanDaniv: For those the proposal makes sense. Seems funky that for entry 5% we expand to entry 95%<br> <TabAtkins> flackr: You can already use 'contain' to do that, but there are use-cases for keeping it in the same range. So i'd prefer not to.<br> <TabAtkins> fantasai: I'd understand if you wanted to expand "name X%" to "name X%" and "name 100%"<br> <TabAtkins> fantasai: so we'd take the name and set it to both longhands, but only use the % in start<br> <flackr> animation-range-start: name x%; animation-range-end: name 100%<br> <fantasai> animation-range: name x%<br> <fantasai> 1) animation-range-start: name x%; animation-range-end: normal<br> <fantasai> 2) animation-range-start: name x%; animation-range-end: name (100 - x)%<br> <fantasai> 3) animation-range-start: name x%; animation-range-end: name 100%<br> <TabAtkins> (this was gonna be my suggestion too - if the concern is just that setting 'end' to an unrelated phase, it seems reasonable to just set to that phase with 100%)<br> <TabAtkins> flackr: good with 2 or 3<br> <TabAtkins> fantasai: Slight pref for 3, okay with 2<br> <TabAtkins> TabAtkins: prefer 3<br> <TabAtkins> emilio: Also prefer 3<br> <TabAtkins> emilio: 2 seems too magic<br> <fantasai> TabAtkins: particularly, I don't know what 2 would do if you start at 55% :)<br> <TabAtkins> astearns: Do we think we'll get a second % in animation-range at some point?<br> <TabAtkins> fantasai: You can specify "name % name %" to end wherever you want<br> <TabAtkins> fantasai: In theory we could say "name % %" default to the previous name<br> <ydaniv> staying with 3 (:<br> <TabAtkins> astearns: If we already have the syntax, no need to complicate until people ask for it<br> <TabAtkins> astearns: So seems like we have option 3 consensus<br> <TabAtkins> RESOLVED: When specifying "animation-range: foo X%", set the -range-end to "foo 100%" (staying in same phase, just setting to end)<br> <fantasai> ACTION: file issue on 3-value syntax<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8438#issuecomment-1476465774 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 March 2023 15:38:14 UTC