[TextField] InputProps vs inputProps confusion

The TextField (nor Input) does not pass the step property through to the input as a step attribute.

• I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

<Textfield type="number" step="0.01" /> renders a <input type="number" step="0.01" />

Current Behavior

<Textfield type="number" step="0.01" /> renders a <input type="number" />

Steps to Reproduce (for bugs)

1. Go to https://codesandbox.io/s/lyxw254vz9
2. Click on the up/down arrows on right of textbox and see differences in behaviour

Context

Your Environment

Tech	Version
Material-UI	1.0.0.rc0
React	16
browser	Safari - Not possible to insert 0.xx number and pass validation. Chrome accepts 0.xx number and validates it but step is still by unit

[sakulstra]

didn’t test, but I guess you should use <TextField inputProps={{step: 0.01}} /> instead? It#s a prop on Input instead of TextField.

update: sry, just checked your sandbox 😄 you already came up with that. What#s the problem with the inputProps solution? I guess there are more props we don’t pass down automagically: https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement so it might be consistent to not do it at all.

[oliviertassinari]

@mnajdova I’m not sure what the right terminology is. From my perspective, props are first applied to the element, then made available in the component’s render method.

At this point, I would either propose:

1. A better documentation https://github.com/mui-org/material-ui/issues/11377#issuecomment-812101655

1. Renaming input → htmlInput to match the htmlFor (React), htmlColor (Icon component) props convention.

We can likely do these two changes.