Delayed-Then-Instant Tooltips with HTML & CSS Alone

Chris Coyier8/13/26About 4 minCSSArticle(s)blogmaster.devcss

Delayed-Then-Instant Tooltips with HTML & CSS Alone 관련

We don't NEED JavaScript to adjust tooltip timing displays. Super modern CSS and HTML has this covered simply, and we can do fully successful fallbacks.

Hey! This post is a response to Abhishek Jakhar’s post about delayed tooltips, or, perhaps better put, a second part showing an alternative approach to the same problem.

I really like Abhishek’s focus on the UX of the tooltips in his app. Both are true: a tooltip that comes up too fast is annoying for just-passing-by mouse cursors, and if you add a delay, they come up too slowly for someone intentionally mousing between them.

That’s just good UX thinking, and I like to see it.

But also, the solutions are quite deep into JavaScript land. The core of the solution is a setTimeout/clearTimeout which sets a “warmed” state that determines the tooltip’s open timing. It’s all done in React, so the React components need to share and pass around state. There is useRef, useState, useEffect, useMemo, and even createContext/useContext all being used to do this.

I would push back against that if that was the technology being used just for this, but that’s almost surely not the case. Abhishek said it’s a part of his larger app, which surely has much more going on, and just so happens to already be in React with Radix and Motion. So he’s implementing a solution within the context of what is already going on, which is understandable.

What I’d like to say is: you don’t need all that just for the UX we’re shooting for here. We can do all this in HTML and CSS with no JavaScript at all. And that solution would work in React-and-friends too, so ultimately might be a better solution overall.

A Master developer has many tools 😉.

A Semantic HTML Foundation

Here’s a decent tooltip setup:

<button
  interestfor="tip-1"
  aria-labelledby="tip-1"
>
  <svg ...></svg>
</button>
<span id="tip-1" popover="hint">
  I'm the tooltip.
</span>

Believe it or not, this HTML alone produces a working tooltip. Hover over the button; you’ll see the HTML tooltip. Hover off, and it’s gone.

That’s the magic of popovers, and the additional magic of popover="hint" and interestfor which deals with “interest”, meaning hovers essentially (or other fancy stuff like you’re clearly gazing at a bit of UI in the metaverse or some crap, which is why web standards is cool: they think of stuff like that).

Another lovely little thing is that when a popover is opened, the “default” anchor is the element that opened it. So we can just use anchor positioning and assume the anchor is the button.

So with just this:

[popover] {
  position: fixed;
  background: red;
  color: white;
  position-area: block-start;
}

We’ll get a popover that opens above the button on hover:

See Super basic hover tooltip by editor/chriscoyier on CodePen.

Plus, some “try” logic that handles edge detection too!

position-try:
  flip-block,
  flip-inline,
  flip-block flip-inline;

That’s a big advantage to CSS/popover style tooltips.

Note

Fair warning that there is no Safari support for popover="hint" yet, but we’ll get fallbacks all sorted out by the end.

Controlling Timing in CSS

The magic just keeps rolling here, I’m telling you. We can control how long the interest-powered hover delays with CSS as well:

button {
  interest-delay-start: 200ms;
  interest-delay-end: 150ms;
}

.area:has(:popover-open) button {
  interest-delay-start: 0s;
}

That’s really the heart of the whole thing Abhishek was going for! In a few lines!

See Super basic hover tooltip with delays by editor/chriscoyier on CodePen.

Fallbacks

We don’t have full browser support here, which is another point in favor of Abhishek’s all-JavaScript method, which shouldn’t have any trouble anywhere. But we can test for support in CSS and design our own fallbacks, which actually can replicate all this behavior anyway (just with more code).

The trick to the timing is to have a --warm variable that is essentially either on or off. The popovers naturally transition their display value, so if we just add a delay, we got what we need.

@supports not (interest-delay-start: 0s) {
  .area {
    --warm: 0;
    transition: --warm 0s 700ms;
    &:hover {
      --warm: 1;
      transition: --warm 0s 250ms;
    }
  }

  [popover] {
    transition-delay: calc((1 - var(--warm)) * 200ms);
  }
}