Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Intent to Extend Experiment: Interest Invokers

284 views
Skip to first unread message

Mason Freed

unread,
Apr 18, 2025, 6:41:00 PMApr 18
to blink-dev

Contact emails

mas...@chromium.org, chro...@keithcirkel.co.uk

Explainer

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

Specification

https://github.com/whatwg/html/pull/11006

Summary

This feature adds an `interesttarget` attribute to <button> and <a> elements. The `interesttarget` attribute adds "interest" behaviors to the element, such that when the user "shows interest" in the element, actions are triggered on the target element. Actions can include things like showing a popover. The user agent will handle detecting when the user "shows interest" in the element, via methods such as hovering the element with a mouse, hitting special hotkeys on the keyboard, or long-pressing the element on touchscreens. When interest is shown or lost, an `InterestEvent` will be fired on the target, which have default actions in the case of popovers - showing and hiding the popover.



Blink component

Blink>DOM

TAG review

https://github.com/w3ctag/design-reviews/issues/1058

TAG review status

Pending

Origin Trial Name

The interesttarget Attribute

Chromium Trial Name

HTMLInterestTargetAttribute

Origin Trial documentation link

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

WebFeature UseCounter name

kInterestTarget

Risks



Interoperability and Compatibility

None



Gecko: No signal (https://github.com/mozilla/standards-positions/issues/1181)

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/464)

Web developers: Strongly positive (https://github.com/openui/open-ui/issues?q=label%3Ainterest-invokers%20)

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



Goals for experimentation



Reason this experiment is being extended

Due to the complexity of this API, the shape is still in progress. For example, the keyboard behavior was recently changed from a hot-key to a focus-based interest mechanism, to address developer feedback. Due to the changes and the ongoing development/testing of this API, I'd like to request an extension of 3 more milestones, to M140.



Ongoing technical constraints

None



Debuggability

None



Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

No

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

No

Flag name on about://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

Origin trial desktop first135
Origin trial desktop last137
Origin trial extension 1 end milestone140
DevTrial on desktop133
Origin trial Android first135
Origin trial Android last137
DevTrial on Android133
Origin trial WebView first135
Origin trial WebView last137


Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/4530756656562176?gate=5185152355139584

Links to previous Intent discussions

Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/B7F891EB-32FE-48FD-B54B-E452AD74CC3E%40igalia.com
Intent to Experiment: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDiTCMXnR6D-5XdYiwgV_FMAKE8VM%2Bq-Pyho9KZqoDpSjQ%40mail.gmail.com


This intent message was generated by Chrome Platform Status.

Dan Clark

unread,
Apr 21, 2025, 2:26:33 PMApr 21
to blink-dev, mas...@chromium.org
Hi Mason,

Can you outline any progress made on the areas listed in https://www.chromium.org/blink/launching-features/#origin-trials?
I know that the spec discussions are ongoing, and the TAG review is in progress, but I'm less up-to-date with what's going on in the other areas. 
  • Draft spec (early draft is ok, but must be spec-like and associated with the appropriate standardization venue, or WICG)
  • TAG review (see exceptions)
  • signals requests
  • Outreach for feedback from the spec community
  • WPT tests
-- Dan

Mason Freed

unread,
Apr 22, 2025, 3:52:14 PMApr 22
to blink-dev, dan...@microsoft.com, Mason Freed
Hi Dan, sure:

On Monday, April 21, 2025 at 11:26:33 AM UTC-7 dan...@microsoft.com wrote:
  • Draft spec (early draft is ok, but must be spec-like and associated with the appropriate standardization venue, or WICG)
https://github.com/w3ctag/design-reviews/issues/1058 (as you mentioned, awaiting feedback) 
WebKit (https://github.com/WebKit/standards-positions/issues/464) - comments are positive on the use case but negative on the specifics of the touchscreen interaction pattern. No alternative suggestions have been provided for touchscreen, however. Only negative opinions on all proposed options.
  • Outreach for feedback from the spec community
-- Dan
On Friday, April 18, 2025 at 3:41:00 PM UTC-7 mas...@chromium.org wrote:

Dan Clark

unread,
Apr 22, 2025, 6:14:47 PMApr 22
to blink-dev, mas...@chromium.org, Dan Clark
Thanks Mason! LGTM to continue experimenting in M138-M140 inclusive.

-- Dan

Reply all
Reply to author
Forward
0 new messages