-
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
setAllowScrolling(false) confusing docs + hide arrows when disabled horizontally #4256
Comments
Where? 🤔 What are you trying to achieve? |
just to be clear: the main problem is that fullpage_api.setAllowScrolling(false); disables the arrows for the slides. please see the jsfiddle. it's a fork of your own fiddle with further options. and that's not a question but a bug: if you show the arrows, they must work : - ) on top of it, the places where you suggest to use `setAllowScrolling(false) are:
you might be setting a random option, to show that option can be set through the API. not really a question either. personally, i'm hesitant to get involved in this ticket and help you improve your library. the unclear license conditions almost made me not to use it at all. (again, to be clear: making it GPL3 with no string attached would help; a liberal license with open core would be even better) you know: the research needed for filling this ticket, solved the issue for me... so i don't have a personal interest in it.... |
Perhaps I need to update the docs to clarify it. So, no, you don't have to use
What would you suggest to use instead on the docs? Answering your two questions:
I'm not suggesting it.
What exactly do you think we have to fix?
Fair enough. |
i might not been clear enough:
disables the horizontal scrolling in the slides but the arrows are still showing. please have a look at the jsfiddle attached. this is a bug. and this is the main part of this ticket. |
concerning the documentation: in my eyes you should show how to initialize fullPage with the minimal needed code. in a second snippet you can then set some random options and tell the user what they can achieve with it. As an example: Initialization with Vanilla JavascriptAll you need to do is call fullPage.js before the closing new fullpage('#fullpage', {
//options here
}); You can set options both by adding values to the optional object or by calling the API functions: new fullpage('#fullpage', {
autoScrolling:true,
scrollHorizontally: true
});
//methods
fullpage_api.setAllowScrolling(false); The first call enables this and that, with the second one you disable blah. |
It never intended to hide the arrows.
Noted! We'll improve the docs in the next release. Thanks! 👍 |
Docs improved! |
Fixed on v4! 👍 |
Description
The documentation suggests to add:
after fullPage has been initialized.
This leads to two issues:
While the second effect might be wanted, the first one is rather disturbing and it took me sometime to understand why the arrow buttons did not work.
I would be glad if:
Link to isolated reproduction with no external CSS / JS
https://jsfiddle.net/tyohu1gj/
Steps to reproduce it
AllowScrolling
Versions
the newest distributed fullPage.js.
The text was updated successfully, but these errors were encountered: