HTML Concepts: Commands and Facets

Published on March 29, 2022 (↻ August 17, 2024), filed under Development (RSS feed for all categories).

In the HTML concepts series I’m presenting lesser known ideas from the huge HTML specification. In this episode, let’s have a quick look at commands and facets.

Commands

Commands should be what you think they are. A command is defined as “the abstraction behind menu items, buttons, and links.” It’s what you issue when you interact with them, that is, click or press on either.

Accordingly,

• an a element with an href attribute defines a command; as does
• a button element (“always”);
• an input element whose type attribute is in a “Submit Button, Reset Button, Image Button, Button, Radio Button, or Checkbox” state;
• an option element with an ancestor select element and either no value attribute, or one that is not the empty string;
• a legend element that has an assigned access key, is a child of a fieldset element, and whose parent has a descendant that defines a command that is neither a label nor a legend element; and
• any element that has an assigned access key.

Facets

Facets are rarely mentioned anywhere; they are something a command has. There are the following facets:

• Label: the name of the command.
• Action: the effect of the command when triggered, like a URL to navigate to, a form submission, or an event handler.
• Access key (optional): a key combination selected by the user agent which triggers the command.
• Hidden state (optional): information on whether the respective command is hidden.
• Disabled state (optional): information on whether the respective command is relevant and can be triggered.

❧ Commands are easy to work with, as they represent something actionable. Facets may be what you can now recall as something that specifies and gives information about a command. Review other concepts, and see you in a follow-up post of this series.

Figure: No, not one of those commands. (Copyright King Features Syndicate, Inc., distr. Bulls.)

About Me

I’m Jens (long: Jens Oliver Meiert), and I’m a frontend engineering leader and tech author/publisher. I’ve worked as a technical lead for companies like Google and as an engineering manager for companies like Miro, I’m a contributor to several web standards, and I write and review books for O’Reilly and Frontend Dogma.

I love trying things, not only in web development (and engineering management), but also in other areas like philosophy. Here on meiert.com I share some of my experiences and views. (Please be critical, interpret charitably, and give feedback.)