Add Invoker Commands, `command` & `commandfor` (previously: Invokers, `invoketarget` & `invokeaction`)

[Schweinepriester]

• Spec:
  • https://open-ui.org/components/invokers.explainer/
  • Add commandfor & command attributes to HTMLButtonElement whatwg/html#9841
• Chrome:
  • Intent to Prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/tDanwUCp2cg/m/IPc9hvHcFAAJ
  • https://chromestatus.com/feature/5142517058371584
• Firefox:
  • Position request: Invokers (command & commandfor) mozilla/standards-positions#902
  • https://bugzilla.mozilla.org/show_bug.cgi?id=1856430
• WebKit:
  • Position request: "command" and "commandfor" attributes WebKit/standards-positions#264
  • https://bugs.webkit.org/show_bug.cgi?id=262840

Adding invoketarget and invokeaction attributes to <button> and <input type="button"> / <input type="reset"> 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 invoketarget will - when clicked, touched, or enacted via keypress - dispatch an InvokeEvent on the element referenced by invoketarget, with some default behaviours.

🤩

[Schweinepriester]

they've been renamed to command & commandfor:

• https://adactio.com/journal/21803

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

  Adding commandfor and command attributes to <button> and 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 command will - when clicked, touched, or enacted via keypress - dispatch a CommandEvent on the element referenced by commandfor, with some default behaviours.

[westonruter]

Has this been implemented? I do see https://caniuse.com/mdn-html_elements_button_commandfor