-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
DropdownMenu V2: add support for rendering in legacy popover slot #56342
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes to Storybook will be removed before merging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here, I'll undo these changes before merging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, and tests well based on your instructions 🚀 🚢
I am going to revert this PR according to what discussed in #56482 |
Part of #50459
What?
This PR introduces changes that allow the the new experimental version of
DropdownMenu
to render in the same slots as the legacyPopover
-based components (including current stableDropdownMenu
)Why?
For better backwards compatibility between the new and the legacy version of the component
How?
slotName
prop, or via the popover slot name contextTesting Instructions
DropdownMenu
component. Open the dropdown menu and make sure that the menu is rendered correctly in the popover slot component (you can do so by inspecting the DOM and comparing it against the default story)DropdownMenu
component. The two components should behave the same way when picking the solt in which to render their popover.