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
Popover can be used with different types of trigger, for example, Button, ButtonLink, Tag or TextLink. We shouldn't limit it to any specific component, a trigger can be basically anything clickable.
There is similar behavior for our search forms (layer on top of the page, containing original input). Not sure if Popover should solve it, I see that more as a new component - something like InputPopover, or similar.
You can find the proposed mobile behavior in Zeplin. It's copied from how Popovers behave in our mobile app (the Close button position). We need to discuss it and make it probably more consistent with Tooltip and Modal behavior (3 different patterns currently).
The text was updated successfully, but these errors were encountered:
Description
A popover can be used as a container for additional content that can be displayed on top of the page.
Visual style
Zeplin: https://zpl.io/agrBvoM
Additional information
Button
,ButtonLink
,Tag
orTextLink
. We shouldn't limit it to any specific component, a trigger can be basically anything clickable.The text was updated successfully, but these errors were encountered: