- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Sep 2024 16:29:08 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-scroll-snap-2] How should competing scroll-start-targets be resolved?`, and agreed to the following: * `RESOLVED: When scroll-start-target targets multiple elements, scroll to each in reverse DOM order with text to specify priority is the first item` <details><summary>The full IRC log of that discussion</summary> <chrishtr> DavidA: we have a property we're adding called scroll-start-target that indicates if an element within a scroll container, then the scroll should start with that element onscreen<br> <chrishtr> DavidA: question is what happens if there are multiple targets<br> <chrishtr> DavidA: propose to do it in reverse-DOM order,<br> <chrishtr> DavidA: this would result in the first one applied last and then be on screen<br> <chrishtr> DavidA: also, should only change the scroll position if you have to<br> <Rossen3> ack fantasai<br> <chrishtr> fantasai: several questions. first: why do we need to add a new property rather than re-using scroll-snap-align?<br> <chrishtr> flackr: setting the scroll alignment for items that don't necessarily become snaps<br> <chrishtr> flackr: scroll-snap-align would also force the developer to set scroll snap areas<br> <chrishtr> fantasai: in that case, should there be a relationship between the two properties?<br> <chrishtr> fantasai: might want to do both behaviors<br> <chrishtr> flackr: I agree the properties should be strongly linked, possibly with a shorthanding relationship<br> <chrishtr> fantasai: suggest thinking about this more on the issue<br> <chrishtr> fantasai: so that we can figure out how the two properties interact<br> <chrishtr> fantasai: there was a bunch of discussion about regular vs reverse-DOM order. where did we end up and why?<br> <chrishtr> flackr: currently, we expect that it scrolls to the first item in DOM order. We probably want that to still happen. That is why the proposal is to scroll to each item in sequence in reverse-DOM order.<br> <chrishtr> flackr: there is also the issue of nearest...<br> <chrishtr> fantasai: can you explain nearest?<br> <chrishtr> flackr: same as scroll into view<br> <chrishtr> fantasai: ?<br> <chrishtr> flackr: this is needed with you scroll multiple things into view and want to find a good position (?)<br> <chrishtr> fantasai: you scroll in reverse-DOM order...when you add the spec can you make it really clear that this is the end result of the algorithm?<br> <chrishtr> flackr: yes absolutely<br> <chrishtr> fantasai: otherwise it seems to make sense<br> <chrishtr> fantasai: have questions in general about the feature but not this issue<br> <chrishtr> flackr: seems we can resolve that the general thing is good?<br> <flackr> Proposed resolution: Add scroll-align property to specify scroll alignment without adding a snap area - details TBD<br> <chrishtr> fantasai: would like to see the interaction with snapping<br> <flackr> Proposed resolution 2: When scroll-start-target targets multiple elements, scroll to each in reverse DOM order with text to specify priority is the first item<br> <chrishtr> rossen: we'll postpone the first resolution until we have more details<br> <chrishtr> RESOLVED: When scroll-start-target targets multiple elements, scroll to each in reverse DOM order with text to specify priority is the first item<br> <chrishtr> flackr: third thing: having a nearest align value<br> <chrishtr> flackr: not sure if we can resolve without details for resolution #1<br> <chrishtr> rossen: maybe we should wait for more details<br> <chrishtr> fantasai: suggest a separate issue be filed about the nearest issue<br> <chrishtr> fantasai: agree we should do something in that direction, just need to figure out all the details<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10774#issuecomment-2358920264 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 September 2024 16:29:09 UTC