Alexandre Fauquette

Don't know if we should merge it or let's wait for #6381

+1 for removing the `TInputDate` The less type with have the less confusing it is for developers and us

A workaround could be the following one ```jsx PopperProps={{ sx: { "& .MuiPaper-root": { backgroundColor: "lightgreen" } } }} ``` https://codesandbox.io/s/basicdaterangepicker-demo-mui-x-forked-rg5ocw?file=/BasicDateRangePicker.js:603-731 But the clean way to solve it is clearly...

It will work as long as we use a `Paper` inside a `Popper` The only breaking change that I can imagine is we remove `PopperProps` in favor `componentsProps: { popper:...

Not really, it's on the todo list, but for now, maintainers are quite busy with some features implementations, maybe some users of the MIT will bring contributions on this topics...

Closing this one in favor of smaller issues about remaining aspect to test: #6552 #6551

Sounds like you have a problem with your `loading` state synchronization. You use `tableData` for providing the rows, but use `data.rows.length` in your loading state. The following diff seems too...

I get confused by the fact you wait one second before setting `loading` to `true`. Effectively it seems the PR #4334 did not solved this one

@elijahkimani instead of passing `mask=""` you can add `disableMaskedInput` to you component. This will have the same effect ## What append internally As noticed by @AlessandroDG the code tries to...

Just checked with @joserodolfofreitas we can mark them as done. I'm opening the PR