-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sections with fp-noscroll won't trigger next section/slide on scroll on mobile #4505
Comments
It can be reproduced here from a phone (Chrome, Safari...) with fullpage.js 4.0.15: HTML code: <div id="fullpage">
<div class="section fp-noscroll">
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
<h1>Section 1</h1>
</div>
<div class="section fp-noscroll">
<div class="slide" data-anchor="slide1">
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
<h1>Section 2</h1>
</div>
<div class="slide" data-anchor="slide2">
<h1>Slide 2.2</h1>
</div>
</div>
<div class="section">
<h2>Section 3</h2>
</div>
</div> JS new fullpage('#fullpage', {
sectionsColor: ['yellow', 'orange', '#C0C0C0', '#ADD8E6'],
// Get your license at https://alvarotrigo.com/fullPage/pricing/
licenseKey: 'YOUR LICENSE KEY HERE '
}); The 1st section containing scrollable works as expected. However, in the 2nd section, this won't happen. Same happens when using keyboard navigation. |
This has been fixed on the new version 4.0.16! 🥳 |
I still need to test it on different environments so I'll update the issue with more details later on.
The text was updated successfully, but these errors were encountered: