-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add popover=hint feature #2250
Comments
@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. |
Yep: mdn/content#37842
See my comment here whatwg/html#9778 (comment) - I'm hoping we can land it now that the objection has been removed. We'll see! |
See: - web-platform-dx/web-features#2680 - web-platform-dx/web-features#2250 Note that the PR above hasn't landed yet, and I don't know what the proper sequencing is there, or even how to connect `kPopoverHint` over to the new entry I added above. Bug: 40256776 Change-Id: Ibfae2d2dc550ed809a4b0bfb4924c94d4899125a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6284402 Reviewed-by: Philip Jägenstedt <[email protected]> Commit-Queue: Mason Freed <[email protected]> Cr-Commit-Position: refs/heads/main@{#1423250}
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: