Intent to Prototype: popover=hint

[Mason Freed]

Contact emails

mas...@chromium.org

Explainer

https://open-ui.org/components/popover.research.explainer

Specification

Summary

The Popover API (https://chromestatus.com/feature/5463833265045504) 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, are slightly different from the other two. For example, only one Hint can be open at a time, in contrast to `auto` and `manual` popovers which can be open simultaneously. There are also other differences in the interactions between Hints and the other popover types.

Blink component

Blink>HTML>Popover

Motivation

One common use case, "Hints" or "Tooltips" was not covered by the original Popover API proposal. This use case was originally included in the prototype, but because some technical issues couldn't be worked out in time, this part of the feature was removed from the initial shipping feature. This intent adds back support for Hints/Tooltips, plus a "hover-triggering" feature to make it easy to trigger them.

Initial public proposal

https://github.com/openui/open-ui/issues/617

TAG review

TAG review status

Pending

Risks

Interoperability and Compatibility

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

Debuggability

Is this feature fully tested by web-platform-tests?

Yes

Flag name

Requires code in //chrome?

False

Tracking bug

https://crbug.com/1416284

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5073251081912320

This intent message was generated by Chrome Platform Status.