Phrasing content, but there must be no interactive content descendant and no descendant with the tabindex attribute specified. If the element is the first child of a select element, then it may also have zero or one descendant selectedcontent element.

Tag omission in text/html:

Neither tag is omissible.

Content attributes:

Global attributes

command — Indicates to the targeted element which action to take.

commandfor — Targets another element to be invoked.

disabled — Whether the form control is disabled

form — Associates the element with a form element

formaction — URL to use for form submission

formenctype — Entry list encoding type to use for form submission

formmethod — Variant to use for form submission

formnovalidate — Bypass form control validation for form submission

formtarget — Navigable for form submission

name — Name of the element to use for form submission and in the form.elements API

popovertarget — Targets a popover element to toggle, show, or hide

popovertargetaction — Indicates whether a targeted popover element is to be toggled, shown, or hidden

type — Type of button

value — Value to be used for form submission

Accessibility considerations:

For authors.

For implementers.

DOM interface:

[Exposed=Window]
interface HTMLButtonElement : HTMLElement {
  [HTMLConstructor] constructor();

  [CEReactions, ReflectSetter] attribute DOMString command;
  [CEReactions, Reflect] attribute Element? commandForElement;
  [CEReactions, Reflect] attribute boolean disabled;
  readonly attribute HTMLFormElement? form;
  [CEReactions, ReflectSetter] attribute USVString formAction;
  [CEReactions] attribute DOMString formEnctype;
  [CEReactions] attribute DOMString formMethod;
  [CEReactions, Reflect] attribute boolean formNoValidate;
  [CEReactions, Reflect] attribute DOMString formTarget;
  [CEReactions, Reflect] attribute DOMString name;
  [CEReactions, ReflectSetter] attribute DOMString type;
  [CEReactions, Reflect] attribute DOMString value;

  readonly attribute boolean willValidate;
  readonly attribute ValidityState validity;
  readonly attribute DOMString validationMessage;
  boolean checkValidity();
  boolean reportValidity();
  undefined setCustomValidity(DOMString error);

  readonly attribute NodeList labels;
};
HTMLButtonElement includes PopoverTargetAttributes;

The button element represents a button labeled by its contents.

The element is a button.

The type attribute controls the behavior of the button when it is activated. It is an enumerated attribute with the following keywords and states:

Keyword	State	Brief description
`submit`	Submit Button	Submits the form.
`reset`	Reset Button	Resets the form.
`button`	Button	Does nothing.

The attribute’s missing value default and invalid value default are both the Auto state.

A button element is said to be a submit button if any of the following are true:

the type attribute is in the Auto state, both the command and commandfor content attributes are not present, and the parent node is not a select element; or
the type attribute is in the Submit Button state.

Constraint validation: If the element is not a submit button, the element is barred from constraint validation.

If a button element is the first child which is an element of a select element, then it is inert.

If specified, the commandfor attribute value must be the ID of an element in the same tree as the button with the commandfor attribute.

The command attribute is an enumerated attribute with the following keywords and states:

Keyword	State	Brief description
`toggle-popover`	Toggle Popover	Shows or hides the targeted `popover` element.
`show-popover`	Show Popover	Shows the targeted `popover` element.
`hide-popover`	Hide Popover	Hides the targeted `popover` element.
`close`	Close	Closes the targeted `dialog` element.
`request-close`	Request Close	Requests to close the targeted `dialog` element.
`show-modal`	Show Modal	Opens the targeted `dialog` element as modal.
A custom command keyword	Custom	Only dispatches the `command` event on the targeted element.

The attribute’s missing value default and invalid value default are both the Unknown state.

A custom command keyword is a string that starts with “--“.

To determine if a command is valid for a target given a command attribute command and an element target:

If command is in the Unknown state, then return false.
If command is in the Custom state, then return true.
If target is not an HTML element, then return false.
If command is in any of the following states:
then return true.
If this standard does not define is valid command steps for target‘s local name, then return false.
Otherwise, return the result of running target‘s corresponding is valid command steps given command.

The intent is to avoid dispatching a command event on an element type that does not support that command.

However, element state is not considered. If an element can support a particular command, the event is dispatched, even if that element is in a state where it cannot execute that command.

This means, for example, that command events are dispatched for popover commands on all HTML elements, even if they do not have a popover attribute.

A button element element‘s activation behavior given event is:

If element is disabled, then return.
If element‘s node document is not fully active, then return.
If element has a form owner:
1. If element is a submit button, then submit element‘s form owner from element with userInvolvement set to event‘s user navigation involvement, and return.
2. If element‘s type attribute is in the Reset Button state, then reset element‘s form owner, and return.
3. If element‘s type attribute is in the Auto state, then return.
Let target be the result of running element‘s get the commandfor-associated element.
If target is not null:
1. Let command be element‘s command attribute.
2. If the result of determining if a command is valid for a target given command and target is false, then return.
3. Let continue be the result of firing an event named command at target, using CommandEvent, with its command attribute initialized to command, its source attribute initialized to element, and its cancelable attribute initialized to true.
  
  DOM standard issue #1328 tracks how to better standardize associated event data in a way which makes sense on Events. Currently an event attribute initialized to a value cannot also have a getter, and so an internal slot (or map of additional fields) is required to properly specify this.
4. If continue is false, then return.
5. If target is not connected, then return.
6. If command is in the Custom state, then return.
7. If command is in the Hide Popover state:
  1. If the result of running check popover validity given target, true, false, and null is true, then run the hide popover algorithm given target, true, true, false, and element.
8. Otherwise, if command is in the Toggle Popover state:
  1. If the result of running check popover validity given target, false, false, and null is true, then run the show popover algorithm given target, false, and this.
  2. Otherwise, if the result of running check popover validity given target, true, false, and null is true, then run the hide popover algorithm given target, true, true, false, and element.
9. Otherwise, if command is in the Show Popover state:
  1. If the result of running check popover validity given target, false, false, and null is true, then run the show popover algorithm given target, false, and this.
10. Otherwise, if this standard defines command steps for target‘s local name, then run the corresponding command steps given target, element, and command.
Otherwise, run the popover target attribute activation behavior given element and event‘s target.

An HTML element can have specific is valid command steps and command steps defined for the element’s local name.

The form attribute is used to explicitly associate the button element with its form owner. The name attribute represents the element’s name. The disabled attribute is used to make the control non-interactive and to prevent its value from being submitted. The formaction, formenctype, formmethod, formnovalidate, and formtarget attributes are attributes for form submission.

The formnovalidate attribute can be used to make submit buttons that do not trigger the constraint validation.

The formaction, formenctype, formmethod, formnovalidate, and formtarget must not be specified if the element is not a submit button.

The command getter steps are:

Let command be this‘s command attribute.
If command is in the Custom state, then return command‘s value.
If command is in the Unknown state, then return the empty string.
Return the keyword corresponding to the value of command.

The value attribute gives the element’s value for the purposes of form submission. The element’s value is the value of the element’s value attribute, if there is one; otherwise the empty string. The element’s optional value is the value of the element’s value attribute, if there is one; otherwise null.

A button (and its value) is only included in the form submission if the button itself was used to initiate the form submission.

The type getter steps are:

If this is a submit button, then return “submit“.
Let state be this‘s type attribute.
Assert: state is not in the Submit Button state.
If state is in the Auto state, then return “button“.
Return the keyword value corresponding to state.

The willValidate, validity, and validationMessage IDL attributes, and the checkValidity(), reportValidity(), and setCustomValidity() methods, are part of the constraint validation API. The labels IDL attribute provides a list of the element’s labels. The disabled, form, and name IDL attributes are part of the element’s forms API.

The following button is labeled “Show hint” and pops up a dialog box when activated:

<button type=button
        onclick="alert('This 15-20 minute piece was composed by George Gershwin.')">
 Show hint
</button>

The following shows how buttons can use commandfor to show and hide an element with the popover attribute when activated:

<button type=button
        commandfor="the-popover"
        command="show-popover">
 Show menu
</button>
<div popover
     id="the-popover">
 <button commandfor="the-popover"
         command="hide-popover">
  Hide menu
 </button>
</div>

The following shows how buttons can use commandfor with a custom command keyword on an element, demonstrating how one could use custom commands for unspecified behavior:

<button type=button
        commandfor="the-image"
        command="--rotate-landscape">
 Rotate Left
</button>
<button type=button
        commandfor="the-image"
        command="--rotate-portrait">
 Rotate Right
</button>
<img id="the-image"
     src="photo.jpg">
<script>
  const image = document.getElementById("the-image");
  image.addEventListener("command", (event) => {
   if ( event.command == "--rotate-landscape" ) {
    event.target.style.rotate = "-90deg"
   } else if ( event.command == "--rotate-portrait" ) {
    event.target.style.rotate = "0deg"
   }
  });
</script>

4.10.7 The `select` element

Firefox1+Safari1+Chrome1+

Opera2+Edge79+

Edge (Legacy)12+Internet ExplorerYes

Firefox Android4+Safari iOS?Chrome Android?WebView Android37+Samsung Internet?Opera Android10.1+

Keyword	State	Brief description
`soft`	Soft	Text is not to be wrapped when submitted (though can still be wrapped in the rendering).
`hard`	Hard	Text is to have newlines added by the user agent so that the text is wrapped when it is submitted.

티스토리 수익 글 보기