Lukas Tyla

> > > And we can't do 2 columns on the demo because of the range pickers who take too much space. > > > > > > I would...

> > For range picker case - if we need two inputs for the demo, then sure, put them in different rows, but if we could have a single input...

Hello @TheRealCuran We've just recently released (v5.0.2) quite a big overhaul of pickers styling in both `themeAugmentation` (TS) side and adding classes to various components missing them. I've tried replicating...

@TheRealCuran Sorry for causing confusion with `sx` solution. I probably mistakenly tested it with `StaticDatePicker` where it would work. In usual `DatePicker` the `sx` prop won't work as it is...

> Yeah, that is basically what this feature request is about: provide a way to style those dynamic parts too through sx (I don't mind if I need to use...

I see, in such case, I'd say that your best bet with the current implementation is the following snippet: ```jsx // overrides style in desktop version PaperProps={{ sx: { '.MuiPickersCalendarHeader-label':...

> Pushing this into the componentsProps (or in this case specialised properties on the picker) has the benefit of clearly separating where a style should be applied. I'm not sure...

This does make total sense to me. 👍 Having less burden on our side managing dates is better for code stability and clarity. As mentioned in the RFC - developers...

There will be various ways on how to apply styling after the next release, I'll look into providing a most appropriate example to the author a bit later.

The styling of date range picker popper is still a bit strange due to it being wrapped in [this div](https://github.com/mui/mui-x/blob/master/packages/x-date-pickers-pro/src/DateRangePicker/DateRangePickerView.tsx#L267) Regarding `styleOverrides` on `MuiDateRangePicker` not being applied - the issue...