You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a button, data-umami-event does not trigger on children elements inside the button. Using Tailwind's p-8 to provide a chunk of padding, and bg-slate-800 is to recognise the padded text:
The expected behaviour should be the same as for normal <a> or <Link> component, where clicking the text/padding triggers the test event. The issue is that when using an external component library such as Flowbite React, it creates the child span element without the ability to pass data-umami-event to the children, which causes the event to not fire.
Database
Umami Cloud
Relevant log output
No response
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered:
Describe the Bug
When using a button,
data-umami-event
does not trigger on children elements inside the button. Using Tailwind'sp-8
to provide a chunk of padding, andbg-slate-800
is to recognise the padded text:With the code above, when you click on the text/padding, the event does not trigger. If you click the button outside the padding, the event triggers.
With the code above, if you set an additional event tag, clicking the text/padding will trigger that event (
test-inside
).The expected behaviour should be the same as for normal
<a>
or<Link>
component, where clicking the text/padding triggers thetest
event. The issue is that when using an external component library such as Flowbite React, it creates the childspan
element without the ability to passdata-umami-event
to the children, which causes the event to not fire.Database
Umami Cloud
Relevant log output
No response
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered: