Lukas Tyla

The focus management needs looking into. - Focus the field - change day with arrows - press `ArrowRight` -> focus jumps to `year` (and in case of date range field...

Regarding accessibility, this, to me, seems like an implementation very similar to the follow [spin button example](https://www.w3.org/WAI/ARIA/apg/example-index/spinbutton/datepicker-spinbuttons.html). I'd say we could implement the same a11y behaviour (of course with a...

Arrow (Up & Down) navigation for month field in letters only works after any month value has already been initialised. Clicking `ArrowDown` when **January** is selected and date is invalid...

[Clearable](https://deploy-preview-5504--material-ui-x.netlify.app/x/react-date-pickers/date-field/#customize-the-input-props) example does not work correctly. It does not reset the value in the component.

[Time format/input](https://deploy-preview-5504--material-ui-x.netlify.app/x/react-date-pickers/date-field/#customize-the-date-format) does not seem like it wants to cooperate. 🤔 https://user-images.githubusercontent.com/4941090/185811088-f350b506-824e-4115-8a8a-93df947d0235.mov

> > [Clearable](https://deploy-preview-5504--material-ui-x.netlify.app/x/react-date-pickers/date-field/#customize-the-input-props) example does not work correctly. It does not reset the value in the component. > > I had a dumb bug where I did not use the...

@flaviendelangle What do you think about adding the following diff? It adds management of `Home`, `End`, `PageUp` and `PageDown` keys [mentioned here](https://www.w3.org/WAI/ARIA/apg/example-index/spinbutton/datepicker-spinbuttons.html) as well as some function name alignment. **Note**:...

@flaviendelangle Nitpick, but consider ignoring [`keyCode` field as it's deprecated](https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/keyCode). `code` and `key` should be the ones we care about. In any case, I double checked and can confirm that...

@samfromaway Do I understand your use case correctly? Do you need to make the `DateRangePicker` take the full width of the container? Would maybe simply adding `fullWidth` to the `TextField`...

Fixed with #6096