Setting min on a number dcc.Input makes the native spinner (or arrow keys) erase the value — it gets cast to None. This is the same symptom as #3689, which was fixed and closed, but it reproduces again on dash 4.4.1.
Reproduction
fromdashimportDash, dcc, htmlapp=Dash()
app.layout=html.Div([
dcc.Input(type="number", value=40, min=0), # spinner/arrows blank the valuedcc.Input(type="number", value=40, step=1), # works fine
])
if__name__=="__main__":
app.run(debug=True)
Click the up/down spinner (or focus + arrow keys) on the first input → the value clears. The second input is unaffected.
Notes
- Only
min triggers it; step and max alone are fine. - Browser/spinner-dependent — did not reproduce in headless Chromium.
Environment
Setting
minon a numberdcc.Inputmakes the native spinner (or arrow keys) erase the value — it gets cast toNone. This is the same symptom as #3689, which was fixed and closed, but it reproduces again on dash 4.4.1.Reproduction
Click the up/down spinner (or focus + arrow keys) on the first input → the value clears. The second input is unaffected.
Notes
mintriggers it;stepandmaxalone are fine.Environment