Re: [csswg-drafts] [css-conditional] @container scroll-state(snapped) and snapchanged vs snapchanging (#10784)

The CSS Working Group just discussed `[css-conditional] @container scroll-state(snapped) and snapchanged vs snapchanging`, and agreed to the following:

* `RESOLVED: snapped matches snapchanging`

<details><summary>The full IRC log of that discussion</summary>
&lt;kbabbitt> futhark: this is an issue about scroll state snapped<br>
&lt;kbabbitt> ...question of whether state queries should match at the same time the snap changes or also including snap changing<br>
&lt;kbabbitt> ...think it makes sense to maek state query change while you're scorlling<br>
&lt;kbabbitt> ...got some feedback from ? that he thought you might want to have 2 separate queries<br>
&lt;TabAtkins> q+<br>
&lt;kbabbitt> ...one that changes with snap query and one that's only matching after ?<br>
&lt;flackr> q+<br>
&lt;kbabbitt> ...just looking for input, if someone thinks current behavior matching snap changing is good or if there are any other suggestions<br>
&lt;miriam> q+<br>
&lt;Rossen4> ack TabAtkins<br>
&lt;kbabbitt> TabAtkins: I agree that if we continue to keep just one query, having it match the snapchanging event so you'll start succeeding on the element that is becoming snapped is right<br>
&lt;kbabbitt> ...Adam's argument about having 2 is intriguing, would like to see an example<br>
&lt;kbabbitt> ...could easily be convinecd that it's a good thing to do<br>
&lt;kbabbitt> futhark: happy to resolve on matching snapchanging<br>
&lt;Rossen4> ack flackr<br>
&lt;kbabbitt> flackr: also agree that snapchanging is the right first step would like to see use cases for snapchanged<br>
&lt;flackr> https://github.com/w3c/csswg-drafts/issues/10838<br>
&lt;kbabbitt> ...also wanted to point out open issue about what snapchanging targets<br>
&lt;kbabbitt> ...10838<br>
&lt;kbabbitt> ...where I think, Adam has potentially requested a third possible query<br>
&lt;kbabbitt> futhark<br>
&lt;kbabbitt> futhark: just to correct a bit about what I have implemented so far<br>
&lt;kbabbitt> ...checking oth snapchanged and snapchanging<br>
&lt;kbabbitt> ...in case there's snapchanged that happened without snapchanging<br>
&lt;kbabbitt> flackr: that is not supposed to happen<br>
&lt;Rossen4> ack miriam<br>
&lt;kbabbitt> miriam: I think I basically agree with TabAtkins and flackr<br>
&lt;kbabbitt> ...to clarify, snapchanging is inclusive of ? changed<br>
&lt;kbabbitt> ...we're not saying it matches only when it's changing but also when it has changed<br>
&lt;kbabbitt> ...agree we're starting in the right way<br>
&lt;kbabbitt> Rossen4: other opinions?<br>
&lt;kbabbitt> futhark: currently snap... if that's a bad name, if we decide to add the scroll changed / snap changed later... [?]<br>
&lt;kbabbitt> flackr: are there other patterns we could follow<br>
&lt;kbabbitt> TabAtkins: I don't think we have precedent yet<br>
&lt;kbabbitt> miriam: I think snap is nice for the default<br>
&lt;kbabbitt> ...we can figure something else out for the other<br>
&lt;kbabbitt> futhark: we can just resolve that snapped matches snapchanging<br>
&lt;kbabbitt> Rossen4: other comments?<br>
&lt;kbabbitt> RESOLVED: snapped matches snapchanging<br>
&lt;TabAtkins> ScribeNick: TabAtkins<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10784#issuecomment-2379901508 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:11:39 UTC