- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Aug 2022 00:34:20 +0000
- To: public-css-archive@w3.org
> The one downside to starting with option 1 is that if this is the string value is what you read back from [getTiming](https://drafts.csswg.org/web-animations-1/#dom-animationeffect-gettiming) then we can't upgrade to option 2 without risking breaking content. Yeah, I mean we _could_ introduce parallel properties -- typed and untyped/string-type -- and precedence rules for when they're both set, but then we'd break code that attempts to roundtrip the values, by fetching the timing, setting only the lower precedence one (e.g. the untyped/string-type one), then re-setting it. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7589#issuecomment-1225026738 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 August 2022 00:34:22 UTC