Re: [csswg-drafts] [css-overflow-5][css-scroll-snap-2] Snapping and generating scroll-marker pseudo-elements from fragments (#10715)

The CSS Working Group just discussed `[css-overflow-5][css-scroll-snap-2] Snapping and generating scroll-marker pseudo-elements from fragments`.

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> flackr: Final thing that really helsp make this fall together is being able to use fragmentation to automatically create the "pages"<br>
&lt;TabAtkins> flackr: So if you specify that you have columns:1, that'll make one fragment per page<br>
&lt;TabAtkins> flackr: You could do multiple columns<br>
&lt;TabAtkins> flackr: we want to support some styling on these columns<br>
&lt;TabAtkins> flackr: scroll-snap-align is a notable one, to align the columns itself<br>
&lt;TabAtkins> flackr: not useful to stop a scroll halfway between columns, would rather it snap<br>
&lt;flackr> demo of columns: https://jsbin.com/modewaj/edit?html,output<br>
&lt;TabAtkins> flackr: the other use is generating a scroll marker<br>
&lt;TabAtkins> flackr: if a column is a destination you want to get to, you might want a scroll marker for it<br>
&lt;flackr> https://codepen.io/flackr/pen/yLmyPEV<br>
&lt;TabAtkins> flackr: combining these features, you can make this demo<br>
&lt;TabAtkins> flackr: note snap alingment isn't working yet<br>
&lt;TabAtkins> flackr: you can see the number of scroll-markers i generate changes as i chagne the container size, since different number of items fit on a scroll page<br>
&lt;TabAtkins> flackr: with snap-align support it would automatically snap to pages, arrows would work properly<br>
&lt;TabAtkins> flackr: this lets authors just write a list of content, and have it present in a full paginated experience<br>
&lt;flackr> TabAtkins: while this is fully generated, all of this can be done with real elements<br>
&lt;flackr> TabAtkins: allowing additional structure / semantics<br>
&lt;TabAtkins> syns: This really excited me, as someone who's lead a dev team thru a carousel<br>
&lt;TabAtkins> TabAtkins: our exploration revealed that there were basically *zero* correct carousels on the web<br>
&lt;wendyreid> q+<br>
&lt;TabAtkins> syns: but there are more correct ones ^_^<br>
</details>


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


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

Received on Wednesday, 25 September 2024 22:25:36 UTC