Fullpage.js: fullpage always advances twice on trackpad scroll - Sierra (mac) and Chrome latest (61)

[danjaworsky]

Description

I couldn't reproduce this until I fired up browser stack and duplicated running Sierra and Chrome 61. Swipe on the trackpad always advances twice.

[alvarotrigo]

I couldn't reproduce this until I fired up browser stack and duplicated running Sierra and Chrome 61. Swipe on the trackpad always advances twice.

Probably issues related with the delay sending the wheel events to the remote machine by using the VPN connection.
I can not reproduce it in the latest Chrome (61) in my Mac.

I'll close the issue until new evidence in real devices is provided.

[danjaworsky]

The issue was sent to me by a user using a real Mac not through browser stack. I couldn't reproduce until I saw it in browser stack.

[danjaworsky]

It def has something to do with how many times the mouse wheel event gets called on trackpad use. I set up a hacky throttle for the mouse wheel event and got it to stop doing it.

[alvarotrigo]

The issue was sent to me by a user using a real Mac not through browser stack. I couldn't reproduce until I saw it in browser stack.

Then it's a duplicate of this issue https://github.com/alvarotrigo/fullPage.js/issues/1654

[danjaworsky]

The scrollingspeed is set to 700 because of all the reading I've already done on this issue - all day looking around through the issues on here, and stackoverflow. It's got me pretty stumped. Thanks.

[alvarotrigo]

The scrollingspeed is set to 700 because of all the reading I've already done on this issue

That's not the case anymore. But in any case, if you read about "kinetic scrolling" and the problem lethargy tries to solve you'll see why.
But as I said, no solution was implemented yet and there's not a proper one out there, just some smart hacks around it that still will fail in some situations.

[danjaworsky]

Ah! Ok thank you. I'll use my throttle function or look at lethargy

On Wed, Sep 27, 2017 at 6:08 PM Álvaro [e-mail] wrote:

The scrollingspeed is set to 700 because of all the reading I've already
done on this issue

That's not the case anymore. If you read about "kinetic scrolling" and the
problem lethargy https://github.com/d4nyll/lethargy tries to solve
you'll see why.
But as I said, no solution was implemented yet and there's not a proper
one out there, just some smart hacks around it.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alvarotrigo/fullPage.js/issues/2921#issuecomment-332669905,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGdCXyJuV-u6433HJkzkZwVMjq_gDLv1ks5smsdwgaJpZM4PmOn1
.

[ProAnastasia]

Have the same issue with fullPage. Furthermore, it appears with magic mouse usage.

[CKMacLeod]

Ugh - just got same bug reported - on Mac Magic Mouse, scrolls two windows per scroll. Can anyone point to a best workaround?

[alvarotrigo]

@CKMacLeod you are probably using a low scrolling speed. Check the demo page, it is using scrollingSpeed: 1000 and you won't get that issue so often. (unless scrolling very fast with the trackpad)

[CKMacLeod]

Thanks - will apply and report!

[CKMacLeod]

Sorry - forgot to confirm that, yes, the low/fast scrolling speed was the problem in this case. I bumped it up to 1000 and the problem went away for the user.

[amityweb]

Is there a solution yet with faster scroll speed? Setting to 500 scrolls twice. Can there not be a timeout on section load or something before waiting for the next scroll?

[alvarotrigo]

@amityweb there is! However we haven't implemented it yet.
The solution is not ideal, as it will force a delay between transitions, around 700 or 800ms, but it will prevent most double scrolls when using fast transitions.

Here's the pull request and the solution I proposed:
https://github.com/alvarotrigo/fullPage.js/pull/3826

It will get implemented in the next release 3.0.9, but meanwhile, you can make the change by yourself :)

[amityweb]

Wonderful I will try that, thanks a lot. I assume the delay is after a scroll ends and before the next starts from a second scroll, in which case should be OK as the user probably is reviewing the section before moving on. I guess its only an issue if someone wants to scroll down the bottom rally fast and so notices these delays but the scroll speed prevents a really fast scroll anyway, and we could put a button on there to get to the bottom or something. We shall see. Thanks.

[alvarotrigo]

I guess its only an issue if someone wants to scroll down the bottom rally fast and so notices these delays but the scroll speed prevents a really fast scroll anyway,

Exactly.

[balsito]

On Macbook pro 2014 and 2015 (15" and 13") it still advances twice on chrome. now on the macbook pro 16 (2019) it doesn´t advance at all on Chrome. on Safari works great.

[alvarotrigo]

@balsito make sure to update to 3.0.9.
If you still having issues then that means you are scrolling too fast :) Try increasing scrollingSpeed value to 1000 or even more. The more you increase it the lower are the chances of getting double scroll on kinetic scrolling devices such as Macbooks' trackpads.

Perhaps we can increase the transitionLapse variable to 1000 to avoid this problem.