React Fullpage.js flickers when scrolling on the first load of the site

[shielakn]

Hi! I hope someone can help me out with this problem...

Here's a screen capture of my site whenever I scroll on the first load of the page: https://www.screencast.com/t/aEhZvtZS

It seems like before it goes to the next section, it goes to the top then quickly goes back to the actual section.

I built the site using Gatsby and I'm not sure what's going on. It doesn't happen when I'm on my localhost but once I pushed it to a staging site, I see the issue.

// fullpage options
const decadeSectionOptions = { anchors: decadeAnchors, paddingTop: '110px', scrollBar: false, scrollingSpeed: 800, lazyLoading: true, autoScrolling: true, continuousVertical: true, recordHistory: true, };

// gatsby-browser.js
export const shouldUpdateScroll = ({ routerProps: { location }, getSavedScrollPosition }) => { if (location.search) { window.setTimeout(() => window.scrollTo(0, 0), 100); } if (location.hash) { return false; } return true; };

This is the only error I get on my console:

Please help.

Thanks!

[alvarotrigo]

Can you provide an isolated reproduction in Codesandbox with no CSS or JS files external to fullPage.js and the minimum amount of HTML code? Use empty sections with a single heading unless strictly necessary for the reproduction.

This is the only error I get on my console:

Did you try clicking on the link provided by the error? :)
Basically, it tells that you need a license if you plan to use it in non open-sourced projects compatible with GPLv3 license:
https://alvarotrigo.com/fullPage/pricing/

[shielakn]

Thanks, @alvarotrigo for the quick reply!

I'll try purchasing the license and see if it solves the problem.

I'll keep you posted! Thanks again.

[alvarotrigo]

The license won't solve it. Only get it when you are sure you'll be using fullpage.

On Fri, 10 Sep 2021 at 22:22, shielakn ***@***.***> wrote: Thanks, @alvarotrigo <https://github.com/alvarotrigo> for the quick reply! I'll try purchasing the license and see if it solves the problem. I'll keep you posted! Thanks again. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#270 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANASVT3WNNVGPHZTXYPKMLUBJSHVANCNFSM5D2AIWVQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- * Alvaro Trigo alvarotrigo.com <http://alvarotrigo.com> [image: Follow me on Twitter!] <https://twitter.com/IMAC2> Check the new fullPage web builder! <https://fullsnap.io> *

[shielakn]

Oh I see. Here's a link to isolated reproduction: https://codesandbox.io/s/react-fullpage-js-example-forked-5di44?file=/src/index.js

I can't seem to reproduce whatever is happening on the site (https://www.screencast.com/t/aEhZvtZS) whenever it's on the production environment.

[alvarotrigo]

I can't seem to reproduce whatever is happening on the site (https://www.screencast.com/t/aEhZvtZS) whenever it's on the production environment.

The whole purpose of the isolated reproduction is trying to reproduce the issue :)
Without an isolated reproduction it will be difficult for me to check it out.