-
-
Notifications
You must be signed in to change notification settings - Fork 32.7k
Open
Labels
design: material youon holdThere is a blocker, we need to wait.There is a blocker, we need to wait.scope: menuChanges related to the menu.Changes related to the menu.
Description
Duplicates
- I have searched the existing issues
Latest version
- I have tested the latest version
Summary 💡
This issue is to track the work for adding the Menu component to @mui/material-next, moving forward with the Material You effort (#29345)
Material You Chip specification: https://m3.material.io/components/menus/overview
Migration Guide steps
- Copy component files from material (v5) to material-next: PR
- Remove deprecated components and componentsProps props (not applicable, the component already uses the
slots
&slotProps
props - Migrate component to Typescript PR
- Refactor component to use Base UI’s hook if it exists PR
- autoFocus should be configurable PR
-
there shouldn't be a need in the test to focus the menu so that the keyboard keys can be tested- this is due to the fact that auto opened menus shouldn't steal focus. We need to document this in the migration guide - select menu variant support (in Base UI the menu items have no notion of selection, this will need to be changed)
- Ensure slots & slotProps have keys for each slot
- Drop support for ThemeProvider in favor of CssVarsProvider
- Implement Material You design specs
- Add component playground to v5 docs
- Refactor styles to use component CSS Variables
Note: If a task is marked as [WIP] it means someone is working on it
Metadata
Metadata
Assignees
Labels
design: material youon holdThere is a blocker, we need to wait.There is a blocker, we need to wait.scope: menuChanges related to the menu.Changes related to the menu.