Lukas Tyla

It looks like the main problem was the fact, that the `className` was being applied to both the inputs wrapper as well as the popup, creating problems. In v6 that's...

Yes, it could potentially be an issue, but that would require some interesting setup, where some package would have either a `specific` `moment` version or `lower or equal` (

[API documents](https://mui.com/x/api/date-pickers/date-picker/#:~:text=for%20your%20format.-,disableOpenPicker,-bool) this prop and mentions that it controls the rendering of the `open picker button`. Is there a use case you @julianCast are trying to achieve and this behavior...

> Oh I misunderstood the meaning of it. I was trying to disable the opening. I think the first option would make sense : After discussing and investigating this issue...

> think that these are a few last nitpicks to iron out before merging: Sorry, you can ignore this one. It's already on "master" and can be solved separately. 👌

This was a bit annoying monorepo bump due to a few breaking changes 🙈 I'd love an eye from @mui/xgrid on the Data Grid test updates/changes. 🤔

I've noticed that my previous workaround to have legible playgrounds when in dark mode [has been reverted](https://github.com/mui/material-ui/pull/35969/files#r1089572951) due to some issues. What do you guys @flaviendelangle @cherniavskii think about this...

> Do you think the word `template` is easy enough to understand ? > `TValue` is a generic, I think all the templates we are using describes generics (but that's...

@flaviendelangle I've looked into Teleric and Spectrum and they both seem to follow the suggested practice of emitting an `onChange` event on every input change. It does make sense, because...

Thank you for the investigation @gerdadesign I've left comments to express my opinion and some clarifications. Maybe @flaviendelangle @alexfauquette or someone else would have anything to add to it?