New min/max dates for pickers in containers require hide and show #432
Comments
sobelk2
changed the title
|
Good call, I'll take a look at this. Should be an easy fix. |
|
Thanks! |
rikkert
pushed a commit
to rikkert/Pikaday
that referenced
this issue
Nov 13, 2015
DylanFM
added a commit
to DylanFM/Pikaday
that referenced
this issue
Mar 2, 2016
* master: (44 commits) Make disabled button not clickable in IE 10 and below [closes Pikaday#288] add formatStrict to Configuration section of README set default value for formatStrict option to false add options flag for strict date parsing with moment Add example to show days in next and previous months. Add simple disable day optional function example. don't change the container example correct data attributes for days in next and prev months Don't set pointer-events: none for days outside current month Show days in next and previous months Release 1.4.0 [Pikaday#410] fixing invalid selector for next and prev buttons redraw after setMinDate() and setMaxDate() - fixes Pikaday#432 remove data after pikaday destroy - fixes Pikaday#382 don't change the container example correct data attributes for days in next and prev months Release 1.4.0 redraw after setMinDate() and setMaxDate() - fixes Pikaday#432 [Pikaday#410] fixing invalid selector for next and prev buttons Add triangle theme example. ... Conflicts: scss/pikaday.scss
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a picker rendered into a container, and I routinely change
minDateandmaxDateusingpicker.setMinDate()andpicker.setMaxDate(). However, by default, the newminDateormaxDatedoes not take effect until I navigate to a new month in the picker. The workaround for this is to hide and show the picker immediately after setting a newminDateormaxDate. I do not believe this should be necessary. This bug only occurs for pickers rendered into a container.The text was updated successfully, but these errors were encountered: