Re: [csswg-drafts] [css-scroll-snap] Multiple nested scrollers and a "default" scrollIntoView()?

The Working Group just discussed `Multiple nested scrollers and a "default" scrollIntoView()?`, and agreed to the following resolutions:

* `RESOLVED: Have the default scrolling behavior for nested scrollers to have scroll snap`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Multiple nested scrollers and a "default" scrollIntoView()?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2593<br>
&lt;dael> TabAtkins: I suspect it's resolved at this point, but making sure. majidvp and our other impl that are getting our scroll snap up to date found an interaction. Spec defines and interaction between scroll methods alignment and scroll snap. You try to align via howt he scroll method says and if you need to snap after you do.<br>
&lt;dael> TabAtkins: Nested scrollers when you have to go multi deep to get hte element in view. Conclusion is you first align all the scrollers as you go down according to scroll method alignment. If any scrollers have scroll snap you honor that to bring them into alignment. And that's about it.<br>
&lt;dael> TabAtkins: Unless anyone disagrees that's what we concluded in the thread which means no edits to the spec except we might want to clarify the wording.<br>
&lt;dael> Rossen_: Sounds reasonable. Any other opinions or objections?<br>
&lt;dael> prop: Have the default scrolling behavior for nested scrollers to have scroll snap<br>
&lt;dael> TabAtkins: Yeah, sure.<br>
&lt;dael> RESOLVED: Have the default scrolling behavior for nested scrollers to have scroll snap<br>
</details>


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

Received on Wednesday, 2 May 2018 23:43:33 UTC