Horizontal snapping sections using GSAP
As part of the answering question in the forum, I am writing this blog to help me and other people.
Horizontal snapping sections (simple) using GSAP. This pen is created by Greensock. Below are the written steps on how to go about creating this with the explanation of what each property does.
See the Pen Horizontal snapping sections (simple) - ScrollTrigger by GreenSock (@GreenSock) on CodePen.
- Create a container in which there are 6 sections(called panel).
- The width of the container is 600%, 100% for each section. Also display property is set to flex, which by default arrange its children row wise (horizontally). Then there is
flex-wrap: nowrapwhich will make sure sections will not come down in the next row.
- In body, overscroll-behavior: none; which will not allow scrolling. Basically overriding scrolling behaviour.
- In body Height is 100vh to make it full viewport vertically. And container is 100% so as to stretch to full viewport height.
- By doing the above there will be first section on the page full width and height without any scroll. All the other sections are on right side of this but not visible.
- To make it horizontally scrollable will use GSAP and scrollTrigger.
- Select all the sections and store in an array using gsap.utils.toArray(“.panel”)
- For each section add xPercent in negative, this will take section in left direction. So 100 * section number will make first section go 100% second section 200% and so on.
- Scrolltrigger is set to trigger container and pin true. And there is no start value define so scrollTrigger will grab the default value which is
start: "top top"in this case. Which means it will start when top of the container meets the top of the scroller. Scrub is set to 1, which is to link scrollTrigger to scrollbar and take 1sec for it to respond.
- End value is vertical scrolling based on how wide the container is so it feels more natural. One can change the end value to manipulate the speed of scrolling.
- Snap is to make scrolling momentum based means as user stops it should not stop simply but stop after certain momentum is applied. The description written in first section is very clear which is: “It also dynamically snaps to the sections in an organic way based on the velocity. The snapping occurs based on the natural ending position after momentum is applied, not a simplistic “wherever it is when the user stops”.