Flavien DELANGLE

https://user-images.githubusercontent.com/3309670/183668935-f57ded52-f24e-4da8-93fc-fb01b466f916.mp4 I'm playing with the range version It add quite a lot of complexity, but it's totally doable with the Telerik approach

@LukasTy there are probably quite a lot of similar problems yes If you want to have a look feel free :+1:

@LukasTy I rewrote the arrow up / down edition on invalid dates, it should be a lot better now

@gerdadesign > Also noting a pattern I've seen of the placeholder labels giving an indication for how many digits the input format is looking for: MM/DD/YYYY or DD/MM/YY For now...

> [Clearable](https://deploy-preview-5504--material-ui-x.netlify.app/x/react-date-pickers/date-field/#customize-the-input-props) example does not work correctly. It does not reset the value in the component. @LukasTy I had a dumb bug where I did not use the controlled value...

I applied @LukasTy suggestion to handle other keys edition

> It sounds easier to customize and to have screen readers Why is that ? For customization, Telerik approach allows users to very easily use there own input whereas in...

> For example in the [date-io adapter for date-fns](https://github.com/dmtrKovalenko/date-io/blob/77f89b4859d228ed8f34c740e3defc78d52bdba1/packages/date-fns/src/date-fns-utils.ts#L57), we have the following encoding. We should be able to do the same thing as the `getFormatHelperText` methods in the adapters...

I confirm that it does seem to work for `date-fns` at least.

For Luxon it's a work in progress (I just tried to use there new method but I still have some issues), but yes it should work in the near future....