- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Dec 2022 00:26:50 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[scroll-animations-1] `scroll-timeline` and `view-timeline` shorthand syntax``, and agreed to the following: * `RESOLVED: Have parsing with fixed order of name and axis` <details><summary>The full IRC log of that discussion</summary> <dael> Rossen_: Who can summerize?<br> <fantasai> -> https://github.com/w3c/csswg-drafts/issues/7627<br> <dael> bramus: I can. In the spec there's a difference between scroll and view timeline argument order.<br> <dael> bramus: Proposal was to have them use same syntax<br> <fantasai> scroll/animation-timeline: <name> || <axis><br> <fantasai> scroll/animation-timeline: <name> <axis>?<br> <dael> fantasai: Other point you raised is timeline name and axis are in same namespace. I put this on agenda to ask WG if we shoudl require an order and require name always? We could change the current syntax<br> <bramus> q+<br> <dael> fantasai: Other ways to disambig but asking if this is what we want to do or something different<br> <Rossen_> ack bramus<br> <dael> bramus: One question on prop new is there is no slash separator but container queries requires one after the name. Seems like a difference<br> <dael> miriam: Likely b/c you can have multiple names<br> <bramus> q-<br> <dael> bramus: Don't think we want to allow multiple names on scroll timeline, do we?<br> <dael> fantasai: Do it with a comma sep syntax and axises are listed with name. Container property doesn't have that; doesn't tie two properties with lists. Only one type of contianment<br> <dael> fantasai: Here we have a list of timelines that have their own properties<br> <dael> flackr: I'm in favor of fixing the order<br> <bramus> +1<br> <dael> Rossen_: Any opposing opinions?<br> <dael> Rossen_: Prop: Have parsing with fixed order of name and axis<br> <dael> Rossen_: Objections?<br> <dael> RESOLVED: Have parsing with fixed order of name and axis<br> <dael> Rossen_: fantasai anything else on this?<br> <dael> fantasai: nope<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7627#issuecomment-1341797323 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 December 2022 00:26:52 UTC