3 ms·
This page loaded quickly for the amount of stuff it has on it, but it scrolls slowly in some parts (and really slowly in one, the part after WORLD WIDE WEB, wit
by yladiz 9y ago
This page loaded quickly for the amount of stuff it has on it, but it scrolls slowly in some parts (and really slowly in one, the part after WORLD WIDE WEB, with the CERN Welcome screens). It also pegs my CPU the entire time. I assume this is due to some of the animations happening constantly throughout the page, even when things are not on screen, since this happens with constantly running CSS transitions on any website. Since this is done in Javascript, why can't they detect if the specific element is on screen and enable/disable the transitions happening for it? A page like this is uncommon since it's a showcase of the tech but I would imagine this would save a lot of headaches for future designers when designing multiple animations on a page (or at least give the option to "stop when not on screen" for an animation).
- leonardsouza 9y agoHey, yladiz! I'm the tech lead on IX2. Are you using Safari by chance? The part after WORLD WIDE WEB is a known issue and we are working on it, but it works smoothly in Chrome (if you could give it a try). We are also looking at how we can best cull off-screen animations to minimize CPU usage. Thank you for the great feedback! Best, Leonard
- alooPotato 9y agoUsing chrome on a brand new macbook pro and scroll is a little janky everywhere on page.
- leonardsouza 9y agoWhich site are you experiencing the jank? https://webflow.com/interactions-animations https://webflow.com/interactions-animations or http://webflow.com/ix2 http://webflow.com/ix2
- alooPotato 9y agoSorry this one: https://webflow.com/interactions-animations https://webflow.com/interactions-animations
- yladiz 9y agoIn that case I'm a little confused. If you're showcasing this new technology but it only works well in one browser or has issues in other browsers (Safari lags and Firefox has some issues as well, not sure about Edge), why not wait until it's more ready in the others before showcasing it, especially if you're creating a new version? It doesn't have to be perfect, but if this is your showcase and it only works well in one browser (and it doesn't say this in the page), it looks kind of bad in my opinion. I thought we were beyond the "Works well in Chrome" phase of web design... I'm not critiquing the actual page, which I think is really slick and well designed, just the process for creating this new technology and forcing customers to deal with this issue implicitly if they use certain animations.