Re: [csswg-drafts] [css-scroll-snap] Proposing `:snapped`: exposing private snapped item browser state for developers and designers (#6985)

The CSS Working Group just discussed ``[css-scroll-snap] Proposing `:snapped`: exposing private snapped item browser state for developers and designers``, and agreed to the following:

* `RESOLVED: Publish css-scroll-snap-2 as FPWD minus scroll-start property`

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> TabAtkins: Want to give a heads up about scroll-snap events<br>
&lt;emeyer> …These are the replacement for the topic originally raised in this issue<br>
&lt;emeyer> …They fire when a thing snaps or is snapping, so you can track them that way<br>
&lt;emeyer> …So, please review the events in the issue so we can get on track for forward movement<br>
&lt;astearns> ack fantasai<br>
&lt;emeyer> fantasai: This doesn't have FPWD, so you're putting a call for FPWD?<br>
&lt;emeyer> TabAtkins: Yeah, let's do it<br>
&lt;emeyer> …This is something one of our editors has been working on and we think it needs more visibility in the group<br>
&lt;emeyer> fantasai: The rest of the stuff in this publication is also ready to go?<br>
&lt;emeyer> …Somewhat<br>
&lt;emeyer> DavidA: Two parts of this spec, part has to do with snap events and part with snap targets<br>
&lt;emeyer> …This is only about the events part; the other part isn't as ready<br>
&lt;emeyer> flackr: I also see styyling in the scroll snap 2 spec<br>
&lt;emeyer> DavidA: Only the events are ready to move forward at the moment<br>
&lt;emeyer> fantasai: What do you mean by that?<br>
&lt;emeyer> DavidA: I think they can be implemented, we have one in Chrome we'd like to ship but we want more eyes on it first<br>
&lt;emeyer> fantasai: What's wrong with the rest of the spec?<br>
&lt;emeyer> flackr: We don't have an implementation of snapped, which is morst likely to change<br>
&lt;emeyer> …There was a request to change it, so we could mark that as at risk<br>
&lt;emeyer> astearns: I don't think we have to At Risk in FPWD<br>
&lt;emeyer> fantasai: Then mark it as an issue that it might change<br>
&lt;emeyer> …For scroll-start, what use cases does it solve that aren't solved by content alignment?<br>
&lt;emeyer> TabAtkins: We're not asking for an overview of the entire draft, so please defer topic discussion about things outside events unless you spot something really bad<br>
&lt;emeyer> fantasai: If you think you're going to drop parts of it, drop them before FPWD?<br>
&lt;emeyer> flackr: I think it would be fine to drop<br>
&lt;emeyer> (missed)<br>
&lt;fantasai> PROPOSED: Publish css-scroll-snap-2 as FPWD minus scroll-start property<br>
&lt;emeyer> astearns: Objections?<br>
&lt;emeyer> (silence)<br>
&lt;emeyer> RESOLVED: Publish css-scroll-snap-2 as FPWD minus scroll-start property<br>
</details>


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


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

Received on Thursday, 13 June 2024 15:52:25 UTC