Testimonials are good on my laptop here, but I do notice that the scrollbar is near the bottom of the page.
Does your scroll bar hit rock bottom at Testimonials due to having a larger screen? If so, you will want to add more blank space at the bottom of the page.
Added triple the amount and testimonials isn’t working still. Neither are working.
Edit-On my screen, the scrolling is stopping 2-3px short of where the actual div starts. E.g. if you click testimonials, that gray/white line? I see a 3px of gray under the blue sticky nav and if I scroll down 3px, then testimonials activates in the menu. Clicking testimonials doesnt’ update the position. LIke, 2nd and 3rd click does nothing. I dunno whether I have too much content and it’s not reading it right, or what…
Edit2 - Wondering whether I should just use a new scroll JS script…
I did mention that if I remove some LI items from featuers, it does read correctly. So that’s why I am suspecting too much content is a factor here. Something along those lines…Also removing -pop and -opacity (scrollflow) doesn’t seem to be any sort of factor, unlike last time with slide-bottom/top scrollflow.
Righto. The Scrollit page seems to work well as designed, so it’s just a matter of figuring out what else with your page is interferring.
This can be done by starting with a simpler version of your page that works, and replacing parts of it with what you currently have until the problem reveals itself.
Before going to extreme efforts though, first make sure that your libraries are up to date.
The off-by-one issue was known about and fixed a few years ago.
After you have updated and are using the most recent versions of the library files that you’re using, only if the problem still persists should we investigate further.
jQuery - 2.x version. Definitely up to date.
Sticky Plugin - Just updated it. Had a 3 year old version but apparently 2 days after I put the plugin in, he updated the 3 year old code. No change once updated
Scrollit - Found out I was on 1.0.1 and upgraded to 1.0.3 and this seems to have fixed the issue!
That’s great to hear. The solution to the problem is that they had an off by one error. You wouldn’t believe it but they fixed it literally by tacking a +1 on to the scroll position.