[discussion] Preparing v8

[flaviendelangle]

This is an umbrella issue that centralizes and lists all the potential improvements that we can consider in MUI X v8. The potential improvements being listed here require breaking changes. We do intend to ship v8 in about 9 months. We plan, as much as possible, to release the next major features in minor versions without breaking changes.

Similar discussion for v7: #7902

Data Grid packages

Breaking changes

• [data grid] Remove the ariaV8 experimental flag #14180
• [data grid] Use new selectors #15478
• [data grid] Deselect row on click by default #15487
• [data grid] Remove the rowPostionsDebounceMs prop #15480
• [data grid] Remove GridOverlays export #15483
• [datagrid] Refactor: make all selectors accept the same argument #11440
• [data grid] Reshape row selection state model #15481
• [data grid] Change the default loading overlay variant #15484
• [data grid] Remove indeterminateCheckboxAction prop #14300
• [data grid] Change row selection propagation defaults #15485
• [data grid] Mark some unstable features stable #15488
• [data grid] Change default TextField variant #15486

Topics to clarify

• Solve issues with slotProps overrides? [RFC] Issues with slotProps overrides #14525

Pickers packages

Decided changes

• [pickers] Remove the PickersMonth and PickersYear component and move their logic inside MonthCalendar and YearCalendar #14474
• [pickers] Remove the re-export from @mui/x-license #14476
• [pickers] Simplify the ownerState on every slot to only pass a small object with valuable information #14475
• [pickers] Make the <input /> version of the fields opt-in #14477
• [pickers] Rename AdapterDateFns into AdapterDateFnsV2 and AdapterDateFnsV3 into AdapterDateFns #14478
• [pickers] Remove utils and value params from translations #14648
• [pickers] Improve and simplify the auto-closing strategy of pickers with a value selected in several steps #9310
• [pickers] Move the range pickers to use the same popper structure as the non-range picker #14786
• [fields] Move the logic of the fields opening to be in the field instead of in the picker #14787
• [pickers] Make the single input field the default field on range pickers #14788
• [fields] Remove UseDateFieldComponentProps and equivalent interfaces #14789
• [pickers] Replace the TDate generic with PickerValidDate in every type / interface #14796
• [DateTimeRangePicker] Change OK button behavior #11829
• [pickers] Is there a way to control the step size sections other than minutes for the field components #13732
• [pickers] Support keyboard entry on mobile #7869
• [Stretch] [DateTimePicker] Use digital clock in all component variants  #14974
• [Stretch] [pickers] Improve PickersDay component gridcell role management #11904

Topics to clarify

• Do we want to keep the TimeClock component as the default UI on mobile or to migrate gradually to DigitalClock?
  We decided to use DigitalClock on all DateTimePicker components to more closely align with the idea and approach of DateTimeRangePicker.
  Created [DateTimePicker] Use digital clock in all component variants  #14974.
• Do we want to revive the effort on [pickers] Update date calendar styling #9276?
  It is almost directly related to MD3 styling.
  We decided to keep it for v9 to align with @mui/material adoption of MD3.
  This would entail both styling as well as updating the Header component to the UI of MD3.
• Can we change the DOM structure of the DateRangePickersDay to have a single HTML element like for PickersDay?
  It is basically the same issue as [pickers] Refactor calendar day cell #14753.
  We can start exploring the feasibility of it.
  However, it's not a necessity for v8, we can deliver it under a feature flag if needed, or keep it for v9.
  StyleOverrides and data state attributes combination was the biggest unclear topic if we go for a semi-base approach of putting the state into data- attributes.
  Would be great to know if MUI Material has a vision of how styling + data attributes will combine when they will use @base_ui components under the hood. 🤔
• [pickers] Field text selection on mouseDown #10048
  It is already the behavior on the accessible DOM structure.
  There is no clear rushing factor to implement it on the input behavior.
  The same behavior is present on other implementations using input (i.e. Kendo).
• Remove minutesStep and unify its behavior with timeSteps (to avoid such confusions: [pickers][TimePicker] minutesStep prop not reflecting in UI intervals #14272)
  [pickers] Is there a way to control the step size sections other than minutes for the field components #13732
• Should we make unstableFieldRef stable?
  We decided to keep it unstable until we use more composition and see if the existing API is sufficient or maybe even redundant.

Charts packages

• [charts] Remove deprecated props #13820
• [charts][RFC] Replace DefaultXxxx by the usage of hooks #13819
• [charts] Provide context-aware types based on props #14340
• [charts] Follow a single naming pattern in context #14028
• [charts] Replace d3-color by CSS filter #13938
• [charts] Pie Chart Positioning #13787

Tree View packages

Decided changes

• [TreeView] Drop TreeItem and rename TreeItem2 into TreeItem (same for useTreeItem2 and all related components) #14767
• [TreeView] Remove the deprecated TreeView component in favor of SimpleTreeView #14768
• [TreeView] Expose the item slots at the tree view level #13867
• [TreeView] Make the label editing and the drag and drop stable #14784
• [TreeView] Move the identation to the item level by default #14785

Topics to clarify

Search keywords: