5 ms·
Please don't interfere with the native scrolling behavior.
by l-p 11y ago
Please don't interfere with the native scrolling behavior.
- gitmagic 11y agoI usually don't like forced scroll myself, but I have to say that I'm personally satisfied with the results of this site. But I hear you and when the site goes from landing page to real website we will make sure to have a nice scroll experience for everyone :)
- icholy 11y agoIt breaks the back button.
- unfunco 11y agoA "nice scroll experience" is no scroll experience, don't even think about the scrollbar, it's the concern of the browser. Good design is unobtrusive. [5] Good design is as little design as possible. [10] [5, 10]: https://www.vitsoe.com/us/about/good-design https://www.vitsoe.com/us/about/good-design
- atom-morgan 11y agoPlease! Maybe I'm weird but sometimes I simply want to reposition text on my screen. Just a slight adjustment, think eye level, so it's a bit easier to read and sites like this don't allow me to do so.
- jc4p 11y agoOr at least use `replaceState` not `pushState`. I scrolled from the top of the page down one section and when I hit back it just went right back to the top of the page.
- andyfleming 11y agoI agree and disagree. As a general rule, you shouldn't be screwing with the scrolling behavior, but in case like this (with a slider-type of interaction), it is a bit more understandable. What I can't stand is when people do it just to affect the acceleration/whatever of scrolling as a gimmick. This has some usefulness at least and doesn't affect my experience negatively at all.
- lojack 11y agoPersonally, this infuriates me. I'm not done reading just because I started scrolling.
- karlkfi 11y agoAgreed. Autoscroll breaks the mobile experience horribly. Small text... No pinch to zoom... Half the text is always off the screen in landscape...
- thisisdave 11y agoAnd don't interfere with the "back" button, either. Scrolling back to the previous location isn't what anyone intends when they press it.