Re: [csswg-drafts] [css-scroll-snap-2] scroll-start-target: auto doesn't match general meaning of auto (#11173)

The CSS Working Group just discussed `[css-scroll-snap-2] scroll-start-target: auto doesn't match general meaning of auto`, and agreed to the following:

* ``RESOLVED: `scroll-initial-target: none | nearest` ``

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> DavidA: scroll-start-target is set on the child of a scrollable container, that makes the container initiall scroll to that child<br>
&lt;TabAtkins> DavidA: got feedback from the TAG that, looking at the name of the property, the -start could be confusing (it's a logical direction in other properties)<br>
&lt;TabAtkins> DavidA: also the values are none|auto, was a question about -- currently auto means the element is a scroll-start target, but "auto" usually is used for something more magical<br>
&lt;TabAtkins> DavidA: so we're lookign for a repalcement value name<br>
&lt;TabAtkins> DavidA: for property name, scroll-container-target and initial-scroll-target are my suggestions. suggest the second one<br>
&lt;TabAtkins> (yeah, I like initial-scroll-target)<br>
&lt;TabAtkins> DavidA: for the values, i'm proposing `none | local`. proposing local because it only effects the nearest scroll container.<br>
&lt;TabAtkins> DavidA: in theory, in future we could expand the scope of the scrolling target, add "global" or something<br>
&lt;TabAtkins> flackr: the thinking is that a value which scrolls all ancestors could explain fragment navigation - that does scroll all scrollers up to the root<br>
&lt;astearns> ack rachelandrew<br>
&lt;astearns> ack fantasai<br>
&lt;TabAtkins> (i think i'd prefer something like "self")<br>
&lt;fantasai> https://drafts.csswg.org/scroll-animations-1/#scroll-notation<br>
&lt;TabAtkins> fantasai: we have scroll() from Scroll Animations. It uses the keyword "nearest", we should be consistent with that<br>
&lt;TabAtkins> +1<br>
&lt;rachelandrew> sorry was muted, yes was just leftover from before<br>
&lt;TabAtkins> fantasai: for property name, would it make sense to put "scroll" first, so scroll-initial-target?<br>
&lt;TabAtkins> DavidA: I think scroll-initial-target is fine too<br>
&lt;TabAtkins> flackr: or overflow-initial-target, since most other scorlling properties are overflow<br>
&lt;TabAtkins> fantasai: we have a lot of scroll-* prefixes, scroll-padding, scroll-snap, etc<br>
&lt;TabAtkins> flackr: fair, i do like it being grouped with other scrollers. tho it does go on the child rather than the scroll container<br>
&lt;TabAtkins> fantasai: also several scroll-* properties that are, like scroll-margin<br>
&lt;TabAtkins> fantasai: I do think these names are better, but we're not clearly managing that this is set on the item<br>
&lt;TabAtkins> fantasai: I think scroll-margin and scroll-snap-align are a little bit indicative, but my initial impression from the property name is it's set on the scroll container, and takes some reference to a child<br>
&lt;TabAtkins> (I think scroll-initial-target is reasonably child-indicative. not 100%, but doable)<br>
&lt;TabAtkins> DavidA: I was thinking scroll-container-target, but not sure if that helps<br>
&lt;TabAtkins> astearns: i think we're converging, at least for now, on scroll-initial-target. might come up with something better<br>
&lt;TabAtkins> astearns: shall we resolve on that?<br>
&lt;TabAtkins> +1<br>
&lt;bramus> +1 on nearest<br>
&lt;TabAtkins> fantasai: and none|nearest for values?<br>
&lt;TabAtkins> DavidA: yeah<br>
&lt;TabAtkins> astearns: so proposed is `scroll-initial-target: none | nearest`<br>
&lt;TabAtkins> astearns: objections?<br>
&lt;TabAtkins> RESOLVED: `scroll-initial-target: none | nearest`<br>
&lt;argyle> 👍🏻<br>
&lt;TabAtkins> fantasai: can we have a comment soliciting better ideas?<br>
&lt;TabAtkins> astearns: specifically about something tha tmight more obviously indicate that it's on the child<br>
&lt;TabAtkins> DavidA: i can write something<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11173#issuecomment-2536659205 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 11 December 2024 17:37:41 UTC