Replies: 5 comments
-
I think the best option would be to use the context menu in a custom component and just use your component for each item and pass the data you need for the trigger through a prop |
Beta Was this translation helpful? Give feedback.
-
^ what @JYLN said. I'll usually do something like |
Beta Was this translation helpful? Give feedback.
-
Is there a fix preventing the multiple context menus showing up that will be released soon? I see that #563 says fixed in "next", but it looks like that is a more substantial longer term branch? |
Beta Was this translation helpful? Give feedback.
-
Any chance a fix for the multiple context menus can be released next week? I like this library, but if not, I'm going to have to go with a different one. 🙁 |
Beta Was this translation helpful? Give feedback.
-
Please 🙏 |
Beta Was this translation helpful? Give feedback.
-
Describe the feature in detail (code, mocks, or screenshots encouraged)
I might be missing something obvious, but I couldn't figure out how to do this (if it's possible) from the docs:
I have a list of items that I would like to have a
ContextMenu
for, for example:However, I can't seem to determine which of the items in the list triggered the context menu to show, or (ideally) how to pass custom data to the
ContextMenu.Content
orContextMenu.Item
so that it knows which "think" to be acting on.It seems like one way to sort of work around this is to create a separate
ContextMenu.Root
and entire set ofContextMenu.Item
for each thing, but that seems like a lot of extra elements are being created, and it also seems to allow multipleContextMenu
s to be shown simultaneously, which is definitely not what I want.What type of pull request would this be?
Enhancement
Provide relevant links or additional information.
No response
Beta Was this translation helpful? Give feedback.
All reactions