You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Popover API specifies the behavior for two values of the popover attribute: auto and manual. This feature describes a third value, popover=hint. Hints, which are most often associated with "tooltip" type behaviors, have slightly different behaviors. Primarily, the difference is that hints are subordinate to autos when opening nested stacks of popovers. So it is possible to open an unrelated hint popover while an existing stack of auto popovers stays open. The canonical example is that a picker is open (popover=auto) and a hover-triggered tooltip (popover=hint) is shown. That action does not close the picker.
@mfreed7 do you know if anyone if this is tracked to be added to BCD (browser-compat-data)? I couldn't find an issue, but may have missed it.
Also, do you know when we can expect the spec PR to be merged?
Specification
whatwg/html#9778
Description
The Popover API specifies the behavior for two values of the
popover
attribute:auto
andmanual
. This feature describes a third value,popover=hint
. Hints, which are most often associated with "tooltip" type behaviors, have slightly different behaviors. Primarily, the difference is thathint
s are subordinate toauto
s when opening nested stacks of popovers. So it is possible to open an unrelatedhint
popover while an existing stack ofauto
popovers stays open. The canonical example is that a picker is open (popover=auto) and a hover-triggered tooltip (popover=hint) is shown. That action does not close the picker.Documentation
https://open-ui.org/components/popover-hint.research.explainer/
Browser support
Chrome is planning to ship this feature (subject to approval) in v133: https://chromestatus.com/feature/5073251081912320
The text was updated successfully, but these errors were encountered: