JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 100
  • Score
    100M100P100Q83238F
  • License MIT

Svelte action to display a tooltip

Package Exports

  • @untemps/svelte-use-tooltip
  • @untemps/svelte-use-tooltip/dist/index.es.js
  • @untemps/svelte-use-tooltip/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@untemps/svelte-use-tooltip) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

svelte-use-tooltip

Svelte action to display a tooltip


npm GitHub Workflow Status Codecov

Demo

🔴  LIVE DEMO 🔴

Installation

yarn add @untemps/svelte-use-tooltip

Usage

Basic usage

<script>
    import { useTooltip } from '@untemps/svelte-use-tooltip'

    const _onTooltipClick = (arg, event) => {
        console.log(arg, event)
    }
</script>

<div use:useTooltip={{
        contentSelector: '.tooltip__content',
        contentClone: false,
        contentActions: {
            '*': {
                eventType: 'click',
                callback: _onTooltipClick,
                callbackParams: ['ok'],
                closeOnCallback: true
            },
        },
        containerClassName: 'tooltip',
        position: 'right',
        animated: true,
        animationEnterClassName: 'tooltip-enter',
        animationLeaveClassName: 'tooltip-leave',
        enterDelay: 200,
        leaveDelay: 400,
        disabled: false
    }
} class="tooltip__target">
    Hover me
</div>
<span class="tooltip__content">Hi!</span>

<style>
    .tooltip__target {
        width: 10rem;
        height: 3rem;
        background-color: white;
        color: black;
        display: flex;
        align-items: center;
        justify-content: center;
        box-shadow: 0 0 5px 0 rgba(0,0,0,0.5);
    }

    .tooltip__target:hover {
        cursor: pointer;
        background-color: black;
        color: white;
    }

    .tooltip__content {
        border: solid 1px white;
        background: none;
    }

    :global(.tooltip) {
        position: absolute;
        z-index: 9999;
        max-width: 120px;
        background-color: #ee7008;
        color: #fff;
        text-align: center;
        border-radius: 6px;
        padding: 0.5rem;
    }

    :global(.tooltip::after) {
        content: '';
        position: absolute;
        top: 100%;
        left: 50%;
        margin-left: -5px;
        border-width: 5px;
        border-style: solid;
        border-color: #ee7008 transparent transparent transparent;
    }
</style>

API

Props Type Default Description
content string null Text content to display in the tooltip.
contentSelector string null Selector of the content to display in the tooltip.
contentClone boolean false Flag to clone the content to display in the tooltip. If false, the content is removed from its previous parent.
contentActions object null Configuration of the tooltip actions (see Content Actions).
containerClassName string '__tooltip' Class name to apply to the tooltip container.
position string 'top' Position of the tooltip. Available values: 'top', 'bottom', 'left', 'right'
animated boolean false Flag to animate tooltip transitions.
animationEnterClassName string '__tooltip-enter' Class name to apply to the tooltip enter transition.
animationLeaveClassName string '__tooltip-leave' Class name to apply to the tooltip leave transition.
enterDelay number 0 Delay before showing the tooltip in milliseconds.
leaveDelay number 0 Delay before hiding the tooltip in milliseconds.
offset number 10 Distance between the tooltip and the target in pixels.
disabled boolean false Flag to disable the tooltip content.

Content Actions

The contentActions prop allows to handle interactions within the tooltip content.

Each element inside the content parent may configure its own action since it can be queried using the key-selector.

One event by element is possible so far as elements are referenced by selector. The last one declared in the contentActions object has precedence over the previous ones.

<script>
    import { useTooltip } from '@untemps/svelte-use-tooltip'
</script>

<div use:useTooltip={{
    contentSelector: '#content',
    contentClone: false,
    contentActions: {
        '#button1': {
            eventType: 'mouseenter',
            callback: (arg) => console.log(arg),
            callbackParams: ['Haha you\'re hovering the button 1'],
            closeOnCallback: false
        },
        '#button2': {
            eventType: 'click',
            callback: (arg1, arg2) => console.log(arg1, arg2),
            callbackParams: ['Haha you\'ve clicked the', 'button 2'],
            closeOnCallback: true
        },
    }
}}>Hover me</div>
<span id="content">
    <button id="button1">Action 1</button>
    <button id="button2">Action 2</button>
</span>
Props Type Default Description
eventType string null Type of the event. All available events can be used.
callback function null Function to be used as event handler.
callbackParams array null List of arguments to pass to the event handler in.
closeOnCallback boolean false Flag to automatically close the tooltip when the event handler is triggered.

* selector

If you need the whole tooltip content to be interactive, you can use the special * key:

<script>
    import { useTooltip } from '@untemps/svelte-use-tooltip'
</script>

<div use:useTooltip={{
    content: 'Foo',
    contentActions: {
        '*': {
            eventType: 'click',
            callback: (arg) => console.log(arg),
            callbackParams: ['Haha you clicked the tooltip'],
            closeOnCallback: true
        }
    }
}}>Hover me</div>

If you combine the * selector with other events, its callback will be triggered along with the other ones.

Development

The component can be served for development purpose on http://localhost:5000/ running:

yarn dev

Contributing

Contributions are warmly welcomed:

  • Fork the repository
  • Create a feature branch
  • Develop the feature AND write the tests (or write the tests AND develop the feature)
  • Commit your changes using Angular Git Commit Guidelines
  • Submit a Pull Request