Intent to Ship: Invoker Commands; the command and commandfor attributes

[Chromestatus]

Contact emails

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

Explainer

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

Specification

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

Summary

Adding command and commandfor attributes to <button> elements would allow authors to assign behaviour to buttons in a more accessible and declarative way, while reducing bugs and simplifying the amount of JavaScript pages are required to ship for interactivity. Buttons with commandfor and command attributes will - when clicked, touched, or enacted via keypress - dispatch a CommandEvent on the element referenced by commandfor, with some default behaviours such as opening dialogs and popovers.

Blink component

Blink>DOM

TAG review

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

TAG review status

Issues addressed

Risks

Interoperability and Compatibility

None

Gecko: Positive (https://github.com/mozilla/standards-positions/issues/902)

WebKit: Support (https://github.com/WebKit/standards-positions/issues/264)

Web developers: Positive (https://twitter.com/search?q=%22invoketarget%22&src=typed_query&f=top) Developers generally supportive.

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

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

Yes

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

Yes

Extensive Web Platform Tests available: https://wpt.fyi/results/html/semantics/the-button-element/command-and-commandfor

Flag name on about://flags

Experimental Web Platform Features

Finch feature name

HTMLCommandAttributes

Requires code in //chrome?

False

Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1490919

Estimated milestones

Shipping on desktop	135
DevTrial on desktop	120
Shipping on Android	135
DevTrial on Android	120
Shipping on WebView	135

Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).

None

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5142517058371584?gate=5071846508855296

Links to previous Intent discussions

Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/54ade4d0-7495-4f4b-92b4-0b967687ef02%40app.fastmail.com

This intent message was generated by Chrome Platform Status.

[Yoav Weiss (@Shopify)]

LGTM1 conditional on landing the PR

On Monday, February 17, 2025 at 11:25:03 PM UTC+1 Chromestatus wrote:

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

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

This is exciting!!

Specification https://github.com/whatwg/html/pull/9841

I see the PR just got approved! 

[Chris Harrelson]

LGTM2

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b8ce08f1-49f0-429a-a6ca-c0d6977c4d82n%40chromium.org.

[Vladimir Levin]

LGTM3

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.