> If a user wants smooth scroll, they will enable it in their browser. I really think comments like this aren't helpful and presumptuous to pressing forward.

> If a user wants smooth scroll, they will enable it in their browser. I really think comments like this aren't helpful and presumptuous to pressing forward. People hate change and love their table layouts... Just going to make a friendly counter argument: - Did you read what this actually does? It's for anchor tags... - Bootstrap 5 uses this by default. - Lot of crappy websites out there. I choose loading one line of CSS versus jQuery + animate all day... - For perspective, almost 100% of every little interaction on native apps are animated these days. It's liked so much by the general population that, some would say, made iOS so appealing in the beginning to take off. People like interaction. - It's possible your opinion does not represent the majority anymore (or even that the HN general opinion). - By making it a browser-defined CSS property versus being JavaScript, you are actually opening accessibility doors for people having this be device configurable. I really think if someone hates it so much or for accessibility reasons, instead they should just disable it in their browser. So literally the opposite of what you said. --- Edit: Example of why this is important to be part of CSS for accessibility versus JavaScript: ``` @media (prefers-reduced-motion: no-preference) { :root { scroll-behavior: smooth; } } ``` or: ``` @media (prefers-reduced-motion) { .animation { animation: none; } :root { scroll-behavior: auto; } } ``` I think HN can chill a bit here.