- From: Majid Valipour via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 May 2018 15:02:46 +0000
- To: public-css-archive@w3.org
I also read the original resolution differently as it meant that snap *only* wins when there is no alignment. I am fine with fantasai's [explanation above](https://github.com/w3c/csswg-drafts/issues/2593#issuecomment-385099549). It basically amounts to snap always be in effect which is consistent and easy to reason about. I don't think we need to talk about wining at all rather snapping operates *after* all other scrolling operations so it always applies. In the case of sIV() if the alignment brings the scroll offset to a location which is a valid snap point then the alignment remains otherwise we adjust it to honor snapping even if it means the alignment is ignored. So effectively: 1. Apply scroll operation (user scroll or programmatic scrolls e.g., scrollTo, scrollBy, scrollIntoView, etc.) 2. Apply scroll snapping -- GitHub Notification of comment by majido Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2593#issuecomment-385693218 using your GitHub account
Received on Tuesday, 1 May 2018 15:02:51 UTC