- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Jun 2023 23:33:34 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[scroll-animations-1] Three-value `animation-range` shorthand notation``, and agreed to the following: * `RESOLVED: No change` <details><summary>The full IRC log of that discussion</summary> <dael> fantasai: We have an animation-range shorthand for start and end. Can take keyword, length, % or both one after the other. Means you can do 2 or 3 component values<br> <fantasai> animation-range: 10% entry 90%;<br> <fantasai> animation-range: contain 10% 90%;<br> <dael> fantasai: Question was what's best way to interpret a 3 component value. Examples ^<br> <dael> fantasai: Could do exactly as specified. Another is make these invalid. Third is duplicate the keyword which feels a little odd in the first example.<br> <dael> fantasai: flackr had another though?<br> <dael> flackr: It was that no spec range would refere to max-range of the timeline. So it's larger than the cover range for view timelines<br> <dael> fantasai: That feels independant from how to assign 3 value<br> <dael> flackr: It is, but gives meaningful value to things without range<br> <dael> fantasai: Animation-range 10% 90% would go from 10-90% of cover<br> <dael> flackr: Then I think we shouldn't do magic with range names in 3 value<br> <dael> Rossen_: Does that leave us no change?<br> <dael> fantasai: I think that is current state<br> <dael> fantasai: First option, assign long hand values as specified<br> <fantasai> s/would go/currently goes/<br> <dael> florian: When you have % keyword % is it unambig by ordering?<br> <dael> fantasai: Yes. animation-range requires keyword first<br> <dael> florian: Good<br> <dael> Rossen_: Do we need a resolution?<br> <dael> flackr: resolve to keep as is?<br> <dael> Rossen_: no change<br> <dael> Rossen_: Objections?<br> <dael> RESOLVED: No change<br> <dael> fantasai: I brought this because we hadn't talked about the 3-value option so needed to cover<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8672#issuecomment-1581653985 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 June 2023 23:33:36 UTC