Starting dash-core-components==1.16, there is a new weird behaviour of dcc.DatePickerRange . With max_date_allowed enabled, when a user selects a start date, then, the disabled day will become unmarked (but user cannot select on it, it seems that only the CSS associated with being disabled has been removed.)
The behaviour does not show up with Dash==1.19.0 and dash-core-components==1.15
For example, the April 16th color will change if I select any start day(even though I cannot select 16th)
Here is the code to reproduce the issue:
import dash
import dash_core_components as dcc
import dash_html_components as html
app = dash.Dash(__name__)
server = app.server # expose server variable for Procfile
app.layout = html.Div(children=[
dcc.DatePickerRange(
id='date-picker',
clearable=True,
initial_visible_month="2022-04-01",
max_date_allowed="2022-04-15",
minimum_nights=0,
disabled_days = ["2022-4-06","2022-04-07","2022-04-08"]
),
])
if __name__ == '__main__':
app.run_server(debug=True)
Starting
dash-core-components==1.16
, there is a new weird behaviour of dcc.DatePickerRange.
Withmax_date_allowed
enabled, when a user selects a start date, then, the disabled day will become unmarked (but user cannot select on it, it seems that only the CSS associated with being disabled has been removed.) The behaviour does not show up withDash==1.19.0
anddash-core-components==1.15
For example, the April 16th color will change if I select any start day(even though I cannot select 16th)
Here is the code to reproduce the issue:
with Dash==2.3.1 and dash-core-components==2.0.0