We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The plugin is awesome and we're using it.
However - when a users navigates - let say 5 months ahead - and then selects range - the calendar goes back to the initial month.
I debugged the plugin's source code and saw that when we use "setRange" - it automatically calls:
(...).datepicker('refresh'); (...).datepicker('setDate', null);
The latter is what brings the calendar back to it's initial month. But we do not want this - our user has navigated months ahead.
Why is this behavior in the first place? ... and can we avoid it?
PS: We do not automatically close the calendar, as in the official examples.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The plugin is awesome and we're using it.
However - when a users navigates - let say 5 months ahead - and then selects range - the calendar goes back to the initial month.
I debugged the plugin's source code and saw that when we use "setRange" - it automatically calls:
The latter is what brings the calendar back to it's initial month. But we do not want this - our user has navigated months ahead.
Why is this behavior in the first place? ... and can we avoid it?
PS: We do not automatically close the calendar, as in the official examples.
The text was updated successfully, but these errors were encountered: