- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Jan 2023 18:33:59 +0000
- To: public-css-archive@w3.org
Based on the resolution in #7901 animation-range should be set with a new set of properties. As a new set of properties we don't have to support legacy values. Based on the resolution in #7748 we should aim for accepting a string equivalent to the CSS syntax or typed OM. Rough proposal, add the following to [EffectTiming](https://www.w3.org/TR/web-animations-1/#dictdef-effecttiming) and [OptionalEffectTiming](https://www.w3.org/TR/web-animations-1/#dictdef-optionaleffecttiming):
```
dictionary TimelineRangeOffset {
CSSOMString? rangeName;
CSSNumericValue offset;
}
DOMString or TimelineRangeOffset rangeStart = "auto";
DOMString or TimelineRangeOffset rangeEnd = "auto";
```
DOMStrings would be parsed the same as the CSS animation-range-start and animation-range-end properties, as `<timeline-range-name>? <percentage> | "auto"`.
--
GitHub Notification of comment by flackr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7589#issuecomment-1380842759 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 12 January 2023 18:34:01 UTC