This repository has been archived by the owner on Jun 3, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 144
datepicker doesn't open if date values are None
#115
Labels
Comments
@chriddyp |
xblad
added a commit
to xblad/dash-core-components
that referenced
this issue
May 16, 2018
Added current date as the last resort for initialVisibleMonth in DatePickerRange.react.js (issue plotly#115)
xblad
added a commit
to xblad/dash-core-components
that referenced
this issue
May 16, 2018
Added current date as the last resort for initialVisibleMonth in DatePickerSingle.react.js (issue plotly#115)
xblad
added a commit
to xblad/dash-core-components
that referenced
this issue
May 16, 2018
Added current date as the last resort for initialVisibleMonth in DatePickerSingle.react.js (issue plotly#115)
xblad
added a commit
to xblad/dash-core-components
that referenced
this issue
May 22, 2018
Added current date as the last resort for the initialVisibleMonth property of the component in DatePickerRange.react.js and in DatePickerSingle.react.js (issue plotly#115)
xblad
added a commit
to xblad/dash-core-components
that referenced
this issue
May 22, 2018
Added current date as the last resort for the initialVisibleMonth property of the component in DatePickerRange.react.js and in DatePickerSingle.react.js (issue plotly#115)
valentijnnieman
added a commit
that referenced
this issue
Nov 21, 2018
* Fix for datepicker initial month Added current date as the last resort for the initialVisibleMonth property of the component in DatePickerRange.react.js and in DatePickerSingle.react.js (issue #115) * Fix formatting * Fix DatePickerSingle formatting
Hi Chris, in the above example what i am facing issue is :
The problem with the initial approach is:
|
issue has been fixed in
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Originally reported in https://community.plot.ly/t/datepickerrange-clearable-in-tabs-not-working-as-expected/6850/4
Quite a few error messages in the console
![image](https://user-images.githubusercontent.com/1280389/33187985-ec8ca686-d063-11e7-9ce2-e4cfae76a676.png)
The text was updated successfully, but these errors were encountered: