- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Apr 2025 19:35:52 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[scroll-snap-2] Rename `scroll-start-target` to `scroll-target`?``, and agreed to the following: * `RESOLVED: Close as fixed; dup of earlier issue` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> fantasai: we ahd a property named scroll-start-target, i complained we use "start" in too many other ways<br> <TabAtkins> fantasai: so my suggestion was to rename to scroll-target<br> <TabAtkins> fantasai: draft is currently using scroll-initial-target<br> <TabAtkins> fantasai: so i think that resolves the concern, tho i still think "initial" might not be needed<br> <fantasai> https://drafts.csswg.org/css-scroll-snap-2/#scroll-initial-target<br> <fantasai> TabAtkins: I do like the 'initial' in there because it's a temporal effect on the scroller<br> <fantasai> TabAtkins: not sure it suggests very well that you start the scroller there<br> <TabAtkins> (it doesnt' suggest if you don't have it there)<br> <fantasai> fantasai: How does it interact with fragids etc.? Do those win?<br> <fantasai> TabAtkins: fragID causes scroll to happen, and that would override these<br> <fantasai> TabAtkins: this is just first layout<br> <fantasai> faceless: ok<br> <fantasai> s/faceless/fantasai/<br> <fantasai> RESOLVED: Close as fixed; dup of earlier issue<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10913#issuecomment-2776748331 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 April 2025 19:35:54 UTC