search

biotope / website

https://biotope.sh
MIT License
4 stars 0 forks source link

prevent scroll and resize issues on Android and iOS #157

Closed clemensf closed 4 years ago

jurekbarth commented 4 years ago

Could you please reconsider that scrolljacking approach overall. It's still buggy even in Chrome, where the scrollbar jumps crazy and you're caught in the middle. There are a lot of articles why thats a bad pattern overall, here's one of them: https://www.robinrendle.com/notes/scrolljacking

clemensf commented 4 years ago

@jurekbarth do you mean scroll based animation in general or the specific „scroll capturing“ here?

@luke-m and @rhafner @timomayer : what do you think? Should we re consider and re-implement the scroll animation?

luke-m commented 4 years ago

I agree but I find it a bit late to make this decision.

clemensf commented 4 years ago

@luke-m yes, I also think it‘s too late to decide that now. If we get more replies like Jureks, maybe a follow-up project can re-design that section.

jurekbarth commented 4 years ago

@clemensf @luke-m I'm not against the animation, it's just about how the scroll itself behaves. I as a user expect that the scroll behaves as it normally behaves. I would really appreciate if you could reconsider your decisions, based on the article i've mentioned before. Otherwise just google "scroll hijacking" and you will find a lot of good reasons why it's poor UX.

luke-m commented 4 years ago

@jurekbarth we talked about the issue and came to the conclusion to remove the scrolljacking while keeping the animation.
Short background: in the past, we already came to a point where we had the animation implemented without any scrolljacking but then it felt like you needed to scroll too "precisely" to the text sections between the transitions to get to the information that we want to provide. That's why we decided to implement the scrolljacking to guide the user to the information. We were already aware of the pitfalls of this technique when we decided on it initially but we weren't too concerned. Now that we see the end product and also the technical difficulties this produces, we decided to move away from it again. We're going to try solve the issue that I described earlier (information "frames" being lost within the animation) by making the actual frame-duration of the text "slides" longer. Thanks for your feedback, it's highly appreciated.