-
-
Notifications
You must be signed in to change notification settings - Fork 329
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
Popover component event handling #2961
Comments
@Hugos68 I know you've got limited availability right now, no worries if you don't get back to this until later, but either way I could use your help. Currently in the Tooltip component for example we have this: <button {...api.getTriggerProps()} class="{triggerBase} {triggerBackground} {triggerClasses}">
{@render trigger?.()}
</button> So Zag is spreading it's own attributes to the button as one would expect. And if I log the output of So there is already an As far as the API Zag exposes, there doesn't appear to be anything related to the button click event. They have Just thought I'd reach out to you before I ask Zag about this. Any ideas are welcome. |
Zag exposes a We can definitely support this if we want to 👍 |
@Hugos68 ok that actually looks fairly straight forward. I'll look to get that setup today. Thank you! |
@phamduylong this would be a great candidate if you're looking for something to work on! We'll just need to implement an |
On it. |
Describe the feature in detail (code, mocks, or screenshots encouraged)
Zag's popup elements are based on a
button
element which causes problems when you want to addonclick
events and such, or when you want to wrap an existing button with aTooltip
.It would be great to be able to pass event handlers to Zag's
button
since it cannot be removed to allow users to decide the markup themselves.What type of pull request would this be?
Enhancement
Provide relevant links or additional information.
#skeleton-next talk in Discord: https://discord.com/channels/1003691521280856084/1191790107867488316/1306346031528673290
The text was updated successfully, but these errors were encountered: