Tippy.js is a highly customizable tooltip and popover library powered by Popper.js. This is a lightweight wrapper that lets you use it declaratively in React.
# npm
npm i @tippy.js/react
# Yarn
yarn add @tippy.js/reactCDN: https://unpkg.com/@tippy.js/react
Requires React 16.8+
Wrap the <Tippy /> component around the element, supplying the tooltip's
content as the content prop. It can take a string or a tree of React elements.
import React from 'react'
import Tippy from '@tippy.js/react'
const StringContent = () => (
<Tippy content="Hello">
<button>My button</button>
</Tippy>
)
const JSXContent = () => (
<Tippy content={<span>Tooltip</span>}>
<button>My button</button>
</Tippy>
)If you want to use a component element as a child, ensure you forward the ref to the DOM node:
import React, { forwardRef } from 'react'
function ThisWontWork() {
return <button>Text</button>
}
const ThisWillWork = forwardRef((props, ref) => {
return <button ref={ref}>Text</button>
})
function App() {
return (
<Tippy content="Tooltip">
<ThisWillWork />
</Tippy>
)
}styled-components v4 does this for you automatically, so it should be seamless
when using the styled constructor.
If you're using a library that doesn't forwardRef for you, and doesn't give
access to the ref via innerRef or similar, you can use a wrapper <span>
element as a workaround.
<Tippy content="Tooltip">
<span>
<LegacyComponent>Unfortunately</LegacyComponent>
</span>
</Tippy>Although Tippy will add
tabindexfor you on the<span>which allows it to receive focus, it may affect accessibility with regards to screenreaders, since<span>is not traditionally focusable (unlike a<button>for example).
All of the native Tippy.js options can be passed as props.
Visit All Options to view the complete table.
<Tippy
content="Tooltip"
arrow={true}
animation="scale"
duration={0}
delay={[300, 0]}
// ...and many more!
>
<button>Text</button>
</Tippy>In addition, there are 4 more props added specifically for the React component.
A React alternative to the theme prop. The className gets added to the tooltip
element's class list as expected, without adding -theme as a suffix.
<Tippy content="Tooltip" className="hello world">
<button />
</Tippy>If you're using styled-components, the className prop allows you to avoid
global styles with the following technique:
const PurpleTippy = styled(Tippy)`
background: purple;
/* Styling the arrow for different placements */
&[x-placement^='top'] {
.tippy-arrow {
border-top-color: purple;
}
}
`See themes for more information.
Note: the following examples are using the new React Hooks API. It isn't required to use this library – the props will work as expected in class components too.
Prop to control the tippy.enable() / tippy.disable() instance methods. Use
this when you want to temporarily disable a tippy from showing.
function App() {
const [enabled, setEnabled] = useState(true)
return (
<Tippy content="Tooltip" enabled={enabled}>
<button />
</Tippy>
)
}Prop to control the tippy.show() / tippy.hide() instance methods. Use this
when you want to programmatically show or hide the tippy instead of relying on
UI events. This puts the tippy in controlled mode so it will only respond to
state.
function App() {
const [visible, setVisible] = useState(true)
return (
<Tippy content="Tooltip" visible={visible}>
<button />
</Tippy>
)
}Note: You should also set the
hideOnClickprop tofalseif you don't want the tippy to hide when the user clicks on the document somewhere.
Callback invoked when the tippy instance has been created. Use this when you need to store the tippy instance on the component.
This should only be done for advanced (imperative) manipulation of the tippy instance – in most cases using props should suffice.
function App() {
const tippyInstance = useRef()
return (
<Tippy
content="Tooltip"
onCreate={instance => (tippyInstance.current = instance)}
>
<button />
</Tippy>
)
}You can create a new component file that imports the component and sets the default props. From this file, you can import the component throughout your app.
import Tippy from '@tippy.js/react'
Tippy.defaultProps = {
...Tippy.defaultProps,
arrow: true,
}
export default TippyYou could also create Proxy components that wrap the base <Tippy /> component
with a new name and sets its own default props:
export const Tooltip = props => <Tippy {...props} />
Tooltip.defaultProps = {
animation: 'fade',
arrow: true,
delay: 150,
theme: 'translucent',
}
export const Popover = props => <Tippy {...props} />
Popover.defaultProps = {
animateFill: false,
animation: 'scale',
interactive: true,
interactiveBorder: 10,
theme: 'light-border',
trigger: 'click',
}
// In another file
import { Tooltip, Popover } from './Tippy'You can nest the components like so:
<Tippy content="Tooltip" placement="bottom">
<Tippy content="Tooltip" placement="left">
<Tippy content="Tooltip" placement="right">
<Tippy content="Tooltip">
<button />
</Tippy>
</Tippy>
</Tippy>
</Tippy>Wraps the tippy.group()
method.
import Tippy, { TippyGroup } from '@tippy.js/react'
function App() {
return (
<TippyGroup delay={1000}>
<Tippy content="a">
<button />
</Tippy>
<Tippy content="b">
<button />
</Tippy>
</TippyGroup>
)
}popper.js≈ 7 kBtippy.js≈ 7.5 kB (including CSS)@tippy.js/react≈ 1 kB
If you're using Popper.js for other parts of your app, the added cost becomes much smaller!
Why should you use this library, and how does it compare to other ones?
MIT
