- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Nov 2022 21:28:04 +0000
- To: public-css-archive@w3.org
> * Any reason to prefer `offset(<timeline-range-name> <percentage>) offset(<timeline-range-name> <percentage>)` over `offset(<timeline-range-name> <percentage>, <timeline-range-name> <percentage>)`? I guess the latter maps better to a single delay value that is expected today, or is there an intent to add end delay to the shorthand's definition? The intent would be to add end delay to the shorthand definition, though putting the start and end in one function is also fine with me. This could be delay or range, whichever we go with in #7901. > * Is `<percentage>` mandatory? Or defaults to `0%`/`50%`? I would prefer it being mandatory, though if we have a positional function like you proposed it might be reasonable to default to 0% for the start range / delay and 100% for the end range / delay. > * How about optional percentages for `range()` ? Like `range(<timeline-range-name>[, <percentage>][, <percentage>])`, first for start and second for end. Isn't this just becoming the same as the offset function? -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8054#issuecomment-1325676296 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 November 2022 21:28:06 UTC