-
Notifications
You must be signed in to change notification settings - Fork 82
MenuItem: change submenu prop to accept a ReactNode #7353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
I've discussed this with @harpalsingh and UX are keen for support to be added cc @ljemmo |
happy from a DS perspective to add support for this @edleeks87 we hav a DS / Carbon ticket on our backlog to add support. |
FE-7278 |
tomdavies73
added a commit
that referenced
this issue
Jun 6, 2025
The `submenu` prop on `MenuItem` now accepts a node, which ensures consumers can create complex compositions for the title with non-interactive elements when the `MenuItem` has a submenu fix #7353
14 tasks
tomdavies73
added a commit
that referenced
this issue
Jun 6, 2025
The `submenu` prop on `MenuItem` now accepts a node, which ensures consumers can create complex compositions for the title with non-interactive elements when the `MenuItem` has a submenu fix #7353
tomdavies73
added a commit
that referenced
this issue
Jun 9, 2025
The `submenu` prop on `MenuItem` now accepts a node, which ensures consumers can create complex compositions for the title with non-interactive elements when the `MenuItem` has a submenu fix #7353
tomdavies73
added a commit
that referenced
this issue
Jun 9, 2025
The `submenu` prop on `MenuItem` now accepts a node, which ensures consumers can create complex compositions for the title with non-interactive elements when the `MenuItem` has a submenu fix #7353
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I want the submenu prop on the
MenuItem
component to accept a ReactNode so that I can use thePortrait
component as part of the title of a submenuSuggested solution
Allow submenu to accept ReactNode
Demo URL
No response
Alternatives
No response
Additional context
No response
Confidentiality
The text was updated successfully, but these errors were encountered: