Intent to Prototype: Interest Invokers

[Luke Warlow]

Contact emails

lwa...@igalia.com, chro...@keithcirkel.co.uk

Explainer

https://open-ui.org/components/interest-invokers.explainer

Specification

None

Summary

Adding interesttarget attribute to <button>, <input type="button"> / <input type="reset">, and <a> elements would allow authors to assign behaviour to buttons in a more accessible and declarative way, while reducing bugs and reducing the amount of JavaScript pages are required to ship for interactivity. Buttons with interesttarget will - when hovered, focused, or long pressed (touch support) - dispatch an interest event on the element referenced by interesttarget, with some default behaviours, and dispatch a loseinterest event when focus, hover or long press is finished.

Blink component

Blink>DOM

Motivation

This proposal builds on invokers by adding a new `interesttarget` attribute that can be used on buttons and links to trigger a popover based on focus, hover or other mechanisms.

Initial public proposal

https://github.com/whatwg/html/issues/9625

TAG review

None

TAG review status

Pending

Risks

Interoperability and Compatibility

None

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?

None

Debuggability

None

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

No

Flag name on chrome://flags

None

Finch feature name

None

Non-finch justification

None

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/326681249

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/4530756656562176

This intent message was generated by Chrome Platform Status.