- From: Matt Rakow via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Sep 2016 18:40:37 +0000
- To: public-css-archive@w3.org
You still seem very focused on the syntax. I can understand why you would associate this new functionality with snapping since both involve "where the scroll goes". However that's where the similarities end I think: snap positions are specifically specified as providing "particular alignments of content within a scroll container" whereas the new proposed functionality doesn't describe any alignment but only a reduced "in view" concept. In fact, if the feature is primarily designed to provide an "in view" concept, I think it has many further implications unrelated to scrolling. Off the top of my head: - An "in view" region would allow for a variety of optimizations in paint and composition, avoiding unnecessary work and memory allocation for non-visible regions. - `IntersectionObserver`'s main objective is to provide advertisements with "in view" notification, which could be better informed with this concept. A feature that unambigously defines an "in view" region could do these things in addition to modifying ScrollIntoView behavior, but to call that feature `scroll-padding` would be a misnomer. So as I mentioned before I think it's an interesting problem space. I just think you're conflating it with the wrong feature. -- GitHub Notification of comment by ChumpChief Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/395#issuecomment-245048074 using your GitHub account
Received on Tuesday, 6 September 2016 18:40:48 UTC