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`, and agreed to the following:

* `RESOLVED: Add ::column pseudo, as a leaf node on the multicol, supporting scroll-marker and scroll-snap-align`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> flackr: we had a previous discussion about the use-cases for snapping and generating scroll markers on column boxes<br>
&lt;TabAtkins> flackr: based on some of the discussion/concerns, i'm proposing we go with a fourth option<br>
&lt;TabAtkins> flackr: define a ::column pseudo<br>
&lt;TabAtkins> flackr: that you can attach scroll markers to, set scroll-snap-align on. potentially we could expose more props in the future<br>
&lt;TabAtkins> flackr: and I think this resolves a lot of the issues we had, and is consistent with some of elika's comments<br>
&lt;TabAtkins> +1 from me<br>
&lt;TabAtkins> Rossen4: Rune, you had comments on this issue<br>
&lt;TabAtkins> flackr: you commented on the ::nth-fragment option, but the proposal now is to go with a ::column pseudo<br>
&lt;TabAtkins> futhark: that's kinda a sidenote, about styling columns when elements fragment across them<br>
&lt;TabAtkins> futhark: is that relevant now?<br>
&lt;TabAtkins> flackr: I think there's one potentially relevant question here.<br>
&lt;TabAtkins> flackr: if you set scroll-snap-align:inherit...<br>
&lt;TabAtkins> futhark: yeah, which one do you align if an element breaks across columns<br>
&lt;TabAtkins> flackr: need to decide if we inherit<br>
&lt;TabAtkins> flackr: if we never support selecting particular columns, it's okay<br>
&lt;TabAtkins> flackr: but if we do, you could inherit different values on each fragment<br>
&lt;TabAtkins> fantasai: there shouldn't be inheritance<br>
&lt;TabAtkins> miriam: why?<br>
&lt;TabAtkins> fantasai: we could go either way in theory<br>
&lt;TabAtkins> fantasai: I think there are use-cases for having *some* sort of inheritable pseudo-element, but that's really complicated<br>
&lt;TabAtkins> fantasai: but a lot of times you just want to address the pseudo itself as a box<br>
&lt;TabAtkins> fantasai: another issue, ::column is a pretty generic name, we have columns elsewhere.<br>
&lt;miriam> got it, makes sense - thanks<br>
&lt;TabAtkins> fantasai: if we have it just be a leaf box in the tree, it's easier for us to reuse it in those other contexts<br>
&lt;TabAtkins> flackr: proposed resolution, add ::column pseudo-element as described in the issue<br>
&lt;TabAtkins> flackr: it's a leaf node (nothing inherits from it), and it supports scroll-marker and scroll-snap-align for now<br>
&lt;futhark> q+<br>
&lt;Rossen4> ack futhark<br>
&lt;TabAtkins> futhark: you said nothing inherits from it, what about ::scroll-marker?<br>
&lt;TabAtkins> fantasai: nothing *in the tree* inherits from it. chained pseudos still do, as normal<br>
&lt;TabAtkins> RESOLVED: Add ::column pseudo, as a leaf node on the multicol, supporting scroll-marker and scroll-snap-align<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-2379924982 using your GitHub account


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

Received on Friday, 27 September 2024 19:29:11 UTC