- From: François REMY via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Aug 2016 23:09:32 +0000
- To: public-houdini-archive@w3.org
I don't believe this will be a very frequent concern, but this remains a valid argument. How about this would act like * for parsing purposes, but would animate/transition as the property would? If the value is not a valid value of the property, then it just acts like a normal pair of non-interpolable values. If you really care about parsing, you can always nest inside at-supports statements. My use case is mainly to have transitions and animations to work. I have multiple use cases but one we already aim to support is similar to how 'translate/rotate/scale' make it possible to have different transitions functions/timing for different subsections of the 'transform' property; I would want to mimick this for 'background' lists, by animating --background-list-1 and --background-list-2 independently. -- GitHub Notification of comment by FremyCompany Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/48#issuecomment-238720038 using your GitHub account
Received on Tuesday, 9 August 2016 23:09:39 UTC