Flavien DELANGLE

Simpler reproduction case https://codesandbox.io/s/date-and-time-pickers-forked-vtepj6?file=/src/App.tsx Thanks for your detailed example :+1:

We discussed it with @joserodolfofreitas, it feel like we all agree that option 2 (see PR description) is the best here

@orforio, @Methuselah96, @sheuertz, @a2441918 Could some of you test this fix on your applications ? You just have to put the following line in place of the `@mui/x-date-pickers` in your...

I will release it in tomorrow's patch I let it open until then in case some other want to test and to give feedbacks :+1:

> 3. Fix the UX to edit the date in the input. When I want to change 18 to 19, as soon as I remove the 8, I'm lost. The...

> @flaviendelangle I had the date field in mind as the "fix" when I wrote this :) :ok_hand: > I'm happy to clarify. Say you have entered your birthdate but...

I guess we have two options 1. We do like the core with a *Migration* section in the nav bar with a "home page" (equivalent of [this page for the...

Thanks for the detailed prototype ! I think we should build this new version with customization in mind. It should be fairly easy to: 1. Add a new section like...

As I understand it, the word `variant` has a very specific meaning in the core packages. It describes a different design for the same component, but with exactly the same...

In term of tree shaking, 2 components is better indeed (not a huge gain compared to the size of the grid though). At first glance I prefer this approach