Flavien DELANGLE

@joserodolfofreitas Didn't we already discuss it several time ? As mentioned on Monday, Telerik dropped this behavior on their last major because it was to much pain to maintain. So...

@alexfauquette Same bug on `next`, but I'll have a look on this PR since the impacted code moves a lot

Should be fixed, I'll add tests for the digit editing (which is basically not tested for now)

> If we could use the '/' (or whichever character used by the user on the date format), that'd be a nice improvement. You can It could be improved to...

@apenab @DanielAndrews43 @gl-aagostino Could you give me a reproduction case on Codesandbox ? I tried a few things but I always have 35-50 calls to `shouldDisableDate` This [template](https://codesandbox.io/s/date-and-time-pickers-forked-72wwl3?file=/src/App.tsx:0-770) could be...

Without a reproduction case it's hard to to a diagnostic. Are you passing the same props to our component both in your application and in the codesandbox ?

The version should be respected yes Can you link me your codesandbox ? If you successfully reproduce it locally on an empty repo (with CRA or Next.JS for instance) I...

Yep, #6146 should close the problem :+1:

The fix has only been done on the v6 alpha. But it should definitely be back-porter to the v5 releases, I'll do it :+1:

With the new field components, this problem will be very different. If we try to solve it, we should have them in mind too.