- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Mar 2023 21:25:39 +0000
- To: public-css-archive@w3.org
OK, edits are in https://github.com/w3c/csswg-drafts/commit/f4a3db2581917c3d38eaea56c1b0243075b15ae2. I added an example with the implications: ``` animation-range: entry 10% exit 90%; animation-range-start: entry 10%; animation-range-end: exit 90%; animation-range: entry; animation-range-start: entry 0%; animation-range-end: exit 100%; animation-range: 10%; animation-range-start: 10%; animation-range-end: normal; animation-range: entry 10% exit; animation-range-start: entry 10%; animation-range-end: exit 100%; animation-range: 10% exit 90%; animation-range-start: 10%; animation-range-end: exit 90%; animation-range: entry 10% 90%; animation-range-start: entry 10%; animation-range-end: 90%; ``` The last three are fallout from defining the shorthand as `<'animation-range-start'> <'animation-range-end'>?`, so rather than trying to carve out those cases as invalid I left them in. We could define some custom handling that takes any single timeline name and duplicates it, which would make `entry 10% 90%` equivalent to `entry 10% entry 90%`--but this would mean that a number of longhand combinations have no valid serialization. @cdoublev @flackr @ydaniv Let me know if this is satisfactory, and if so I'll close the issue; otherwise lmk what you think needs further adjustment. :) -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8438#issuecomment-1487614227 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 March 2023 21:25:40 UTC