The HTMLFormControlsCollection interface is used for
collections of listed
- elements in form elements.
[Exposed=Window]
interface HTMLFormControlsCollection : HTMLCollection {
@@ -23172,10 +23172,12 @@ document.body.appendChild(wbr);href attribute.
- Similarly, for form elements with a rel
+
Similarly, for forms
+ with a rel
attribute, links must be created for the keywords of the rel
attribute as defined for those keywords in the link types section.
- form elements that do not have a rel attribute,
+ forms
+ that do not have a rel attribute,
or whose rel attribute has no keywords that are defined as
specifying hyperlinks, must also create a hyperlink.
@@ -23807,8 +23809,8 @@ document.body.appendChild(wbr);
This is also used by form submission for
- the form element. The exception for a elements is for compatibility with
- web content.
a elements is for
+ compatibility with web content.
To get an element's noopener, given an a, area, or
form element element and a string target:
linka and areaformform elements.form elements; it creates a
+ form elements; it creates an external
- resource link.form elements; it annotates other hyperlinks created by the
- element.Form submissions are exposed to servers in a variety of ways, most commonly as HTTP GET or POST
requests. To specify the exact method used, the method
- attribute is specified on the form element. This doesn't specify how the form data is
+ attribute is specified on the form.
+ This doesn't specify how the form data is
encoded, though; to specify that, you use the enctype
attribute. You also have to specify the URL of the service that will handle the
submitted data, using the action attribute.
Denotes elements that can be used for constructing the entry list when a
- form element is submitted.
Denotes elements that can be affected when a form element is reset.
Denotes elements that can be affected when a form is + reset.
HTMLFormElement.The form element represents a hyperlink that can be
+
A form + represents a hyperlink that can be manipulated through a collection of form-associated elements, some of which can represent editable values that can be submitted to a server for processing.
@@ -43315,7 +43320,8 @@ interface HTMLFormElement : HTMLElement { case-insensitive match for "UTF-8".
The name attribute
- represents the form's name within the forms
+ represents the form's
+ name within the forms
collection. The value must not be the empty string, and the value must be unique amongst the
form elements in the forms collection that
it is in, if any.
The rel attribute on
- form elements controls what kinds of links the elements create. The attribute's value
+ forms
+ controls what kinds of links the elements create. The attribute's value
must be a unordered set of unique space-separated tokens. The allowed keywords and their meanings are defined in an earlier section.
The rel's supported
tokens are the keywords defined in HTML link types which are
- allowed on form elements, impact the processing model, and are supported by the user
+ allowed on forms,
+ impact the processing model, and are supported by the user
agent. The possible supported tokens are noreferrer, noopener, and opener. rel's HTMLFormElement : HTMLElement {
elements
IDL attribute must return an HTMLFormControlsCollection rooted at the
- form element's root, whose filter matches form's root, whose filter matches listed elements whose form owner is the
- form element, with the exception of input elements whose type attribute is in the form, with the exception of input elements whose
+ type attribute is in the Image Button state, which must, for historical reasons, be
excluded from this particular collection.
To determine the value of an indexed property for a
- form element, the user agent must return the value returned by the form,
+ the user agent must return the value returned by the item method on the elements collection, when invoked with the given index as its
argument.
Each Each form
+ has a mapping of names to elements called the past names
map. It is used to persist names of controls even when they change names. The supported property names consist of the names obtained from the following
@@ -43497,7 +43507,8 @@ interface HTMLFormElement : HTMLElement {
For each listed element candidate
- whose form owner is the For each form element has a mapping of names to elements called the past names
+ form element, with the exception of any
+ whose form owner is the form,
+ with the exception of any
input elements whose type attribute is in the
Image Button state:img element candidate whose form owner is the
- form element:
To determine the value of a named property name
- for a form element, the user agent must run the following steps:
Let candidates be a live If candidates is empty, let candidates be a live
If candidates is empty, name is the name of one of
- the entries in the RadioNodeList object
containing all the listed elements, whose form
- owner is the form element, that have either an is the form, that have either an id attribute or a name attribute equal
to name, with the exception of input elements whose type attribute is in the HTMLFormElement : HTMLElement {
RadioNodeList object containing all the img elements, whose form
- owner is the form element, that have either an is the form, that have either an id attribute or a name attribute
equal to name, in tree order.form element's past names map: return the object
- associated with name in that map.
If candidates contains more than one node, return candidates.
Otherwise, candidates contains exactly one node. Add a mapping from
- name to the node in candidates in the form
- element's past names map, replacing the previous entry with the same name, if
- any.
Return the node in candidates.
If an element listed in a form element's past names map changes
+
If an element listed in a form's + past names map changes form owner, then its entries must be removed from that map.
-Otherwise, if element has an ancestor Otherwise, if element has an ancestor
+ form, then associate element with the nearest such
- ancestor form element, then form element.
This example is a non-conforming document, though, as it is a violation of the content models
- to nest form elements, and there is a parse error for the forms,
+ and there is a parse error for the </form> tag.
The name content attribute gives the name of the form control, as
- used in form submission and in the form element's form submission and in the form's elements object. If the attribute is specified, its value must
not be the empty string or isindex.
Attributes for form submission can be specified both on form elements
+
Attributes for form submission can be specified both on
+ forms
and on submit buttons (elements that represent buttons
that submit forms, e.g. an input element whose type attribute is in the Submit Button state).
-
The attributes for form submission that may be specified on form
- elements are action, The attributes for form submission that may be specified on
+ forms
+ are action, enctype, method, novalidate, and target.
formnovalidate, and formtarget. When omitted, they default to the values given on
- the corresponding attributes on the form element.
+ the corresponding attributes on the form.
dialog, mapping to the state dialog, indicating that submitting the form is
+ data-x="attr-fs-method-dialog">dialog, indicating that submitting the
+ form is
intended to close the dialog box in which the form finds itself, if any, and
otherwise not submit.In this example, a form is used with a dialog. The In this example, a form
+ is used with a dialog. The method attribute's "dialog" keyword is used to have the dialog
automatically close when the form is submitted.
When the user agent is required to statically validate the constraints of
- form element form, it must run the following steps, which return
+ a form
+ form, it must run the following steps, which return
either a positive result (all the controls in the form are valid) or a negative
result (there are invalid controls) along with a (possibly empty) list of elements that are
invalid and for which no script has claimed responsibility:
If a user agent is to interactively validate the constraints of form
- element form, then the user agent must run the following steps:
If a user agent is to interactively validate the constraints of + form + form, then the user agent must run the following steps:
Statically validate the constraints of form, and let @@ -56541,9 +56575,9 @@ fur
A form element's default button is the first A form's default button is the first submit button in tree order whose form
- owner is that form element.
If the user agent supports letting the user submit a form implicitly (for example, on some platforms hitting the "enter" key while a text control is focused implicitly submits @@ -56558,12 +56592,14 @@ fur
If the form has
no submit button, then the implicit submission
mechanism must do nothing if the form has more than one field that blocks implicit
- submission, and must submit the form
- element from the form element itself otherwise.
For the purpose of the previous paragraph, an element is a field that blocks implicit
- submission of a Each Each form has a constructing entry list
+ boolean, initially false. Each Each form has a firing submission events
+ boolean, initially false. When a Each Each form
+ has a planned navigation, which is either null or a
+ task; when the
+ form is first created, its
planned navigation must be set to null. In the behaviors described below, when the
user agent is required to plan to navigate to a particular resource destination, it must run the following steps:form element if it is an input element whose
- form owner is that form element and whose of a form
+ if it is an input element whose
+ form owner is that form and whose type attribute is in one of the following states:
Text,
Search,
@@ -56586,13 +56622,13 @@ fur
Form submission algorithm
- form element has a constructing entry list boolean, initially
- false.form element has a firing submission events boolean, initially
- false.form element form is When a form form is submitted from an element submitter
(typically a button), optionally with a submitted from submit() method flag set, the user agent must run the
@@ -56771,8 +56807,10 @@ fur
defining this, act in a manner analogous to that defined in this specification for similar
schemes.form element has a planned navigation, which is either null or a
- task; when the form is first created, its
+
If the If the form's
+ link types include the form element's link types include the noreferrer keyword, then set destination's referrer to "no-referrer".
If the form has a non-null planned navigation, remove it from
- its task queue.
If the form has a non-null + planned navigation, remove it from its task queue.
Queue an element task on the DOM manipulation task source given
- the form element and the following steps:
Set the form's planned navigation to null.
Set the form's + planned navigation to null.
Navigate target browsing context to destination, with historyHandling set to @@ -56803,8 +56843,8 @@ fur
Set the form's planned navigation to the just-queued task.
Set the form's planned navigation + to the just-queued task.
The behaviors are as follows:
@@ -57204,12 +57244,12 @@ furLet encoding be the document's character encoding.
If the form element has an If the form has an accept-charset attribute, set encoding to
the return value of running these substeps:
Let input be the value of the Let input be the value of the form's form element's accept-charset attribute.
Let candidate encoding labels be the result of form. Operations on the FormData
+ object will affect form data to be submitted.
The formData attribute must return the value it was
initialized to. It represents a FormData object associated to the entry list that is
- constructed when the form is
- submitted.
When a form element form is When a form form is reset, run these steps:
You can use the custom element my-checkbox like a built-in
form-associated element. For example, putting it in form or label
associates the my-checkbox element with them, and submitting the
- form will send data provided by my-checkbox implementation.
+ form
+ will send data provided by my-checkbox implementation.
<form action="..." method="...">
@@ -68797,10 +68838,10 @@ customElements.define("x-foo", class extends HTMLElement {
If element is a form-associated custom element, then:
Reset the form owner of element. If element is
- associated with a form element, then
+ associated with a form, then
enqueue a custom element callback reaction with element, callback
- name "formAssociatedCallback", and « the associated form
- ».
formAssociatedCallback", and « the associated
+ form ».
If element is disabled, then enqueue a custom element callback reaction with element, callback name @@ -70386,7 +70427,8 @@ Demos: constraint validation and that satisfy their constraints
form elements that are not the form owner of any elements that
+ form elements that are the form owner of one or more elements
+ Similarly, a canvas element with the hidden
attribute could be used by a scripted graphics engine as an off-screen buffer, and a form control
- could refer to a hidden form element using its form using its form attribute.
The autocapitalize attribute can be used on an editing host to control autocapitalization behavior for the hosted
editable region, on an input or textarea element to control the behavior
- for inputting text into that element, or on a form element to control the default
+ for inputting text into that element, or on a form
+ to control the default
behavior for all autocapitalize-inheriting elements
- associated with the form element.
+ associated with the form.
The Returns the current autocapitalization state for the element, or an empty string if it hasn't
been set. Note that for autocapitalize attribute never causes
autocapitalization to be enabled for input elements whose
input and textarea elements that inherit their
- state from a form element, this will return the autocapitalization state of the
- form element, but for an element in an editable region, this will not return the
- autocapitalization state of the editing host (unless this element is, in fact, the editing
- host).
Can be set, to set the autocapitalize content
attribute (and thereby change the autocapitalization behavior for the element).
head element pointer gets set to point to this node.
The form element pointer points to the last
- form element that was opened and whose end tag has not yet been seen. It is used to
+ form (form or search element)
+ that was opened and whose end tag has not yet been seen. It is used to
make form controls associate with forms in the face of dramatically bad markup, for historical
reasons. It is ignored inside template elements.
form element
pointer, then associate element
- with the form element pointed to by the form element
+ with the form pointed to by the
+ form element
pointer and set element's parser inserted flag.
Return element.
If the form element pointer is not null, and there is
+
If the form element pointer is not null, and there is
no template element on the stack of open elements, then this is a
parse error; ignore the token.
Insert an HTML element for the token, and, if there is no template
element on the stack of open elements, set the form element pointer to point to the element created.
If the stack of open elements does not have a form element in scope, then this is a parse
- error; return and ignore the token.
Generate implied end tags.
If the current node is not a form element, then this is a
- parse error.
If the current node is not a form, + then this is a parse error.
Pop elements from the stack of open elements until a form
- element has been popped from the stack.
Pop elements from the stack of open elements until a
+ form (form or search element)
+ has been popped from the stack.
Parse error.
If there is a template element on the stack of open elements, or if
- the form element pointer is not null, ignore the
+ the form element pointer is not null, ignore the
token.
Otherwise:
Insert an HTML element for the token, and set the form element pointer to point to the element created.
Pop that form element off the stack of open elements.
Pop that form off the + stack of open elements.
@@ -115060,8 +115108,9 @@ document.body.appendChild(text);form
- element ancestor (use of the form element pointer in the parser)form element pointer in the parser)template elements.htmlheadbodyform id="outer"divform id="inner"inputThe input element will be associated with the inner form element.
+
The input element will be associated with the inner
+ form.
Now, if this tree structure is serialized and reparsed, the <form
id="inner"> start tag will be ignored, and so the input element will be
- associated with the outer form element instead.
<html><head></head><body><form id="outer"><div><form id="inner"><input></form></div></form></body></html>Set the parser's form element pointer to the nearest node to the
- context element that is a form
- element (going straight up the ancestor chain, and including the element itself, if it is a
- form element), if any. (If there is no such form element, the
- form element pointer keeps its initial value, null.)
Set the parser's form element pointer
+ to the nearest node to the context
+ element that is a form
+ (going straight up the ancestor chain, and including the element itself, if it is a
+ form), if any. (If there is no such
+ form, the
+ form element pointer keeps its initial value, null.)
urn on link elementsSpecify the preferred persistent identifier using the href attribute instead.
accept on form elementsaccept on formsUse the accept attribute directly on the input elements instead.
hreflang on area
@@ -124028,7 +124080,7 @@ interface External {
select;
textarea;
form-associated custom elements
- form element
+ formaction
@@ -125821,8 +125873,9 @@ INSERT INTERFACES HERE
formdata
FormDataEvent
- form elements
- form element when it is constructing the entry list
+ hashchange
@@ -125924,8 +125977,9 @@ INSERT INTERFACES HERE
reset
Event
- form elements
- form element when it is reset
+ securitypolicyviolation
@@ -125954,8 +126008,9 @@ INSERT INTERFACES HERE
submit
SubmitEvent
- form elements
- form element when it is submitted
+ toggle