> For instance, it is easy for a user to land at an awkward scroll position which leaves an item partially on-screen when panning.
> To this end, this module introduces scroll snap positions which enforce the scroll positions that a scroll container’s scrollport may end at after a scrolling operation has completed.
Which is exactly what this page is doing.
> primarily a touch interaction
It's exclusively a scroll interaction, whether the pointer event is the result of mouse or touch input.
> the DOM page is still scrolling natively
I'm not sure what you're trying to say by "DOM page." JS is reacting to the scroll position of the viewport. The user experience is the same.
Interesting aside. Back on topic: the homes were not granted to Zuckerberg; and his residents are not serfs. So they are not "perfectly comparable," they are barely comparable.
(not to mention serfs could not be bought alone, they could be sold with the land. Maybe you are thinking of slaves?)
https://www.audacy.com/wwjnewsradio/news/local/mdot-names-al...