Open UI's proposed Interest Invoker API is now an experiment in Chrome 139. Its purpose is to make hover-driven UI — tooltips, hover menus, hover cards, quick actions — declarative: authors write plain HTML and the browser takes over the mouseenter and mouseleave bookkeeping that would otherwise require JavaScript.
<a interestfor="target-id">Interest trigger</a>
<div id="target-id" popover>Interest target</div>
Declaration as a popover isn't formally required, but the feature builds in the appropriate accessibility hints.
The trigger and the target
The interest trigger is the element the user hovers, or long-presses on touchscreens, to reveal the target. Only three element types can serve as triggers: an <a>, a <button>, or an <area>. Each carries an interestfor attribute pointing at the id of the interest target.
<!-- Link -->
<a interestfor="link">Interest trigger</a>
<div id="link" popover>Interest target</div>
<!-- Button -->
<button interestfor="button">Interest trigger</button>
<div id="button" popover>Interest target</div>
<!-- Image map -->
<img src="" alt="" usemap="#map">
<map name="map">
<area interestfor="area" shape="" coords="" alt="">
</map>
<div id="area" popover>Interest target</div>
When the target is a popover — as in the examples above — interestfor stands in for the popovertarget attribute that declarative popovers would normally need, so the usual
<!-- Button -->
<button popovertarget="button">Interest trigger</button>
<div id="button" popover>Interest target</div>
becomes:
<!-- Button -->
<button interestfor="button">Interest trigger</button>
<div id="button" popover>Interest target</div>
Choice of popover type matters, since each ships different functional and accessibility behavior.
- A valueless, empty, or
autopopover can be dismissed lightly — via esc or a click outside — and on opening it closes otherautoandhintpopovers that aren't nested. hintpopovers, the newest type, also dismiss lightly but close only otherhintpopovers when opened.manualpopovers are independent: no light dismissal, no effect on other popovers, and several can be open at once.
<div id="target-id" popover>Interest target</div>
<!-- Equivalent to -->
<div id="target-id" popover="">Interest target</div>
<!-- Equivalent to -->
<div id="target-id" popover="auto">Interest target</div>
<div id="target-id" popover="hint">Interest target</div>
<div id="target-id" popover="manual">Interest target</div>
Both the explainer and Chrome's current implementation indicate that interest targets vanish on mouseleave no matter which popover type is in play. That raises a question about why the type distinction exists at all in this context — a manual interest target, intuitively, ought to survive mouseleave. Open UI's justification for layering interest invokers on popovers is that browsers bake accessibility in according to popover type; a counterargument is that accessibility should follow the content unless ARIA attributes override it. Interest invokers are early and experimental, so this may still change.
JavaScript events and delays
Script hooks exist and follow conventional patterns. The interest and loseinterest events should cover most edge cases.
interestTrigger.addEventListener("interest", () => {
/* User showed interest */
});
interestTrigger.addEventListener("loseinterest", () => {
/* User lost interest */
});
Interest targets do not appear or disappear instantly. The delay is trying at first, but becomes obviously necessary once you build with the API. The hide delay gives users recovery time after an accidental mouseleave, which is easy to do when the target is small. The show delay does two jobs: it lets keyboard and screen reader users skip past the target, and it prevents the pointer from triggering it by accident.
For unobtrusive targets, dropping the show delay is probably harmless. The hide delay can likewise be removed for keyboard and screen reader users, who are unlikely to lose interest by accident. Two new CSS properties, interest-show-delay and interest-hide-delay, accept 0 for this; both default to 0.5s and are set on the trigger rather than the target. There is also an interest-delay shorthand. Note that the delays are currently buggy, particularly with unitless values.
/* If unobtrusive */
.unobtrusive[interestfor] {
interest-show-delay: 0;
}
/* If keyboard-focused on a trigger */
[interestfor]:focus-visible {
interest-hide-delay: 0;
}
/*
If keyboard-focused within a target of interest,
or target of partial interest (these are always keyboard-triggered),
the interest trigger that currently has interest
or partial interest has the hide delay removed
*/
body:has(:target-of-interest :focus-visible, :target-of-partial-interest) [interestfor]:where(:has-interest, :has-partial-interest) {
interest-hide-delay: 0;
}
Partial interest and the new pseudo-selectors
Keyboard or screen reader navigation to a trigger whose target contains focusable elements puts it in what is called "partial" interest. The target's focusable descendants are then not focusable, making them easy to skip, unless the user presses option+up or alt+up, or the equivalent screen reader hotkey. A message can be customized through :target-of-partial-interest::after; since it advertises the correct shortcut for the user's device by default, restyling makes more sense than rewriting the text.
:target-of-partial-interest::after {
content: "Press ⌥↑ to activate.";
}
The user agent also supplies the following:
:target-of-partial-interest {
interactivity: not-keyboard-focusable;
}
The new not-keyboard-focusable value on interactivity blocks keyboard focus much as tabindex="-1" does, but from CSS.
The full set of moving parts:
:has-interest— triggers with mouse interest:has-partial-interest— triggers with keyboard interest:target-of-interest— targets with mouse interest:target-of-partial-interest— targets with keyboard interest:target-of-partial-interest::after— the message shown for keyboard interestinterest-show-delay—<time>before the target appearsinterest-hide-delay—<time>before the target disappearsinterest-delay— shorthand for the two delays
Anchor elements work declaratively with interest invokers in the same way.
Open questions
Hover-triggered popovers look simple, but hovering has never translated well to touchscreens, it is prone to human error, and nobody wants keyboard or screen reader users tabbing through a minefield of focusables. Open UI has handled much of that by delegating work to user agents; questions remain, though. Touchscreen activation is unresolved, with long-press plus a context-menu "View more info" entry currently the leading candidate. Delay values, trigger and target styling under interest, hotkey instruction presentation, and the new UX conventions these concepts imply all need decisions too. The bonus interactivity: not-keyboard-focusable may help build keyboard-friendlier components in CSS.



