v150 · covered on mdn
Popover=hint behavior changes
Chrome 150 refines the behavior of popover="hint": hint popovers are now properly subordinate to auto popovers when building nested popover stacks, and they dismiss each other in the correct order — matching the HTML specification and aligning with Firefox and Safari.
this API is documented on MDN
popover — HTML: Global attributes — MDN Web Docsgendn doesn't duplicate APIs that MDN already covers. MDN's popover global attribute page documents all three popover types — auto, hint, and manual — including their stacking, dismissal, and nested behaviour. Chrome 150 browser-compat data will be reflected once updated.
what changed in Chrome 150
The original popover="hint" implementation (shipped Chrome 147) had an edge case in nested stacks: when an auto popover opened after a hint popover, the dismissal order was not correctly enforced. Chrome 150 fixes the ordering so that:
- Opening an
autopopover dismisses any openhintpopover first. - A
hintpopover cannot be added to a stack that already contains anautopopover at a higher position. - Light-dismiss ("clicking outside") closes popovers from the top of the stack in the correct order.
This is a spec-compliance fix, not a new API surface. Sites that use popover="hint" for simple tooltips are unaffected; only those that deliberately nest hint and auto popovers in the same stack may notice the corrected ordering.
at a glance
| Shipped in | Chrome 150 (desktop); DevTrial in Chrome 149 |
|---|---|
| Type | Spec-compliance / behaviour fix |
| Finch flag | PopoverHintNewBehavior |
| ChromeStatus | 5073251081912320 — Popover=hint behavior changes |