Skip to content
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

Closed
mfreed7 opened this issue Nov 14, 2024 · 2 comments · Fixed by #2680
Closed

Add popover=hint feature #2250

mfreed7 opened this issue Nov 14, 2024 · 2 comments · Fixed by #2680
Labels
early features Feature definition work for features without shipping implementations feature definition Creating or defining new features or groups of features.

Comments

@mfreed7
Copy link
Contributor

mfreed7 commented Nov 14, 2024

Specification

whatwg/html#9778

Description

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.

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

@mfreed7 mfreed7 added the feature definition Creating or defining new features or groups of features. label Nov 14, 2024
@captainbrosset
Copy link
Contributor

@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?

@mfreed7
Copy link
Contributor Author

mfreed7 commented Dec 2, 2024

@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

Also, do you know when we can expect the spec PR to be merged?

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!

@ddbeck ddbeck added the early features Feature definition work for features without shipping implementations label Jan 29, 2025
mfreed7 added a commit to mfreed7/web-features that referenced this issue Feb 20, 2025
@ddbeck ddbeck closed this as completed in 8362f13 Feb 21, 2025
aarongable pushed a commit to chromium/chromium that referenced this issue Feb 21, 2025
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}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
early features Feature definition work for features without shipping implementations feature definition Creating or defining new features or groups of features.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants