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
I am working on an OSS component library project built on top of Radix-ui primitives to help my current company build standards upon its multiple projects.
We need interactive tooltips - a tooltip which content can be hovered and clicked, without closing the tooltip - to allow users interact with links inside tooltip content, for instance.
For now, I need an extra layer of customization on top of Radix-ui Tooltip primitive to implement that behaviour.
I'd like a simple configuration, such as an interactive variant, or this behaviour by default.
Examples in other libraries
I used MUI for a while and know they implemented this behaviour by default on their tooltips. They seem to argue it's the recommended behaviour: https://mui.com/components/tooltips/#interactive
Who does this impact? Who is this for?
I expect implementing this behaviour by default on tooltips might bring breaking changes to Radix-ui integrators.
On the other hand, I would expect adding this behaviour as part of a variant of the Tooltip primitive component might bring no impact on the current integrator base.
If I'm right expecting this is a standard recommended by WCAG, I guess this implementation would bring value to every integrator 🙂
I think this feature doesn't bring value to users without a pointing device, though.
Additional context
/
The text was updated successfully, but these errors were encountered:
Feature request
Overview
I am working on an OSS component library project built on top of Radix-ui primitives to help my current company build standards upon its multiple projects.
We need interactive tooltips - a tooltip which content can be hovered and clicked, without closing the tooltip - to allow users interact with links inside tooltip content, for instance.
As far as I understand, WCAG recommends enabling tooltip content to be interactive: WCAG 2.1 success criterion 1.4.13.
For now, I need an extra layer of customization on top of Radix-ui Tooltip primitive to implement that behaviour.
I'd like a simple configuration, such as an
interactive
variant, or this behaviour by default.Examples in other libraries
I used MUI for a while and know they implemented this behaviour by default on their tooltips. They seem to argue it's the recommended behaviour: https://mui.com/components/tooltips/#interactive
Who does this impact? Who is this for?
I expect implementing this behaviour by default on tooltips might bring breaking changes to Radix-ui integrators.
On the other hand, I would expect adding this behaviour as part of a variant of the Tooltip primitive component might bring no impact on the current integrator base.
If I'm right expecting this is a standard recommended by WCAG, I guess this implementation would bring value to every integrator 🙂
I think this feature doesn't bring value to users without a pointing device, though.
Additional context
/
The text was updated successfully, but these errors were encountered: