Re: [csswg-drafts] [css-scroll-snap-1] Improve or clarify nested snap behaviors (#9187)

The CSS Working Group just discussed `[css-scroll-snap-1] Improve or clarify nested snap behaviors`, and agreed to the following:

* `RESOLVED: Better define this behavior when you have nested snap areas and children with interleaved content from the parent`

<details><summary>The full IRC log of that discussion</summary>
&lt;bramus> flackr: brought up a few weeks ago and got some comments<br>
&lt;bramus> … situation right now is that if snap area b inside of snap area a, there is almost no effect as ??? is a valid snap position.<br>
&lt;astearns> s/???/anywhere in a/<br>
&lt;bramus> … proposed to snap to inner element (b) or snap to position that avoids showing inner elem on the outer element<br>
&lt;bramus> … there is a linked demo with example<br>
&lt;astearns> ack fantasai<br>
&lt;bramus> … this came up as best way to implement desired snap behavior that search was exploring, or some free scrolling on some region and than mandatory in nested sections<br>
&lt;bramus> fantasai: if you end up snapping to margin in between things … which would not be … its a tricky situation but I am OK …<br>
&lt;bramus> … I trust Rob with poking around at this.<br>
&lt;bramus> … main concern if we are creating snap areas in segments in between child elements (eg margin)<br>
&lt;bramus> flackr: agree and that is where more complicated part of proposal gets into it<br>
&lt;bramus> … might need some better formulation<br>
&lt;bramus> … there are situation where innner area should be necessary as well<br>
&lt;bramus> … but i have same concern<br>
&lt;bramus> fantasai: agree that inner area should be accessible<br>
&lt;bramus> astearns: at moment spec say nothing about nested snap areas?<br>
&lt;bramus> flackr: it says something but its not …<br>
&lt;bramus> fantasai: it doesnt handle the interleaved case<br>
&lt;bramus> … we dont say what happens when you have content in between snappable areas<br>
&lt;bramus> flackr: so it sounds we are generally in favor but we need to define the edge conditions?<br>
&lt;bramus> astearns: PROPOSED RESOLUTION: Better define this behavior when you have nested snap areas and children with interleaved content from the parent<br>
&lt;bramus> … comments or concerns?<br>
&lt;bramus> … objections?<br>
&lt;bramus> RESOLVED: Better define this behavior when you have nested snap areas and children with interleaved content from the parent<br>
&lt;bramus> astearns: given complexity of this, might be good to have explainer with these demos<br>
&lt;bramus> flackr: yep<br>
</details>


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


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

Received on Wednesday, 15 November 2023 17:44:56 UTC