(the part in parentheses)
that evaluates to true, or using the last item (calc(33vw -
100px)) if they all evaluate to false.
For example, if the viewport width is 29em, then (max-width: 30em)
evaluates to true and 100vw is used, so the image size, for the
purpose of resource selection, is 29em. If the viewport width is
instead 32em, then (max-width: 30em) evaluates to false, but
(max-width: 50em) evaluates to true and 50vw is used, so the image
size, for the purpose of resource selection, is 16em (half the
viewport width). Notice that the slightly wider viewport results
in a smaller image because of the different layout.
The user agent can then calculate the effective pixel density and
choose an appropriate resource similarly to the previous example.
Art direction-based selection
The picture element and the source element, together with the
media attribute, can be used, to provide multiple images that vary
the image content (for intance the smaller image might be a
cropped version of the bigger image).
The user agent will choose the first source element for which the
media query in the media attribute matches, and then choose an
appropriate URL from its srcset attribute.
The rendered size of the image varies depending on which resource
is chosen. To specify dimensions that the user agent can use
before having downloaded the image, CSS can be used.
img { width: 300px; height: 300px }
@media (min-width: 32em) { img { width: 500px; height:300px } }
@media (min-width: 45em) { img { width: 700px; height:400px } }
This example combines art direction- and device-pixel-ratio-based
selection. A banner that takes half the viewport is provided in
two versions, one for wide screens and one for narrow screens.
Image format-based selection
The type attribute on the source element can be used, to provide
multiple images in different formats.
From today’s featured article
Marie Lloyd music hall singer, ...
In this example, the user agent will choose the first source that
has a type attribute with a supported MIME type. If the user agent
supports WebP images, the first source element will be chosen. If
not, but the user agent does support JPEG XR images, the second
source element will be chosen. If neither of those formats are
supported, the img element will be chosen.
4.7.2. Dependencies
Media Queries [MEDIAQ]
CSS Values and Units [CSS-VALUES]
CSS Syntax [CSS-SYNTAX-3]
Parse a comma-separated list of component values
component value
4.7.3. The picture element
Categories:
Flow content.
Phrasing content.
Embedded content.
Contexts in which this element can be used:
Where embedded content is expected.
Content model:
Zero or more source elements, followed by one img element,
optionally intermixed with script-supporting elements.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
None
DOM interface:
interface HTMLPictureElement : HTMLElement {};
The picture element is a container which provides multiples sources to its
contained img element to allow authors to declaratively control or give
hints to the user agent about which image resource to use, based on the
screen pixel density, viewport size, image format, and other factors. It
represents its children.
The picture element is somewhat different from the similar-looking video
and audio elements. While all of them contain source elements, the source
element’s src attribute has no meaning when the element is nested within a
picture element, and the resource selection algorithm is different. As
well, the picture element itself does not display anything; it merely
provides a context for its contained img element that enables it to choose
from multiple URLs.
4.7.4. The source element
Categories:
None.
Contexts in which this element can be used:
As a child of a picture element, before the img element.
As a child of a media element, before any flow content or track
elements.
Content model:
Nothing.
Tag omission in text/html:
No end tag
Content attributes:
Global attributes
src - Address of the resource
type - Type of embedded resource
srcset - Images to use in different situations (e.g.,
high-resolution displays, small monitors, etc)
sizes - Image sizes between breakpoints
media - Applicable media
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
DOM interface:
interface HTMLSourceElement : HTMLElement {
attribute DOMString src;
attribute DOMString type;
attribute DOMString srcset;
attribute DOMString sizes;
attribute DOMString media;
};
The source element allows authors to specify multiple alternative source
sets for img elements or multiple alternative media resources for media
elements. It does not represent anything on its own.
The type attribute may be present. If present, the value must be a valid
MIME type.
The remainder of the requirements depend on whether the parent is a
picture element or a media element:
source element’s parent is a picture element
The srcset content attribute must be present, and must consist of
one or more image candidate strings, each separated from the next
by a U+002C COMMA character (,). If an image candidate string
contains no descriptors and no space characters after the URL, the
following image candidate string, if there is one, must begin with
one or more space characters.
If the srcset attribute has any image candidate strings using a
width descriptor, the sizes content attribute must also be
present, and the value must be a valid source size list.
The media content attribute may also be present. If present, the
value must contain a valid media query list.
The type gives the type of the images in the source set, to allow
the user agent to skip to the next source element if it does not
support the given type.
If the type attribute is not specified, the user agent will not
select a different source element if it finds that it does not
support the image format after fetching it.
When a source element has a following sibling source element or
img element with a srcset attribute specified, it must have at
least one of the following:
* A media attribute specified with a value that, after
stripping leading and trailing white space, is not the empty
string and is not an ASCII case-insensitive match for the
string "all".
* A type attribute specified.
The src attribute must not be present.
source element’s parent is a media element
The src attribute gives the address of the media resource. The
value must be a valid non-empty URL potentially surrounded by
spaces. This attribute must be present.
Dynamically modifying a source element and its attribute when the
element is already inserted in a video or audio element will have
no effect. To change what is playing, just use the src attribute
on the media element directly, possibly making use of the
canPlayType() method to pick from amongst available resources.
Generally, manipulating source elements manually after the
document has been parsed is an unnecessarily complicated approach.
The type content attribute gives the type of the media resource,
to help the user agent determine if it can play this media
resource before fetching it. If specified, its value must be a
valid MIME type. The codecs parameter, which certain MIME types
define, might be necessary to specify exactly how the resource is
encoded. [RFC6381]
The following list shows some examples of how to use the codecs=
MIME parameter in the type attribute.
H.264 Constrained baseline profile video (main and extended
video compatible) level 3 and Low-Complexity AAC audio in MP4
container
H.264 Extended profile video (baseline-compatible) level 3
and Low-Complexity AAC audio in MP4 container
H.264 Main profile video level 3 and Low-Complexity AAC audio
in MP4 container
H.264 "High" profile video (incompatible with main, baseline,
or extended profiles) level 3 and Low-Complexity AAC audio in
MP4 container
MPEG-4 Visual Simple Profile Level 0 video and Low-Complexity
AAC audio in MP4 container
MPEG-4 Advanced Simple Profile Level 0 video and
Low-Complexity AAC audio in MP4 container
MPEG-4 Visual Simple Profile Level 0 video and AMR audio in
3GPP container
Theora video and Vorbis audio in Ogg container
Theora video and Speex audio in Ogg container
Vorbis audio alone in Ogg container
Speex audio alone in Ogg container
FLAC audio alone in Ogg container
Dirac video and Vorbis audio in Ogg container
The srcset, sizes, and media attributes must not be present.
If a source element is inserted as a child of a media element that has no
src attribute and whose networkState has the value NETWORK_EMPTY, the user
agent must invoke the media element’s resource selection algorithm.
The IDL attributes src, type, srcset, sizes and media must reflect the
respective content attributes of the same name.
If the author isn’t sure if user agents will all be able to render the
media resources provided, the author can listen to the error event on the
last source element and trigger fallback behavior:
...
4.7.5. The img element
Categories:
Flow content.
Phrasing content.
Embedded content.
Form-associated element.
If the element has a usemap attribute: interactive content.
Palpable content.
Contexts in which this element can be used:
Where embedded content is expected.
Content model:
Nothing
Tag omission in text/html:
No end tag.
Content attributes:
Global attributes
alt - Replacement text for use when images are not available
src - Address of the resource
srcset - Images to use in different situations (e.g.,
high-resolution displays, small monitors, etc)
sizes - Image sizes between breakpoints
crossorigin - How the element handles crossorigin requests
usemap - Name of image map to use
ismap - Whether the image is a server-side image map
width - Horizontal dimension
height - Vertical dimension
referrerpolicy - Referrer policy for fetches initiated by the
element
longdesc - A url that provides a link to an expanded description
of the image, defined in [html-longdesc]
Allowed ARIA role attribute values:
presentation or none role only, for an img element whose alt
attribute’s value is empty (alt=""), otherwise Any role value.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
[NamedConstructor=Image(optional unsigned long width, optional unsigned long height)]
interface HTMLImageElement : HTMLElement {
attribute DOMString alt;
attribute DOMString src;
attribute DOMString srcset;
attribute DOMString sizes;
attribute DOMString? crossOrigin;
attribute DOMString useMap;
attribute DOMString longDesc;
attribute boolean isMap;
attribute unsigned long width;
attribute unsigned long height;
readonly attribute unsigned long naturalWidth;
readonly attribute unsigned long naturalHeight;
readonly attribute boolean complete;
readonly attribute DOMString currentSrc;
attribute DOMString referrerPolicy;
};
An img element represents an image and its fallback content.
The image given by the src and srcset attributes, and any previous sibling
source elements' srcset attributes if the parent is a picture element, is
the embedded content; the value of the alt attribute and the content
referred to by the longdesc attribute are the img element’s fallback
content, and provide equivalent content for users and user agents who
cannot process images or have image loading disabled.
Requirements for alternative representations of the image are described in
the next section.
The src attribute must be present, and must contain a valid non-empty URL
potentially surrounded by spaces referencing a non-interactive, optionally
animated, image resource that is neither paged nor scripted.
The srcset attribute may also be present. If present, its value must
consist of one or more image candidate strings, each separated from the
next by a U+002C COMMA character (,). If an image candidate string
contains no descriptors and no space characters after the URL, the
following image candidate string, if there is one, must begin with one or
more space characters.
An image candidate string consists of the following components, in order,
with the further restrictions described below this list:
1. Zero or more space characters.
2. A valid non-empty URL that does not start or end with a U+002C COMMA
character (,), referencing a non-interactive, optionally animated,
image resource that is neither paged nor scripted.
3. Zero or more space characters.
4. Zero or one of the following:
* A width descriptor, consisting of: a space character, a valid
non-negative integer giving a number greater than zero
representing the width descriptor value, and a U+0077 LATIN SMALL
LETTER W character.
* A pixel density descriptor, consisting of: a space character, a
valid floating-point number giving a number greater than zero
representing the pixel density descriptor value, and a U+0078
LATIN SMALL LETTER X character.
5. Zero or more space characters.
There must not be an image candidate string for an element that has the
same width descriptor value as another image candidate string’s width
descriptor value for the same element.
There must not be an image candidate string for an element that has the
same pixel density descriptor value as another image candidate string’s
pixel density descriptor value for the same element. For the purpose of
this requirement, an image candidate string with no descriptors is
equivalent to an image candidate string with a 1x descriptor.
If a source element has a sizes attribute present or an img element has a
sizes attribute present, all image candidate strings for that element must
have the width descriptor specified.
If an image candidate string for a source or img element has the width
descriptor specified, all other image candidate strings for that element
must also have the width descriptor specified.
The specified width in an image candidate string’s width descriptor must
match the intrinsic width in the resource given by the image candidate
string’s URL, if it has an intrinsic width.
The requirements above imply that images can be static bitmaps (e.g.,
PNGs, GIFs, JPEGs), single-page vector documents (single-page PDFs, XML
files with an SVG document element), animated bitmaps (APNGs, animated
GIFs), animated vector graphics (XML files with an SVG document element
that use declarative SMIL animation), and so forth. However, these
definitions preclude SVG files with script, multipage PDF files,
interactive MNG files, HTML documents, plain text documents, and so forth.
[PNG] [GIF] [JPEG] [PDF] [XML] [APNG] [SVG11] [MNG]
If the srcset attribute is present, the sizes attribute may also be
present. If present, its value must be a valid source size list.
A valid source size list is a string that matches the following grammar:
[CSS-VALUES] [MEDIAQ]
= # [ , ]? |
=
=
A must not be negative.
Percentages are not allowed in a , to avoid confusion
about what it would be relative to. The vw unit can be used for sizes
relative to the viewport width.
The img element must not be used as a layout tool. In particular, img
elements should not be used to display transparent images, as such images
rarely convey meaning and rarely add anything useful to the document.
----------------------------------------------------------------------
The crossorigin attribute is a CORS settings attribute. Its purpose is to
allow images from third-party sites that allow cross-origin access to be
used with canvas.
The referrerpolicy attribute is a referrer policy attribute. Its purpose
is to set the referrer policy used when fetching the image.
[REFERRERPOLICY]
----------------------------------------------------------------------
An img element has a current request and a pending request. The current
request is initially set to a new image request. The pending request is
initially set to null. The current request is usually referred to as the
img element itself.
An image request has a state, current URL and image data.
An image request’s state is one of the following:
Unavailable
The user agent hasn’t obtained any image data, or has obtained
some or all of the image data but hasn’t yet decoded enough of the
image to get the image dimensions.
Partially available
The user agent has obtained some of the image data and at least
the image dimensions are available.
Completely available
The user agent has obtained all of the image data and at least the
image dimensions are available.
Broken
The user agent has obtained all of the image data that it can, but
it cannot even decode the image enough to get the image dimensions
(e.g., the image is corrupted, or the format is not supported, or
no data could be obtained).
An image request’s current URL is initially the empty string.
An image request’s image data is the decoded image data.
When an image request is either in the partially available state or in the
completely available state, it is said to be available.
An image request is initially unavailable.
When an img element is available, it provides a paint source whose width
is the image’s density-corrected intrinsic width (if any), whose height is
the image’s density-corrected intrinsic height (if any), and whose
appearance is the intrinsic appearance of the image.
In a browsing context where scripting is disabled, user agents may obtain
images immediately or on demand. In a browsing context where scripting is
enabled, user agents must obtain images immediately.
A user agent that obtains images immediately must immediately update the
image data of an img element, with the restart animation flag set if so
stated, whenever that element is created or has experienced relevant
mutations.
A user agent that obtains images on demand must update the image data of
an img element whenever it needs the image data (i.e., on demand), but
only if the img element is in the unavailable state. When an img element
has experienced relevant mutations, if the user agent only obtains images
on demand, the img element must return to the unavailable state.
The relevant mutations for an img element are as follows:
* The element’s src, srcset, width, or sizes attributes are set,
changed, or removed.
* The element’s src attribute is set to the same value as the previous
value. This must set the restart animation flag for the update the
image data algorithm.
* The element’s crossorigin attribute’s state is changed.
* The element is inserted into or removed from a picture parent element.
* The element’s parent is a picture element and a source element is
inserted as a previous sibling.
* The element’s parent is a picture element and a source element that
was a previous sibling is removed.
* The element’s parent is a picture element and a source element that is
a previous sibling has its srcset, sizes, media or type attributes
set, changed, or removed.
* The element’s adopting steps are run.
Each img element has a last selected source, which must initially be null.
Each image request has a current pixel density, which must initially be
undefined.
When an img element has a current pixel density that is not 1.0, the
element’s image data must be treated as if its resolution, in device
pixels per CSS pixels, was the current pixel density. The image’s
density-corrected intrinsic width and height are the intrinsic width and
height after taking into account the current pixel density.
For example, given a screen with 96 CSS pixels per CSS inch, if the
current pixel density is 3.125, that means that there are 96 × 3.125 = 300
device pixels per CSS inch, and thus if the image data is 300x600, it has
intrinsic dimensions of 300 ÷ 3.125 = 96 CSS pixels by 600 ÷ 3.125 = 192
CSS pixels. With a current pixel density of 2.0 (192 device pixels per CSS
inch) and the same image data (300x600), the intrinsic dimensions would be
150x300.
Each Document object must have a list of available images. Each image in
this list is identified by a tuple consisting of an absolute URL, a CORS
settings attribute mode, and, if the mode is not No CORS, an origin. Each
image furthermore has an ignore higher-layer caching flag. User agents may
copy entries from one Document object’s list of available images to
another at any time (e.g., when the Document is created, user agents can
add to it all the images that are loaded in other Documents), but must not
change the keys of entries copied in this way when doing so, and must
unset the ignore higher-layer caching flag for the copied entry. User
agents may also remove images from such lists at any time (e.g., to save
memory). User agents must remove entries in the list of available images
as appropriate given higher-layer caching semantics for the resource
(e.g., the HTTP Cache-Control response header) when the ignore
higher-layer caching flag is unset.
The list of available images is intended to enable synchronous switching
when changing the src attribute to a URL that has previously been loaded,
and to avoid re-downloading images in the same document even when they
don’t allow caching per HTTP. It is not used to avoid re-downloading the
same image while the previous image is still loading.
For example, if a resource has the HTTP response header Cache-Control:
must-revalidate, the user agent would remove it from the list of available
images but could keep the image data separately, and use that if the
server responds with a 204 No Content status.
When the user agent is to update the image data of an img element,
optionally with the restart animations flag set, it must run the following
steps:
1. If the element’s node document is not the active document, then run
these substeps:
1. Continue running this algorithm in parallel.
2. Wait until the element’s node document is the active document.
3. If another instance of this algorithm for this img element was
started after this instance (even if it aborted and is no longer
running), then abort these steps.
4. Queue a microtask to continue this algorithm.
2. If the user agent cannot support images, or its support for images has
been disabled, then abort the image request for the current request
and the pending request, set current request to the unavailable state,
let pending request be null, and abort these steps.
3. If the element does not use srcset or picture and it does not have a
parent or it has a parent but it is not a picture element, and it has
a src attribute specified and its value is not the empty string, let
selected source be the value of the element’s src attribute, and
selected pixel density be 1.0. Otherwise, let selected source be null
and selected pixel density be undefined.
4. Let the img element’s last selected source be selected source.
5. If selected source is not null, run these substeps:
1. Parse selected source, relative to the element’s node document.
If that is not successful, then abort these inner set of steps.
Otherwise, let urlString be the resulting URL string.
2. Let key be a tuple consisting of urlString, the img element’s
crossorigin attribute’s mode, and, if that mode is not No CORS,
the node document’s origin.
3. If the list of available images contains an entry for key, run
these subsubsteps:
1. Set the ignore higher-layer caching flag for that entry.
2. Abort the image request for the current request and the
pending request.
3. Let pending request be null.
4. Let current request be a new image request whose image data
is that of the entry and whose state is set to the
completely available state.
5. Update the presentation of the image appropriately.
6. Let the current request’s current pixel density be selected
pixel density.
7. Queue a task to restart the animation if restart animation
is set, change current request’s current URL to urlString,
and then fire a simple event named load at the img element.
8. Abort the update the image data algorithm.
6. in parallel await a stable state, allowing the task that invoked this
algorithm to continue. The synchronous section consists of all the
remaining steps of this algorithm until the algorithm says the
synchronous section has ended. (Steps in synchronous sections are
marked with ⌛.)
7. ⌛ If another instance of this algorithm for this img element was
started after this instance (even if it aborted and is no longer
running), then abort these steps.
Only the last instance takes effect, to avoid multiple requests when,
for example, the src, srcset, and crossorigin attributes are all set
in succession.
8. ⌛ Let selected source and selected pixel density be the URL and pixel
density that results from selecting an image source, respectively.
9. ⌛ If selected source is null, run these substeps:
1. ⌛ Set the current request to the broken state, abort the image
request for the current request and the pending request, and let
pending request be null.
2. ⌛ Queue a task to change the current request’s current URL to the
empty string, and then, if the element has a src attribute or it
uses srcset or picture, fire a simple event named error at the
img element.
3. ⌛ Abort this algorithm.
10. ⌛ Queue a task to fire a progress event named loadstart at the img
element.
⌛ Parse selected source, relative to the element’s node document, and
let urlString be the resulting URL string. If that is not successful,
run these substeps:
1. ⌛ Abort the image request for the current request and the pending
request.
2. ⌛ Set the current request to the broken state.
3. ⌛ Let pending request be null.
4. ⌛ Queue a task to change the current request’s current URL to
selected source, fire a simple event named error at the img
element and then fire a simple event named loadend at the img
element.
5. ⌛ Abort the update the image data algorithm.
11. ⌛ If the pending request is not null, and urlString is the same as the
pending request’s current URL, then abort these steps.
⌛ If urlString is the same as the current request’s current URL, and
current request is in the partially available state, then abort the
image request for the pending request, queue a task to restart the
animation if restart animation is set, and abort these steps.
⌛ If the pending request is not null, abort the image request for the
pending request.
⌛ Let image request be a new image request whose current URL is
urlString.
⌛ If current request is in the unavailable state or the broken state,
let the current request be image request. Otherwise, let the pending
request be image request.
⌛ Let request be the result of creating a potential-CORS request given
urlString and the current state of the element’s crossorigin content
attribute.
⌛ Set request’s client to the element’s node document’s Window
object’s environment settings object and type to "image".
⌛ If the element uses srcset or picture, set request’s initiator to
"imageset".
⌛ Set request’s referrer policy to the current state of the element’s
referrerpolicy attribute.
⌛ Fetch request. Let this instance of the fetching algorithm be
associated with image request.
The resource obtained in this fashion, if any, is image request’s
image data. It can be either CORS-same-origin or CORS-cross-origin;
this affects the origin of the image itself (e.g., when used on a
canvas).
Fetching the image must delay the load event of the element’s node
document until the task that is queued by the networking task source
once the resource has been fetched (defined below) has been run.
This, unfortunately, can be used to perform a rudimentary port scan of
the user’s local network (especially in conjunction with scripting,
though scripting isn’t actually necessary to carry out such an
attack). User agents may implement cross-origin access control
policies that are stricter than those described above to mitigate this
attack, but unfortunately such policies are typically not compatible
with existing Web content.
If the resource is CORS-same-origin, each task that is queued by the
networking task source while the image is being fetched, if image
request is the current request, must fire a progress event named
progress at the img element.
12. End the synchronous section, continuing the remaining steps in
parallel, but without missing any data from fetching.
13. As soon as possible, jump to the first applicable entry from the
following list:
If the resource type is multipart/x-mixed-replace
The next task that is queued by the networking task
source while the image is being fetched must run the
following steps:
1. If image request is the pending request and at least
one body part has been completely decoded, abort the
image request for the current request, upgrade the
pending request to the current request.
2. Otherwise, if image request is the pending request
and the user agent is able to determine that image
request’s image is corrupted in some fatal way such
that the image dimensions cannot be obtained, abort
the image request for the current request, upgrade
the pending request to the current request and set
the current request’s state to broken.
3. Otherwise, if image request is the current request,
it is in the unavailable state, and the user agent
is able to determine image request’s image’s width
and height, set the current request’s state to
partially available.
4. Otherwise, if image request is the current request,
it is in the unavailable state, and the user agent
is able to determine that image request’s image is
corrupted in some fatal way such that the image
dimensions cannot be obtained, set the current
request’s state to broken.
Each task that is queued by the networking task source
while the image is being fetched must update the
presentation of the image, but as each new body part
comes in, it must replace the previous image. Once one
body part has been completely decoded, the user agent
must set the img element to the completely available
state and queue a task to fire a simple event named load
at the img element.
The progress and loadend events are not fired for
multipart/x-mixed-replace image streams.
If the resource type and data corresponds to a supported image
format, as described below
The next task that is queued by the networking task
source while the image is being fetched must run the
following steps:
1. If the user agent is able to determine image
request’s image’s width and height, and image
request is pending request, set image request’s
state to partially available.
2. Otherwise, if the user agent is able to determine
image request’s image’s width and height, and image
request is current request, update the img element’s
presentation appropriately and set image request’s
state to partially available.
3. Otherwise, if the user agent is able to determine
that image request’s image is corrupted in some
fatal way such that the image dimensions cannot be
obtained, and image request is pending request,
abort the image request for the current request and
the pending request, upgrade the pending request to
the current request, set current request to the
broken state, fire a simple event named error at the
img element, fire a simple event named loadend at
the img element, and abort these steps.
4. Otherwise, if the user agent is able to determine
that image request’s image is corrupted in some
fatal way such that the image dimensions cannot be
obtained, and image request is current request,
abort the image request for image request, fire a
simple event named error at the img element, fire a
simple event named loadend at the img element, and
abort these steps.
That task, and each subsequent task, that is queued by
the networking task source while the image is being
fetched, if image request is the current request, must
update the presentation of the image appropriately (e.g.,
if the image is a progressive JPEG, each packet can
improve the resolution of the image).
Furthermore, the last task that is queued by the
networking task source once the resource has been fetched
must additionally run these steps:
1. If image request is the pending request, abort the
image request for the current request, upgrade the
pending request to the current request and update
the img element’s presentation appropriately.
2. Set image request to the completely available state.
3. Add the image to the list of available images using
the key key, with the ignore higher-layer caching
flag set.
4. Fire a progress event or simple event named load at
the img element, depending on the resource in image
request.
5. Fire a progress event or simple event named loadend
at the img element, depending on the resource in
image request.
Otherwise
The image data is not in a supported file format; the
user agent must set image request to the broken state,
abort the image request for the current request and the
pending request, upgrade the pending request to the
current request if image request is the pending request,
and then queue a task to first fire a simple event named
error at the img element and then fire a simple event
named loadend at the img element.
To abort the image request for an image request image request means to run
the following steps:
1. Forget image request’s image data, if any.
2. Abort any instance of the fetching algorithm for image request,
discarding any pending tasks generated by that algorithm.
To upgrade the pending request to the current request for an img element
means to run the following steps:
1. Let the img element’s current request be the pending request.
2. Let the img element’s pending request be null.
To fire a progress event or simple event named type at an element e,
depending on resource r, means to fire a progress event named type at e if
r is CORS-same-origin, and otherwise fire a simple event named type at e.
While a user agent is running the above algorithm for an element x, there
must be a strong reference from the element’s node document to the element
x, even if that element is not in its Document.
An img element is said to use srcset or picture if it has a srcset
attribute specified or if it has a parent that is a picture element.
When an img element is in the completely available state and the user
agent can decode the media data without errors, then the img element is
said to be fully decodable.
Whether the image is fetched successfully or not (e.g., whether the
response status was an ok status) must be ignored when determining the
image’s type and whether it is a valid image.
This allows servers to return images with error responses, and have them
displayed.
The user agent should apply the image sniffing rules to determine the type
of the image, with the image’s associated Content-Type headers giving the
official type. If these rules are not applied, then the type of the image
must be the type given by the image’s associated Content-Type headers.
User agents must not support non-image resources with the img element
(e.g., XML files whose document element is an HTML element). User agents
must not run executable code (e.g., scripts) embedded in the image
resource. User agents must only display the first page of a multipage
resource (e.g., a PDF file). User agents must not allow the resource to
act in an interactive fashion, but should honor any animation in the
resource.
This specification does not specify which image types are to be supported.
----------------------------------------------------------------------
An img element is associated with a source set.
A source set is an ordered set of zero or more image sources and a source
size.
An image source is a URL, and optionally either a density descriptor, or a
width descriptor.
A source size is a . When a source size has a unit
relative to the viewport, it must be interpreted relative to the img
element’s document’s viewport. Other units must be interpreted the same as
in Media Queries. [MEDIAQ]
When asked to select an image source for a given img element el, user
agents must do the following:
1. Update the source set for el.
2. If el’s source set is empty, return null as the URL and undefined as
the pixel density and abort these steps.
3. Otherwise, take el’s source set and let it be source set.
4. If an entry b in source set has the same associated density descriptor
as an earlier entry a in source set, then remove entry b. Repeat this
step until none of the entries in source set have the same associated
density descriptor as an earlier entry.
5. In a user agent-specific manner, choose one image source from source
set. Let this be selected source.
6. Return selected source and its associated pixel density.
When asked to update the source set for a given img element el, user
agents must do the following:
1. Set el’s source set to an empty source set.
2. If el has a parent node and that is a picture element, let elements be
an array containing el’s parent node’s child elements, retaining
relative order. Otherwise, let elements be array containing only el.
3. If el has a width attribute, and parsing that attribute’s value using
the rules for parsing dimension values doesn’t generate an error or a
percentage value, then let width be the returned integer value.
Otherwise, let width be null.
4. Iterate through elements, doing the following for each item child:
1. If child is el:
1. If child has a srcset attribute, parse child’s srcset
attribute and let the returned source set be source set.
Otherwise, let source set be an empty source set.
2. Parse child’s sizes attribute with the fallback width width,
and let source set’s source size be the returned value.
3. If child has a src attribute whose value is not the empty
string and source set does not contain an image source with
a density descriptor value of 1, and no image source with a
width descriptor, append child’s src attribute value to
source set.
4. Normalize the source densities of source set.
5. Let el’s source set be source set.
6. Abort this algorithm.
2. If child is not a source element, continue to the next child.
Otherwise, child is a source element.
3. If child does not have a srcset attribute, continue to the next
child.
4. Parse child’s srcset attribute and let the returned source set be
source set.
5. If source set has zero image sources, continue to the next child.
6. If child has a media attribute, and its value does not match the
environment, continue to the next child.
7. Parse child’s sizes attribute with the fallback width width, and
let source set’s source size be the returned value.
8. If child has a type attribute, and its value is an unknown or
unsupported MIME type, continue to the next child.
9. Normalize the source densities of source set.
10. Let el’s source set be source set.
11. Abort this algorithm.
Each img element independently considers its previous sibling source
elements plus the img element itself for selecting an image source,
ignoring any other (invalid) elements, including other img elements in the
same picture element, or source elements that are following siblings of
the relevant img element.
When asked to parse a srcset attribute from an element, parse the value of
the element’s srcset attribute as follows:
1. Let input be the value passed to this algorithm.
2. Let position be a pointer into input, initially pointing at the start
of the string.
3. Let candidates be an initially empty source set.
4. Splitting loop: Collect a sequence of characters that are space
characters or U+002C COMMA characters. If any U+002C COMMA characters
were collected, that is a parse error.
5. If position is past the end of input, return candidates and abort
these steps.
6. Collect a sequence of characters that are not space characters, and
let that be url.
7. Let descriptors be a new empty list.
8. If url ends with a U+002C COMMA character (,), follow these substeps:
1. Remove all trailing U+002C COMMA characters from url. If this
removed more than one character, that is a parse error.
Otherwise, follow these substeps:
1. Descriptor tokenizer: Skip white space
2. Let current descriptor be the empty string.
3. Let state be in descriptor.
4. Let c be the character at position. Do the following depending on
the value of state. For the purpose of this step, "EOF" is a
special character representing that position is past the end of
input.
In descriptor
Do the following, depending on the value of c:
Space character
If current descriptor is not empty,
append current descriptor to
descriptors and let current descriptor
be the empty string. Set state to after
descriptor.
U+002C COMMA (,)
Advance position to the next character
in input. If current descriptor is not
empty, append current descriptor to
descriptors. Jump to the step labeled
descriptor parser.
U+0028 LEFT PARENTHESIS (()
Append c to current descriptor. Set
state to in parens.
EOF
If current descriptor is not empty,
append current descriptor to
descriptors. Jump to the step labeled
descriptor parser.
Anything else
Append c to current descriptor.
In parens
Do the following, depending on the value of c:
U+0029 RIGHT PARENTHESIS ())
Append c to current descriptor. Set
state to in descriptor.
EOF
Append current descriptor to
descriptors. Jump to the step labeled
descriptor parser.
Anything else
Append c to current descriptor.
After descriptor
Do the following, depending on the value of c:
Space character
Stay in this state.
EOF
Jump to the step labeled descriptor
parser.
Anything else
Set state to in descriptor. Set
position to the previous character in
input.
Advance position to the next character in input. Repeat this
substep.
In order to be compatible with future additions, this algorithm
supports multiple descriptors and descriptors with parens.
9. Descriptor parser: Let error be no.
10. Let width be absent.
11. Let density be absent.
12. Let future-compat-h be absent.
13. For each descriptor in descriptors, run the appropriate set of steps
from the following list:
If the descriptor consists of a valid non-negative integer
followed by a U+0077 LATIN SMALL LETTER W character
1. If the user agent does not support the sizes
attribute, let error be yes.
A conforming user agent will support the sizes
attribute. However, user agents typically implement
and ship features in an incremental manner in
practice.
2. If width and density are not both absent, then let
error be yes.
3. Apply the rules for parsing non-negative integers to
the descriptor. If the result is zero, let error be
yes. Otherwise, let width be the result.
If the descriptor consists of a valid floating-point number
followed by a U+0078 LATIN SMALL LETTER X character
1. If width, density and future-compat-h are not all
absent, then let error be yes.
2. Apply the rules for parsing floating-point number
values to the descriptor. If the result is less than
zero, let error be yes. Otherwise, let density be
the result.
If density is zero, the intrinsic dimensions will be
infinite. User agents are expected to have limits in
how big images can be rendered, which is allowed by
the hardware limitations clause.
If the descriptor consists of a valid non-negative integer
followed by a U+0068 LATIN SMALL LETTER H character
This is a parse error.
1. If future-compat-h and density are not both absent,
then let error be yes.
2. Apply the rules for parsing non-negative integers to
the descriptor. If the result is zero, let error be
yes. Otherwise, let future-compat-h be the result.
Anything else
Let error be yes.
14. If future-compat-h is not absent and width is absent, let error be
yes.
15. If error is still no, then append a new image source to candidates
whose URL is url, associated with a width width if not absent and a
pixel density density if not absent. Otherwise, there is a parse
error.
16. Return to the step labeled splitting loop.
When asked to parse a sizes attribute from an element, parse a
comma-separated list of component values from the value of the element’s
sizes attribute (or the empty string, if the attribute is absent), and let
unparsed sizes list be the result. [CSS-SYNTAX-3]
For each unparsed size in unparsed sizes list:
1. Remove all consecutive s from the end of unparsed
size. If unparsed size is now empty, that is a parse error; continue
to the next iteration of this algorithm.
2. If the last component value in unparsed size is a valid non-negative
, let size be its value and remove the component
value from unparsed size. Any CSS function other than the calc()
function is invalid. Otherwise, there is a parse error; continue to
the next iteration of this algorithm.
3. Remove all consecutive s from the end of unparsed
size. If unparsed size is now empty, return size and exit this
algorithm. If this was not the last item in unparsed sizes list, that
is a parse error.
4. Parse the remaining component values in unparsed size as a
. If it does not parse correctly, or it does parse
correctly but the evaluates to false, continue to
the next iteration of this algorithm. [MEDIAQ]
5. Return size and exit this algorithm.
If the above algorithm exhausts unparsed sizes list without returning a
size value, follow these steps:
1. If width is not null, return a with the value width and the
unit px.
2. Return 100vw.
A parse error for the algorithms above indicates a non-fatal mismatch
between input and requirements. User agents are encouraged to expose parse
errors somehow.
While a valid source size list only contains a bare
(without an accompanying ) as the last entry in the
, the parsing algorithm technically allows such at any
point in the list, and will accept it immediately as the size if the
preceding entries in the list weren’t used. This is to enable future
extensions, and protect against simple author errors such as a final
trailing comma.
An image source can have a density descriptor, a width descriptor, or no
descriptor at all accompanying its URL. Normalizing a source set gives
every image source a density descriptor.
When asked to normalize the source densities of a source set source set,
the user agent must do the following:
1. Let source size be source set’s source size.
2. For each image source in source set:
1. If the image source has a density descriptor, continue to the
next image source.
2. Otherwise, if the image source has a width descriptor, replace
the width descriptor with a density descriptor with a value of
the width descriptor divided by the source size and a unit of x.
If the source size is zero, the density would be infinity, which
results in the intrinsic dimensions being zero by zero.
3. Otherwise, give the image source a density descriptor of 1x.
The user agent may at any time run the following algorithm to update an
img element’s image in order to react to changes in the environment. (User
agents are not required to ever run this algorithm; for example, if the
user is not looking at the page any more, the user agent might want to
wait until the user has returned to the page before determining which
image to use, in case the environment changes again in the meantime.)
User agents are encouraged to run this algorithm in particular when the
user changes the viewport’s size (e.g., by resizing the window or changing
the page zoom), and when an img element is inserted into a document, so
that the density-corrected intrinsic width and height match the new
viewport, and so that the correct image is chosen when art direction is
involved.
1. in parallel await a stable state. The synchronous section consists of
all the remaining steps of this algorithm until the algorithm says the
synchronous section has ended. (Steps in synchronous sections are
marked with ⌛.)
2. ⌛ If the img element does not use srcset or picture, its node document
is not the active document, has image data whose resource type is
multipart/x-mixed-replace, or the pending request is not null, then
abort this algorithm.
3. ⌛ Let selected source and selected pixel density be the URL and pixel
density that results from selecting an image source, respectively.
4. ⌛ If selected source is null, then abort these steps.
5. ⌛ If selected source and selected pixel density are the same as the
element’s last selected source and current pixel density, then abort
these steps.
6. ⌛ Parse selected source, relative to the element’s node document, and
let urlString be the resulting URL string. If that is not successful,
abort these steps.
7. ⌛ Let corsAttributeState be the state of the element’s crossorigin
content attribute.
8. ⌛ Let origin be the origin of the img element’s node document.
9. ⌛ Let client be the img element’s node document’s Window object’s
environment settings object.
10. ⌛ Let key be a tuple consisting of urlString, corsAttributeState, and,
if corsAttributeState is not No CORS, origin.
11. ⌛ Let image request be a new image request whose current URL is
urlString
12. ⌛ Let the element’s pending request be image request.
13. End the synchronous section, continuing the remaining steps in
parallel.
14. If the list of available images contains an entry for key, then set
image request’s image data to that of the entry. Continue to the next
step.
Otherwise, run these substeps:
1. Let request be the result of creating a potential-CORS request
given urlString and corsAttributeState.
2. Set request’s client to client, type to "image", and set
request’s synchronous flag.
3. Set request’s referrer policy to the current state of the
element’s referrerpolicy attribute.
4. Let response be the result of fetching request.
5. If response’s unsafe response is a network error or if the image
format is unsupported (as determined by applying the image
sniffing rules, again as mentioned earlier), or if the user agent
is able to determine that image request’s image is corrupted in
some fatal way such that the image dimensions cannot be obtained,
or if the resource type is multipart/x-mixed-replace, then let
pending request be null and abort these steps.
6. Otherwise, response’s unsafe response is image request’s image
data. It can be either CORS-same-origin or CORS-cross-origin;
this affects the origin of the image itself (e.g., when used on a
canvas).
15. Queue a task to run the following substeps:
1. If the img element has experienced relevant mutations since this
algorithm started, then let pending request be null and abort
these steps.
2. Let the img element’s last selected source be selected source and
the img element’s current pixel density be selected pixel
density.
3. Set image request to the completely available state.
4. Add the image to the list of available images using the key key,
with the ignore higher-layer caching flag set.
5. Upgrade the pending request to the current request.
6. Update the img element’s presentation appropriately.
7. Fire a simple event named load at the img element.
----------------------------------------------------------------------
The task source for the tasks queued by algorithms in this section is the
DOM manipulation task source.
----------------------------------------------------------------------
What an img element represents depends on the src attribute and the alt
attribute.
If the src attribute is set and the alt attribute is set to the empty
string
The image is either decorative or supplemental to the rest of the
content, redundant with some other information in the document.
If the image is available and the user agent is configured to
display that image, then the element represents the element’s
image data.
Otherwise, the element represents nothing, and may be omitted
completely from the rendering. User agents may provide the user
with a notification that an image is present but has been omitted
from the rendering.
If the src attribute is set and the alt attribute is set to a value that
isn’t empty
The image is a key part of the content; the alt attribute gives a
textual equivalent or replacement for the image.
If the image is available and the user agent is configured to
display that image, then the element represents the element’s
image data.
Otherwise, the element represents the text given by the alt
attribute. User agents may provide the user with a notification
that an image is present but has been omitted from the rendering.
If the src attribute is set and the alt attribute is not
There is no textual equivalent of the image available.
If the image is available and the user agent is configured to
display that image, then the element represents the element’s
image data.
Otherwise, the user agent should display some sort of indicator
that there is an image that is not being rendered, and may, if
requested by the user, or if so configured, or when required to
provide contextual information in response to navigation, provide
caption information for the image, derived as follows:
1. If the image is a descendant of a figure element that has a
child figcaption element, and, ignoring the figcaption
element and its descendants, the figure element has no Text
node descendants other than inter-element white space, and no
embedded content descendant other than the img element, then
the contents of the first such figcaption element are the
caption information; abort these steps.
2. There is no caption information.
If the src attribute is not set and either the alt attribute is set to the
empty string or the alt attribute is not set at all
The element represents nothing.
Otherwise
The element represents the text given by the alt attribute.
The alt attribute does not represent advisory information. User agents
must not present the contents of the alt attribute in the same way as
content of the title attribute.
User agents may always provide the user with the option to display any
image, or to prevent any image from being displayed. User agents may also
apply heuristics to help the user make use of the image when the user is
unable to see it, e.g., due to a visual disability or because they are
using a text terminal with no graphics capabilities. Such heuristics could
include, for instance, optical character recognition (OCR) of text found
within the image.
In the case where an img without an alt attribute is the child of a figure
element with a non-empty figcaption element, the image’s presence should
be minimally conveyed to a user by Assistive Technology, typically by
identifying the image role.
While user agents are encouraged to repair cases of missing alt
attributes, authors must not rely on such behavior. Requirements for
providing text to act as an alternative for images are described in detail
below.
The contents of img elements, if any, are ignored for the purposes of
rendering.
----------------------------------------------------------------------
The usemap attribute, if present, can indicate that the image has an
associated image map.
The ismap attribute, when used on an element that is a descendant of an a
element with an href attribute, indicates by its presence that the element
provides access to a server-side image map. This affects how events are
handled on the corresponding a element.
The ismap attribute is a boolean attribute. The attribute must not be
specified on an element that does not have an ancestor a element with an
href attribute.
The usemap and ismap attributes can result in confusing behavior when used
together with source elements with the media attribute specified in a
picture element.
The img element supports dimension attributes.
The alt, src, srcset and sizes IDL attributes must reflect the respective
content attributes of the same name.
The crossOrigin IDL attribute must reflect the crossorigin content
attribute.
The useMap IDL attribute must reflect the usemap content attribute.
The isMap IDL attribute must reflect the ismap content attribute.
The referrerPolicy IDL attribute must reflect the referrerpolicy content
attribute, limited to only known values.
The longDesc IDL attribute is defined in [html-longdesc]. The IDL
attribute must reflect the longdesc content attribute.
image . width [ = value ]
image . height [ = value ]
These attributes return the actual rendered dimensions of the
image, or zero if the dimensions are not known.
They can be set, to change the corresponding content attributes.
image . naturalWidth
image . naturalHeight
These attributes return the intrinsic dimensions of the image, or
zero if the dimensions are not known.
image . complete
Returns true if the image has been completely downloaded or if no
image is specified; otherwise, returns false.
image . currentSrc
Returns the image’s absolute URL.
image = new Image( [ width [, height ] ] )
Returns a new img element, with the width and height attributes
set to the values passed in the relevant arguments, if applicable.
The IDL attributes width and height must return the rendered width and
height of the image, in CSS pixels, if the image is being rendered, and is
being rendered to a visual medium; or else the density-corrected intrinsic
width and height of the image, in CSS pixels, if the image has intrinsic
dimensions and is available but not being rendered to a visual medium; or
else 0, if the image is not available or does not have intrinsic
dimensions. [CSS-2015]
On setting, they must act as if they reflected the respective content
attributes of the same name.
The IDL attributes naturalWidth and naturalHeight must return the
density-corrected intrinsic width and height of the image, in CSS pixels,
if the image has intrinsic dimensions and is available, or else 0.
[CSS-2015]
The IDL attribute complete must return true if any of the following
conditions is true:
* Both the src attribute and the srcset attribute are omitted.
* The srcset attribute is omitted and the src attribute’s value is the
empty string.
* The final task that is queued by the networking task source once the
resource has been fetched has been queued.
* The img element is completely available.
* The img element is broken.
Otherwise, the attribute must return false.
The value of complete can thus change while a script is executing.
The currentSrc IDL attribute must return the img element’s current
request’s current URL.
A constructor is provided for creating HTMLImageElement objects (in
addition to the factory methods from DOM such as createElement()):
Image(width, height). When invoked as a constructor, this must return a
new HTMLImageElement object (a new img element). If the width argument is
present, the new object’s width content attribute must be set to width. If
the height argument is also present, the new object’s height content
attribute must be set to height. The element’s node document must be the
active document of the browsing context of the Window object on which the
interface object of the invoked constructor is found.
4.7.5.1. Requirements for providing text to act as an alternative for
images
Text alternatives, [WCAG20] are a primary way of making visual information
accessible, because they can be rendered through many sensory modalities
(for example, visual, auditory or tactile) to match the needs of the user.
Providing text alternatives allows the information to be rendered in a
variety of ways by a variety of user agents. For example, a person who
cannot see a picture can hear the text alternative read aloud using
synthesized speech.
The alt attribute on images is a very important accessibility attribute.
Authoring useful alt attribute content requires the author to carefully
consider the context in which the image appears and the function that
image may have in that context.
The longdesc attribute on images is likely to be read far less often by
users and is necessary for far fewer images. Nevertheless it provides an
important way for users who cannot see an image or cannot see it clearly,
and user agents that cannot automatically process images, to understand
what it shows. The longdesc attribute’s use cases are more fully described
in [html-longdesc]
The guidance included here addresses the most common ways authors use
images. Additional guidance and techniques are available in Resources on
Alternative Text for Images.
4.7.5.1.1. Examples of scenarios where users benefit from text
alternatives for images
* They have a very slow connection and are browsing with images
disabled.
* They have a vision impairment and use text to speech software.
* They have a cognitive impairment and use text to speech software.
* They are using a text-only browser.
* They are listening to the page being read out by a voice Web browser.
* They have images disabled to save on download costs.
* They have problems loading images or the source of an image is wrong.
4.7.5.1.2. General guidelines
Except where otherwise specified, the alt attribute must be specified and
its value must not be empty; the value must be an appropriate functional
replacement for the image. The specific requirements for the alt attribute
content depend on the image’s function in the page, as described in the
following sections.
To determine an appropriate text alternative it is important to think
about why an image is being included in a page. What is its purpose?
Thinking like this will help you to understand what is important about the
image for the intended audience. Every image has a reason for being on a
page, because it provides useful information, performs a function, labels
an interactive element, enhances aesthetics or is purely decorative.
Therefore, knowing what the image is for, makes writing an appropriate
text alternative easier.
4.7.5.1.3. A link or button containing nothing but an image
When an a element that is a hyperlink, or a button element, has no text
content but contains one or more images, include text in the alt
attribute(s) that together convey the purpose of the link or button.
In this example, a portion of an editor interface is displayed. Each
button has an icon representing an action a user can take on content they
are editing. For users who cannot view the images, the action names are
included within the alt attributes of the images:
5 buttons: bold, italic, strike through, bulleted list and numbered list.
In this example, a link contains a logo. The link points to the W3C web
site from an external site. The text alternative is a brief description of
the link target.
W3C logo used as link content.
This example is the same as the previous example, except that the link is
on the W3C web site. The text alternative is a brief description of the
link target.
W3C logo used as link content.
Depending on the context in which an image of a logo is used it could be
appropriate to provide an indication, as part of the text alternative,
that the image is a logo. Refer to section §4.7.5.1.19 Logos, insignia,
flags, or emblems.
In this example, a link contains a print preview icon. The link points to
a version of the page with a print stylesheet applied. The text
alternative is a brief description of the link target.
Print preview icon used as link content.
In this example, a button contains a search icon. The button submits a
search form. The text alternative is a brief description of what the
button does.
Search icon used as button content.
In this example, a company logo for the PIP Corporation has been split
into the following two images, the first containing the word PIP and the
second with the abbreviated word CO. The images are the sole content of a
link to the PIPCO home page. In this case a brief description of the link
target is provided. As the images are presented to the user as a single
entity the text alternative PIP CO home is in the alt attribute of the
first image.
Image containing the text 'PIP'.Image containing the text 'CO'.
4.7.5.1.4. Graphical Representations: Charts, diagrams, graphs, maps,
illustrations
Users can benefit when content is presented in graphical form, for example
as a flowchart, a diagram, a graph, or a map showing directions. Users who
are unable to view the image also benefit when content presented in a
graphical form is provided in a text-based format. Software agents that
process text content, but cannot automatically process images (e.g.
translation services, many search engines), also benefit from a text-based
description.
In the following example we have an image of a pie chart, with text in the
alt attribute representing the data shown in the pie chart:
Browser Share: Internet Explorer 25%, Firefox 40%, Chrome 25%, Safari 6%
and Opera 4%.
According to a recent study Firefox has a 40% browser share,
Internet Explorer has 25%, Chrome has 25%, Safari has 6% and Opera has 4%.
It can be seen that when the image is not available, for example because
the src attribute value is incorrect, the text alternative provides the
user with a brief description of the image content:
Representation of the code snippet above.
In cases where the text alternative is lengthy, more than a sentence or
two, or would benefit from the use of structured markup, provide a brief
description or label using the alt attribute, and an associated text
alternative.
Here’s an example of a flowchart image, with a short text alternative
included in the alt attribute, in this case the text alternative is a
description of the link target as the image is the sole content of a link.
The link points to a description, within the same document, of the process
represented in the flowchart.
Flowchart: Dealing with a broken lamp.
Dealing with a broken lamp
Check if it’s plugged in, if not, plug it in.
If it still doesn’t work; check if the bulb is burned out. If it is, replace the bulb.
If it still doesn’t work; buy a new lamp.
In this example, there is an image of a chart. It would be inappropriate
to provide the information depicted in the chart as a plain text
alternative in an alt attribute as the information is a data set. Instead
a structured text alternative is provided below the image in the form of a
data table using the data that is represented in the chart image.
Bar Chart: average rainfall by Country and Season. Full description in
Table below.
Indications of the highest and lowest rainfall for each season have been
included in the table, so trends easily identified in the chart are also
available in the data table.
Average rainfall in millimetres by country and season.
+------------------------------------------------+
| | United Kingdom | Japan | Australia |
|--------+----------------+-------+--------------|
| Spring | 5.3 (highest) | 2.4 | 2 (lowest) |
|--------+----------------+-------+--------------|
| Summer | 4.5 (highest) | 3.4 | 2 (lowest) |
|--------+----------------+-------+--------------|
| Autumn | 3.5 (highest) | 1.8 | 1.5 (lowest) |
|--------+----------------+-------+--------------|
| Winter | 1.5 (highest) | 1.2 | 1 (lowest) |
+------------------------------------------------+
Rainfall Data
Rainfall in millimetres by Country and Season.
UK Japan Australia Spring 5.5 (highest) 2.4 2 (lowest) Summer 4.5 (highest) 3.4 2 (lowest) Autumn 3.5 (highest) 1.8 1.5 (lowest) Winter 1.5 (highest) 1.2 1 lowest
The figure element is used to group the Bar Chart image and data table.
The figcaption element provides a caption for the grouped content.
For any of the examples in this section the details and summary elements
could be used so that the text descriptions for the images are only
displayed on demand:
Details element in the closed state.
Details element in the open state with list content displayed.
Dealing with a broken lamp
Check if it’s plugged in, if not, plug it in.
If it still doesn’t work; check if the bulb is burned out. If it is, replace the bulb.
If it still doesn’t work; buy a new lamp.
The details and summary elements are not currently well supported by
browsers, until such times they are supported, if used, you will need to
use scripting to provide the functionality. There are a number of scripted
Polyfills and scripted custom controls available, in popular JavaScript UI
widget libraries, which provide similar functionality.
4.7.5.1.5. Images of text
Sometimes, an image only contains text, and the purpose of the image is to
display text using visual effects and /or fonts. It is strongly
recommended that text styled using CSS be used, but if this is not
possible, provide the same text in the alt attribute as is in the image.
This example shows an image of the text "Get Happy!" written in a fancy
multi colored freehand style. The image makes up the content of a heading.
In this case the text alternative for the image is "Get Happy!".
Get Happy!
In situations where there is also a photo or other graphic along with the
image of text, ensure that the words in the image text are included in the
text alternative, along with any other description of the image that
conveys meaning to users who can view the image, so the information is
also available to users who cannot view the image.
When an image is used to represent a character that cannot otherwise be
represented in Unicode, for example gaiji, itaiji, or new characters such
as novel currency symbols, the alternative text should be a more
conventional way of writing the same thing, e.g., using the phonetic
hiragana or katakana to give the character’s pronunciation.
In this example from 1997, a new-fangled currency symbol that looks like a
curly E with two bars in the middle instead of one is represented using an
image. The alternative text gives the character’s pronunciation.
Only euro5.99!
Only
Here’s another example of the same pie chart image, showing a short text
alternative included in the alt attribute and a longer text alternative in
text. The figure and figcaption elements are used to associate the longer
text alternative with the image. The alt attribute is used to label the
image.
Figure 1. Distribution of Articles by Journal Category.
Pie chart: Language=68%, Education=14% and Science=18%.
The advantage of this method over the previous example is that the text
alternative is available to all users at all times. It also allows
structured mark up to be used in the text alternative, where as a text
alternative provided using the alt attribute does not.
4.7.5.1.7. Images that enhance the themes or subject matter of the page
content
An image that isn’t discussed directly by the surrounding text but still
has some relevance can be included in a page using the img element. Such
images are more than mere decoration, they may augment the themes or
subject matter of the page content and so still form part of the content.
In these cases, it is recommeneded that a text alternative be provided.
Here is an example of an image closely related to the subject matter of
the page content but not directly discussed. An image of a painting
inspired by a poem, on a page reciting that poem. The following snippet
shows an example. The image is a painting titled the "Lady of Shallot", it
is inspired by the poem and its subject matter is derived from the poem.
Therefore it is strongly recommended that a text alternative is provided.
There is a short description of the content of the image in the alt
attribute and a link below the image to a longer description located at
the bottom of the document. At the end of the longer description there is
also a link to further information about the painting.
A painting inspired by Alfred Tennyson’s poem The Lady of Shalott
Description of the painting .
...
...
...
The woman in the painting is wearing a flowing white dress. A large piece of intricately
patterned fabric is draped over the side. In her right hand she holds the chain mooring the boat. Her expression
is mournful. She stares at a crucifix lying in front of her. Beside it are three candles. Two have blown out.
Further information about the painting .
This example illustrates the provision of a text alternative identifying
an image as a photo of the main subject of a page.
Portrait photo(black and white) of Robin, accompanied by a heading 'Robin
Berjon' and a question 'what more needs to be said?'
Robin Berjon
What more needs to be said?
It is not always easy to write a useful text alternative for an image,
another option is to provide a link to a description or further
information about the image when one is available. In this example of the
same image, there is a short text alternative included in the alt
attribute, and there is a link after the image. The link points to a page
containing information about the painting.
The Lady of Shalott
A poem by Alfred Lord Tennyson.
Painting of a woman in a white flowing dress, sitting in a small boat.
About this painting
Full recitation of Alfred, Lord Tennyson’s poem.
About this painting: The Lady of Shalott.
4.7.5.1.8. A graphical representation of some of the surrounding text
In many cases, the image is actually just supplementary, and its presence
merely reinforces the surrounding text. In these cases, the alt attribute
must be present but its value must be the empty string.
In general, an image falls into this category if removing the image
doesn’t make the page any less useful, but including the image makes it a
lot easier for users of visual browsers to understand the concept.
This example includes a screenshot of part of a text editor with the file
described in the instruction, displayed:
In the text file, add SleepMode=1 under [options], then save and close.
In the text file, add SleepMode=1 under [options], then save and close.
Welcome to my blog...
4.7.5.1.10. Inline images
When images are used inline as part of the flow of text in a sentence,
provide a word or phrase as a text alternative which makes sense in the
context of the sentence it is apart of.
I love you.
I Rating:
4.7.5.1.12. Image maps
If an img element has a usemap attribute which references a map element
containing area elements that have href attributes, the img is considered
to be interactive content. In such cases, always provide a text
alternative for the image using the alt attribute.
Consider the following image which is a map of Katoomba, it has 2
interactive regions corresponding to the areas of North and South
Katoomba:
Map of Katoomba.
The text alternative is a brief description of the image. The alt
attribute on each of the area elements provides text describing the
content of the target page of each linked region:
View houses for sale in North Katoomba or South Katoomba:
4.7.5.1.13. A group of images that form a single larger picture with
links
Sometimes, when you create a composite picture from multiple images, you
may wish to link one or more of the images. Provide an alt attribute for
each linked image to describe the purpose of the link.
In the following example, a composite picture is used to represent a
"crocoduck"; a fictional creature which defies evolutionary principles by
being part crocodile and part duck. You are asked to interact with the
crocoduck, but you need to exercise caution...
crocodile’s angry, chomping headduck’s soft, feathery body
The crocoduck
You encounter a strange creature called a "crocoduck".
The creature seems angry! Perhaps some friendly stroking will help to calm
it, but be careful not to stroke any crocodile parts. This would just enrage
the beast further.
Lola prefers a bath to a shower.
This example is of an image that defies a complete description, as the
subject of the image is open to interpretation. The image has a text
alternative in the alt attribute which gives users who cannot view the
image a sense of what the image is. It also has a caption provided by
including the img element in a figure element and using a figcaption
element to identify the caption text.
An abstract, freeform, vertically symmetrical, black inkblot on a light
background.
The first of the ten cards in the Rorschach test.
The first of the ten cards in the Rorschach test.
4.7.5.1.15. Webcam images
Webcam images are static images that are automatically updated
periodically. Typically the images are from a fixed viewpoint, the images
may update on the page automatically as each new image is uploaded from
the camera or the user may be required to refresh the page to view an
updated image. Examples include traffic and weather cameras.
This example is fairly typical; the title and a time stamp are included in
the image, automatically generated by the webcam software. It would be
better if the text information was not included in the image, but as it is
part of the image, include it as part of the text alternative. A caption
is also provided using the figure and figcaption elements. As the image is
provided to give a visual indication of the current weather near a
building, a link to a local weather forecast is provided, as with
automatically generated and uploaded webcam images it may be impractical
to provide such information as a text alternative.
The text of the alt attribute includes a prose version of the timestamp,
designed to make the text more understandable when announced by text to
speech software. The text alternative also includes a description of some
aspects of what can be seen in the image which are unchanging, although
weather conditions and time of day change.
Sopwith house weather cam. Taken on the 21/04/10 at 11:51 and 34 seconds.
In the foreground are the safety rails on the flat part of the roof.
Nearby ther are low rize industrial buildings, beyond those are block of
flats. In the distance there’s a church steeple.
View from the top of Sopwith house, looking towards North Kingston. This
image is updated every hour.
View the latest weather details for Kingston upon Thames.
View from Sopwith house, looking towards north Kingston. This image is updated every hour.
View the latest weather details for Kingston upon Thames.
4.7.5.1.16. When a text alternative is not available at the time of
publication
In some cases an image is included in a published document, but the author
is unable to provide an appropriate text alternative. In such cases the
minimum requirement is to provide a caption for the image using the figure
and figcaption elements under the following conditions:
* The img element is in a figure element
* The figure element contains a figcaption element
* The figcaption element contains content other than inter-element white
space
* Ignoring the figcaption element and its descendants, the figure
element has no Text node descendants other than inter-element white
space, and no embedded content descendant other than the img element.
In other words, the only content of the figure is an img element and a
figcaption element, and the figcaption element must include (caption)
content.
Such cases are to be kept to an absolute minimum. If there is even the
slightest possibility of the author having the ability to provide real
alternative text, then it would not be acceptable to omit the alt
attribute.
In this example, a person uploads a photo, as part of a bulk upload of
many images, to a photo sharing site. The user has not provided a text
alternative or a caption for the image. The site’s authoring tool inserts
a caption automatically using whatever useful information it has for the
image. In this case it’s the file name and date the photo was taken.
The caption text in the example below is not a suitable text alternative
and is not conforming to the Web Accessibility Guidelines 2.0. [WCAG20]
no text alternative provided
clara.jpg, taken on 12/11/2010.
clara.jpg, taken on 12/11/2010.
Notice that even in this example, as much useful information as possible
is still included in the figcaption element.
In this second example, a person uploads a photo to a photo sharing site.
She has provided a caption for the image but not a text alternative. This
may be because the site does not provide users with the ability to add a
text alternative in the alt attribute.
no text alternative provided
Eloisa with Princess Belle
Eloisa with Princess Belle
Sometimes the entire point of the image is that a textual description is
not available, and the user is to provide the description. For example,
software that displays images and asks for alternative text precisely for
the purpose of then writing a page with correct alternative text. Such a
page could have a table of images, like this:
Since some users cannot use images at all (e.g., because they are blind)
the alt attribute is only allowed to be omitted when no text alternative
is available and none can be made available, as in the above examples.
4.7.5.1.17. An image not intended for the user
Generally authors should avoid using img elements for purposes other than
showing images.
If an img element is being used for purposes other than showing an image,
e.g., as part of a service to count page views, use an empty alt
attribute.
An example of an img element used to collect web page statistics. The alt
attribute is empty as the image has no meaning.
Home
In this example, there is a warning message, with a warning icon. The word
"Warning!" is in emphasized text next to the icon. As the information
conveyed by the icon is redundant the img element is given an empty alt
attribute.
Warning! Warning! Your session is about to expire.
Warning!
Your session is about to expire
When an icon conveys additional information not available in text, provide
a text alternative.
In this example, there is a warning message, with a warning icon. The icon
emphasizes the importance of the message and identifies it as a particular
type of content.
Warning! Your session is about to expire.
4.7.5.1.19. Logos, insignia, flags, or emblems
Many pages include logos, insignia, flags, or emblems, which stand for a
company, organization, project, band, software package, country, or other
entity. What can be considered as an appropriate text alternative depends
upon, like all images, the context in which the image is being used and
what function it serves in the given context.
If a logo is the sole content of a link, provide a brief description of
the link target in the alt attribute.
This example illustrates the use of the HTML5 logo as the sole content of
a link to the HTML specification.
HTML 5.1 Nightly specification
If a logo is being used to represent the entity, e.g., as a page heading,
provide the name of the entity being represented by the logo as the text
alternative.
This example illustrates the use of the WebPlatform.org logo being used to
represent itself.
WebPlatform.org and other developer resources
The text alternative in the example above could also include the word
"logo" to describe the type of image content. If so, it is suggested that
square brackets be used to delineate this information: alt="[logo]
WebPlatform.org".
If a logo is being used next to the name of the what that it represents,
then the logo is supplemental. Include an empty alt attribute as the text
alternative is already provided.
This example illustrates the use of a logo next to the name of the
organization it represents.
WebPlatform.org
Information about HTML
4.7.5.1.20. CAPTCHA Images
CAPTCHA stands for "Completely Automated Public Turing test to tell
Computers and Humans Apart". CAPTCHA images are used for security purposes
to confirm that content is being accessed by a person rather than a
computer. This authentication is done through visual verification of an
image. CAPTCHA typically presents an image with characters or words in it
that the user is to re-type. The image is usually distorted and has some
noise applied to it to make the characters difficult to read.
To improve the accessibility of CAPTCHA provide text alternatives that
identify and describe the purpose of the image, and provide alternative
forms of the CAPTCHA using output modes for different types of sensory
perception. For instance provide an audio alternative along with the
visual image. Place the audio option right next to the visual one. This
helps but is still problematic for people without sound cards, the
deaf-blind, and some people with limited hearing. Another method is to
include a form that asks a question along with the visual image. This
helps but can be problematic for people with cognitive impairments.
It is strongly recommended that alternatives to CAPTCHA be used, as all
forms of CAPTCHA introduce unacceptable barriers to entry for users with
disabilities. Further information is available in Inaccessibility of
CAPTCHA.
This example shows a CAPTCHA test which uses a distorted image of text.
The text alternative in the alt attribute provides instructions for a user
in the case where she cannot access the image content.
captcha containing the words 'aides' and 'sprucest'. The letters are
distorted and the color of the letters and background is partially
inverted,
Example code:
Is it a ghost?
The large and small versions (both versions are displayed for
demonstration purposes) of the image portray the same scene: Reflection of
a girls face in a train window, while the small version (displayed on
smaller screens) is cropped, this does not effect the subject matter or
the appropriateness of the alt text.
Reflection of a girls face in a train window. Reflection of a girls face
in a train window.
4.7.5.1.22. Guidance for markup generators
Markup generators (such as WYSIWYG authoring tools) should, wherever
possible, obtain alternative text from their users. However, it is
recognized that in many cases, this will not be possible.
For images that are the sole contents of links, markup generators should
examine the link target to determine the title of the target, or the URL
of the target, and use information obtained in this manner as the
alternative text.
For images that have captions, markup generators should use the figure and
figcaption elements to provide the image’s caption.
As a last resort, implementors should either set the alt attribute to the
empty string, under the assumption that the image is a purely decorative
image that doesn’t add any information but is still specific to the
surrounding content, or omit the alt attribute altogether, under the
assumption that the image is a key part of the content.
Markup generators may specify a generator-unable-to-provide-required-alt
attribute on img elements for which they have been unable to obtain a text
alternative and for which they have therefore omitted the alt attribute.
The value of this attribute must be the empty string. Documents containing
such attributes are not conforming, but conformance checkers will silently
ignore this error.
This is intended to avoid markup generators from being pressured into
replacing the error of omitting the alt attribute with the even more
egregious error of providing phony text alternatives, because
state-of-the-art automated conformance checkers cannot distinguish phony
text alternatives from correct text alternatives.
Markup generators should generally avoid using the image’s own file name
as the text alternative. Similarly, markup generators should avoid
generating text alternatives from any content that will be equally
available to presentation user agents (e.g., Web browsers).
This is because once a page is generated, it will typically not be
updated, whereas the browsers that later read the page can be updated by
the user, therefore the browser is likely to have more up-to-date and
finely-tuned heuristics than the markup generator did when generating the
page.
4.7.5.1.23. Guidance for conformance checkers
A conformance checker must report the lack of an alt attribute as an error
unless one of the conditions listed below applies:
* The img element is in a figure element that satisfies the conditions
described above.
* The img element has a (non-conforming)
generator-unable-to-provide-required-alt attribute whose value is the
empty string. A conformance checker that is not reporting the lack of
an alt attribute as an error must also not report the presence of the
empty generator-unable-to-provide-required-alt attribute as an error.
(This case does not represent a case where the document is conforming,
only that the generator could not determine appropriate alternative
text — validators are not required to show an error in this case,
because such an error might encourage markup generators to include
bogus alternative text purely in an attempt to silence validators.
Naturally, conformance checkers may report the lack of an alt
attribute as an error even in the presence of the
generator-unable-to-provide-required-alt attribute; for example, there
could be a user option to report all conformance errors even those
that might be the more or less inevitable result of using a markup
generator.)
4.7.6. The iframe element
Categories:
Flow content.
Phrasing content.
Embedded content.
Interactive content.
Palpable content.
Contexts in which this element can be used:
Where embedded content is expected.
Content model:
Text that conforms to the requirements given in the prose.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
src - Address of the resource
srcdoc - A document to render in the iframe
name - Name of nested browsing context
sandbox - Security rules for nested content
allowfullscreen - Whether to allow the iframe’s contents to use
requestFullscreen()
allowpaymentrequest - Whether the iframe’s contents are allowed to
use the PaymentRequest interface to make payment requests
width - Horizontal dimension
height - Vertical dimension
referrerpolicy - Referrer policy for fetches initiated by the
element
Allowed ARIA role attribute values:
application, document, or img.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
interface HTMLIFrameElement : HTMLElement {
attribute DOMString src;
attribute DOMString srcdoc;
attribute DOMString name;
[SameObject, PutForwards=value] readonly attribute DOMTokenList sandbox;
attribute boolean allowFullscreen;
attribute boolean allowPaymentRequest;
attribute DOMString width;
attribute DOMString height;
attribute DOMString referrerPolicy;
readonly attribute Document? contentDocument;
readonly attribute WindowProxy? contentWindow;
};
The iframe element represents a nested browsing context.
The src attribute gives the address of a page that the nested browsing
context is to contain. The attribute, if present, must be a valid
non-empty URL potentially surrounded by spaces.
The srcdoc attribute gives the content of the page that the nested
browsing context is to contain. The value of the attribute is the source
of an iframe srcdoc document.
The srcdoc attribute, if present, must have a value using the HTML syntax
that consists of the following syntactic components, in the given order:
1. Any number of comments and space characters.
2. Optionally, a DOCTYPE.
3. Any number of comments and space characters.
4. The document element, in the form of an html element.
5. Any number of comments and space characters.
For iframe elements in XML documents, the srcdoc attribute, if present,
must have a value that matches the production labeled document in the XML
specification. [XML]
Here a blog uses the srcdoc attribute in conjunction with the sandbox
attributes described below to provide users of user agents that support
this feature with an extra layer of protection from script injection in
the blog post comments:
I got my own magazine!
After much effort, I’ve finally found a publisher, and so now I
have my own magazine! Isn’t that awesome?! The first issue will come
out in September, and we have articles about getting food, and about
getting in boxes, it’s going to be great!
Thirteen minutes ago, ch wrote:
Nine minutes ago, cap wrote:
Five minutes ago, ch wrote:
Notice the way that quotes have to be escaped (otherwise the srcdoc
attribute would end prematurely), and the way raw ampersands (e.g., in
URLs or in prose) mentioned in the sandboxed content have to be doubly
escaped — once so that the ampersand is preserved when originally parsing
the srcdoc attribute, and once more to prevent the ampersand from being
misinterpreted when parsing the sandboxed content.
Furthermore, notice that since the DOCTYPE is optional in iframe srcdoc
documents, and the html, head, and body elements have optional start and
end tags, and the title element is also optional in iframe srcdoc
documents, the markup in a srcdoc attribute can be relatively succinct
despite representing an entire document, since only the contents of the
body element need appear literally in the syntax. The other elements are
still present, but only by implication.
In the HTML syntax, authors need only remember to use U+0022 QUOTATION
MARK characters (") to wrap the attribute contents and then to escape all
U+0026 AMPERSAND (&) and U+0022 QUOTATION MARK (") characters, and to
specify the sandbox attribute, to ensure safe embedding of content.
Due to restrictions of the XHTML syntax, in XML the U+003C LESS-THAN SIGN
character (<) needs to be escaped as well. In order to prevent
attribute-value normalization, some of XML’s white space characters —
specifically U+0009 CHARACTER TABULATION (tab), U+000A LINE FEED (LF), and
U+000D CARRIAGE RETURN (CR) — also need to be escaped. [XML]
If the src attribute and the srcdoc attribute are both specified together,
the srcdoc attribute takes priority. This allows authors to provide a
fallback URL for legacy user agents that do not support the srcdoc
attribute.
----------------------------------------------------------------------
When an iframe element is inserted into a document that has a browsing
context, the user agent must create a nested browsing context, and then
process the iframe attributes for the "first time".
When an iframe element is removed from a document, the user agent must
discard the nested browsing context, if any.
This happens without any unload events firing (the nested browsing context
and its Document are discarded, not unloaded).
Whenever an iframe element with a nested browsing context has its srcdoc
attribute set, changed, or removed, the user agent must process the iframe
attributes.
Similarly, whenever an iframe element with a nested browsing context but
with no srcdoc attribute specified has its src attribute set, changed, or
removed, the user agent must process the iframe attributes.
When the user agent is to process the iframe attributes, it must run the
first appropriate steps from the following list:
If the srcdoc attribute is specified
Navigate the element’s child browsing context to a new response
whose url list consists of about:srcdoc, header list consists of
Content-Type/text/html, body is the value of the attribute, CSP
list is the CSP list of the iframe element’s node document, and
HTTPS state is the HTTPS state of the iframe element’s node
document.
The resulting Document must be considered an iframe srcdoc
document.
Otherwise, if the element has no src attribute specified, and the user
agent is processing the iframe’s attributes for the "first time"
Queue a task to run the iframe load event steps.
The task source for this task is the DOM manipulation task source.
Otherwise
Run the otherwise steps for iframe or frame elements.
The otherwise steps for iframe or frame elements are as follows:
1: If the element has no src attribute specified, or its value is the
empty string, let url be the URL "about:blank".
Otherwise, parse the value of the src attribute, relative to the element’s
node document.
If that is not successful, then let url be the URL "about:blank".
Otherwise, let url be the resulting URL record.
2. If there exists an ancestor browsing context whose active document’s
URL, ignoring fragments, is equal to url, then abort these steps.
3. Let resource be a new request whose url is URL and whose referrer
policy is the current state of the element’s referrerpolicy content
attribute.
4. Navigate the element’s child browsing context to resource.
Furthermore, if the active document of the element’s child browsing
context before such a navigation was not completely loaded at the time of
the new navigation, then the navigation must be completed with replacement
enabled.
Similarly, if the child browsing context’s session history contained only
one Document when the process the iframe attributes algorithm was invoked,
and that was the about:blank Document created when the child browsing
context was created, then any navigation required of the user agent in
that algorithm must be completed with replacement enabled.
When a Document in an iframe is marked as completely loaded, the user
agent must run the iframe load event steps in parallel.
A load event is also fired at the iframe element when it is created if no
other data is loaded in it.
Each Document has an iframe load in progress flag and a mute iframe load
flag. When a Document is created, these flags must be unset for that
Document.
The iframe load event steps are as follows:
1. Let child document be the active document of the iframe element’s
nested browsing context.
2. If child document has its mute iframe load flag set, abort these
steps.
3. Set child document’s iframe load in progress flag.
4. Fire a simple event named load at the iframe element.
5. Unset child document’s iframe load in progress flag.
This, in conjunction with scripting, can be used to probe the URL space of
the local network’s HTTP servers. User agents may implement cross-origin
access control policies that are stricter than those described above to
mitigate this attack, but unfortunately such policies are typically not
compatible with existing Web content.
When the iframe’s browsing context’s active document is not ready for
post-load tasks, and when anything in the iframe is delaying the load
event of the iframe’s browsing context’s active document, and when the
iframe’s browsing context is in the delaying load events mode, the iframe
must delay the load event of its document.
If, during the handling of the load event, the browsing context in the
iframe is again navigated, that will further delay the load event.
If, when the element is created, the srcdoc attribute is not set, and the
src attribute is either also not set or set but its value cannot be
parsed, the browsing context will remain at the initial about:blank page.
If the user navigates away from this page, the iframe’s corresponding
WindowProxy object will proxy new Window objects for new Document objects,
but the src attribute will not change.
----------------------------------------------------------------------
The name attribute, if present, must be a valid browsing context name. The
given value is used to name the nested browsing context. When the browsing
context is created, if the attribute is present, the browsing context name
must be set to the value of this attribute; otherwise, the browsing
context name must be set to the empty string.
Whenever the name attribute is set, the nested browsing context’s name
must be changed to the new value. If the attribute is removed, the
browsing context name must be set to the empty string.
----------------------------------------------------------------------
The sandbox attribute, when specified, enables a set of extra restrictions
on any content hosted by the iframe. Its value must be an unordered set of
unique space-separated tokens that are ASCII case-insensitive. The allowed
values are allow-forms, allow-pointer-lock, allow-popups,
allow-presentation, allow-same-origin, allow-scripts, and
allow-top-navigation.
When the attribute is set, the content is treated as being from a unique
origin, forms, scripts, and various potentially annoying APIs are
disabled, links are prevented from targeting other browsing contexts, and
plugins are secured. The allow-same-origin keyword causes the content to
be treated as being from its real origin instead of forcing it into a
unique origin; the allow-top-navigation keyword allows the content to
navigate its top-level browsing context; and the allow-forms,
allow-pointer-lock, allow-popups, allow-presentation and allow-scripts
keywords re-enable forms, the pointer lock API, popups, the presentation
API, and scripts respectively. [POINTERLOCK] [PRESENTATION-API]
Setting both the allow-scripts and allow-same-origin keywords together
when the embedded page has the same origin as the page containing the
iframe allows the embedded page to simply remove the sandbox attribute and
then reload itself, effectively breaking out of the sandbox altogether.
These flags only take effect when the nested browsing context of the
iframe is navigated. Removing them, or removing the entire sandbox
attribute, has no effect on an already-loaded page.
Potentially hostile files should not be served from the same server as the
file containing the iframe element. Sandboxing hostile content is of
minimal help if an attacker can convince the user to just visit the
hostile content directly, rather than in the iframe. To limit the damage
that can be caused by hostile HTML content, it should be served from a
separate dedicated domain. Using a different domain ensures that scripts
in the files are unable to attack the site, even if the user is tricked
into visiting those pages directly, without the protection of the sandbox
attribute.
When an iframe element with a sandbox attribute has its nested browsing
context created (before the initial about:blank Document is created), and
when an iframe element’s sandbox attribute is set or changed while it has
a nested browsing context, the user agent must parse the sandboxing
directive using the attribute’s value as the input, the iframe element’s
nested browsing context’s iframe sandboxing flag set as the output, and,
if the iframe has an allowfullscreen attribute, the allow fullscreen flag.
When an iframe element’s sandbox attribute is removed while it has a
nested browsing context, the user agent must empty the iframe element’s
nested browsing context’s iframe sandboxing flag set as the output.
In this example, some completely-unknown, potentially hostile,
user-provided HTML content is embedded in a page. Because it is served
from a separate domain, it is affected by all the normal cross-site
restrictions. In addition, the embedded page has scripting disabled,
plugins disabled, forms disabled, and it cannot navigate any frames or
windows other than itself (or any frames or windows it itself embeds).
We’re not scared of you! Here is your content, unedited:
It is important to use a separate domain so that if the attacker convinces
the user to visit that page directly, the page doesn’t run in the context
of the site’s origin, which would make the user vulnerable to any attack
found in the page.
In this example, a gadget from another site is embedded. The gadget has
scripting and forms enabled, and the origin sandbox restrictions are
lifted, allowing the gadget to communicate with its originating server.
The sandbox is still useful, however, as it disables plugins and popups,
thus reducing the risk of the user being exposed to malware and other
annoyances.
Suppose a file A contained the following fragment:
Suppose that file B contained an iframe also:
Further, suppose that file C contained a link:
Link
For this example, suppose all the files were served as text/html.
Page C in this scenario has all the sandboxing flags set. Scripts are
disabled, because the iframe in A has scripts disabled, and this overrides
the allow-scripts keyword set on the iframe in B. Forms are also disabled,
because the inner iframe (in B) does not have the allow-forms keyword set.
Suppose now that a script in A removes all the sandbox attributes in A and
B. This would change nothing immediately. If the user clicked the link in
C, loading page D into the iframe in B, page D would now act as if the
iframe in B had the allow-same-origin and allow-forms keywords set,
because that was the state of the nested browsing context in the iframe in
A when page B was loaded.
Generally speaking, dynamically removing or changing the sandbox attribute
is ill-advised, because it can make it quite hard to reason about what
will be allowed and what will not.
----------------------------------------------------------------------
The allowfullscreen attribute is a boolean attribute. When specified, it
indicates that Document objects in the iframe element’s browsing context
are to be allowed to use requestFullscreen() (if it’s not blocked for
other reasons, e.g., there is another ancestor iframe without this
attribute set).
Here, an iframe is used to embed a player from a video site. The
allowfullscreen attribute is needed to enable the player to show its video
fullscreen.
Check out my new ride!
----------------------------------------------------------------------
The allowpaymentrequest attribute is a boolean attribute. When specified,
it indicates that Document objects in the iframe element’s browsing
context are to be allowed to use the PaymentRequest interface to make
payment requests.
To determine whether a Document object document is allowed to use the
feature indicated by attribute name allowattribute, run these steps:
1. If document has no browsing context, then return false.
2. If document’s browsing context is a top-level browsing context, then
return true.
3. If document’s browsing context has a browsing context container that
is an iframe element with an allowattribute attribute specified, and
whose node document is allowed to use the feature indicated by
allowattribute, then return true.
4. Return false.
----------------------------------------------------------------------
The iframe element supports dimension attributes for cases where the
embedded content has specific dimensions (e.g., ad units have well-defined
dimensions).
An iframe element never has fallback content, as it will always create a
nested browsing context, regardless of whether the specified initial
contents are successfully used.
The referrerpolicy attribute is a referrer policy attribute. Its purpose
is to set the referrer policy used when processing the iframe attributes.
[REFERRERPOLICY]
----------------------------------------------------------------------
Descendants of iframe elements represent nothing. (In legacy user agents
that do not support iframe elements, the contents would be parsed as
markup that could act as fallback content.)
When used in HTML documents, the allowed content model of iframe elements
is text, except that invoking the HTML fragment parsing algorithm with the
iframe element as the context element and the text contents as the input
must result in a list of nodes that are all phrasing content, with no
parse errors having occurred, with no script elements being anywhere in
the list or as descendants of elements in the list, and with all the
elements in the list (including their descendants) being themselves
conforming.
The iframe element must be empty in XML documents.
The HTML parser treats markup inside iframe elements as text.
----------------------------------------------------------------------
The IDL attributes src, srcdoc, name, and sandbox must reflect the
respective content attributes of the same name.
The supported tokens for sandbox's DOMTokenList are the allowed values
defined in the sandbox attribute and supported by the user agent.
The allowFullscreen IDL attribute must reflect the allowfullscreen content
attribute.
The allowPaymentRequest IDL attribute must reflect the allowpaymentrequest
content attribute.
The referrerPolicy IDL attribute must reflect the referrerpolicy content
attribute, limited to only known values.
The contentDocument IDL attribute must return the Document object of the
active document of the iframe element’s nested browsing context, if any
and if its origin is the same origin-domain as the origin specified by the
incumbent settings object, or null otherwise.
The contentWindow IDL attribute must return the WindowProxy object of the
iframe element’s nested browsing context, if any, or null otherwise.
Here is an example of a page using an iframe to include advertising from
an advertising broker:
4.7.7. The embed element
Categories:
Flow content.
Phrasing content.
Embedded content.
Interactive content.
Palpable content.
Contexts in which this element can be used:
Where embedded content is expected.
Content model:
Nothing.
Tag omission in text/html:
No end tag
Content attributes:
Global attributes
src - Address of the resource
type - Type of embedded resource
width - Horizontal dimension
height- Vertical dimension
Any other attribute that has no namespace (see prose).
Allowed ARIA role attribute values:
application, document or img or presentation.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
interface HTMLEmbedElement : HTMLElement {
attribute DOMString src;
attribute DOMString type;
attribute DOMString width;
attribute DOMString height;
legacycaller any (any... arguments);
};
Depending on the type of content instantiated by the embed
element, the node may also support other interfaces.
The embed element provides an integration point for an external (typically
non-HTML) application or interactive content.
The src attribute gives the address of the resource being embedded. The
attribute, if present, must contain a valid non-empty URL potentially
surrounded by spaces.
The type attribute, if present, gives the MIME type by which the plugin to
instantiate is selected. The value must be a valid mime type. If both the
type attribute and the src attribute are present, then the type attribute
must specify the same type as the explicit Content-Type metadata of the
resource given by the src attribute.
While any of the following conditions are occurring, any plugin
instantiated for the element must be removed, and the embed element
represents nothing:
* The element has neither a src attribute nor a type attribute.
* The element has a media element ancestor.
* The element has an ancestor object element that is not showing its
fallback content.
An embed element is said to be potentially active when the following
conditions are all met simultaneously:
* The element is in a Document or was in a Document the last time the
event loop reached step 1.
* The element’s node document is fully active.
* The element has either a src attribute set or a type attribute set (or
both).
* The element’s src attribute is either absent or its value is not the
empty string.
* The element is not a descendant of a media element.
* The element is not a descendant of an object element that is not
showing its fallback content.
* The element is being rendered, or was being rendered the last time the
event loop reached step 1.
Whenever an embed element that was not potentially active becomes
potentially active, and whenever a potentially active embed element that
is remaining potentially active and has its src attribute set, changed, or
removed or its type attribute set, changed, or removed, the user agent
must queue a task using the embed task source to run the embed element
setup steps.
The embed element setup steps are as follows:
1. If another task has since been queued to run the embed element setup
steps for this element, then abort these steps.
2. If the element has a src attribute set
The user agent must parse the value of the element’s src
attribute, relative to the element. If that is
successful, the user agent should run these steps:
1. Let request be a new request whose URL is the
resulting URL string, client is the element’s node
document’s Window object’s environment settings
object, destination is "unknown", omit-Origin-header
flag is set if the element doesn’t have a browsing
context scope origin, credentials mode is "include",
and whose use-URL-credentials flag is set.
2. Fetch request.
The task that is queued by the networking task source
once the resource has been fetched must run the following
steps:
1. If another task has since been queued to run the
embed element setup steps for this element, then
abort these steps.
2. Determine the type of the content being embedded, as
follows (stopping at the first substep that
determines the type):
1. If the element has a type attribute, and that
attribute’s value is a type that a plugin
supports, then the value of the type attribute
is the content’s type.
2. Otherwise, if applying the URL parser algorithm
to the URL of the specified resource (after any
redirects) results in a URL record whose path
component matches a pattern that a plugin
supports, then the content’s type is the type
that the plugin can handle.
For example, a plugin might say that it can
handle resources with path components that end
with the four character string ".swf".
3. Otherwise, if the specified resource has
explicit Content-Type metadata, then that is
the content’s type.
4. Otherwise, the content has no type and there
can be no appropriate plugin for it.
3. If the previous step determined that the content’s
type is image/svg+xml, then run the following
substeps:
1. If the embed element is not associated with a
nested browsing context, associate the element
with a newly created nested browsing context,
and, if the element has a name attribute, set
the browsing context name of the element’s
nested browsing context to the value of this
attribute.
2. Navigate the nested browsing context to the
fetched resource, with replacement enabled, and
with the embed element’s node document’s
browsing context as the source browsing
context. (The src attribute of the embed
element doesn’t get updated if the browsing
context gets further navigated to other
locations.)
3. The embed element now represents its associated
nested browsing context.
4. Otherwise, find and instantiate an appropriate
plugin based on the content’s type, and hand that
plugin the content of the resource, replacing any
previously instantiated plugin for the element. The
embed element now represents this plugin instance.
5. Once the resource or plugin has completely loaded,
queue a task to fire a simple event named load at
the element.
Whether the resource is fetched successfully or not
(e.g., whether the response status was an ok status) must
be ignored when determining the content’s type and when
handing the resource to the plugin.
This allows servers to return data for plugins even with
error responses (e.g., HTTP 500 Internal Server Error
codes can still contain plugin data).
Fetching the resource must delay the load event of the
element’s node document.
If the element has no src attribute set
The user agent should find and instantiate an appropriate
plugin based on the value of the type attribute. The
embed element now represents this plugin instance.
Once the plugin is completely loaded, queue a task to
fire a simple event named load at the element.
The embed element has no fallback content. If the user agent can’t find a
suitable plugin when attempting to find and instantiate one for the
algorithm above, then the user agent must use a default plugin. This
default could be as simple as saying "Unsupported Format".
Whenever an embed element that was potentially active stops being
potentially active, any plugin that had been instantiated for that element
must be unloaded.
When a plugin is to be instantiated but it cannot be secured and the
sandboxed plugins browsing context flag is set on the embed element’s node
document’s active sandboxing flag set, then the user agent must not
instantiate the plugin, and must instead render the embed element in a
manner that conveys that the plugin was disabled. The user agent may offer
the user the option to override the sandbox and instantiate the plugin
anyway; if the user invokes such an option, the user agent must act as if
the conditions above did not apply for the purposes of this element.
Plugins that cannot be secured are disabled in sandboxed browsing contexts
because they might not honor the restrictions imposed by the sandbox
(e.g., they might allow scripting even when scripting in the sandbox is
disabled). User agents should convey the danger of overriding the sandbox
to the user if an option to do so is provided.
When an embed element represents a nested browsing context: if the embed
element’s nested browsing context’s active document is not ready for
post-load tasks, and when anything is delaying the load event of the embed
element’s browsing context’s active document, and when the embed element’s
browsing context is in the delaying load events mode, the embed must delay
the load event of its document.
The task source for the tasks mentioned in this section is the DOM
manipulation task source.
Any namespace-less attribute other than name, align, hspace, and vspace
may be specified on the embed element, so long as its name is
XML-compatible and contains no uppercase ASCII letters. These attributes
are then passed as parameters to the plugin.
All attributes in HTML documents get lowercased automatically, so the
restriction on uppercase letters doesn’t affect such documents.
The four exceptions are to exclude legacy attributes that have
side-effects beyond just sending parameters to the plugin.
The user agent should pass the names and values of all the attributes of
the embed element that have no namespace to the plugin used, when one is
instantiated.
The HTMLEmbedElement object representing the element must expose the
scriptable interface of the plugin instantiated for the embed element, if
any. At a minimum, this interface must implement the legacy caller
operation. (It is suggested that the default behavior of this legacy
caller operation, e.g., the behavior of the default plugin’s legacy caller
operation, be to throw a NotSupportedError exception.)
The embed element supports dimension attributes.
The IDL attributes src and type each must reflect the respective content
attributes of the same name.
Here’s a way to embed a resource that requires a proprietary plugin, like
Flash:
If the user does not have the plugin (for example if the plugin vendor
doesn’t support the user’s platform), then the user will be unable to use
the resource.
To pass the plugin a parameter "quality" with the value "high", an
attribute can be specified:
This would be equivalent to the following, when using an object element
instead:
4.7.8. The object element
Categories:
Flow content.
Phrasing content.
Embedded content.
listed, submittable, and reassociateable form-associated element.
Palpable content.
Contexts in which this element can be used:
Where embedded content is expected.
Content model:
Zero or more param elements, then, transparent.
Tag omission in text/html:
Neither tag is omissible.
Content attributes:
Global attributes
data - Address of the resource
type - Type of embedded resource
typemustmatch - Whether the type attribute and the Content-Type
value need to match for the resource to be used
name - Name of nested browsing context
form - Associates the control with a form element
width - Horizontal dimension
height - Vertical dimension
Allowed ARIA role attribute values:
application, document or img or presentation.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
interface HTMLObjectElement : HTMLElement {
attribute DOMString data;
attribute DOMString type;
attribute boolean typeMustMatch;
attribute DOMString name;
readonly attribute HTMLFormElement? form;
attribute DOMString width;
attribute DOMString height;
readonly attribute Document? contentDocument;
readonly attribute WindowProxy? contentWindow;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
legacycaller any (any... arguments);
};
Depending on the type of content instantiated by the object
element, the node also supports other interfaces.
The object element can represent an external resource, which, depending on
the type of the resource, will either be treated as an image, as a nested
browsing context, or as an external resource to be processed by a plugin.
The data attribute, if present, specifies the address of the resource. If
present, the attribute must be a valid non-empty URL potentially
surrounded by spaces.
Authors who reference resources from other origins that they do not trust
are urged to use the typemustmatch attribute defined below. Without that
attribute, it is possible in certain cases for an attacker on the remote
host to use the plugin mechanism to run arbitrary scripts, even if the
author has used features such as the Flash "allowScriptAccess" parameter.
The type attribute, if present, specifies the type of the resource. If
present, the attribute must be a valid mime type.
At least one of either the data attribute or the type attribute must be
present.
The typemustmatch attribute is a boolean attribute whose presence
indicates that the resource specified by the data attribute is only to be
used if the value of the type attribute and the Content-Type of the
aforementioned resource match.
The typemustmatch attribute must not be specified unless both the data
attribute and the type attribute are present.
The name attribute, if present, must be a valid browsing context name. The
given value is used to name the nested browsing context, if applicable.
Whenever one of the following conditions occur:
* the element is created,
* the element is popped off the stack of open elements of an HTML parser
or XML parser,
* the element is not on the stack of open elements of an HTML parser or
XML parser, and it is either inserted into a document or removed from
a document,
* the element’s node document changes whether it is fully active,
* one of the element’s ancestor object elements changes to or from
showing its fallback content,
* the element’s classid attribute is set, changed, or removed,
* the element’s classid attribute is not present, and its data attribute
is set, changed, or removed,
* neither the element’s classid attribute nor its data attribute are
present, and its type attribute is set, changed, or removed,
* the element changes from being rendered to not being rendered, or vice
versa,
...the user agent must queue a task to run the following steps to
(re)determine what the object element represents. This task being queued
or actively running must delay the load event of the element’s node
document.
1. If the user has indicated a preference that this object element’s
fallback content be shown instead of the element’s usual behavior,
then jump to the step below labeled fallback.
For example, a user could ask for the element’s fallback content to be
shown because that content uses a format that the user finds more
accessible.
2. If the element has an ancestor media element, or has an ancestor
object element that is not showing its fallback content, or if the
element is not in a Document with a browsing context, or if the
element’s node document is not fully active, or if the element is
still in the stack of open elements of an HTML parser or XML parser,
or if the element is not being rendered, or if the Should element be
blocked a priori by Content Security Policy? algorithm returns
"Blocked" when executed on the element, then jump to the step below
labeled fallback. [CSP3].
3. If the classid attribute is present, and has a value that isn’t the
empty string, then: if the user agent can find a plugin suitable
according to the value of the classid attribute, and either plugins
aren’t being sandboxed or that plugin can be secured, then that plugin
should be used, and the value of the data attribute, if any, should be
passed to the plugin. If no suitable plugin can be found, or if the
plugin reports an error, jump to the step below labeled fallback.
4. If the data attribute is present and its value is not the empty
string, then:
1. If the type attribute is present and its value is not a type that
the user agent supports, and is not a type that the user agent
can find a plugin for, then the user agent may jump to the step
below labeled fallback without fetching the content to examine
its real type.
2. Parse the URL specified by the data attribute, relative to the
element.
3. If that failed, fire a simple event named error at the element,
then jump to the step below labeled fallback.
4. Let request be a new request whose URL is the resulting URL
string, client is the element’s node document’s Window object’s
environment settings object, destination is "unknown",
omit-Origin-header flag is set if the element doesn’t have a
browsing context scope origin, credentials mode is "include", and
whose use-URL-credentials flag is set.
5. Fetch request.
Fetching the resource must delay the load event of the element’s
node document until the task that is queued by the networking
task source once the resource has been fetched (defined next) has
been run.
6. If the resource is not yet available (e.g., because the resource
was not available in the cache, so that loading the resource
required making a request over the network), then jump to the
step below labeled fallback. The task that is queued by the
networking task source once the resource is available must
restart this algorithm from this step. Resources can load
incrementally; user agents may opt to consider a resource
"available" whenever enough data has been obtained to begin
processing the resource.
7. If the load failed (e.g., there was an HTTP 404 error, there was
a DNS error), fire a simple event named error at the element,
then jump to the step below labeled fallback.
8. Determine the resource type, as follows:
1. Let the resource type be unknown.
2. If the object element has a type attribute and a
typemustmatch attribute, and the resource has associated
Content-Type metadata, and the type specified in the
resource’s Content-Type metadata is an ASCII
case-insensitive match for the value of the element’s type
attribute, then let resource type be that type and jump to
the step below labeled handler.
3. If the object element has a typemustmatch attribute, jump to
the step below labeled handler.
4. If the user agent is configured to strictly obey
Content-Type headers for this resource, and the resource has
associated Content-Type metadata, then let the resource type
be the type specified in the resource’s Content-Type
metadata, and jump to the step below labeled handler.
This can introduce a vulnerability, wherein a site is trying
to embed a resource that uses a particular plugin, but the
remote site overrides that and instead furnishes the user
agent with a resource that triggers a different plugin with
different security characteristics.
5. If there is a type attribute present on the object element,
and that attribute’s value is not a type that the user agent
supports, but it is a type that a plugin supports, then let
the resource type be the type specified in that type
attribute, and jump to the step below labeled handler.
6. Run the appropriate set of steps from the following list:
If the resource has associated Content-Type metadata
1. Let binary be false.
2. If the type specified in the resource’s
Content-Type metadata is "text/plain", and
the result of applying the rules for
distinguishing if a resource is text or
binary to the resource is that the
resource is not text/plain, then set
binary to true.
3. If the type specified in the resource’s
Content-Type metadata is
"application/octet-stream", then set
binary to true.
4. If binary is false, then let the resource
type be the type specified in the
resource’s Content-Type metadata, and jump
to the step below labeled handler.
5. If there is a type attribute present on
the object element, and its value is not
application/octet-stream, then run the
following steps:
1. If the attribute’s value is a type
that a plugin supports, or the
attribute’s value is a type that
starts with "image/" that is not also
an XML MIME type, then let the
resource type be the type specified
in that type attribute.
2. Jump to the step below labeled
handler.
Otherwise, if the resource does not have associated
Content-Type metadata
1. If there is a type attribute present on
the object element, then let the tentative
type be the type specified in that type
attribute.
Otherwise, let tentative type be the
computed type of the resource.
2. If tentative type is not
application/octet-stream, then let
resource type be tentative type and jump
to the step below labeled handler.
7. If applying the URL parser algorithm to the URL of the
specified resource (after any redirects) results in a URL
record whose path component matches a pattern that a plugin
supports, then let resource type be the type that the plugin
can handle.
For example, a plugin might say that it can handle resources
with path components that end with the four character string
".swf".
It is possible for this step to finish, or for one of the
substeps above to jump straight to the next step, with resource
type still being unknown. In both cases, the next step will
trigger fallback.
9. Handler: Handle the content as given by the first of the
following cases that matches:
If the resource type is not a type that the user agent
supports, but it is a type that a plugin supports
If plugins are being sandboxed and the plugin that
supports resource type cannot be secured, jump to
the step below labeled fallback.
Otherwise, the user agent should use the plugin that
supports resource type and pass the content of the
resource to that plugin. If the plugin reports an
error, then jump to the step below labeled fallback.
If the resource type is an XML MIME type, or if the resource
type does not start with "image/"
The object element must be associated with a newly
created nested browsing context, if it does not
already have one.
If the URL of the given resource is not about:blank,
the element’s nested browsing context must then be
navigated to that resource, with replacement
enabled, and with the object element’s node
document’s browsing context as the source browsing
context. (The data attribute of the object element
doesn’t get updated if the browsing context gets
further navigated to other locations.)
If the URL of the given resource is about:blank,
then, instead, the user agent must queue a task to
fire a simple event named load at the object
element. No load event is fired at the about:blank
document itself.
The object element represents the nested browsing
context.
If the name attribute is present, the browsing
context name must be set to the value of this
attribute; otherwise, the browsing context name must
be set to the empty string.
If the resource type starts with "image/", and support for
images has not been disabled
Apply the image sniffing rules to determine the type
of the image.
The object element represents the specified image.
The image is not a nested browsing context.
If the image cannot be rendered, e.g., because it is
malformed or in an unsupported format, jump to the
step below labeled fallback.
Otherwise
The given resource type is not supported. Jump to
the step below labeled fallback.
If the previous step ended with the resource type
being unknown, this is the case that is triggered.
10. The element’s contents are not part of what the object element
represents.
11. Abort these steps. Once the resource is completely loaded, queue
a task to fire a simple event named load at the element.
5. If the data attribute is absent but the type attribute is present, and
the user agent can find a plugin suitable according to the value of
the type attribute, and either plugins aren’t being sandboxed or the
plugin can be secured, then that plugin should be used. If these
conditions cannot be met, or if the plugin reports an error, jump to
the step below labeled fallback. Otherwise abort these steps; once the
plugin is completely loaded, queue a task to fire a simple event named
load at the element.
6. Fallback: The object element represents the element’s children,
ignoring any leading param element children. This is the element’s
fallback content. If the element has an instantiated plugin, then
unload it.
When the algorithm above instantiates a plugin, the user agent should pass
to the plugin used the names and values of all the attributes on the
element, in the order they were added to the element, with the attributes
added by the parser being ordered in source order, followed by a parameter
named "PARAM" whose value is null, followed by all the names and values of
parameters given by param elements that are children of the object
element, in tree order. If the plugin supports a scriptable interface, the
HTMLObjectElement object representing the element should expose that
interface. The object element represents the plugin. The plugin is not a
nested browsing context.
Plugins are considered sandboxed for the purpose of an object element if
the sandboxed plugins browsing context flag is set on the object element’s
node document’s active sandboxing flag set.
Due to the algorithm above, the contents of object elements act as
fallback content, used only when referenced resources can’t be shown
(e.g., because it returned a 404 error). This allows multiple object
elements to be nested inside each other, targeting multiple user agents
with different capabilities, with the user agent picking the first one it
supports.
When an object element represents a nested browsing context: if the object
element’s nested browsing context’s active document is not ready for
post-load tasks, and when anything is delaying the load event of the
object element’s browsing context’s active document, and when the object
element’s browsing context is in the delaying load events mode, the object
must delay the load event of its document.
The task source for the tasks mentioned in this section is the DOM
manipulation task source.
Whenever the name attribute is set, if the object element has a nested
browsing context, its name must be changed to the new value. If the
attribute is removed, if the object element has a browsing context, the
browsing context name must be set to the empty string.
The form attribute is used to explicitly associate the object element with
its form owner.
Constraint validation: object elements are always barred from constraint
validation.
The object element supports dimension attributes.
The IDL attributes data, type and name each must reflect the respective
content attributes of the same name. The typeMustMatch IDL attribute must
reflect the typemustmatch content attribute.
The contentDocument IDL attribute must return the Document object of the
active document of the object element’s nested browsing context, if any
and if its origin is the same origin-domain as the origin specified by the
incumbent settings object, or null otherwise.
The contentWindow IDL attribute must return the WindowProxy object of the
object element’s nested browsing context, if it has one; otherwise, it
must return null.
The willValidate, validity, and validationMessage attributes, and the
checkValidity(), reportValidity(), and setCustomValidity() methods, are
part of the constraint validation API. The form IDL attribute is part of
the element’s forms API.
All object elements have a legacy caller operation. If the object element
has an instantiated plugin that supports a scriptable interface that
defines a legacy caller operation, then that must be the behavior of the
object’s legacy caller operation. Otherwise, the object’s legacy caller
operation must be to throw a NotSupportedError exception.
In the following example, a Java applet is embedded in a page using the
object element. (Generally speaking, it is better to avoid using applets
like these and instead use native JavaScript and HTML to provide the
functionality, since that way the application will work on all Web
browsers without requiring a third-party plugin. Many devices, especially
embedded devices, do not support third-party technologies like Java.)
You do not have Java available, or it is disabled.
My Java Clock
In this example, an HTML page is embedded in another using the object
element.
My HTML Clock
The following example shows how a plugin can be used in HTML (in this case
the Flash plugin, to show a video file). Fallback is provided for users
who do not have Flash enabled, in this case using the video element to
show the video for those using user agents that support video, and finally
providing a link to the video for those who have neither Flash nor a
video-capable browser.
Look at my video:
View video .
4.7.9. The param element
Categories:
None.
Contexts in which this element can be used:
As a child of an object element, before any flow content.
Content model:
Nothing.
Tag omission in text/html:
No end tag
Content attributes:
Global attributes
name - Name of parameter
value - Value of parameter
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
DOM interface:
interface HTMLParamElement : HTMLElement {
attribute DOMString name;
attribute DOMString value;
};
The param element defines parameters for plugins invoked by object
elements. It does not represent anything on its own.
The name attribute gives the name of the parameter.
The value attribute gives the value of the parameter.
Both attributes must be present. They may have any value.
If both attributes are present, and if the parent element of the param is
an object element, then the element defines a parameter with the given
name-value pair.
If either the name or value of a parameter defined by a param element that
is the child of an object element that represents an instantiated plugin
changes, and if that plugin is communicating with the user agent using an
API that features the ability to update the plugin when the name or value
of a parameter so changes, then the user agent must appropriately exercise
that ability to notify the plugin of the change.
The IDL attributes name and value must both reflect the respective content
attributes of the same name.
The following example shows how the param element can be used to pass a
parameter to a plugin, in this case the O3D plugin.
O3D Utah Teapot
To see the teapot actually rendered by O3D on your
computer, please download and install the O3D plugin .
4.7.10. The video element
Categories:
Flow content.
Phrasing content.
Embedded content.
If the element has a controls attribute: interactive content.
Palpable content.
Contexts in which this element can be used:
Where embedded content is expected.
Content model:
If the element has a src attribute: zero or more track elements,
then transparent, but with no media element descendants.
If the element does not have a src attribute: zero or more source
elements, then zero or more track elements, then transparent, but
with no media element descendants.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
src - Address of the resource
crossorigin - How the element handles crossorigin requests
poster - Poster frame to show prior to video playback
preload - Hints how much buffering the media resource will likely
need
autoplay - Hint that the media resource can be started
automatically when the page is loaded
loop - Whether to loop the media resource
muted - Whether to mute the media resource by default
controls - Show user agent controls
width - Horizontal dimension
height - Vertical dimension
Allowed ARIA role attribute values:
application.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
interface HTMLVideoElement : HTMLMediaElement {
attribute unsigned long width;
attribute unsigned long height;
readonly attribute unsigned long videoWidth;
readonly attribute unsigned long videoHeight;
attribute DOMString poster;
};
A video element is used for playing videos or movies, and audio files with
captions.
Content may be provided inside the video element. User agents should not
show this content to the user; it is intended for older Web browsers which
do not support video, so that legacy video plugins can be tried, or to
show text to the users of these older browsers informing them of how to
access the video contents.
In particular, this content is not intended to address accessibility
concerns. To make video content accessible to people with disabilities, a
variety of features are available. Captions and sign language tracks can
be embedded in the video stream, or as external files using the track
element. Audio descriptions can be provided, either as a separate track
embedded in the video stream, or by referencing a WebVTT file with the
track element that the user agent can present as synthesized speech.
WebVTT can also be used to provide chapter titles. For users who would
rather not use a media element at all, transcripts or other textual
alternatives can be provided by simply linking to them in the prose near
the video element. [WEBVTT]
The video element is a media element whose media data is ostensibly video
data, possibly with associated audio data.
The src, preload, autoplay, loop, muted, and controls attributes are the
attributes common to all media elements.
The poster content attribute gives the address of an image file that the
user agent can show while no video data is available. The attribute, if
present, must contain a valid non-empty URL potentially surrounded by
spaces.
If the specified resource is to be used, then, when the element is created
or when the poster attribute is set, changed, or removed, the user agent
must run the following steps to determine the element’s poster frame
(regardless of the value of the element’s show poster flag):
1. If there is an existing instance of this algorithm running for this
video element, abort that instance of this algorithm without changing
the poster frame.
2. If the poster attribute’s value is the empty string or if the
attribute is absent, then there is no poster frame; abort these steps.
3. Parse the poster attribute’s value relative to the element. If this
fails, then there is no poster frame; abort these steps.
4. Let request be a new request whose URL is the resulting URL string,
client is the element’s node document’s Window object’s environment
settings object, type is "image", destination is "subresource",
credentials mode is "include", and whose use-URL-credentials flag is
set.
5. Fetch request. This must delay the load event of the element’s node
document.
6. If an image is thus obtained, the poster frame is that image.
Otherwise, there is no poster frame.
The image given by the poster attribute, the poster frame, is intended to
be a representative frame of the video (typically one of the first
non-blank frames) that gives the user an idea of what the video is like.
----------------------------------------------------------------------
A video element represents what is given for the first matching condition
in the list below:
When no video data is available (the element’s readyState attribute is
either HAVE_NOTHING, or HAVE_METADATA but no video data has yet been
obtained at all, or the element’s readyState attribute is any subsequent
value but the media resource does not have a video channel)
The video element represents its poster frame, if any, or else
transparent black with no intrinsic dimensions.
When the video element is paused, the current playback position is the
first frame of video, and the element’s show poster flag is set
The video element represents its poster frame, if any, or else the
first frame of the video.
When the video element is paused, and the frame of video corresponding to
the current playback position is not available (e.g., because the video is
seeking or buffering)
When the video element is neither potentially playing nor paused (e.g.,
when seeking or stalled)
The video element represents the last frame of the video to have
been rendered.
When the video element is paused
The video element represents the frame of video corresponding to
the current playback position.
Otherwise (the video element has a video channel and is potentially
playing)
The video element represents the frame of video at the
continuously increasing "current" position. When the current
playback position changes such that the last frame rendered is no
longer the frame corresponding to the current playback position in
the video, the new frame must be rendered.
Frames of video must be obtained from the video track that was selected
when the event loop last reached step 1.
Which frame in a video stream corresponds to a particular playback
position is defined by the video stream’s format.
The video element also represents any text track cues whose text track cue
active flag is set and whose text track is in the showing mode, and any
audio from the media resource, at the current playback position.
Any audio associated with the media resource must, if played, be played
synchronized with the current playback position, at the element’s
effective media volume. The user agent must play the audio from audio
tracks that were enabled when the event loop last reached step 1.
In addition to the above, the user agent may provide messages to the user
(such as "buffering", "no video loaded", "error", or more detailed
information) by overlaying text or icons on the video or other areas of
the element’s playback area, or in another appropriate manner.
User agents that cannot render the video may instead make the element
represent a link to an external video playback utility or to the video
data itself.
When a video element’s media resource has a video channel, the element
provides a paint source whose width is the media resource’s intrinsic
width, whose height is the media resource’s intrinsic height, and whose
appearance is the frame of video corresponding to the current playback
position, if that is available, or else (e.g., when the video is seeking
or buffering) its previous appearance, if any, or else (e.g., because the
video is still loading the first frame) blackness.
----------------------------------------------------------------------
video . videoWidth
video . videoHeight
These attributes return the intrinsic dimensions of the video, or
zero if the dimensions are not known.
The intrinsic width and intrinsic height of the media resource are the
dimensions of the resource in CSS pixels after taking into account the
resource’s dimensions, aspect ratio, clean aperture, resolution, and so
forth, as defined for the format used by the resource. If an anamorphic
format does not define how to apply the aspect ratio to the video data’s
dimensions to obtain the "correct" dimensions, then the user agent must
apply the ratio by increasing one dimension and leaving the other
unchanged.
The videoWidth IDL attribute must return the intrinsic width of the video
in CSS pixels. The videoHeight IDL attribute must return the intrinsic
height of the video in CSS pixels. If the element’s readyState attribute
is HAVE_NOTHING, then the attributes must return 0.
Whenever the intrinsic width or intrinsic height of the video changes
(including, for example, because the selected video track was changed), if
the element’s readyState attribute is not HAVE_NOTHING, the user agent
must queue a task to fire a simple event named resize at the media
element.
The video element supports dimension attributes.
In the absence of style rules to the contrary, video content should be
rendered inside the element’s playback area such that the video content is
shown centered in the playback area at the largest possible size that fits
completely within it, with the video content’s aspect ratio being
preserved. Thus, if the aspect ratio of the playback area does not match
the aspect ratio of the video, the video will be shown letterboxed or
pillarboxed. Areas of the element’s playback area that do not contain the
video represent nothing.
In user agents that implement CSS, the above requirement can be
implemented by using the style rule suggested in §10 Rendering.
The intrinsic width of a video element’s playback area is the intrinsic
width of the poster frame, if that is available and the element currently
represents its poster frame; otherwise, it is the intrinsic width of the
video resource, if that is available; otherwise the intrinsic width is
missing.
The intrinsic height of a video element’s playback area is the intrinsic
height of the poster frame, if that is available and the element currently
represents its poster frame; otherwise it is the intrinsic height of the
video resource, if that is available; otherwise the intrinsic height is
missing.
The default object size is a width of 300 CSS pixels and a height of 150
CSS pixels. [CSS3-IMAGES]
----------------------------------------------------------------------
User agents should provide controls to enable or disable the display of
closed captions, audio description tracks, and other additional data
associated with the video stream, though such features should, again, not
interfere with the page’s normal rendering.
User agents may allow users to view the video content in manners more
suitable to the user (e.g., fullscreen or in an independent resizable
window). Captions, subtitles or other additional visual tracks should
remain available and visible when enabled. As for the other user interface
features, controls to enable this should not interfere with the page’s
normal rendering unless the user agent is exposing a user interface. As
for the other user interface features, controls to enable this should not
interfere with the page’s normal rendering unless the user agent is
exposing a user interface. In such an independent context, however, user
agents may make full user interfaces visible e.g., play, pause, seeking,
and volume controls even if the controls attribute is absent.
User agents may allow video playback to affect system features that could
interfere with the user’s experience; for example, user agents could
disable screensavers while video playback is in progress.
----------------------------------------------------------------------
The poster IDL attribute must reflect the poster content attribute.
This example shows how to detect when a video has failed to play
correctly:
Download the video file .
4.7.11. The audio element
Categories:
Flow content.
Phrasing content.
Embedded content.
If the element has a controls attribute: Interactive content.
If the element has a controls attribute: Palpable content.
Contexts in which this element can be used:
Where embedded content is expected.
Content model:
If the element has a src attribute: zero or more track elements,
then transparent, but with no media element descendants.
If the element does not have a src attribute: zero or more source
elements, then zero or more track elements, then transparent, but
with no media element descendants.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
src - Address of the resource
crossorigin - How the element handles crossorigin requests
preload - Hints how much buffering the media resource will likely
need
autoplay - Hint that the media resource can be started
automatically when the page is loaded
loop - Whether to loop the media resource
muted - Whether to mute the media resource by default
controls - Show user agent controls
Allowed ARIA role attribute values:
application.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
[NamedConstructor=Audio(optional DOMString src)]
interface HTMLAudioElement : HTMLMediaElement {};
An audio element represents a sound or audio stream.
Content may be provided inside the audio element. User agents should not
show this content to the user; it is intended for older Web browsers which
do not support audio, so that legacy audio plugins can be tried, or to
show text to the users of these older browsers informing them of how to
access the audio contents.
In particular, this content is not intended to address accessibility
concerns. To make audio content accessible to the deaf or to those with
other physical or cognitive disabilities, a variety of features are
available. If captions or a sign language video are available, the video
element can be used instead of the audio element to play the audio,
allowing users to enable the visual alternatives. Chapter titles can be
provided to aid navigation, using the track element and a WebVTT file.
And, naturally, transcripts or other textual alternatives can be provided
by simply linking to them in the prose near the audio element. [WEBVTT]
The audio element is a media element whose media data is ostensibly audio
data.
The src, preload, autoplay, loop, muted, and controls attributes are the
attributes common to all media elements.
When an audio element is potentially playing, it must have its audio data
played synchronized with the current playback position, at the element’s
effective media volume. The user agent must play the audio from audio
tracks that were enabled when the event loop last reached step 1.
When an audio element is not potentially playing, audio must not play for
the element.
audio = new Audio( [ url ] )
Returns a new audio element, with the src attribute set to the
value passed in the argument, if applicable.
A constructor is provided for creating HTMLAudioElement objects (in
addition to the factory methods from DOM such as createElement()):
Audio(src). When invoked as a constructor, it must return a new
HTMLAudioElement object (a new audio element). The element must be created
with its preload attribute set to the literal value "auto". If the src
argument is present, the object created must be created with its src
content attribute set to the provided value (this will cause the user
agent to invoke the object’s resource selection algorithm before
returning). The element’s node document must be the active document of the
browsing context of the Window object on which the interface object of the
invoked constructor is found.
4.7.12. The track element
Categories:
None.
Contexts in which this element can be used:
As a child of a media element, before any flow content.
Content model:
Nothing.
Tag omission in text/html:
No end tag
Content attributes:
Global attributes
kind - The type of text track
src - Address of the resource
srclang - Language of the text track
label - User-visible label
default - Enable the track if no other text track is more suitable
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
DOM interface:
interface HTMLTrackElement : HTMLElement {
attribute DOMString kind;
attribute DOMString src;
attribute DOMString srclang;
attribute DOMString label;
attribute boolean default;
const unsigned short NONE = 0;
const unsigned short LOADING = 1;
const unsigned short LOADED = 2;
const unsigned short ERROR = 3;
readonly attribute unsigned short readyState;
readonly attribute TextTrack track;
};
The track element allows authors to specify explicit external text
resources for media elements. It does not represent anything on its own.
The kind attribute is an enumerated attribute. The following table lists
the keywords defined for this attribute. The keyword given in the first
cell of each row maps to the state given in the second cell.
Keyword State Brief description
Transcription or translation of the dialog,
suitable for when the sound is available but not
subtitles Subtitles understood (e.g., because the user does not
understand the language of the media resource’s
audio track). Overlaid on the video.
Transcription or translation of the dialog,
sound effects, relevant musical cues, and other
relevant audio information, suitable for when
captions Captions sound is unavailable or not clearly audible
(e.g., because it is muted, drowned-out by
ambient noise, or because the user is deaf).
Overlaid on the video; labeled as appropriate
for the hard-of-hearing.
Textual descriptions of the video component of
the media resource, intended for audio synthesis
when the visual component is obscured,
descriptions Descriptions unavailable, or not usable (e.g., because the
user is interacting with the application without
a screen while driving, or because the user is
blind). Synthesized as audio.
Chapter titles, intended to be used for
chapters Chapters navigating the media resource. Displayed as an
interactive (potentially nested) list in the
user agent’s interface.
metadata Metadata Tracks intended for use from script. Not
displayed by the user agent.
The attribute may be omitted. The missing value default is the subtitles
state. The invalid value default is the metadata state.
The src attribute gives the address of the text track data. The value must
be a valid non-empty URL potentially surrounded by spaces. This attribute
must be present.
If the element has a src attribute whose value is not the empty string and
whose value, when the attribute was set, could be successfully parsed
relative to the element’s node document, then the element’s track URL is
the resulting URL string. Otherwise, the element’s track URL is the empty
string.
If the element’s track URL identifies a WebVTT resource, and the element’s
kind attribute is not in the Metadata state, then the WebVTT file must be
a WebVTT file using cue text. [WEBVTT]
Furthermore, if the element’s track URL identifies a WebVTT resource, and
the element’s kind attribute is in the chapters state, then the WebVTT
file must be both a WebVTT file using chapter title text and a WebVTT file
using only nested cues. [WEBVTT]
The srclang attribute gives the language of the text track data. The value
must be a valid BCP 47 language tag. This attribute must be present if the
element’s kind attribute is in the subtitles state. [BCP47]
If the element has a srclang attribute whose value is not the empty
string, then the element’s track language is the value of the attribute.
Otherwise, the element has no track language.
The label attribute gives a user-readable title for the track. This title
is used by user agents when listing subtitle, caption, and audio
description tracks in their user interface.
The value of the label attribute, if the attribute is present, must not be
the empty string. Furthermore, there must not be two track element
children of the same media element whose kind attributes are in the same
state, whose srclang attributes are both missing or have values that
represent the same language, and whose label attributes are again both
missing or both have the same value.
If the element has a label attribute whose value is not the empty string,
then the element’s track label is the value of the attribute. Otherwise,
the element’s track label is an empty string.
The default attribute is a boolean attribute, which, if specified,
indicates that the track is to be enabled if the user’s preferences do not
indicate that another track would be more appropriate.
Each media element must have no more than one track element child whose
kind attribute is in the Subtitles or Captions state and whose default
attribute is specified.
Each media element must have no more than one track element child whose
kind attribute is in the Descriptions state and whose default attribute is
specified.
Each media element must have no more than one track element child whose
kind attribute is in the Chapters state and whose default attribute is
specified.
There is no limit on the number of track elements whose kind attribute is
in the Metadata state and whose default attribute is specified.
track . readyState
Returns the text track readiness state, represented by a number
from the following list:
track . NONE (0)
The text track not loaded state.
track . LOADING (1)
The text track loading state.
track . LOADED (2)
The text track loaded state.
track . ERROR (3)
The text track failed to load state.
track . track
Returns the TextTrack object corresponding to the text track of
the track element.
The readyState attribute must return the numeric value corresponding to
the text track readiness state of the track element’s text track, as
defined by the following list:
NONE (numeric value 0)
The text track not loaded state.
LOADING (numeric value 1)
The text track loading state.
LOADED (numeric value 2)
The text track loaded state.
ERROR (numeric value 3)
The text track failed to load state.
The track IDL attribute must, on getting, return the track element’s text
track’s corresponding TextTrack object.
The src, srclang, label, and default IDL attributes must reflect the
respective content attributes of the same name. The kind IDL attribute
must reflect the content attribute of the same name, limited to only known
values.
This video has subtitles in several languages:
(The lang attributes on the last two describe the language of the label
attribute, not the language of the subtitles themselves. The language of
the subtitles is given by the srclang attribute.)
4.7.13. Media elements
HTMLMediaElement objects (audio and video, in this specification) are
simply known as media elements.
enum CanPlayTypeResult { "" /* empty string */, "maybe", "probably" };
typedef (MediaStream or MediaSource or Blob) MediaProvider;
interface HTMLMediaElement : HTMLElement {
// error state
readonly attribute MediaError? error;
// network state
attribute DOMString src;
attribute MediaProvider? srcObject;
readonly attribute DOMString currentSrc;
attribute DOMString? crossOrigin;
const unsigned short NETWORK_EMPTY = 0;
const unsigned short NETWORK_IDLE = 1;
const unsigned short NETWORK_LOADING = 2;
const unsigned short NETWORK_NO_SOURCE = 3;
readonly attribute unsigned short networkState;
attribute DOMString preload;
readonly attribute TimeRanges buffered;
void load();
CanPlayTypeResult canPlayType(DOMString type);
// ready state
const unsigned short HAVE_NOTHING = 0;
const unsigned short HAVE_METADATA = 1;
const unsigned short HAVE_CURRENT_DATA = 2;
const unsigned short HAVE_FUTURE_DATA = 3;
const unsigned short HAVE_ENOUGH_DATA = 4;
readonly attribute unsigned short readyState;
readonly attribute boolean seeking;
// playback state
attribute double currentTime;
void fastSeek(double time);
readonly attribute unrestricted double duration;
object getStartDate();
readonly attribute boolean paused;
attribute double defaultPlaybackRate;
attribute double playbackRate;
readonly attribute TimeRanges played;
readonly attribute TimeRanges seekable;
readonly attribute boolean ended;
attribute boolean autoplay;
attribute boolean loop;
void play();
void pause();
// controls
attribute boolean controls;
attribute double volume;
attribute boolean muted;
attribute boolean defaultMuted;
// tracks
[SameObject] readonly attribute AudioTrackList audioTracks;
[SameObject] readonly attribute VideoTrackList videoTracks;
[SameObject] readonly attribute TextTrackList textTracks;
TextTrack addTextTrack(TextTrackKind kind, optional DOMString label = "", optional DOMString language = "");
};
The media element attributes, src, crossorigin, preload, autoplay, loop,
muted, and controls, apply to all media elements. They are defined in this
section.
Media elements are used to present audio data, or video and audio data, to
the user. This is referred to as media data in this section, since this
section applies equally to media elements for audio or for video.
The term media resource is used to refer to the complete set of media
data, e.g., the complete video file, or complete audio file.
A media resource can have multiple audio and video tracks. For the
purposes of a media element, the video data of the media resource is only
that of the currently selected track (if any) as given by the element’s
videoTracks attribute when the event loop last reached step 1, and the
audio data of the media resource is the result of mixing all the currently
enabled tracks (if any) given by the element’s audioTracks attribute when
the event loop last reached step 1.
Both audio and video elements can be used for both audio and video. The
main difference between the two is simply that the audio element has no
playback area for visual content (such as video or captions), whereas the
video element does.
Except where otherwise explicitly specified, the task source for all the
tasks queued in this section and its subsections is the media element
event task source of the media element in question.
4.7.13.1. Error codes
media . error
Returns a MediaError object representing the current error state
of the element.
Returns null if there is no error.
All media elements have an associated error status, which records the last
error the element encountered since its resource selection algorithm was
last invoked. The error attribute, on getting, must return the MediaError
object created for this last error, or null if there has not been an
error.
interface MediaError {
const unsigned short MEDIA_ERR_ABORTED = 1;
const unsigned short MEDIA_ERR_NETWORK = 2;
const unsigned short MEDIA_ERR_DECODE = 3;
const unsigned short MEDIA_ERR_SRC_NOT_SUPPORTED = 4;
readonly attribute unsigned short code;
};
media . error . code
Returns the current error’s error code, from the list below.
The code attribute of a MediaError object must return the code for the
error, which must be one of the following:
MEDIA_ERR_ABORTED (numeric value 1)
The fetching process for the media resource was aborted by the
user agent at the user’s request.
MEDIA_ERR_NETWORK (numeric value 2)
A network error of some description caused the user agent to stop
fetching the media resource, after the resource was established to
be usable.
MEDIA_ERR_DECODE (numeric value 3)
An error of some description occurred while decoding the media
resource, after the resource was established to be usable.
MEDIA_ERR_SRC_NOT_SUPPORTED (numeric value 4)
The media resource indicated by the src attribute or assigned
media provider object was not suitable.
4.7.13.2. Location of the media resource
The src content attribute on media elements gives the address of the media
resource (video, audio) to show. The attribute, if present, must contain a
valid non-empty URL potentially surrounded by spaces.
The crossorigin content attribute on media elements is a CORS settings
attribute.
If a media element is created with a src attribute, the user agent must
immediately invoke the media element’s resource selection algorithm.
If a src attribute of a media element is set or changed, the user agent
must invoke the media element’s media element load algorithm. (Removing
the src attribute does not do this, even if there are source elements
present.)
The src IDL attribute on media elements must reflect the content attribute
of the same name.
The crossOrigin IDL attribute must reflect the crossorigin content
attribute.
A media provider object is an object that can represent a media resource,
separate from a URL. MediaStream objects, MediaSource objects, Blob
objects, and File objects are all media provider objects.
Each media element can have an assigned media provider object, which is a
media provider object. When a media element is created, it has no assigned
media provider object.
media . srcObject [ = source ]
Allows the media element to be assigned a media provider object.
media . currentSrc
Returns the URL of the current media resource, if any.
Returns the empty string when there is no media resource, or it
doesn’t have a URL.
The currentSrc IDL attribute is initially the empty string. Its value is
changed by the resource selection algorithm defined below.
The srcObject IDL attribute, on getting, must return the element’s
assigned media provider object, if any, or null otherwise. On setting, it
must set the element’s assigned media provider object to the new value,
and then invoke the element’s media element load algorithm.
There are three ways to specify a media resource, the srcObject IDL
attribute, the src content attribute, and source elements. The IDL
attribute takes priority, followed by the content attribute, followed by
the elements.
4.7.13.3. MIME types
A media resource can be described in terms of its type, specifically a
MIME type, in some cases with a codecs parameter. (Whether the codecs
parameter is allowed or not depends on the MIME type.) [RFC6381]
Types are usually somewhat incomplete descriptions; for example
"video/mpeg" doesn’t say anything except what the container type is, and
even a type like "video/mp4; codecs="avc1.42E01E, mp4a.40.2"" doesn’t
include information like the actual bitrate (only the maximum bitrate).
Thus, given a type, a user agent can often only know whether it might be
able to play media of that type (with varying levels of confidence), or
whether it definitely cannot play media of that type.
A type that the user agent knows it cannot render is one that describes a
resource that the user agent definitely does not support, for example
because it doesn’t recognize the container type, or it doesn’t support the
listed codecs.
The MIME type "application/octet-stream" with no parameters is never a
type that the user agent knows it cannot render. User agents must treat
that type as equivalent to the lack of any explicit Content-Type metadata
when it is used to label a potential media resource.
Only the MIME type "application/octet-stream" with no parameters is
special-cased here; if any parameter appears with it, it will be treated
just like any other MIME type. This is a deviation from the rule that
unknown MIME type parameters should be ignored.
media . canPlayType(type)
Returns the empty string (a negative response), "maybe", or
"probably" based on how confident the user agent is that it can
play media resources of the given type.
The canPlayType(type) method must return the empty string if type is a
type that the user agent knows it cannot render or is the type
"application/octet-stream"; it must return "probably" if the user agent is
confident that the type represents a media resource that it can render if
used in with this audio or video element; and it must return "maybe"
otherwise. Implementors are encouraged to return "maybe" unless the type
can be confidently established as being supported or not. Generally, a
user agent should never return "probably" for a type that allows the
codecs parameter if that parameter is not present.
This script tests to see if the user agent supports a (fictional) new
format to dynamically decide whether to use a video element or a plugin:
The type attribute of the source element allows the user agent to avoid
downloading resources that use formats it cannot render.
4.7.13.4. Network states
media . networkState
Returns the current state of network activity for the element,
from the codes in the list below.
As media elements interact with the network, their current network
activity is represented by the networkState attribute. On getting, it must
return the current network state of the element, which must be one of the
following values:
NETWORK_EMPTY (numeric value 0)
The element has not yet been initialized. All attributes are in
their initial states.
NETWORK_IDLE (numeric value 1)
The element’s resource selection algorithm is active and has
selected a resource, but it is not actually using the network at
this time.
NETWORK_LOADING (numeric value 2)
The user agent is actively trying to download data.
NETWORK_NO_SOURCE (numeric value 3)
The element’s resource selection algorithm is active, but it has
not yet found a resource to use.
The resource selection algorithm defined below describes exactly when the
networkState attribute changes value and what events fire to indicate
changes in this state.
4.7.13.5. Loading the media resource
media . load()
Causes the element to reset and start selecting and loading a new
media resource from scratch.
All media elements have an autoplaying flag, which must begin in the true
state, and a delaying-the-load-event flag, which must begin in the false
state. While the delaying-the-load-event flag is true, the element must
delay the load event of its document.
When the load() method on a media element is invoked, the user agent must
run the media element load algorithm.
The media element load algorithm consists of the following steps.
1. Abort any already-running instance of the resource selection algorithm
for this element.
2. If there are any tasks from the media element’s media element event
task source in one of the task queues, then remove those tasks.
Basically, pending events and callbacks for the media element are
discarded when the media element starts loading a new resource.
3. If the media element’s networkState is set to NETWORK_LOADING or
NETWORK_IDLE, queue a task to fire a simple event named abort at the
media element.
4. If the media element’s networkState is not set to NETWORK_EMPTY, then
run these substeps:
1. Queue a task to fire a simple event named emptied at the media
element.
2. If a fetching process is in progress for the media element, the
user agent should stop it.
3. If the media element’s assigned media provider object is a
MediaSource object, then detach it.
4. Forget the media element’s media-resource-specific tracks.
5. If readyState is not set to HAVE_NOTHING, then set it to that
state.
6. If the paused attribute is false, then set it to true.
7. If seeking is true, set it to false.
8. Set the current playback position to 0.
Set the official playback position to 0.
If this changed the official playback position, then queue a task
to fire a simple event named timeupdate at the media element.
9. Set the initial playback position to 0.
10. Set the timeline offset to Not-a-Number (NaN).
11. Update the duration attribute to Not-a-Number (NaN).
The user agent will not fire a durationchange event for this
particular change of the duration.
5. Set the playbackRate attribute to the value of the defaultPlaybackRate
attribute.
6. Set the error attribute to null and the autoplaying flag to true.
7. Invoke the media element’s resource selection algorithm.
8. Playback of any previously playing media resource for this element
stops.
The resource selection algorithm for a media element is as follows. This
algorithm is always invoked as part of a task, but one of the first steps
in the algorithm is to return and continue running the remaining steps in
parallel. In addition, this algorithm interacts closely with the event
loop mechanism; in particular, it has synchronous sections (which are
triggered as part of the event loop algorithm). Steps in such sections are
marked with ⌛.
1. Set the element’s networkState attribute to the NETWORK_NO_SOURCE
value.
2. Set the element’s show poster flag to true.
3. Set the media element’s delaying-the-load-event flag to true (this
delays the load event).
4. in parallel await a stable state, allowing the task that invoked this
algorithm to continue. The synchronous section consists of all the
remaining steps of this algorithm until the algorithm says the
synchronous section has ended. (Steps in synchronous sections are
marked with ⌛.)
5. ⌛ If the media element’s blocked-on-parser flag is false, then
populate the list of pending text tracks.
6. ⌛ If the media element has an assigned media provider object, then let
mode be object.
⌛ Otherwise, if the media element has no assigned media provider
object but has a src attribute, then let mode be attribute.
⌛ Otherwise, if the media element does not have an assigned media
provider object and does not have a src attribute, but does have a
source element child, then let mode be children and let candidate be
the first such source element child in tree order.
⌛ Otherwise the media element has no assigned media provider object
and has neither a src attribute nor a source element child: set the
networkState to NETWORK_EMPTY, and abort these steps; the synchronous
section ends.
7. ⌛ Set the media element’s networkState to NETWORK_LOADING.
8. ⌛ Queue a task to fire a simple event named loadstart at the media
element.
9. Run the appropriate steps from the following list:
If mode is object
1. ⌛ Set the currentSrc attribute to the empty string.
2. End the synchronous section, continuing the
remaining steps in parallel.
3. Run the resource fetch algorithm with the assigned
media provider object. If that algorithm returns
without aborting this one, then the load failed.
4. Failed with media provider: Reaching this step
indicates that the media resource failed to load.
Queue a task to run the dedicated media source
failure steps.
5. Wait for the task queued by the previous step to
have executed.
6. Abort these steps. The element won’t attempt to load
another resource until this algorithm is triggered
again.
If mode is attribute
1. ⌛ If the src attribute’s value is the empty string,
then end the synchronous section, and jump down to
the failed with attribute step below.
2. ⌛ Let urlString and urlRecord be the resulting URL
string and the resulting URL record, respectively,
that would have resulted from parsing the URL
specified by the src attribute’s value relative to
the media element's node document when the src
attribute was last changed.
3. ⌛ If urlString was obtained successfully, set the
currentSrc attribute to urlString.
4. End the synchronous section, continuing the
remaining steps in parallel.
5. If urlRecord was obtained successfully, run the
resource fetch algorithm with urlRecord. If that
algorithm returns without aborting this one, then
the load failed.
6. Failed with attribute: Reaching this step indicates
that the media resource failed to load or that the
given URL could not be parsed. Queue a task to run
the dedicated media source failure steps.
7. Wait for the task queued by the previous step to
have executed.
8. Abort these steps. The element won’t attempt to load
another resource until this algorithm is triggered
again.
Otherwise (mode is children)
1. ⌛ Let pointer be a position defined by two adjacent
nodes in the media element’s child list, treating
the start of the list (before the first child in the
list, if any) and end of the list (after the last
child in the list, if any) as nodes in their own
right. One node is the node before pointer, and the
other node is the node after pointer. Initially, let
pointer be the position between the candidate node
and the next node, if there are any, or the end of
the list, if it is the last node.
As nodes are inserted and removed into the media
element, pointer must be updated as follows:
If a new node is inserted between the two nodes
that define pointer
Let pointer be the point between the
node before pointer and the new node.
In other words, insertions at pointer
go after pointer.
If the node before pointer is removed
Let pointer be the point between the
node after pointer and the node before
the node after pointer. In other words,
pointer doesn’t move relative to the
remaining nodes.
If the node after pointer is removed
Let pointer be the point between the
node before pointer and the node after
the node before pointer. Just as with
the previous case, pointer doesn’t move
relative to the remaining nodes.
Other changes don’t affect pointer.
2. ⌛ Process candidate: If candidate does not have a
src attribute, or if its src attribute’s value is
the empty string, then end the synchronous section,
and jump down to the failed with elements step
below.
3. ⌛ Let urlString and urlRecord be the resulting URL
string and the resulting URL record, respectively,
that would have resulted from parsing the URL
specified by candidate’s src attribute’s value
relative to the candidate’s node document when the
src attribute was last changed.
4. ⌛ If urlString was not obtained successfully, then
end the synchronous section, and jump down to the
Failed with elements step below.
5. ⌛ If candidate has a type attribute whose value,
when parsed as a MIME type (including any codecs
described by the codecs parameter, for types that
define that parameter), represents a type that the
user agent knows it cannot render, then end the
synchronous section, and jump down to the failed
with elements step below.
6. ⌛ Set the currentSrc attribute to urlString.
7. End the synchronous section, continuing the
remaining steps in parallel.
8. Run the resource fetch algorithm with urlRecord. If
that algorithm returns without aborting this one,
then the load failed.
9. Failed with elements: Queue a task to fire a simple
event named error at the candidate element.
10. Await a stable state. The synchronous section
consists of all the remaining steps of this
algorithm until the algorithm says the synchronous
section has ended. (Steps in synchronous sections
are marked with ⌛.)
11. ⌛ Forget the media element’s media-resource-specific
tracks.
12. ⌛ Find next candidate: Let candidate be null.
13. ⌛ Search loop: If the node after pointer is the end
of the list, then jump to the waiting step below.
14. ⌛ If the node after pointer is a source element, let
candidate be that element.
15. ⌛ Advance pointer so that the node before pointer is
now the node that was after pointer, and the node
after pointer is the node after the node that used
to be after pointer, if any.
16. ⌛ If candidate is null, jump back to the search loop
step. Otherwise, jump back to the process candidate
step.
17. ⌛ Waiting: Set the element’s networkState attribute
to the NETWORK_NO_SOURCE value.
18. ⌛ Set the element’s show poster flag to true.
19. ⌛ Queue a task to set the element’s
delaying-the-load-event flag to false. This stops
delaying the load event.
20. End the synchronous section, continuing the
remaining steps in parallel.
21. Wait until the node after pointer is a node other
than the end of the list. (This step might wait
forever.)
22. Await a stable state. The synchronous section
consists of all the remaining steps of this
algorithm until the algorithm says the synchronous
section has ended. (Steps in synchronous sections
are marked with ⌛.)
23. ⌛ Set the element’s delaying-the-load-event flag
back to true (this delays the load event again, in
case it hasn’t been fired yet).
24. ⌛ Set the networkState back to NETWORK_LOADING.
25. ⌛ Jump back to the find next candidate step above.
The dedicated media source failure steps are the following steps:
1. Set the error attribute to a new MediaError object whose code
attribute is set to MEDIA_ERR_SRC_NOT_SUPPORTED.
2. Forget the media element’s media-resource-specific tracks.
3. Set the element’s networkState attribute to the NETWORK_NO_SOURCE
value.
4. Set the element’s show poster flag to true.
5. Fire a simple event named error at the media element.
6. Set the element’s delaying-the-load-event flag to false. This
stops delaying the load event.
The resource fetch algorithm for a media element and a given URL record or
media provider object is as follows:
1. If the algorithm was invoked with media provider object or a URL
record whose object is a media provider object, then let mode be
local. Otherwise let mode be remote.
2. If mode is remote, then let the current media resource be the resource
given by the URL record passed to this algorithm; otherwise, let the
current media resource be the resource given by the media provider
object. Either way, the current media resource is now the element’s
media resource.
3. Remove all media-resource-specific text tracks from the media
element’s list of pending text tracks, if any.
4. Run the appropriate steps from the following list:
If mode is remote
1. Optionally, run the following substeps. This is the
expected behavior if the user agent intends to not
attempt to fetch the resource until the user
requests it explicitly (e.g., as a way to implement
the preload attribute’s none keyword).
1. Set the networkState to NETWORK_IDLE.
2. Queue a task to fire a simple event named
suspend at the element.
3. Queue a task to set the element’s
delaying-the-load-event flag to false. This
stops delaying the load event.
4. Wait for the task to be run.
5. Wait for an implementation-defined event (e.g.,
the user requesting that the media element
begin playback).
6. Set the element’s delaying-the-load-event flag
back to true (this delays the load event again,
in case it hasn’t been fired yet).
7. Set the networkState to NETWORK_LOADING.
2. Let request be the result of creating a
potential-CORS request given current media
resource’s URL record and the media element’s
crossorigin content attribute value.
Set request’s client to the media element’s node
document’s Window object’s environment settings
object and type to "audio" if the media element is
an audio element and to "video" otherwise.
Fetch request.
The response’s unsafe response obtained in this
fashion, if any, contains the media data. It can be
CORS-same-origin or CORS-cross-origin; this affects
whether subtitles referenced in the media data are
exposed in the API and, for video elements, whether
a canvas gets tainted when the video is drawn on it.
The stall timeout is a user-agent defined length of
time, which should be about three seconds. When a
media element that is actively attempting to obtain
media data has failed to receive any data for a
duration equal to the stall timeout, the user agent
must queue a task to fire a simple event named
stalled at the element.
User agents may allow users to selectively block or
slow media data downloads. When a media element’s
download has been blocked altogether, the user agent
must act as if it was stalled (as opposed to acting
as if the connection was closed). The rate of the
download may also be throttled automatically by the
user agent, e.g., to balance the download with other
connections sharing the same bandwidth.
User agents may decide to not download more content
at any time, e.g., after buffering five minutes of a
one hour media resource, while waiting for the user
to decide whether to play the resource or not, while
waiting for user input in an interactive resource,
or when the user navigates away from the page. When
a media element’s download has been suspended, the
user agent must queue a task, to set the
networkState to NETWORK_IDLE and fire a simple event
named suspend at the element. If and when
downloading of the resource resumes, the user agent
must queue a task to set the networkState to
NETWORK_LOADING. Between the queuing of these tasks,
the load is suspended (so progress events don’t
fire, as described above).
The preload attribute provides a hint regarding how
much buffering the author thinks is advisable, even
in the absence of the autoplay attribute.
When a user agent decides to completely suspend a
download, e.g., if it is waiting until the user
starts playback before downloading any further
content, the user agent must queue a task to set the
element’s delaying-the-load-event flag to false.
This stops delaying the load event.
The user agent may use whatever means necessary to
fetch the resource (within the constraints put
forward by this and other specifications); for
example, reconnecting to the server in the face of
network errors, using HTTP range retrieval requests,
or switching to a streaming protocol. The user agent
must consider a resource erroneous only if it has
given up trying to fetch it.
To determine the format of the media resource, the
user agent must use the rules for sniffing audio and
video specifically.
While the load is not suspended (see below), every
350ms (±200ms) or for every byte received, whichever
is least frequent, queue a task to fire a simple
event named progress at the element.
The networking task source tasks to process the data
as it is being fetched must each immediately queue a
task to run the first appropriate steps from the
media data processing steps list below. (A new task
is used for this so that the work described below
occurs relative to the media element event task
source rather than the networking task source.)
When the networking task source has queued the last
task as part of fetching the media resource (i.e.,
once the download has completed), if the fetching
process completes without errors, including decoding
the media data, and if all of the data is available
to the user agent without network access, then, the
user agent must move on to the final step below.
This might never happen, e.g., when streaming an
infinite resource such as Web radio, or if the
resource is longer than the user agent’s ability to
cache data.
While the user agent might still need network access
to obtain parts of the media resource, the user
agent must remain on this step.
For example, if the user agent has discarded the
first half of a video, the user agent will remain at
this step even once the playback has ended, because
there is always the chance the user will seek back
to the start. In fact, in this situation, once
playback has ended, the user agent will end up
firing a suspend event, as described earlier.
Otherwise (mode is local)
The resource described by the current media resource, if
any, contains the media data. It is CORS-same-origin.
If the current media resource is a raw data stream (e.g.,
from a File object), then to determine the format of the
media resource, the user agent must use the rules for
sniffing audio and video specifically. Otherwise, if the
data stream is pre-decoded, then the format is the format
given by the relevant specification.
Set the element’s delaying-the-load-event flag to false.
This stops delaying the load event when the resource is
local.
Whenever new data for the current media resource becomes
available, queue a task to run the first appropriate
steps from the media data processing steps list below.
When the current media resource is permanently exhausted
(e.g., all the bytes of a Blob have been processed), if
there were no decoding errors, then the user agent must
move on to the final step below. This might never happen,
e.g., if the current media resource is a MediaStream.
The media data processing steps list is as follows:
If the media data cannot be fetched at all, due to network
errors, causing the user agent to give up trying to fetch the
resource
If the media data can be fetched but is found by inspection to be
in an unsupported format, or can otherwise not be rendered at all
DNS errors, HTTP 4xx and 5xx errors (and equivalents in
other protocols), and other fatal network errors that
occur before the user agent has established whether the
current media resource is usable, as well as the file
using an unsupported container format, or using
unsupported codecs for all the data, must cause the user
agent to execute the following steps:
1. The user agent should cancel the fetching process.
2. Abort this subalgorithm, returning to the resource
selection algorithm.
If the media resource is found to have an audio track
1. Create an AudioTrack object to represent the audio
track.
2. Update the media element’s audioTracks attribute’s
AudioTrackList object with the new AudioTrack
object.
3. Let enable be unknown.
4. If either the media resource or the address of the
current media resource indicate a particular set of
audio tracks to enable, or if the user agent has
information that would facilitate the selection of
specific audio tracks to improve the user’s
experience, then: if this audio track is one of the
ones to enable, then set enable to true, otherwise,
set enable to false.
This could be triggered by Media Fragments URI
fragment identifier syntax, but it could also be
triggered e.g., by the user agent selecting a 5.1
surround sound audio track over a stereo audio
track. [MEDIA-FRAGS]
5. If enable is still unknown, then, if the media
element does not yet have an enabled audio track,
then set enable to true, otherwise, set enable to
false.
6. If enable is true, then enable this audio track,
otherwise, do not enable this audio track.
7. Fire a trusted event with the name addtrack, that
does not bubble and is not cancelable, and that uses
the TrackEvent interface, with the track attribute
initialized to the new AudioTrack object, at this
AudioTrackList object.
If the media resource is found to have a video track
1. Create a VideoTrack object to represent the video
track.
2. Update the media element’s videoTracks attribute’s
VideoTrackList object with the new VideoTrack
object.
3. Let enable be unknown.
4. If either the media resource or the address of the
current media resource indicate a particular set of
video tracks to enable, or if the user agent has
information that would facilitate the selection of
specific video tracks to improve the user’s
experience, then: if this video track is the first
such video track, then set enable to true,
otherwise, set enable to false.
This could again be triggered by media fragments
syntax.
5. If enable is still unknown, then, if the media
element does not yet have a selected video track,
then set enable to true, otherwise, set enable to
false.
6. If enable is true, then select this track and
unselect any previously selected video tracks,
otherwise, do not select this video track. If other
tracks are unselected, then a change event will be
fired.
7. Fire a trusted event with the name addtrack, that
does not bubble and is not cancelable, and that uses
the TrackEvent interface, with the track attribute
initialized to the new VideoTrack object, at this
VideoTrackList object.
Once enough of the media data has been fetched to determine the
duration of the media resource, its dimensions, and other
metadata
This indicates that the resource is usable. The user
agent must follow these substeps:
1. Establish the media timeline for the purposes of the
current playback position and the earliest possible
position, based on the media data.
2. Update the timeline offset to the date and time that
corresponds to the zero time in the media timeline
established in the previous step, if any. If no
explicit time and date is given by the media
resource, the timeline offset must be set to
Not-a-Number (NaN).
3. Set the current playback position and the official
playback position to the earliest possible position.
4. Update the duration attribute with the time of the
last frame of the resource, if known, on the media
timeline established above. If it is not known
(e.g., a stream that is in principle infinite),
update the duration attribute to the value positive
Infinity.
The user agent will queue a task to fire a simple
event named durationchange at the element at this
point.
5. For video elements, set the videoWidth and
videoHeight attributes, and queue a task to fire a
simple event named resize at the media element.
Further resize events will be fired if the
dimensions subsequently change.
6. Set the readyState attribute to HAVE_METADATA.
A loadedmetadata DOM event will be fired as part of
setting the readyState attribute to a new value.
7. Let jumped be false.
8. If the media element’s default playback start
position is greater than zero, then seek to that
time, and let jumped be true.
9. Let the media element’s default playback start
position be zero.
10. Let the initial playback position be zero.
11. If either the media resource or the address of the
current media resource indicate a particular start
time, then set the initial playback position to that
time and, if jumped is still false, seek to that
time and let jumped be true.
For example, with media formats that support the
media fragment syntax the fragment, can be used to
indicate a start position. [MEDIA-FRAGS]
12. If there is no enabled audio track, then enable an
audio track. This will cause a change event to be
fired.
13. If there is no selected video track, then select a
video track. This will cause a change event to be
fired.
Once the readyState attribute reaches HAVE_CURRENT_DATA,
after the loadeddata event has been fired, set the
element’s delaying-the-load-event flag to false. This
stops delaying the load event.
A user agent that is attempting to reduce network usage
while still fetching the metadata for each media resource
would also stop buffering at this point, following the
rules described previously, which involve the
networkState attribute switching to the NETWORK_IDLE
value and a suspend event firing.
The user agent is required to determine the duration of
the media resource and go through this step before
playing.
Once the entire media resource has been fetched (but potentially
before any of it has been decoded)
Fire a simple event named progress at the media element.
Set the networkState to NETWORK_IDLE and fire a simple
event named suspend at the media element.
If the user agent ever discards any media data and then
needs to resume the network activity to obtain it again,
then it must queue a task to set the networkState to
NETWORK_LOADING.
If the user agent can keep the media resource loaded,
then the algorithm will continue to its final step below,
which aborts the algorithm.
If the connection is interrupted after some media data has been
received, causing the user agent to give up trying to fetch the
resource
Fatal network errors that occur after the user agent has
established whether the current media resource is usable
(i.e., once the media element’s readyState attribute is
no longer HAVE_NOTHING) must cause the user agent to
execute the following steps:
1. The user agent should cancel the fetching process.
2. Set the error attribute to a new MediaError object
whose code attribute is set to MEDIA_ERR_NETWORK.
3. Set the element’s networkState attribute to the
NETWORK_IDLE value.
4. Set the element’s delaying-the-load-event flag to
false. This stops delaying the load event.
5. Fire a simple event named error at the media
element.
6. Abort the overall resource selection algorithm.
If the media data is corrupted
Fatal errors in decoding the media data that occur after
the user agent has established whether the current media
resource is usable (i.e., once the media element’s
readyState attribute is no longer HAVE_NOTHING) must
cause the user agent to execute the following steps:
1. The user agent should cancel the fetching process.
2. Set the error attribute to a new MediaError object
whose code attribute is set to MEDIA_ERR_DECODE.
3. Set the element’s networkState attribute to the
NETWORK_IDLE value.
4. Set the element’s delaying-the-load-event flag to
false. This stops delaying the load event.
5. Fire a simple event named error at the media
element.
6. Abort the overall resource selection algorithm.
If the media data fetching process is aborted by the user
The fetching process is aborted by the user, e.g.,
because the user pressed a "stop" button, the user agent
must execute the following steps. These steps are not
followed if the load() method itself is invoked while
these steps are running, as the steps above handle that
particular kind of abort.
1. The user agent should cancel the fetching process.
2. Set the error attribute to a new MediaError object
whose code attribute is set to MEDIA_ERR_ABORTED.
3. Fire a simple event named abort at the media
element.
4. If the media element’s readyState attribute has a
value equal to HAVE_NOTHING, set the element’s
networkState attribute to the NETWORK_EMPTY value,
set the element’s show poster flag to true, and fire
a simple event named emptied at the element.
Otherwise, set the element’s networkState attribute
to the NETWORK_IDLE value.
5. Set the element’s delaying-the-load-event flag to
false. This stops delaying the load event.
6. Abort the overall resource selection algorithm.
If the media data can be fetched but has non-fatal errors or
uses, in part, codecs that are unsupported, preventing the user
agent from rendering the content completely correctly but not
preventing playback altogether
The server returning data that is partially usable but
cannot be optimally rendered must cause the user agent to
render just the bits it can handle, and ignore the rest.
If the media resource is found to declare a
media-resource-specific text track that the user agent supports
If the media data is CORS-same-origin, run the steps to
expose a media-resource-specific text track with the
relevant data.
Cross-origin videos do not expose their subtitles, since
that would allow attacks such as hostile sites reading
subtitles from confidential videos on a user’s intranet.
5. Final step: If the user agent ever reaches this step (which can only
happen if the entire resource gets loaded and kept available): abort
the overall resource selection algorithm.
When a media element is to forget the media element’s
media-resource-specific tracks, the user agent must remove from the media
element’s list of text tracks all the media-resource-specific text tracks,
then empty the media element’s audioTracks attribute’s AudioTrackList
object, then empty the media element’s videoTracks attribute’s
VideoTrackList object. No events (in particular, no removetrack events)
are fired as part of this; the error and emptied events, fired by the
algorithms that invoke this one, can be used instead.
----------------------------------------------------------------------
The preload attribute is an enumerated attribute. The following table
lists the keywords and states for the attribute — the keywords in the left
column map to the states in the cell in the second column on the same row
as the keyword. The attribute can be changed even once the media resource
is being buffered or played; the descriptions in the table below are to be
interpreted with that in mind.
Keyword State Brief description
Hints to the user agent that either the author does not
expect the user to need the media resource, or that the
server wants to minimize unnecessary traffic. This
none None state does not provide a hint regarding how
aggressively to actually download the media resource if
buffering starts anyway (e.g., once the user hits
"play").
Hints to the user agent that the author does not expect
the user to need the media resource, but that fetching
the resource metadata (dimensions, track list,
duration, etc), and maybe even the first few frames, is
reasonable. If the user agent precisely fetches no more
than the metadata, then the media element will end up
with its readyState attribute set to HAVE_METADATA;
metadata Metadata typically though, some frames will be obtained as well
and it will probably be HAVE_CURRENT_DATA or
HAVE_FUTURE_DATA. When the media resource is playing,
hints to the user agent that bandwidth is to be
considered scarce, e.g., suggesting throttling the
download so that the media data is obtained at the
slowest possible rate that still maintains consistent
playback.
Hints to the user agent that the user agent can put the
auto Automatic user’s needs first without risk to the server, up to
and including optimistically downloading the entire
resource.
The empty string is also a valid keyword, and maps to the Automatic state.
The attribute’s missing value default is user-agent defined, though the
Metadata state is suggested as a compromise between reducing server load
and providing an optimal user experience.
Authors might switch the attribute from "none" or "metadata" to "auto"
dynamically once the user begins playback. For example, on a page with
many videos this might be used to indicate that the many videos are not to
be downloaded unless requested, but that once one is requested it is to be
downloaded aggressively.
The preload attribute is intended to provide a hint to the user agent
about what the author thinks will lead to the best user experience. The
attribute may be ignored altogether, for example based on explicit user
preferences or based on the available connectivity.
The preload IDL attribute must reflect the content attribute of the same
name, limited to only known values.
The autoplay attribute can override the preload attribute (since if the
media plays, it naturally has to buffer first, regardless of the hint
given by the preload attribute). Including both is not an error, however.
----------------------------------------------------------------------
media . buffered
Returns a TimeRanges object that represents the ranges of the
media resource that the user agent has buffered.
The buffered attribute must return a new static normalized TimeRanges
object that represents the ranges of the media resource, if any, that the
user agent has buffered, at the time the attribute is evaluated. Users
agents must accurately determine the ranges available, even for media
streams where this can only be determined by tedious inspection.
Typically this will be a single range anchored at the zero point, but if,
e.g., the user agent uses HTTP range requests in response to seeking, then
there could be multiple ranges.
User agents may discard previously buffered data.
Thus, a time position included within a range of the objects return by the
buffered attribute at one time can end up being not included in the
range(s) of objects returned by the same attribute at later times.
4.7.13.6. Offsets into the media resource
media . duration
Returns the length of the media resource, in seconds, assuming
that the start of the media resource is at time zero.
Returns NaN if the duration isn’t available.
Returns Infinity for unbounded streams.
media . currentTime [ = value ]
Returns the official playback position, in seconds.
Can be set, to seek to the given time.
A media resource has a media timeline that maps times (in seconds) to
positions in the media resource. The origin of a timeline is its earliest
defined position. The duration of a timeline is its last defined position.
Establishing the media timeline: If the media resource somehow specifies
an explicit timeline whose origin is not negative (i.e., gives each frame
a specific time offset and gives the first frame a zero or positive
offset), then the media timeline should be that timeline. (Whether the
media resource can specify a timeline or not depends on the media
resource’s format.) If the media resource specifies an explicit start time
and date, then that time and date should be considered the zero point in
the media timeline; the timeline offset will be the time and date, exposed
using the getStartDate() method.
If the media resource has a discontinuous timeline, the user agent must
extend the timeline used at the start of the resource across the entire
resource, so that the media timeline of the media resource increases
linearly starting from the earliest possible position (as defined below),
even if the underlying media data has out-of-order or even overlapping
time codes.
For example, if two clips have been concatenated into one video file, but
the video format exposes the original times for the two clips, the video
data might expose a timeline that goes, say, 00:15..00:29 and then
00:05..00:38. However, the user agent would not expose those times; it
would instead expose the times as 00:15..00:29 and 00:29..01:02, as a
single video.
In the rare case of a media resource that does not have an explicit
timeline, the zero time on the media timeline should correspond to the
first frame of the media resource. In the even rarer case of a media
resource with no explicit timings of any kind, not even frame durations,
the user agent must itself determine the time for each frame in a
user-agent-defined manner. (This is a fingerprinting vector.)
An example of a file format with no explicit timeline but with explicit
frame durations is the Animated GIF format. An example of a file format
with no explicit timings at all is the JPEG-push format
(multipart/x-mixed-replace with JPEG frames, often used as the format for
MJPEG streams).
If, in the case of a resource with no timing information, the user agent
will nonetheless be able to seek to an earlier point than the first frame
originally provided by the server, then the zero time should correspond to
the earliest seekable time of the media resource; otherwise, it should
correspond to the first frame received from the server (the point in the
media resource at which the user agent began receiving the stream).
At the time of writing, there is no known format that lacks explicit frame
time offsets yet still supports seeking to a frame before the first frame
sent by the server.
Consider a stream from a TV broadcaster, which begins streaming on a sunny
Friday afternoon in October, and always sends connecting user agents the
media data on the same media timeline, with its zero time set to the start
of this stream. Months later, user agents connecting to this stream will
find that the first frame they receive has a time with millions of
seconds. The getStartDate() method would always return the date that the
broadcast started; this would allow controllers to display real times in
their scrubber (e.g., "2:30pm") rather than a time relative to when the
broadcast began ("8 months, 4 hours, 12 minutes, and 23 seconds").
Consider a stream that carries a video with several concatenated
fragments, broadcast by a server that does not allow user agents to
request specific times but instead just streams the video data in a
predetermined order, with the first frame delivered always being
identified as the frame with time zero. If a user agent connects to this
stream and receives fragments defined as covering timestamps 2010-03-20
23:15:00 UTC to 2010-03-21 00:05:00 UTC and 2010-02-12 14:25:00 UTC to
2010-02-12 14:35:00 UTC, it would expose this with a media timeline
starting at 0s and extending to 3,600s (one hour). Assuming the streaming
server disconnected at the end of the second clip, the duration attribute
would then return 3,600. The getStartDate() method would return a Date
object with a time corresponding to 2010-03-20 23:15:00 UTC. However, if a
different user agent connected five minutes later, it would (presumably)
receive fragments covering timestamps 2010-03-20 23:20:00 UTC to
2010-03-21 00:05:00 UTC and 2010-02-12 14:25:00 UTC to 2010-02-12 14:35:00
UTC, and would expose this with a media timeline starting at 0s and
extending to 3,300s (fifty five minutes). In this case, the getStartDate()
method would return a Date object with a time corresponding to 2010-03-20
23:20:00 UTC.
In both of these examples, the seekable attribute would give the ranges
that the controller would want to actually display in its UI; typically,
if the servers don’t support seeking to arbitrary times, this would be the
range of time from the moment the user agent connected to the stream up to
the latest frame that the user agent has obtained; however, if the user
agent starts discarding earlier information, the actual range might be
shorter.
In any case, the user agent must ensure that the earliest possible
position (as defined below) using the established media timeline, is
greater than or equal to zero.
The media timeline also has an associated clock. Which clock is used is
user-agent defined, and may be media resource-dependent, but it should
approximate the user’s wall clock.
Media elements have a current playback position, which must initially
(i.e., in the absence of media data) be zero seconds. The current playback
position is a time on the media timeline.
Media elements also have an official playback position, which must
initially be set to zero seconds. The official playback position is an
approximation of the current playback position that is kept stable while
scripts are running.
Media elements also have a default playback start position, which must
initially be set to zero seconds. This time is used to allow the element
to be seeked even before the media is loaded.
Each media element has a show poster flag. When a media element is
created, this flag must be set to true. This flag is used to control when
the user agent is to show a poster frame for a video element instead of
showing the video contents.
The currentTime attribute must, on getting, return the media element’s
default playback start position, unless that is zero, in which case it
must return the element’s official playback position. The returned value
must be expressed in seconds. On setting, if the media element’s
readyState is HAVE_NOTHING, then it must set the media element’s default
playback start position to the new value; otherwise, it must set the
official playback position to the new value and then seek to the new
value. The new value must be interpreted as being in seconds.
Media elements have an initial playback position, which must initially
(i.e., in the absence of media data) be zero seconds. The initial playback
position is updated when a media resource is loaded. The initial playback
position is a time on the media timeline.
If the media resource is a streaming resource, then the user agent might
be unable to obtain certain parts of the resource after it has expired
from its buffer. Similarly, some media resources might have a media
timeline that doesn’t start at zero. The earliest possible position is the
earliest position in the stream or resource that the user agent can ever
obtain again. It is also a time on the media timeline.
The earliest possible position is not explicitly exposed in the API; it
corresponds to the start time of the first range in the seekable
attribute’s TimeRanges object, if any, or the current playback position
otherwise.
When the earliest possible position changes, then: if the current playback
position is before the earliest possible position, the user agent must
seek to the earliest possible position; otherwise, if the user agent has
not fired a timeupdate event at the element in the past 15 to 250ms and is
not still running event handlers for such an event, then the user agent
must queue a task to fire a simple event named timeupdate at the element.
Because of the above requirement and the requirement in the resource fetch
algorithm that kicks in when the metadata of the clip becomes known, the
current playback position can never be less than the earliest possible
position.
If at any time the user agent learns that an audio or video track has
ended and all media data relating to that track corresponds to parts of
the media timeline that are before the earliest possible position, the
user agent may queue a task to first remove the track from the audioTracks
attribute’s AudioTrackList object or the videoTracks attribute’s
VideoTrackList object as appropriate and then fire a trusted event with
the name removetrack, that does not bubble and is not cancelable, and that
uses the TrackEvent interface, with the track attribute initialized to the
AudioTrack or VideoTrack object representing the track, at the media
element’s aforementioned AudioTrackList or VideoTrackList object.
The duration attribute must return the time of the end of the media
resource, in seconds, on the media timeline. If no media data is
available, then the attributes must return the Not-a-Number (NaN) value.
If the media resource is not known to be bounded (e.g., streaming radio,
or a live event with no announced end time), then the attribute must
return the positive Infinity value.
The user agent must determine the duration of the media resource before
playing any part of the media data and before setting readyState to a
value equal to or greater than HAVE_METADATA, even if doing so requires
fetching multiple parts of the resource.
When the length of the media resource changes to a known value (e.g., from
being unknown to known, or from a previously established length to a new
length) the user agent must queue a task to fire a simple event named
durationchange at the media element. (The event is not fired when the
duration is reset as part of loading a new media resource.) If the
duration is changed such that the current playback position ends up being
greater than the time of the end of the media resource, then the user
agent must also seek to the time of the end of the media resource.
If an "infinite" stream ends for some reason, then the duration would
change from positive Infinity to the time of the last frame or sample in
the stream, and the durationchange event would be fired. Similarly, if the
user agent initially estimated the media resource’s duration instead of
determining it precisely, and later revises the estimate based on new
information, then the duration would change and the durationchange event
would be fired.
Some video files also have an explicit date and time corresponding to the
zero time in the media timeline, known as the timeline offset. Initially,
the timeline offset must be set to Not-a-Number (NaN).
The getStartDate() method must return a new Date object representing the
current timeline offset.
----------------------------------------------------------------------
The loop attribute is a boolean attribute that, if specified, indicates
that the media element is to seek back to the start of the media resource
upon reaching the end.
The loop IDL attribute must reflect the content attribute of the same
name.
4.7.13.7. Ready states
media . readyState
Returns a value that expresses the current state of the element
with respect to rendering the current playback position, from the
codes in the list below.
Media elements have a ready state, which describes to what degree they are
ready to be rendered at the current playback position. The possible values
are as follows; the ready state of a media element at any particular time
is the greatest value describing the state of the element:
HAVE_NOTHING (numeric value 0)
No information regarding the media resource is available. No data
for the current playback position is available. Media elements
whose networkState attribute are set to NETWORK_EMPTY are always
in the HAVE_NOTHING state.
HAVE_METADATA (numeric value 1)
Enough of the resource has been obtained that the duration of the
resource is available. In the case of a video element, the
dimensions of the video are also available. No media data is
available for the immediate current playback position.
HAVE_CURRENT_DATA (numeric value 2)
Data for the immediate current playback position is available, but
either not enough data is available that the user agent could
successfully advance the current playback position in the
direction of playback at all without immediately reverting to the
HAVE_METADATA state, or there is no more data to obtain in the
direction of playback. For example, in video this corresponds to
the user agent having data from the current frame, but not the
next frame, when the current playback position is at the end of
the current frame; and to when playback has ended.
HAVE_FUTURE_DATA (numeric value 3)
Data for the immediate current playback position is available, as
well as enough data for the user agent to advance the current
playback position in the direction of playback at least a little
without immediately reverting to the HAVE_METADATA state, and the
text tracks are ready. For example, in video this corresponds to
the user agent having data for at least the current frame and the
next frame when the current playback position is at the instant in
time between the two frames, or to the user agent having the video
data for the current frame and audio data to keep playing at least
a little when the current playback position is in the middle of a
frame. The user agent cannot be in this state if playback has
ended, as the current playback position can never advance in this
case.
HAVE_ENOUGH_DATA (numeric value 4)
All the conditions described for the HAVE_FUTURE_DATA state are
met, and, in addition, either of the following conditions is also
true:
* The user agent estimates that data is being fetched at a rate
where the current playback position, if it were to advance at
the effective playback rate, would not overtake the available
data before playback reaches the end of the media resource.
* The user agent has entered a state where waiting longer will
not result in further data being obtained, and therefore
nothing would be gained by delaying playback any further.
(For example, the buffer might be full.)
In practice, the difference between HAVE_METADATA and HAVE_CURRENT_DATA is
negligible. Really the only time the difference is relevant is when
painting a video element onto a canvas, where it distinguishes the case
where something will be drawn (HAVE_CURRENT_DATA or greater) from the case
where nothing is drawn (HAVE_METADATA or less). Similarly, the difference
between HAVE_CURRENT_DATA (only the current frame) and HAVE_FUTURE_DATA
(at least this frame and the next) can be negligible (in the extreme, only
one frame). The only time that distinction really matters is when a page
provides an interface for "frame-by-frame" navigation.
When the ready state of a media element whose networkState is not
NETWORK_EMPTY changes, the user agent must follow the steps given below:
1. Apply the first applicable set of substeps from the following list:
If the previous ready state was HAVE_NOTHING, and the new ready
state is HAVE_METADATA
Queue a task to fire a simple event named loadedmetadata
at the element.
Before this task is run, as part of the event loop
mechanism, the rendering will have been updated to resize
the video element if appropriate.
If the previous ready state was HAVE_METADATA and the new ready
state is HAVE_CURRENT_DATA or greater
If this is the first time this occurs for this media
element since the load() algorithm was last invoked, the
user agent must queue a task to fire a simple event named
loadeddata at the element.
If the new ready state is HAVE_FUTURE_DATA or
HAVE_ENOUGH_DATA, then the relevant steps below must then
be run also.
If the previous ready state was HAVE_FUTURE_DATA or more, and the
new ready state is HAVE_CURRENT_DATA or less
If the media element was potentially playing before its
readyState attribute changed to a value lower than
HAVE_FUTURE_DATA, and the element has not ended playback,
and playback has not stopped due to errors, paused for
user interaction, or paused for in-band content, the user
agent must queue a task to fire a simple event named
timeupdate at the element, and queue a task to fire a
simple event named waiting at the element.
If the previous ready state was HAVE_CURRENT_DATA or less, and
the new ready state is HAVE_FUTURE_DATA
The user agent must queue a task to fire a simple event
named canplay at the element.
If the element’s paused attribute is false, the user
agent must queue a task to fire a simple event named
playing at the element.
If the new ready state is HAVE_ENOUGH_DATA
If the previous ready state was HAVE_CURRENT_DATA or
less, the user agent must queue a task to fire a simple
event named canplay at the element, and, if the element’s
paused attribute is false, queue a task to fire a simple
event named playing at the element.
If the autoplaying flag is true, and the paused attribute
is true, and the media element has an autoplay attribute
specified, and the media element’s node document’s active
sandboxing flag set does not have the sandboxed automatic
features browsing context flag set, then the user agent
may also run the following substeps:
1. Set the paused attribute to false.
2. If the element’s show poster flag is true, set it to
false and run the time marches on steps.
3. Queue a task to fire a simple event named play at
the element.
4. Queue a task to fire a simple event named playing at
the element.
5. Set the autoplaying flag to false.
User agents do not need to support autoplay, and it is
suggested that user agents honor user preferences on the
matter. Authors are urged to use the autoplay attribute
rather than using script to force the video to play, so
as to allow the user to override the behavior if so
desired.
In any case, the user agent must finally queue a task to
fire a simple event named canplaythrough at the element.
It is possible for the ready state of a media element to jump between
these states discontinuously. For example, the state of a media element
can jump straight from HAVE_METADATA to HAVE_ENOUGH_DATA without passing
through the HAVE_CURRENT_DATA and HAVE_FUTURE_DATA states.
The readyState IDL attribute must, on getting, return the value described
above that describes the current ready state of the media element.
The autoplay attribute is a boolean attribute. When present, the user
agent (as described in the algorithm described herein) will automatically
begin playback of the media resource as soon as it can do so without
stopping.
Authors are urged to use the autoplay attribute rather than using script
to trigger automatic playback, as this allows the user to override the
automatic playback when it is not desired, e.g., when using a screen
reader. Authors are also encouraged to consider not using the automatic
playback behavior at all, and instead to let the user agent wait for the
user to start playback explicitly.
The autoplay IDL attribute must reflect the content attribute of the same
name.
4.7.13.8. Playing the media resource
media . paused
Returns true if playback is paused; false otherwise.
media . ended
Returns true if playback has reached the end of the media
resource.
media . defaultPlaybackRate [ = value ]
Returns the default rate of playback, for when the user is not
fast-forwarding or reversing through the media resource.
Can be set, to change the default rate of playback.
The default rate has no direct effect on playback, but if the user
switches to a fast-forward mode, when they return to the normal
playback mode, it is expected that the rate of playback will be
returned to the default rate of playback.
media . playbackRate [ = value ]
Returns the current rate playback, where 1.0 is normal speed.
Can be set, to change the rate of playback.
media . played
Returns a TimeRanges object that represents the ranges of the
media resource that the user agent has played.
media . play()
Sets the paused attribute to false, loading the media resource and
beginning playback if necessary. If the playback had ended, will
restart it from the start.
media . pause()
Sets the paused attribute to true, loading the media resource if
necessary.
The paused attribute represents whether the media element is paused or
not. The attribute must initially be true.
A media element is a blocked media element if its readyState attribute is
in the HAVE_NOTHING state, the HAVE_METADATA state, or the
HAVE_CURRENT_DATA state, or if the element has paused for user interaction
or paused for in-band content.
A media element is said to be potentially playing when its paused
attribute is false, the element has not ended playback, playback has not
stopped due to errors, and the element is not a blocked media element.
A waiting DOM event can be fired as a result of an element that is
potentially playing stopping playback due to its readyState attribute
changing to a value lower than HAVE_FUTURE_DATA.
A media element is said to have ended playback when:
* The element’s readyState attribute is HAVE_METADATA or greater, and
* Either:
* The current playback position is the end of the media resource,
and
* The direction of playback is forwards, and
* The media element does not have a loop attribute specified.
Or:
* The current playback position is the earliest possible position,
and
* The direction of playback is backwards.
The ended attribute must return true if, the last time the event loop
reached step 1, the media element had ended playback and the direction of
playback was forwards, and false otherwise.
A media element is said to have stopped due to errors when the element’s
readyState attribute is HAVE_METADATA or greater, and the user agent
encounters a non-fatal error during the processing of the media data, and
due to that error, is not able to play the content at the current playback
position.
A media element is said to have paused for user interaction when its
paused attribute is false, the readyState attribute is either
HAVE_FUTURE_DATA or HAVE_ENOUGH_DATA and the user agent has reached a
point in the media resource where the user has to make a selection for the
resource to continue.
It is possible for a media element to have both ended playback and paused
for user interaction at the same time.
When a media element that is potentially playing stops playing because it
has paused for user interaction, the user agent must queue a task to fire
a simple event named timeupdate at the element.
A media element is said to have paused for in-band content when its paused
attribute is false, the readyState attribute is either HAVE_FUTURE_DATA or
HAVE_ENOUGH_DATA and the user agent has suspended playback of the media
resource in order to play content that is temporally anchored to the media
resource and has a non-zero length, or to play content that is temporally
anchored to a segment of the media resource but has a length longer than
that segment.
One example of when a media element would be paused for in-band content is
when the user agent is playing audio descriptions from an external WebVTT
file, and the synthesized speech generated for a cue is longer than the
time between the text track cue start time and the text track cue end
time.
----------------------------------------------------------------------
When the current playback position reaches the end of the media resource
when the direction of playback is forwards, then the user agent must
follow these steps:
1. If the media element has a loop attribute specified, then seek to the
earliest possible position of the media resource and abort these
steps.
2. As defined above, the ended IDL attribute starts returning true once
the event loop returns to step 1.
3. Queue a task to fire a simple event named timeupdate at the media
element.
4. Queue a task that, if the media element has still ended playback, and
the direction of playback is still forwards, and paused is false,
changes paused to true and fires a simple event named pause at the
media element.
5. Queue a task to fire a simple event named ended at the media element.
When the current playback position reaches the earliest possible position
of the media resource when the direction of playback is backwards, then
the user agent must only queue a task to fire a simple event named
timeupdate at the element.
The word "reaches" here does not imply that the current playback position
needs to have changed during normal playback; it could be via seeking, for
instance.
----------------------------------------------------------------------
The defaultPlaybackRate attribute gives the desired speed at which the
media resource is to play, as a multiple of its intrinsic speed. The
attribute is mutable: on getting it must return the last value it was set
to, or 1.0 if it hasn’t yet been set; on setting the attribute must be set
to the new value.
The defaultPlaybackRate is used by the user agent when it exposes a user
interface to the user.
The playbackRate attribute gives the effective playback rate which is the
speed at which the media resource plays, as a multiple of its intrinsic
speed. If it is not equal to the defaultPlaybackRate, then the implication
is that the user is using a feature such as fast forward or slow motion
playback. The attribute is mutable: on getting it must return the last
value it was set to, or 1.0 if it hasn’t yet been set; on setting the
attribute must be set to the new value, and the playback will change speed
(if the element is potentially playing).
When the defaultPlaybackRate or playbackRate attributes change value
(either by being set by script or by being changed directly by the user
agent, e.g., in response to user control) the user agent must queue a task
to fire a simple event named ratechange at the media element.
----------------------------------------------------------------------
The played attribute must return a new static normalized TimeRanges object
that represents the ranges of points on the media timeline of the media
resource reached through the usual monotonic increase of the current
playback position during normal playback, if any, at the time the
attribute is evaluated.
----------------------------------------------------------------------
When the play() method on a media element is invoked, the user agent must
run the following steps.
1. If the media element’s networkState attribute has the value
NETWORK_EMPTY, invoke the media element’s resource selection
algorithm.
2. If the playback has ended and the direction of playback is forwards,
seek to the earliest possible position of the media resource.
This will cause the user agent to queue a task to fire a simple event
named timeupdate at the media element.
3. If the media element’s paused attribute is true, run the following
substeps:
1. Change the value of paused to false.
2. If the show poster flag is true, set the element’s show poster
flag to false and run the time marches on steps.
3. Queue a task to fire a simple event named play at the element.
4. If the media element’s readyState attribute has the value
HAVE_NOTHING, HAVE_METADATA, or HAVE_CURRENT_DATA, queue a task
to fire a simple event named waiting at the element.
Otherwise, the media element’s readyState attribute has the value
HAVE_FUTURE_DATA or HAVE_ENOUGH_DATA: queue a task to fire a
simple event named playing at the element.
4. Set the media element’s autoplaying flag to false.
----------------------------------------------------------------------
When the pause() method is invoked, and when the user agent is required to
pause the media element, the user agent must run the following steps:
1. If the media element’s networkState attribute has the value
NETWORK_EMPTY, invoke the media element’s resource selection
algorithm.
2. Run the internal pause steps for the media element.
The internal pause steps for a media element are as follows:
1. Set the media element’s autoplaying flag to false.
2. If the media element’s paused attribute is false, run the following
steps:
1. Change the value of paused to true.
2. Queue a task to fire a simple event named timeupdate at the
element.
3. Queue a task to fire a simple event named pause at the element.
4. Set the official playback position to the current playback
position.
----------------------------------------------------------------------
The effective playback rate is just the element’s playbackRate.
If the effective playback rate is positive or zero, then the direction of
playback is forwards. Otherwise, it is backwards.
When a media element is potentially playing and its Document is a fully
active Document, its current playback position must increase monotonically
at effective playback rate units of media time per unit time of the media
timeline’s clock. (This specification always refers to this as an
increase, but that increase could actually be a decrease if the effective
playback rate is negative.)
The effective playback rate can be 0.0, in which case the current playback
position doesn’t move, despite playback not being paused (paused doesn’t
become true, and the pause event doesn’t fire).
This specification doesn’t define how the user agent achieves the
appropriate playback rate — depending on the protocol and media available,
it is plausible that the user agent could negotiate with the server to
have the server provide the media data at the appropriate rate, so that
(except for the period between when the rate is changed and when the
server updates the stream’s playback rate) the client doesn’t actually
have to drop or interpolate any frames.
Any time the user agent provides a stable state, the official playback
position must be set to the current playback position.
While the direction of playback is backwards, any corresponding audio must
be muted. While the effective playback rate is so low or so high that the
user agent cannot play audio usefully, the corresponding audio must also
be muted. If the effective playback rate is not 1.0, the user agent may
apply pitch adjustments to the audio as necessary to render it faithfully.
Media elements that are potentially playing while not in a Document must
not play any video, but should play any audio component. Media elements
must not stop playing just because all references to them have been
removed; only once a media element is in a state where no further audio
could ever be played by that element may the element be garbage collected.
It is possible for an element to which no explicit references exist to
play audio, even if such an element is not still actively playing: for
instance, a media element whose media resource has no audio tracks could
eventually play audio again if it had an event listener that changes the
media resource.
----------------------------------------------------------------------
Each media element has a list of newly introduced cues, which must be
initially empty. Whenever a text track cue is added to the list of cues of
a text track that is in the list of text tracks for a media element, that
cue must be added to the media element’s list of newly introduced cues.
Whenever a text track is added to the list of text tracks for a media
element, all of the cues in that text track’s list of cues must be added
to the media element’s list of newly introduced cues. When a media
element’s list of newly introduced cues has new cues added while the media
element’s show poster flag is not set, then the user agent must run the
time marches on steps.
When a text track cue is removed from the list of cues of a text track
that is in the list of text tracks for a media element, and whenever a
text track is removed from the list of text tracks of a media element, if
the media element’s show poster flag is not set, then the user agent must
run the time marches on steps.
When the current playback position of a media element changes (e.g., due
to playback or seeking), the user agent must run the time marches on
steps. If the current playback position changes while the steps are
running, then the user agent must wait for the steps to complete, and then
must immediately rerun the steps. (These steps are thus run as often as
possible or needed — if one iteration takes a long time, this can cause
certain cues to be skipped over as the user agent rushes ahead to "catch
up".)
The time marches on steps are as follows:
1. Let current cues be a list of cues, initialized to contain all the
cues of all the hidden or showing text tracks of the media element
(not the disabled ones) whose start times are less than or equal to
the current playback position and whose end times are greater than the
current playback position.
2. Let other cues be a list of cues, initialized to contain all the cues
of hidden and showing text tracks of the media element that are not
present in current cues.
3. Let last time be the current playback position at the time this
algorithm was last run for this media element, if this is not the
first time it has run.
4. If the current playback position has, since the last time this
algorithm was run, only changed through its usual monotonic increase
during normal playback, then let missed cues be the list of cues in
other cues whose start times are greater than or equal to last time
and whose end times are less than or equal to the current playback
position. Otherwise, let missed cues be an empty list.
5. Remove all the cues in missed cues that are also in the media
element’s list of newly introduced cues, and then empty the element’s
list of newly introduced cues.
6. If the time was reached through the usual monotonic increase of the
current playback position during normal playback, and if the user
agent has not fired a timeupdate event at the element in the past 15
to 250ms and is not still running event handlers for such an event,
then the user agent must queue a task to fire a simple event named
timeupdate at the element. (In the other cases, such as explicit
seeks, relevant events get fired as part of the overall process of
changing the current playback position.)
The event thus is not to be fired faster than about 66Hz or slower
than 4Hz (assuming the event handlers don’t take longer than 250ms to
run). User agents are encouraged to vary the frequency of the event
based on the system load and the average cost of processing the event
each time, so that the UI updates are not any more frequent than the
user agent can comfortably handle while decoding the video.
7. If all of the cues in current cues have their text track cue active
flag set, none of the cues in other cues have their text track cue
active flag set, and missed cues is empty, then abort these steps.
8. If the time was reached through the usual monotonic increase of the
current playback position during normal playback, and there are cues
in other cues that have their text track cue pause-on-exit flag set
and that either have their text track cue active flag set or are also
in missed cues, then immediately pause the media element.
In the other cases, such as explicit seeks, playback is not paused by
going past the end time of a cue, even if that cue has its text track
cue pause-on-exit flag set.
9. Let events be a list of tasks, initially empty. Each task in this list
will be associated with a text track, a text track cue, and a time,
which are used to sort the list before the tasks are queued.
Let affected tracks be a list of text tracks, initially empty.
When the steps below say to prepare an event named event for a text
track cue target with a time time, the user agent must run these
substeps:
1. Let track be the text track with which the text track cue target
is associated.
2. Create a task to fire a simple event named event at target.
3. Add the newly created task to events, associated with the time
time, the text track track, and the text track cue target.
4. Add track to affected tracks.
10. For each text track cue in missed cues, prepare an event named enter
for the TextTrackCue object with the text track cue start time.
11. For each text track cue in other cues that either has its text track
cue active flag set or is in missed cues, prepare an event named exit
for the TextTrackCue object with the later of the text track cue end
time and the text track cue start time.
12. For each text track cue in current cues that does not have its text
track cue active flag set, prepare an event named enter for the
TextTrackCue object with the text track cue start time.
13. Sort the tasks in events in ascending time order (tasks with earlier
times first).
Further sort tasks in events that have the same time by the relative
text track cue order of the text track cues associated with these
tasks.
Finally, sort tasks in events that have the same time and same text
track cue order by placing tasks that fire enter events before those
that fire exit events.
14. Queue each task in events, in list order.
15. Sort affected tracks in the same order as the text tracks appear in
the media element’s list of text tracks, and remove duplicates.
16. For each text track in affected tracks, in the list order, queue a
task to fire a simple event named cuechange at the TextTrack object,
and, if the text track has a corresponding track element, to then fire
a simple event named cuechange at the track element as well.
17. Set the text track cue active flag of all the cues in the current
cues, and unset the text track cue active flag of all the cues in the
other cues.
18. Run the rules for updating the text track rendering of each of the
text tracks in affected tracks that are showing, providing the text
track’s text track language as the fallback language if it is not the
empty string. For example, for text tracks based on WebVTT, the rules
for updating the display of WebVTT text tracks. [WEBVTT]
For the purposes of the algorithm above, a text track cue is considered to
be part of a text track only if it is listed in the text track list of
cues, not merely if it is associated with the text track.
If the media element’s node document stops being a fully active document,
then the playback will stop until the document is active again.
When a media element is removed from a Document, the user agent must run
the following steps:
1. Await a stable state, allowing the task that removed the media element
from the Document to continue. The synchronous section consists of all
the remaining steps of this algorithm. (Steps in the synchronous
section are marked with ⌛.)
2. ⌛ If the media element is in a Document, abort these steps.
3. ⌛ Run the internal pause steps for the media element.
4.7.13.9. Seeking
media . seeking
Returns true if the user agent is currently seeking.
media . seekable
Returns a TimeRanges object that represents the ranges of the
media resource to which it is possible for the user agent to seek.
media . fastSeek( time )
Seeks to near the given time as fast as possible, trading
precision for speed. (To seek to a precise time, use the
currentTime attribute.)
This does nothing if the media resource has not been loaded.
The seeking attribute must initially have the value false.
The fastSeek() method must seek to the time given by the method’s
argument, with the approximate-for-speed flag set.
When the user agent is required to seek to a particular new playback
position in the media resource, optionally with the approximate-for-speed
flag set, it means that the user agent must run the following steps. This
algorithm interacts closely with the event loop mechanism; in particular,
it has a synchronous section (which is triggered as part of the event loop
algorithm). Steps in that section are marked with ⌛.
1. Set the media element’s show poster flag to false.
2. If the media element’s readyState is HAVE_NOTHING, abort these steps.
3. If the element’s seeking IDL attribute is true, then another instance
of this algorithm is already running. Abort that other instance of the
algorithm without waiting for the step that it is running to complete.
4. Set the seeking IDL attribute to true.
5. If the seek was in response to a DOM method call or setting of an IDL
attribute, then continue the script. The remainder of these steps must
be run in parallel. With the exception of the steps marked with ⌛,
they could be aborted at any time by another instance of this
algorithm being invoked.
6. If the new playback position is later than the end of the media
resource, then let it be the end of the media resource instead.
7. If the new playback position is less than the earliest possible
position, let it be that position instead.
8. If the (possibly now changed) new playback position is not in one of
the ranges given in the seekable attribute, then let it be the
position in one of the ranges given in the seekable attribute that is
the nearest to the new playback position. If two positions both
satisfy that constraint (i.e., the new playback position is exactly in
the middle between two ranges in the seekable attribute) then use the
position that is closest to the current playback position. If there
are no ranges given in the seekable attribute then set the seeking IDL
attribute to false and abort these steps.
9. If the approximate-for-speed flag is set, adjust the new playback
position to a value that will allow for playback to resume promptly.
If new playback position before this step is before current playback
position, then the adjusted new playback position must also be before
the current playback position. Similarly, if the new playback position
before this step is after current playback position, then the adjusted
new playback position must also be after the current playback
position.
For example, the user agent could snap to a nearby key frame, so that
it doesn’t have to spend time decoding then discarding intermediate
frames before resuming playback.
10. Queue a task to fire a simple event named seeking at the element.
11. Set the current playback position to the new playback position.
If the media element was potentially playing immediately before it
started seeking, but seeking caused its readyState attribute to change
to a value lower than HAVE_FUTURE_DATA, then a waiting event will be
fired at the element.
This step sets the current playback position, and thus can immediately
trigger other conditions, such as the rules regarding when playback
"reaches the end of the media resource" (part of the logic that
handles looping), even before the user agent is actually able to
render the media data for that position (as determined in the next
step).
The currentTime attribute returns the official playback position, not
the current playback position, and therefore gets updated before
script execution, separate from this algorithm.
12. Wait until the user agent has established whether or not the media
data for the new playback position is available, and, if it is, until
it has decoded enough data to play back that position.
13. Await a stable state. The synchronous section consists of all the
remaining steps of this algorithm. (Steps in the synchronous section
are marked with ⌛.)
14. ⌛ Set the seeking IDL attribute to false.
15. ⌛ Run the time marches on steps.
16. ⌛ Queue a task to fire a simple event named timeupdate at the element.
17. ⌛ Queue a task to fire a simple event named seeked at the element.
----------------------------------------------------------------------
The seekable attribute must return a new static normalized TimeRanges
object that represents the ranges of the media resource, if any, that the
user agent is able to seek to, at the time the attribute is evaluated.
If the user agent can seek to anywhere in the media resource, e.g.,
because it is a simple movie file and the user agent and the server
support HTTP Range requests, then the attribute would return an object
with one range, whose start is the time of the first frame (the earliest
possible position, typically zero), and whose end is the time of the last
frame.
The range might be continuously changing, e.g., if the user agent is
buffering a sliding window on an infinite stream. This is the behavior
seen with DVRs viewing live TV, for instance.
User agents should adopt a very liberal and optimistic view of what is
seekable. User agents should also buffer recent content where possible to
enable seeking to be fast.
For instance, consider a large video file served on an HTTP server without
support for HTTP Range requests. A browser could implement this by only
buffering the current frame and data obtained for subsequent frames, never
allow seeking, except for seeking to the very start by restarting the
playback. However, this would be a poor implementation. A high quality
implementation would buffer the last few minutes of content (or more, if
sufficient storage space is available), allowing the user to jump back and
rewatch something surprizing without any latency, and would in addition
allow arbitrary seeking by reloading the file from the start if necessary,
which would be slower but still more convenient than having to literally
restart the video and watch it all the way through just to get to an
earlier unbuffered spot.
Media resources might be internally scripted or interactive. Thus, a media
element could play in a non-linear fashion. If this happens, the user
agent must act as if the algorithm for seeking was used whenever the
current playback position changes in a discontinuous fashion (so that the
relevant events fire).
4.7.13.10. Media resources with multiple media tracks
A media resource can have multiple embedded audio and video tracks. For
example, in addition to the primary video and audio tracks, a media
resource could have foreign-language dubbed dialogs, director’s
commentaries, audio descriptions, alternative angles, or sign-language
overlays.
media . audioTracks
Returns an AudioTrackList object representing the audio tracks
available in the media resource.
media . videoTracks
Returns a VideoTrackList object representing the video tracks
available in the media resource.
The audioTracks attribute of a media element must return a live
AudioTrackList object representing the audio tracks available in the media
element’s media resource.
The videoTracks attribute of a media element must return a live
VideoTrackList object representing the video tracks available in the media
element’s media resource.
There are only ever one AudioTrackList object and one VideoTrackList
object per media element, even if another media resource is loaded into
the element: the objects are reused. (The AudioTrack and VideoTrack
objects are not, though.)
In this example, a script defines a function that takes a URL to a video
and a reference to an element where the video is to be placed. That
function then tries to load the video, and, once it is loaded, checks to
see if there is a sign-language track available. If there is, it also
displays that track. Both tracks are just placed in the given container;
it’s assumed that styles have been applied to make this work in a pretty
way!
4.7.13.10.1. AudioTrackList and VideoTrackList objects
The AudioTrackList and VideoTrackList interfaces are used by attributes
defined in the previous section.
interface AudioTrackList : EventTarget {
readonly attribute unsigned long length;
getter AudioTrack (unsigned long index);
AudioTrack? getTrackById(DOMString id);
attribute EventHandler onchange;
attribute EventHandler onaddtrack;
attribute EventHandler onremovetrack;
};
interface AudioTrack {
readonly attribute DOMString id;
readonly attribute DOMString kind;
readonly attribute DOMString label;
readonly attribute DOMString language;
attribute boolean enabled;
};
interface VideoTrackList : EventTarget {
readonly attribute unsigned long length;
getter VideoTrack (unsigned long index);
VideoTrack? getTrackById(DOMString id);
readonly attribute long selectedIndex;
attribute EventHandler onchange;
attribute EventHandler onaddtrack;
attribute EventHandler onremovetrack;
};
interface VideoTrack {
readonly attribute DOMString id;
readonly attribute DOMString kind;
readonly attribute DOMString label;
readonly attribute DOMString language;
attribute boolean selected;
};
media . audioTracks . length
media . videoTracks . length
Returns the number of tracks in the list.
audioTrack = media . audioTracks[index]
videoTrack = media . videoTracks[index]
Returns the specified AudioTrack or VideoTrack object.
audioTrack = media . audioTracks . getTrackById( id )
videoTrack = media . videoTracks . getTrackById( id )
Returns the AudioTrack or VideoTrack object with the given
identifier, or null if no track has that identifier.
audioTrack . id
videoTrack . id
Returns the ID of the given track. This is the ID that can be used
with a fragment if the format supports the media fragments syntax,
and that can be used with the getTrackById() method. [MEDIA-FRAGS]
audioTrack . kind
videoTrack . kind
Returns the category the given track falls into. The possible
track categories are given below.
audioTrack . label
videoTrack . label
Returns the label of the given track, if known, or the empty
string otherwise.
audioTrack . language
videoTrack . language
Returns the language of the given track, if known, or the empty
string otherwise.
audioTrack . enabled [ = value ]
Returns true if the given track is active, and false otherwise.
Can be set, to change whether the track is enabled or not. If
multiple audio tracks are enabled simultaneously, they are mixed.
media . videoTracks . selectedIndex
Returns the index of the currently selected track, if any, or -1
otherwise.
videoTrack . selected [ = value ]
Returns true if the given track is active, and false otherwise.
Can be set, to change whether the track is selected or not. Either
zero or one video track is selected; selecting a new track while a
previous one is selected will unselect the previous one.
An AudioTrackList object represents a dynamic list of zero or more audio
tracks, of which zero or more can be enabled at a time. Each audio track
is represented by an AudioTrack object.
A VideoTrackList object represents a dynamic list of zero or more video
tracks, of which zero or one can be selected at a time. Each video track
is represented by a VideoTrack object.
Tracks in AudioTrackList and VideoTrackList objects must be consistently
ordered. If the media resource is in a format that defines an order, then
that order must be used; otherwise, the order must be the relative order
in which the tracks are declared in the media resource. The order used is
called the natural order of the list.
Each track in one of these objects thus has an index; the first has the
index 0, and each subsequent track is numbered one higher than the
previous one. If a media resource dynamically adds or removes audio or
video tracks, then the indices of the tracks will change dynamically. If
the media resource changes entirely, then all the previous tracks will be
removed and replaced with new tracks.
The AudioTrackList.length and VideoTrackList.length attributes must return
the number of tracks represented by their objects at the time of getting.
The supported property indices of AudioTrackList and VideoTrackList
objects at any instant are the numbers from zero to the number of tracks
represented by the respective object minus one, if any tracks are
represented. If an AudioTrackList or VideoTrackList object represents no
tracks, it has no supported property indices.
To determine the value of an indexed property for a given index index in
an AudioTrackList or VideoTrackList object list, the user agent must
return the AudioTrack or VideoTrack object that represents the indexth
track in list.
The AudioTrackList.getTrackById(id) and VideoTrackList.getTrackById(id)
methods must return the first AudioTrack or VideoTrack object
(respectively) in the AudioTrackList or VideoTrackList object
(respectively) whose identifier is equal to the value of the id argument
(in the natural order of the list, as defined above). When no tracks match
the given argument, the methods must return null.
The AudioTrack and VideoTrack objects represent specific tracks of a media
resource. Each track can have an identifier, category, label, and
language. These aspects of a track are permanent for the lifetime of the
track; even if a track is removed from a media resource’s AudioTrackList
or VideoTrackList objects, those aspects do not change.
In addition, AudioTrack objects can each be enabled or disabled; this is
the audio track’s enabled state. When an AudioTrack is created, its
enabled state must be set to false (disabled). The resource fetch
algorithm can override this.
Similarly, a single VideoTrack object per VideoTrackList object can be
selected, this is the video track’s selection state. When a VideoTrack is
created, its selection state must be set to false (not selected). The
resource fetch algorithm can override this.
The AudioTrack.id and VideoTrack.id attributes must return the identifier
of the track, if it has one, or the empty string otherwise. If the media
resource is in a format that supports the Media Fragments URI fragment
identifier syntax, the identifier returned for a particular track must be
the same identifier that would enable the track if used as the name of a
track in the track dimension of such a fragment identifier. [MEDIA-FRAGS]
[INBANDTRACKS]
For example, in Ogg files, this would be the Name header field of the
track. [OGGSKELETON]
The AudioTrack.kind and VideoTrack.kind attributes must return the
category of the track, if it has one, or the empty string otherwise.
The category of a track is the string given in the first column of the
table below that is the most appropriate for the track based on the
definitions in the table’s second and third columns, as determined by the
metadata included in the track in the media resource. The cell in the
third column of a row says what the category given in the cell in the
first column of that row applies to; a category is only appropriate for an
audio track if it applies to audio tracks, and a category is only
appropriate for video tracks if it applies to video tracks. Categories
must only be returned for AudioTrack objects if they are appropriate for
audio, and must only be returned for VideoTrack objects if they are
appropriate for video.
Return values for AudioTrack.kind and VideoTrack.kind
Category Definition Applies to...
A possible alternative to the main
"alternative" track, e.g., a different take of a song Audio and video.
(audio), or a different angle (video).
A version of the main video track with
"captions" captions burnt in. (For legacy content; Video only.
new content would use text tracks.)
"descriptions" An audio description of a video track. Audio only.
"main" The primary audio or video track. Audio and video.
"main-desc" The primary audio track, mixed with Audio only.
audio descriptions.
"sign" A sign-language interpretation of an Video only.
audio track.
A version of the main video track with
"subtitles" subtitles burnt in. (For legacy Video only.
content; new content would use text
tracks.)
"translation" A translated version of the main audio Audio only.
track.
Commentary on the primary audio or
"commentary" video track, e.g., a director’s Audio and video.
commentary.
No explicit kind, or the kind given by
"" (empty string) the track’s metadata is not recognized Audio and video.
by the user agent.
The AudioTrack.label and VideoTrack.label attributes must return the label
of the track, if it has one, or the empty string otherwise. [INBANDTRACKS]
The AudioTrack.language and VideoTrack.language attributes must return the
BCP 47 language tag of the language of the track, if it has one, or the
empty string otherwise. If the user agent is not able to express that
language as a BCP 47 language tag (for example because the language
information in the media resource’s format is a free-form string without a
defined interpretation), then the method must return the empty string, as
if the track had no language.
Source attribute values for id, kind, label and language of multitrack
audio and video tracks as described for the relevant media resource
format. [INBANDTRACKS]
The AudioTrack.enabled attribute, on getting, must return true if the
track is currently enabled, and false otherwise. On setting, it must
enable the track if the new value is true, and disable it otherwise. (If
the track is no longer in an AudioTrackList object, then the track being
enabled or disabled has no effect beyond changing the value of the
attribute on the AudioTrack object.)
Whenever an audio track in an AudioTrackList that was disabled is enabled,
and whenever one that was enabled is disabled, the user agent must queue a
task to fire a simple event named change at the AudioTrackList object.
An audio track that has no data for a particular position on the media
timeline, or that does not exist at that position, must be interpreted as
being silent at that point on the timeline.
The VideoTrackList.selectedIndex attribute must return the index of the
currently selected track, if any. If the VideoTrackList object does not
currently represent any tracks, or if none of the tracks are selected, it
must instead return -1.
The VideoTrack.selected attribute, on getting, must return true if the
track is currently selected, and false otherwise. On setting, it must
select the track if the new value is true, and unselect it otherwise. If
the track is in a VideoTrackList, then all the other VideoTrack objects in
that list must be unselected. (If the track is no longer in a
VideoTrackList object, then the track being selected or unselected has no
effect beyond changing the value of the attribute on the VideoTrack
object.)
Whenever a track in a VideoTrackList that was previously not selected is
selected, and whenever the selected track in a VideoTrackList is
unselected without a new track being selected in its stead, the user agent
must queue a task to fire a simple event named change at the
VideoTrackList object. This task must be queued before the task that fires
the resize event, if any.
A video track that has no data for a particular position on the media
timeline must be interpreted as being fully transparent black at that
point on the timeline, with the same dimensions as the last frame before
that position, or, if the position is before all the data for that track,
the same dimensions as the first frame for that track. A track that does
not exist at all at the current position must be treated as if it existed
but had no data.
For instance, if a video has a track that is only introduced after one
hour of playback, and the user selects that track then goes back to the
start, then the user agent will act as if that track started at the start
of the media resource but was simply transparent until one hour in.
----------------------------------------------------------------------
The following are the event handlers (and their corresponding event
handler event types) that must be supported, as event handler IDL
attributes, by all objects implementing the AudioTrackList and
VideoTrackList interfaces:
Event handler Event handler event type
onchange change
onaddtrack addtrack
onremovetrack removetrack
4.7.13.10.2. Selecting specific audio and video tracks declaratively
The audioTracks and videoTracks attributes allow scripts to select which
track should play, but it is also possible to select specific tracks
declaratively, by specifying particular tracks in the fragment of the URL
of the media resource. The format of the fragment depends on the MIME type
of the media resource. [RFC2046] [URL]
In this example, a video that uses a format that supports the media
fragments syntax is embedded in such a way that the alternative angles
labeled "Alternative" are enabled instead of the default video track.
[MEDIA-FRAGS]
Babies™: Toys
Toys
...
4.7.15. The area element
Categories:
Flow content.
Phrasing content.
Contexts in which this element can be used:
Where phrasing content is expected, but only if there is a map
element ancestor or a template element ancestor.
Content model:
Nothing.
Tag omission in text/html:
No end tag
Content attributes:
Global attributes
alt - Replacement text for use when images are not available
coords - Coordinates for the shape to be created in an image map
download - Whether to download the resource instead of navigating
to it, and its file name if so
href - Address of the hyperlink
hreflang - Language of the linked resource
rel - Relationship of this document (or subsection/topic) to the
destination resource
shape - The kind of shape to be created in an image map
target - browsing context for hyperlink navigation
type - Hint for the type of the referenced resource
referrerpolicy - Referrer policy for fetches initiated by the
element
Allowed ARIA role attribute values:
link role (default - do not set).
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
interface HTMLAreaElement : HTMLElement {
attribute DOMString alt;
attribute DOMString coords;
attribute DOMString shape;
attribute DOMString target;
attribute DOMString download;
attribute DOMString rel;
[SameObject, PutForwards=value] readonly attribute DOMTokenList relList;
attribute DOMString hreflang;
attribute DOMString type;
attribute DOMString referrerPolicy;
};
HTMLAreaElement implements HTMLHyperlinkElementUtils;
The area element represents either a hyperlink with some text and a
corresponding area on an image map, or a dead area on an image map.
An area element with a parent node must have a map element ancestor or a
template element ancestor.
If the area element has an href attribute, then the area element
represents a hyperlink. In this case, the alt attribute must be present.
It specifies the text of the hyperlink. Its value must be text that
informs the user about the destination of the link.
If the area element has no href attribute, then the area represented by
the element cannot be selected, and the alt attribute must be omitted.
In both cases, the shape and coords attributes specify the area.
The shape attribute is an enumerated attribute. The following table lists
the keywords defined for this attribute. The states given in the first
cell of the rows with keywords give the states to which those keywords
map. Some of the keywords are non-conforming, as noted in the last column.
State Keywords Notes
Circle state circle
circ Non-conforming
Default state default
Polygon state poly
polygon Non-conforming
Rectangle state rect
rectangle Non-conforming
The attribute may be omitted. The missing value default is the rectangle
state.
The coords attribute must, if specified, contain a valid list of
floating-point numbers. This attribute gives the coordinates for the shape
described by the shape attribute. The processing for this attribute is
described as part of the image map processing model.
In the circle state, area elements must have a coords attribute present,
with three integers, the last of which must be non-negative. The first
integer must be the distance in CSS pixels from the left edge of the image
to the center of the circle, the second integer must be the distance in
CSS pixels from the top edge of the image to the center of the circle, and
the third integer must be the radius of the circle, again in CSS pixels.
In the default state state, area elements must not have a coords
attribute. (The area is the whole image.)
In the polygon state, area elements must have a coords attribute with at
least six integers, and the number of integers must be even. Each pair of
integers must represent a coordinate given as the distances from the left
and the top of the image in CSS pixels respectively, and all the
coordinates together must represent the points of the polygon, in order.
In the rectangle state, area elements must have a coords attribute with
exactly four integers, the first of which must be less than the third, and
the second of which must be less than the fourth. The four points must
represent, respectively, the distance from the left edge of the image to
the left side of the rectangle, the distance from the top edge to the top
side, the distance from the left edge to the right side, and the distance
from the top edge to the bottom side, all in CSS pixels.
When user agents allow users to follow hyperlinks or download hyperlinks
created using the area element, as described in the next section, the
href, target, and download attributes decide how the link is followed. The
rel, and hreflang attributes may be used to indicate to the user the
likely nature of the target resource before the user follows the link.
The target, download, rel, hreflang, type, and referrerpolicy attributes
must be omitted if the href attribute is not present.
The activation behavior of area elements is to run the following steps:
1. If the area element’s node document is not fully active, then abort
these steps.
2. If the area element has a download attribute and the algorithm is not
allowed to show a popup; or, if the user has not indicated a specific
browsing context for following the link, and the element’s target
attribute is present, and applying the rules for choosing a browsing
context given a browsing context name, using the value of the target
attribute as the browsing context name, would result in there not
being a chosen browsing context, then run these substeps:
1. If there is an entry settings object, throw an InvalidAccessError
exception.
2. Abort these steps without following the hyperlink.
3. Otherwise, the user agent must follow the hyperlink or download the
hyperlink created by the area element, if any, and as determined by
the download attribute and any expressed user preference.
The IDL attributes alt, coords, target, download, rel, and hreflang, each
must reflect the respective content attributes of the same name.
The IDL attribute shape must reflect the shape content attribute.
The IDL attribute relList must reflect the rel content attribute.
The IDL attribute referrerPolicy must reflect the referrerpolicy content
attribute, limited to only known values.
----------------------------------------------------------------------
The area element also supports the HTMLHyperlinkElementUtils interface.
[URL]
When the element is created, and whenever the element’s href content
attribute is set, changed, or removed, the user agent must invoke the
element’s HTMLHyperlinkElementUtils interface’s set the input algorithm
with the value of the href content attribute, if any, or the empty string
otherwise, as the given value.
The element’s HTMLHyperlinkElementUtils interface’s get the base algorithm
must simply return the document base URL.
The element’s HTMLHyperlinkElementUtils interface’s query encoding is the
document’s character encoding.
When the element’s HTMLHyperlinkElementUtils interface invokes its update
steps with a string value, the user agent must set the element’s href
content attribute to the string value.
4.7.16. Image maps
4.7.16.1. Authoring
An image map allows geometric areas on an image to be associated with
hyperlinks.
An image, in the form of an img element, may be associated with an image
map (in the form of a map element) by specifying a usemap attribute on the
img element. The usemap attribute, if specified, must be a valid hash-name
reference to a map element.
Consider an image that looks as follows:
A line with four shapes in it, equally spaced: a red hollow box, a green
circle, a blue triangle, and a yellow four-pointed star.
If we wanted just the colored areas to be clickable, we could do it as
follows:
Please select a shape:
4.7.16.2. Processing model
If an img element has a usemap attribute specified, user agents must
process it as follows:
1. Parse the attribute’s value using the rules for parsing a hash-name
reference to a map element, with the element’s node document as the
context node. This will return either an element (the map) or null.
2. If that returned null, then abort these steps. The image is not
associated with an image map after all.
3. Otherwise, the user agent must collect all the area elements that are
descendants of the map. Let those be the areas.
Having obtained the list of area elements that form the image map (the
areas), interactive user agents must process the list in one of two ways.
If the user agent intends to show the text that the img element
represents, then it must use the following steps.
In user agents that do not support images, or that have images disabled,
object elements cannot represent images, and thus this section never
applies (the fallback content is shown instead). The following steps
therefore only apply to img elements.
1. Remove all the area elements in areas that have no href attribute.
2. Remove all the area elements in areas that have no alt attribute, or
whose alt attribute’s value is the empty string, if there is another
area element in areas with the same value in the href attribute and
with a non-empty alt attribute.
3. Each remaining area element in areas represents a hyperlink. Those
hyperlinks should all be made available to the user in a manner
associated with the text of the img.
In this context, user agents may represent area and img elements with
no specified alt attributes, or whose alt attributes are the empty
string or some other non-visible text, in a user-agent-defined fashion
intended to indicate the lack of suitable author-provided text.
If the user agent intends to show the image and allow interaction with the
image to select hyperlinks, then the image must be associated with a set
of layered shapes, taken from the area elements in areas, in reverse tree
order (so the last specified area element in the map is the bottom-most
shape, and the first element in the map, in tree order, is the top-most
shape).
Each area element in areas must be processed as follows to obtain a shape
to layer onto the image:
1. Find the state that the element’s shape attribute represents.
2. Use the rules for parsing a list of floating-point numbers to parse
the element’s coords attribute, if it is present, and let the result
be the coords list. If the attribute is absent, let the coords list be
the empty list.
3. If the number of items in the coords list is less than the minimum
number given for the area element’s current state, as per the
following table, then the shape is empty; abort these steps.
State Minimum number of items
Circle state 3
Default state 0
Polygon state 6
Rectangle state 4
4. Check for excess items in the coords list as per the entry in the
following list corresponding to the shape attribute’s state:
Circle state
Drop any items in the list beyond the third.
Default state
Drop all items in the list.
Polygon state
Drop the last item if there’s an odd number of items.
Rectangle state
Drop any items in the list beyond the fourth.
5. If the shape attribute represents the rectangle state, and the first
number in the list is numerically greater than the third number in the
list, then swap those two numbers around.
6. If the shape attribute represents the rectangle state, and the second
number in the list is numerically greater than the fourth number in
the list, then swap those two numbers around.
7. If the shape attribute represents the circle state, and the third
number in the list is less than or equal to zero, then the shape is
empty; abort these steps.
8. Now, the shape represented by the element is the one described for the
entry in the list below corresponding to the state of the shape
attribute:
Circle state
Let x be the first number in coords, y be the second
number, and r be the third number.
The shape is a circle whose center is x CSS pixels from
the left edge of the image and y CSS pixels from the top
edge of the image, and whose radius is r CSS pixels.
Default state
The shape is a rectangle that exactly covers the entire
image.
Polygon state
Let x_i be the (2i)th entry in coords, and y_i be the
(2i+1)th entry in coords (the first entry in coords being
the one with index 0).
Let the coordinates be (x_i, y_i), interpreted in CSS
pixels measured from the top left of the image, for all
integer values of i from 0 to (N/2)-1, where N is the
number of items in coords.
The shape is a polygon whose vertices are given by the
coordinates, and whose interior is established using the
even-odd rule. [GRAPHICS]
Rectangle state
Let x_1 be the first number in coords, y_1 be the second
number, x_2 be the third number, and y_2 be the fourth
number.
The shape is a rectangle whose top-left corner is given
by the coordinate (x_1, y_1) and whose bottom right
corner is given by the coordinate (x_2, y_2), those
coordinates being interpreted as CSS pixels from the top
left corner of the image.
For historical reasons, the coordinates must be interpreted relative
to the displayed image after any stretching caused by the CSS width
and height properties (or, for non-CSS browsers, the image element’s
width and height attributes — CSS browsers map those attributes to the
aforementioned CSS properties).
Browser zoom features and transforms applied using CSS or SVG do not
affect the coordinates.
Pointing device interaction with an image associated with a set of layered
shapes per the above algorithm must result in the relevant user
interaction events being first fired to the top-most shape covering the
point that the pointing device indicated, if any, or to the image element
itself, if there is no shape covering that point. User agents should make
area elements representing hyperlinks focusable, to ensure that they can
be selected and activated by all users.
Because a map element (and its area elements) can be associated with
multiple img and object elements, it is possible for an area element to
correspond to multiple focusable areas of the document.
Image maps are live; if the DOM is mutated, then the user agent must act
as if it had rerun the algorithms for image maps.
4.7.17. MathML
The MathML math element falls into the embedded content, phrasing content,
flow content, and palpable content categories for the purposes of the
content models in this specification.
When the MathML annotation-xml element contains elements from the HTML
namespace, such elements must all be flow content.
When the MathML token elements (MathML mi, MathML mo, MathML mn, MathML
ms, and MathML mtext) are descendants of HTML elements, they may contain
phrasing content elements from the HTML namespace. [MATHML]
User agents must handle text other than inter-element white space found in
MathML elements whose content models do not allow straight text by
pretending for the purposes of MathML content models, layout, and
rendering that the text is actually wrapped in an MathML mtext element in
the MathML namespace. (Such text is not, however, conforming.)
User agents must act as if any MathML element whose contents does not
match the element’s content model was replaced, for the purposes of MathML
layout and rendering, by an MathML merror element containing some
appropriate error message.
To enable authors to use MathML tools that only accept MathML in its XML
form, interactive HTML user agents are encouraged to provide a way to
export any MathML fragment as an XML namespace-well-formed XML fragment.
The semantics of MathML elements are defined by the MathML specification
and other applicable specifications. [MATHML]
Here is an example of the use of MathML in an HTML document:
The quadratic formula
The quadratic formula
x
=
- b
±
b 2
-
4 a c
2 a
4.7.18. SVG
The SVG svg element falls into the embedded content, phrasing content,
flow content, and palpable content categories for the purposes of the
content models in this specification.
To enable authors to use SVG tools that only accept SVG in its XML form,
interactive HTML user agents are encouraged to provide a way to export any
SVG fragment as an XML namespace-well-formed XML fragment.
When the SVG foreignObject element contains elements from the HTML
namespace, such elements must all be flow content. [SVG11]
The content model for SVG title elements inside HTML documents is phrasing
content. (This further constrains the requirements given in the SVG
specification.)
The semantics of SVG elements are defined by the SVG specification and
other applicable specifications. [SVG11]
4.7.19. Dimension attributes
Author requirements: The width and height attributes on img, iframe,
embed, object, video, and, when their type attribute is in the Image
Button state, input elements may be specified to give the dimensions of
the visual content of the element (the width and height respectively,
relative to the nominal direction of the output medium), in CSS pixels.
The attributes, if specified, must have values that are valid non-negative
integers.
The specified dimensions given may differ from the dimensions specified in
the resource itself, since the resource may have a resolution that differs
from the CSS pixel resolution. (On screens, CSS pixels have a resolution
of 96ppi, but in general the CSS pixel resolution depends on the reading
distance.) If both attributes are specified, then one of the following
statements must be true:
* specified width - 0.5 ≤ specified height * target ratio ≤ specified
width + 0.5
* specified height - 0.5 ≤ specified width / target ratio ≤ specified
height + 0.5
* specified height = specified width = 0
The target ratio is the ratio of the intrinsic width to the intrinsic
height in the resource. The specified width and specified height are the
values of the width and height attributes respectively.
The two attributes must be omitted if the resource in question does not
have both an intrinsic width and an intrinsic height.
If the two attributes are both zero, it indicates that the element is not
intended for the user (e.g., it might be a part of a service to count page
views).
The dimension attributes are not intended to be used to stretch the image.
User agent requirements: User agents are expected to use these attributes
as hints for the rendering.
The width and height IDL attributes on the iframe, embed, object, and
video elements must reflect the respective content attributes of the same
name.
For iframe, embed, and object the IDL attributes are DOMString; for video
the IDL attributes are unsigned long.
The corresponding IDL attributes for img and input elements are defined in
those respective elements' sections, as they are slightly more specific to
those elements' other behaviors.
4.8. Links
4.8.1. Introduction
Links are a conceptual construct, created by a, area, and link elements,
that represent a connection between two resources, one of which is the
current Document. There are two kinds of links in HTML:
Links to external resources
These are links to resources that are to be used to augment the
current document, generally automatically processed by the user
agent.
Hyperlinks
These are links to other resources that are generally exposed to
the user by the user agent so that the user can cause the user
agent to navigate to those resources, e.g., to visit them in a
browser or download them.
For link elements with an href attribute and a rel attribute, links must
be created for the keywords of the rel attribute, as defined for those
keywords in the link types section.
Similarly, for a and area elements with an href attribute and a rel
attribute, links must be created for the keywords of the rel attribute as
defined for those keywords in the link types section. Unlike link
elements, however, a and area elements with an href attribute that either
do not have a rel attribute, or whose rel attribute has no keywords that
are defined as specifying hyperlinks, must also create a hyperlink. This
implied hyperlink has no special meaning (it has no link type) beyond
linking the element’s node document to the resource given by the element’s
href attribute.
A hyperlink can have one or more hyperlink annotations that modify the
processing semantics of that hyperlink.
4.8.2. Links created by a and area elements
The href attribute on a and area elements must have a value that is a
valid URL potentially surrounded by spaces.
The href attribute on a and area elements is not required; when those
elements do not have href attributes they do not create hyperlinks.
The target attribute, if present, must be a valid browsing context name or
keyword. It gives the name of the browsing context that will be used. User
agents use this name when following hyperlinks.
When an a or area element’s activation behavior is invoked, the user agent
may allow the user to indicate a preference regarding whether the
hyperlink is to be used for navigation or whether the resource it
specifies is to be downloaded.
In the absence of a user preference, the default should be navigation if
the element has no download attribute, and should be to download the
specified resource if it does.
Whether determined by the user’s preferences or via the presence or
absence of the attribute, if the decision is to use the hyperlink for
navigation then the user agent must follow the hyperlink, and if the
decision is to use the hyperlink to download a resource, the user agent
must download the hyperlink. These terms are defined in subsequent
sections below.
The download attribute, if present, indicates that the author intends the
hyperlink to be used for downloading a resource. The attribute may have a
value; the value, if any, specifies the default file name that the author
recommends for use in labeling the resource in a local file system. There
are no restrictions on allowed values, but authors are cautioned that most
file systems have limitations with regard to what punctuation is supported
in file names, and user agents are likely to adjust file names
accordingly.
The rel attribute on a and area elements controls what kinds of links the
elements create. The attribute’s value must be a set of space-separated
tokens. The allowed keywords and their meanings are defined below.
rel's supported tokens are the keywords defined in HTML link types which
are allowed on a and area elements, impact the processing model, and are
supported by the user agent. The possible supported tokens are noreferrer,
and noopener. rel's supported tokens must only include the tokens from
this list that the user agent implements the processing model for.
Other specifications may add HTML link types as defined in Other link
types, with the following additional requirements:
* Such specifications may require that their link types be included in
rel's supported tokens.
* Such specifications may specify that their link types are body-ok.
The rel attribute has no default value. If the attribute is omitted or if
none of the values in the attribute are recognized by the user agent, then
the document has no particular relationship with the destination resource
other than there being a hyperlink between the two.
link and a elements may also have a rev attribute, which is used to
describe a reverse link relationship from the resource specified by the
href to the current document. If present, the value of this attribute must
be a set of space-separated tokens. Like the rel attribute, §4.8.6 Link
types describes the allowed keywords and their meanings for the rev
attribute. Both the rel and rev attributes may be present on the same
element.
Reverse links are a way to express the reverse directional relationship of
a link. In contrast to the rel attribute, whose value conveys a forward
directional relationship ("how is the link related to me"), the rev
attribute allows for similiar relationships to be expressed in the reverse
direction ("how am I related to this link"). These values can enable user
agents to build a more comprehensive map of linked documents.
Given two documents, each containing a chapter of a book, the links
between them could be described with the rel and rev attributes as
follows:
Document with URL "chapter1.html"
chapter 1
From the table of contents, the "next" logical path is to the first
chapter, expressed using rel. Each chapter link has a "toc" rev value
which indicates that the current document is the table of contents
document for every chapter.
The hreflang attribute on a elements that create hyperlinks, if present,
gives the language of the linked resource. It is purely advisory. The
value must be a valid BCP 47 language tag. [BCP47] User agents must not
consider this attribute authoritative — upon fetching the resource, user
agents must use only language information associated with the resource to
determine its language, not metadata included in the link to the resource.
The type attribute, if present, gives the MIME type of the linked
resource. It is purely advisory. The value must be a valid mime type. User
agents must not consider the type attribute authoritative — upon fetching
the resource, user agents must not use metadata included in the link to
the resource to determine its type.
The referrerpolicy attribute is a referrer policy attribute. Its purpose
is to set the referrer policy used when following hyperlinks.
[REFERRERPOLICY]
4.8.3. API for a and area elements
[NoInterfaceObject]
interface HTMLHyperlinkElementUtils {
stringifier attribute USVString href;
readonly attribute USVString origin;
attribute USVString protocol;
attribute USVString username;
attribute USVString password;
attribute USVString host;
attribute USVString hostname;
attribute USVString port;
attribute USVString pathname;
attribute USVString search;
attribute USVString hash;
};
hyperlink . toString()
hyperlink . href
Returns the hyperlink’s URL.
Can be set, to change the URL.
hyperlink . origin
Returns the hyperlink’s URL’s origin.
hyperlink . protocol
Returns the hyperlink’s URL’s scheme.
Can be set, to change the URL’s scheme.
hyperlink . username
Returns the hyperlink’s URL’s username.
Can be set, to change the URL’s username.
hyperlink . password
Returns the hyperlink’s URL’s password.
Can be set, to change the URL’s password.
hyperlink . host
Returns the hyperlink’s URL’s host and port (if different from the
default port for the scheme).
Can be set, to change the URL’s host and port.
hyperlink . hostname
Returns the hyperlink’s URL’s host.
Can be set, to change the URL’s host.
hyperlink . port
Returns the hyperlink’s URL’s port.
Can be set, to change the URL’s port.
hyperlink . pathname
Returns the hyperlink’s URL’s path.
Can be set, to change the URL’s path.
hyperlink . search
Returns the hyperlink’s URL’s query (includes leading "?" if
non-empty).
Can be set, to change the URL’s query (ignores leading "?").
hyperlink . hash
Returns the hyperlink’s URL’s fragment (includes leading "#" if
non-empty).
Can be set, to change the URL’s fragment (ignores leading "#").
An element implementing the HTMLHyperlinkElementUtils mixin has an
associated url (null or a URL). It is initially null.
An element implementing the HTMLHyperlinkElementUtils mixin has an
associated set the url algorithm, which sets this element’s URL to the
resulting URL string of parsing this element’s href content attribute
value relative to this element. If parsing was aborted with an error, set
this element’s URL to null.
When elements implementing the HTMLHyperlinkElementUtils mixin are
created, and whenever those elements have their href content attribute
set, changed, or removed, the user agent must set the url.
This is only observable for blob: URLs as parsing them involves the
StructuredSerialize abstract operation.
An element implementing the HTMLHyperlinkElementUtils mixin has an
associated reinitialise url algorithm, which runs these steps:
1. If element’s URL is non-null, its scheme is "blob", and its
non-relative flag is set, terminate these steps.
2. Set the url.
To update href, set the element’s href content attribute’s value to the
element’s URL, serialized.
----------------------------------------------------------------------
The href attribute’s getter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url is null and this element has no href content attribute, return
the empty string.
4. Otherwise, if url is null, return this element’s href content
attribute’s value.
5. Return url, serialized.
The href attribute’s setter must set this element’s href content
attribute’s value to the given value.
The origin attribute’s getter must run these steps:
1. Reinitialise url.
2. If this element’s URL is null, return the empty string.
3. Return the Unicode serialization of this element’s URL's origin.
It returns the Unicode rather than the ASCII serialization for
compatibility with MessageEvent.
The protocol attribute’s getter must run these steps:
1. Reinitialise url.
2. If this element’s URL is null, return "
:".
3. Return this element’s URL's scheme, followed by ":".
The protocol attribute’s setter must run these steps:
1. Reinitialise url.
2. If this element’s URL is null, terminate these steps.
3. Basic URL parse the given value, followed by :", with this element’s
URL as url and scheme start state as state override.
4. Update href.
The username attribute’s getter must run these steps:
1. Reinitialise url.
2. If this element’s URL is null, return the empty string.
3. Return this element’s URL's username.
The username attribute’s setter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url or url’s host is null, or url’s non-relative flag is set,
terminate these steps.
4. set the username, given url and the given value.
5. Update href.
The password attribute’s getter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url or url’s password is null, return the empty string.
4. Return url’s password.
The password attribute’s setter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url or url’s host is null, or url’s non-relative flag is set,
terminate these steps.
4. Set the password, given url and the given value.
5. Update href.
The host attribute’s getter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url or url’s host is null, return the empty string.
4. If url’s port is null, return url’s host, serialized.
5. Return url’s host, serialized, followed by ":" and url’s port,
serialized.
The host attribute’s setter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url is null or url’s non-relative flag is set, terminate these
steps.
4. Basic URL parse the given value, with url as url and host state as
state override.
5. Update href.
The hostname attribute’s getter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url or url’s host is null, return the empty string.
4. Return url’s host, serialized.
The hostname attribute’s setter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url is null or url’s non-relative flag is set, terminate these
steps.
4. Basic URL parse the given value, with url as url and hostname state as
state override.
5. Update href.
The port attribute’s getter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url or url’s port is null, return the empty string.
4. Return url’s port, serialized.
The port attribute’s setter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url or url’s host is null, url’s non-relative flag is set, or url’s
scheme is "file", terminate these steps.
4. Basic URL parse the given value, with url as url and port state as
state override.
5. Update href.
The pathname attribute’s getter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url is null, return the empty string.
4. If url’s non-relative flag is set, return the first string in url’s
path.
5. Return "/", followed by the strings in url’s path (including empty
strings), separated from each other by "/".
The pathname attribute’s setter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url is null or url’s non-relative flag is set, terminate these
steps.
4. Set url’s path to the empty list.
5. Basic URL parse the given value, with url as url and path start state
as state override.
6. Update href.
The search attribute’s getter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url is null, or url’s query is either null or the empty string,
return the empty string.
4. Return "?", followed by url’s query.
The search attribute’s setter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url is null, terminate these steps.
4. If the given value is the empty string, set url’s query to null.
5. Otherwise, run these substeps:
1. Let input be the given value with a single leading "?" removed,
if any.
2. Set url’s query to the empty string.
3. Basic URL parse input, with url as url and query state as state
override, and this element’s node document’s document’s character
encoding as encoding override.
6. Update href.
The hash attribute’s getter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url is null, or url’s fragment is either null or the empty string,
return the empty string.
4. Return "#", followed by url’s fragment.
The hash attribute’s setter must run these steps:
1. Reinitialise url.
2. Let url be this element’s URL.
3. If url is null or url’s scheme is "javascript", terminate these steps.
4. If the given value is the empty string, set url’s fragment to null.
5. Otherwise, run these substeps:
1. Let input be the given value with a single leading "#" removed,
if any.
2. Set url’s fragment to the empty string.
3. Basic URL parse input, with url as url and fragment state as
state override.
6. Update href.
4.8.4. Following hyperlinks
When a user follows a hyperlink created by an element subject, optionally
with a hyperlink suffix, the user agent must run the following steps:
1. Let replace be false.
2. Let source be the browsing context that contains the Document object
with which subject in question is associated.
3. If the user indicated a specific browsing context when following the
hyperlink, or if the user agent is configured to follow hyperlinks by
navigating a particular browsing context, then let target be that
browsing context. If this is a new top-level browsing context (e.g.,
when the user followed the hyperlink using "Open in New Tab"), then
source must be set as the new browsing context’s one permitted
sandboxed navigator.
Otherwise, if subject is an a or area element that has a target
attribute, then let target be the browsing context that is chosen by
applying the rules for choosing a browsing context given a browsing
context name, using the value of the target attribute as the browsing
context name. If these rules result in the creation of a new browsing
context, set replace to true.
Otherwise, if target is an a or area element with no target attribute,
but the Document contains a base element with a target attribute, then
let target be the browsing context that is chosen by applying the
rules for choosing a browsing context given a browsing context name,
using the value of the target attribute of the first such base element
as the browsing context name. If these rules result in the creation of
a new browsing context, set replace to true.
Otherwise, let target be the browsing context that subject itself is
in.
4. If subject’s link types include the noreferrer or noopener keyword,
and replace is true, then disown target’s opener.
5. Parse the URL given by subject’s href attribute, relative to subject’s
node document.
6. If that is successful, let URL be the resulting URL string.
Otherwise, if parsing the URL failed, the user agent may report the
error to the user in a user-agent-specific manner, may queue a task to
navigate the target browsing context to an error page to report the
error, or may ignore the error and do nothing. In any case, the user
agent must then abort these steps.
7. If there is a hyperlink suffix, append it to URL.
8. Let resource be a new request whose url is URL and whose referrer
policy is the current state of subject’s referrerpolicy content
attribute.
9. Queue a task to navigate the target browsing context to resource. If
replace is true, the navigation must be performed with replacement
enabled. The source browsing context must be source.
The task source for the tasks mentioned above is the DOM manipulation task
source.
4.8.5. Downloading resources
In some cases, resources are intended for later use rather than immediate
viewing. To indicate that a resource is intended to be downloaded for use
later, rather than immediately used, the download attribute can be
specified on the a or area element that creates the hyperlink to that
resource.
The attribute can furthermore be given a value, to specify the file name
that user agents are to use when storing the resource in a file system.
This value can be overridden by the Content-Disposition HTTP header’s
filename parameters. [RFC6266]
In cross-origin situations, the download attribute has to be combined with
the Content-Disposition HTTP header, specifically with the attachment
disposition type, to avoid the user being warned of possibly nefarious
activity. (This is to protect users from being made to download sensitive
personal or confidential information without their full understanding.)
----------------------------------------------------------------------
When a user downloads a hyperlink created by an element subject,
optionally with a hyperlink suffix, the user agent must run the following
steps:
1. Parse the URL given by subject’s href attribute, relative to subject.
2. If parsing the URL fails, the user agent may report the error to the
user in a user-agent-specific manner, may navigate to an error page to
report the error, or may ignore the error and do nothing. In either
case, the user agent must abort these steps.
3. Otherwise, let URL be the resulting URL string.
4. If there is a hyperlink suffix, append it to URL.
5. Return to whatever algorithm invoked these steps and continue these
steps in parallel.
6. Fetch URL and handle the resulting resource as a download.
When a user agent is to handle a resource obtained from a fetch as a
download, it should provide the user with a way to save the resource for
later use, if a resource is successfully obtained; or otherwise should
report any problems downloading the file to the user.
If the user agent needs a file name for a resource being handled as a
download, it should select one using the following algorithm.
This algorithm is intended to mitigate security dangers involved in
downloading files from untrusted sites, and user agents are strongly urged
to follow it.
1. Let filename be the void value.
2. If the resource has a Content-Disposition header, that header
specifies the attachment disposition type, and the header includes
file name information, then let filename have the value specified by
the header, and jump to the step labeled sanitize below. [RFC6266]
3. Let interface origin be the origin of the Document in which the
download or navigate action resulting in the download was initiated,
if any.
4. Let resource origin be the origin of the URL of the resource being
downloaded, unless that URL’s scheme component is data, in which case
let resource origin be the same as the interface origin, if any.
5. If there is no interface origin, then let trusted operation be true.
Otherwise, let trusted operation be true if resource origin is the
same origin as interface origin, and false otherwise.
6. If trusted operation is true and the resource has a
Content-Disposition header and that header includes file name
information, then let filename have the value specified by the header,
and jump to the step labeled sanitize below. [RFC6266]
7. If the download was not initiated from a hyperlink created by an a or
area element, or if the element of the hyperlink from which it was
initiated did not have a download attribute when the download was
initiated, or if there was such an attribute but its value when the
download was initiated was the empty string, then jump to the step
labeled no proposed file name.
8. Let proposed filename have the value of the download attribute of the
element of the hyperlink that initiated the download at the time the
download was initiated.
9. If trusted operation is true, let filename have the value of proposed
filename, and jump to the step labeled sanitize below.
10. If the resource has a Content-Disposition header and that header
specifies the attachment disposition type, let filename have the value
of proposed filename, and jump to the step labeled sanitize below.
[RFC6266]
11. No proposed file name: If trusted operation is true, or if the user
indicated a preference for having the resource in question downloaded,
let filename have a value derived from the URL of the resource in a
user-agent-defined manner, and jump to the step labeled sanitize
below.
12. Act in a user-agent-defined manner to safeguard the user from a
potentially hostile cross-origin download. If the download is not to
be aborted, then let filename be set to the user’s preferred file name
or to a file name selected by the user agent, and jump to the step
labeled sanitize below.
If the algorithm reaches this step, then a download was begun from a
different origin than the resource being downloaded, and the origin
did not mark the file as suitable for downloading, and the download
was not initiated by the user. This could be because a download
attribute was used to trigger the download, or because the resource in
question is not of a type that the user agent supports.
This could be dangerous, because, for instance, a hostile server could
be trying to get a user to unknowingly download private information
and then re-upload it to the hostile server, by tricking the user into
thinking the data is from the hostile server.
Thus, it is in the user’s interests that the user be somehow notified
that the resource in question comes from quite a different source, and
to prevent confusion, any suggested file name from the potentially
hostile interface origin should be ignored.
13. Sanitize: Optionally, allow the user to influence filename. For
example, a user agent could prompt the user for a file name,
potentially providing the value of filename as determined above as a
default value.
14. Adjust filename to be suitable for the local file system.
For example, this could involve removing characters that are not legal
in file names, or trimming leading and trailing white space.
15. If the platform conventions do not in any way use extensions to
determine the types of file on the file system, then return filename
as the file name and abort these steps.
16. Let claimed type be the type given by the resource’s Content-Type
metadata, if any is known. Let named type be the type given by
filename’s extension, if any is known. For the purposes of this step,
a type is a mapping of a MIME type to an extension.
17. If named type is consistent with the user’s preferences (e.g., because
the value of filename was determined by prompting the user), then
return filename as the file name and abort these steps.
18. If claimed type and named type are the same type (i.e., the type given
by the resource’s Content-Type metadata is consistent with the type
given by filename’s extension), then return filename as the file name
and abort these steps.
19. If the claimed type is known, then alter filename to add an extension
corresponding to claimed type.
Otherwise, if named type is known to be potentially dangerous (e.g.,
it will be treated by the platform conventions as a native executable,
shell script, HTML application, or executable-macro-capable document)
then optionally alter filename to add a known-safe extension (e.g.,
".txt").
This last step would make it impossible to download executables, which
might not be desirable. As always, implementors are forced to balance
security and usability in this matter.
20. Return filename as the file name.
For the purposes of this algorithm, a file extension consists of any part
of the file name that platform conventions dictate will be used for
identifying the type of the file. For example, many operating systems use
the part of the file name following the last dot (".") in the file name to
determine the type of the file, and from that the manner in which the file
is to be opened or executed.
User agents should ignore any directory or path information provided by
the resource itself, its URL, and any download attribute, in deciding
where to store the resulting file in the user’s file system.
4.8.6. Link types
The following table summarizes the link types that are defined by this
specification, by their coresponding keywords. This table is
non-normative; the actual definitions for the link types are given in the
next few sections.
In this section, the term referenced document refers to the resource
identified by the element representing the link, and the term current
document refers to the resource within which the element representing the
link finds itself.
To determine which link types apply to a link, a, or area element, the
element’s rel attribute must be split on spaces. The resulting tokens are
the keywords for the link types that apply to that element.
Except where otherwise specified, a keyword must not be specified more
than once per rel attribute.
Some of the sections that follow the table below list synonyms for certain
keywords. The indicated synonyms are to be handled as specified by user
agents, but must not be used in documents (for example, the keyword
"copyright").
Keywords are always ASCII case-insensitive, and must be compared as such.
Thus, rel="next" is the same as rel="NEXT".
Keywords that are body-ok affect whether link elements are allowed in the
body. The body-ok keyword defined by this specification is stylesheet.
Other specifications can also define body-ok keywords.
Link type Effect on... body-ok Brief description
link a and area
Gives alternate
alternate hyperlink hyperlink · representations of the current
document.
Gives a link to the author of
author hyperlink hyperlink · the current document or
article.
bookmark not allowed hyperlink · Gives the permalink for the
nearest ancestor section.
Indicates that the referenced
external not allowed Annotation · document is not part of the
same site as the current
document.
help hyperlink hyperlink · Provides a link to
context-sensitive help.
icon External not allowed · Imports an icon to represent
Resource the current document.
Indicates that the main
content of the current
license hyperlink hyperlink · document is covered by the
copyright license described by
the referenced document.
Indicates that the current
document is a part of a
next hyperlink hyperlink · series, and that the next
document in the series is the
referenced document.
Indicates that the current
nofollow not allowed Annotation · document’s original author or
publisher does not endorse the
referenced document.
Requires that any browsing
noopener not allowed Annotation · context created by following
the hyperlink to disown its
opener.
Requires that the user agent
noreferrer not allowed Annotation · not send an HTTP Referer (sic)
header if the user follows the
hyperlink.
Indicates that the current
document is a part of a
prev hyperlink hyperlink · series, and that the previous
document in the series is the
referenced document.
Gives a link to a resource
search hyperlink hyperlink · that can be used to search
through the current document
and its related pages.
stylesheet External not allowed Yes Imports a stylesheet.
Resource
Gives a tag (identified by the
tag not allowed hyperlink · given address) that applies to
the current document.
4.8.6.1. Link type "alternate"
The alternate keyword may be used with link, a, and area elements.
The meaning of this keyword depends on the values of the other attributes.
If the element is a link element and the rel attribute also contains the
keyword stylesheet
The alternate keyword modifies the meaning of the stylesheet
keyword in the way described for that keyword. The alternate
keyword does not create a link of its own.
Here, a set of link elements provide some style sheets:
You can access the planets database using Atom feeds:
Otherwise
The keyword creates a hyperlink referencing an alternate
representation of the current document.
The nature of the referenced document is given by the hreflang,
and type attributes.
If the alternate keyword is used with the hreflang attribute, and
that attribute’s value differs from the document element’s
language, it indicates that the referenced document is a
translation.
If the alternate keyword is used with the type attribute, it
indicates that the referenced document is a reformulation of the
current document in the specified format.
The hreflang and type attributes can be combined when specified
with the alternate keyword.
The following example shows how you can specify versions of the
page that use alternative formats, are aimed at other languages,
and that are intended for other media:
Example of permalinks
Second example
This permalink applies to
the outer ARTICLE element (which could be, e.g., a blog post).
This permalink applies to
the inner ARTICLE element (which could be, e.g., a blog comment).
...
4.8.6.4. Link type "help"
The help keyword may be used with link, a, and area elements. This keyword
creates a hyperlink.
For a and area elements, the help keyword indicates that the referenced
document provides further help information for the parent of the element
defining the hyperlink, and its children.
In the following example, the form control has associated
context-sensitive help. The user agent could use this information, for
example, displaying the referenced document if the user presses the "Help"
or "F1" key.
Topic: (Help)
For link elements, the help keyword indicates that the referenced document
provides help for the page as a whole.
For a and area elements, on some browsers, the help keyword causes the
link to use a different cursor.
4.8.6.5. Link type "icon"
The icon keyword may be used with link elements. This keyword creates an
external resource link.
The specified resource is an icon representing the page or site, and
should be used by the user agent when representing the page in the user
interface.
Icons could be auditory icons, visual icons, or other kinds of icons. If
multiple icons are provided, the user agent must select the most
appropriate icon according to the type, media, and sizes attributes. If
there are multiple equally appropriate icons, user agents must use the
last one declared in tree order at the time that the user agent collected
the list of icons. If the user agent tries to use an icon but that icon is
determined, upon closer examination, to in fact be inappropriate (e.g.,
because it uses an unsupported format), then the user agent must try the
next-most-appropriate icon as determined by the attributes.
User agents are not required to update icons when the list of icons
changes, but are encouraged to do so.
There is no default type for resources given by the icon keyword. However,
for the purposes of determining the type of the resource, user agents must
expect the resource to be an image.
The sizes keyword represent icon sizes in raw pixels (as opposed to CSS
pixels).
An icon that is 50 CSS pixels wide intended for displays with a device
pixel density of two device pixels per CSS pixel (2x, 192dpi) would have a
width of 100 raw pixels. This feature does not support indicating that a
different resource is to be used for small high-resolution icons vs large
low-resolution icons (e.g., 50×50 2x vs 100×100 1x).
To parse and process the attribute’s value, the user agent must first
split the attribute’s value on spaces, and must then parse each resulting
keyword to determine what it represents.
The any keyword represents that the resource contains a scalable icon,
e.g., as provided by an SVG image.
Other keywords must be further parsed as follows to determine what they
represent:
* If the keyword doesn’t contain exactly one U+0078 LATIN SMALL LETTER X
or U+0058 LATIN CAPITAL LETTER X character, then this keyword doesn’t
represent anything. Abort these steps for that keyword.
* Let width string be the string before the "x" or "X".
* Let height string be the string after the "x" or "X".
* If either width string or height string start with a U+0030 DIGIT ZERO
(0) character or contain any characters other than ASCII digits, then
this keyword doesn’t represent anything. Abort these steps for that
keyword.
* Apply the rules for parsing non-negative integers to width string to
obtain width.
* Apply the rules for parsing non-negative integers to height string to
obtain height.
* The keyword represents that the resource contains a bitmap icon with a
width of width device pixels and a height of height device pixels.
The keywords specified on the sizes attribute must not represent icon
sizes that are not actually available in the linked resource.
In the absence of a link with the icon keyword, for Document objects
obtained over HTTP or HTTPS, user agents may instead run these steps in
parallel:
1. Let request be a new request whose URL is the absolute URL obtained by
resolving the URL "/favicon.ico" against the document’s URL, client is
the Document object’s Window object’s environment settings object,
type is "image", destination is "subresource", synchronous flag is
set, credentials mode is "include", and whose use-URL-credentials flag
is set.
2. Let response be the result of fetching request.
3. Use response’s unsafe response as an icon as if it had been declared
using the icon keyword.
The following snippet shows the top part of an application with several
icons.
lsForums — Inbox
Exampl Pictures: Kissat
Kissat
Return to photo index
Kissat
One of them has six toes!
This photograph is MIT Licensed
In this case the license applies to just the photo (the main content of
the document), not the whole document. In particular not the design of the
page itself, which is covered by the copyright given at the bottom of the
document. This should be made clear in the text referencing the licensing
link and could also be made clearer in the styling (e.g., making the
license link prominently positioned near the photograph, while having the
page copyright in small text at the foot of the page, or adding a border
to the main element.)
Synonyms: For historical reasons, user agents must also treat the keyword
"copyright" like the license keyword.
4.8.6.7. Link type "nofollow"
The nofollow keyword may be used with a and area elements. This keyword
does not create a hyperlink, but annotates any other hyperlinks created by
the element (the implied hyperlink, if no other keywords create one).
The nofollow keyword indicates that the link is not endorsed by the
original author or publisher of the page, or that the link to the
referenced document was included primarily because of a commercial
relationship between people affiliated with the two pages.
4.8.6.8. Link type "noopener"
The noopener keyword may be used with a and area elements. This keyword
does not create a hyperlink, but annotates any other hyperlinks created by
the element (the implied hyperlink, if no other keywords create one).
The keyword indicates that any newly created browsing context which
results from following the hyperlink will have disowned its opener, which
means that its window.opener property will be null.
4.8.6.9. Link type "noreferrer"
The noreferrer keyword may be used with a and area elements. This keyword
does not create a hyperlink, but annotates any other hyperlinks created by
the element (the implied hyperlink, if no other keywords create one).
It indicates that no referrer information is to be leaked when following
the link.
If a user agent follows a link defined by an a or area element that has
the noreferrer keyword, the user agent must set their request’s referrer
to "no-referrer".
For historical reasons, the noreferrer keyword implies the behavior
associated with the noopener keyword when present on a hyperlink that
creates a new browsing context. That is, has the same behavior as .
4.8.6.10. Link type "search"
The search keyword may be used with link, a, and area elements. This
keyword creates a hyperlink.
The search keyword indicates that the referenced document provides an
interface specifically for searching the document and its related
resources.
OpenSearch description documents can be used with link elements and the
search link type to enable user agents to autodiscover search interfaces.
[OPENSEARCH]
4.8.6.11. Link type "stylesheet"
The stylesheet keyword may be used with link elements. This keyword
creates an external resource link that contributes to the styling
processing model. This keyword is body-ok.
The specified resource is a resource that describes how to present the
document. Exactly how the resource is to be processed depends on the
actual type of the resource.
If the alternate keyword is also specified on the link element, then the
link is an alternative stylesheet; in this case, the title attribute must
be specified on the link element, with a non-empty value.
The default type for resources given by the stylesheet keyword is
text/css.
The appropriate times to obtain the resource are:
* When the external resource link is created on a link element that is
already in a Document.
* When the external resource link’s link element is inserted into a
document.
* When the href attribute of the link element of an external resource
link that is already in a Document is changed.
* When the crossorigin attribute of the link element of an external
resource link that is already in a Document is set, changed, or
removed.
* When the type attribute of the link element of an external resource
link that is already in a Document is set or changed to a value that
does not or no longer matches the Content-Type metadata of the
previous obtained external resource, if any.
* When the type attribute of the link element of an external resource
link that is already in a Document but was previously not obtained due
to the type attribute specifying an unsupported type is set, removed,
or changed.
* When the external resource link changes from being an alternative
stylesheet to not being one, or vice versa.
Quirk: If the document has been set to quirks mode, has the same origin as
the URL of the external resource, and the Content-Type metadata of the
external resource is not a supported style sheet type, the user agent must
instead assume it to be text/css.
Once a resource has been obtained, if its Content-Type metadata is
text/css, the user agent must run these steps:
1. Let element be the link element that created the external resource
link.
2. If element has an associated CSS style sheet, remove the CSS style
sheet in question.
3. If element no longer creates an external resource link that
contributes to the styling processing model, or if, since the resource
in question was obtained, it has become appropriate to obtain it again
(meaning this algorithm is about to be invoked again for a newly
obtained resource), then abort these steps.
4. Create a CSS style sheet with the following properties:
type
text/css
location
The resulting URL string determined during the obtain
algorithm.
This is before any redirects get applied.
owner node
element
media
The media attribute of element.
This is a reference to the (possibly absent at this time)
attribute, rather than a copy of the attribute’s current
value. The CSSOM specification defines what happens when
the attribute is dynamically set, changed, or removed.
title
The title attribute of element.
This is similarly a reference to the attribute, rather
than a copy of the attribute’s current value.
alternate flag
Set if the link is an alternative stylesheet; unset
otherwise.
origin-clean flag
Set if the resource is CORS-same-origin; unset otherwise.
parent CSS style sheet
owner CSS rule
null
disabled flag
Left at its default value.
CSS rules
Left uninitialized.
The CSS environment encoding is the result of running the following
steps: [CSS-SYNTAX-3]
1. If the element has a charset attribute, get an encoding from that
attribute’s value. If that succeeds, return the resulting
encoding and abort these steps. [ENCODING]
2. Otherwise, return the document’s character encoding. [DOM41]
4.8.6.12. Link type "tag"
The tag keyword may be used with a and area elements. This keyword creates
a hyperlink.
The tag keyword indicates that the tag that the referenced document
represents applies to the current document.
Since it indicates that the tag applies to the current document, it would
be inappropriate to use this keyword in the markup of a tag cloud, which
lists the popular tags across a set of pages.
This document is about some gems, and so it is tagged with
"https://en.wikipedia.org/wiki/Gemstone" to unambiguously categorize it as
applying to the "jewel" kind of gems, and not to, say, the towns in the
US, the Ruby package format, or the Swiss locomotive class:
My Precious
Recently I managed to dispose of a red gem that had been
bothering me. I now have a much nicer blue sapphire.
The red gem had been found in a bauxite stone while I was digging
out the office level, but nobody was willing to haul it away. The
same red gem stayed there for literally years.
In this document, there are two articles. The "tag" link, however, applies
to the whole page (and would do so wherever it was placed, including if it
was within the article elements).
Gem 4/4
801: Steinbock
The number 801 Gem 4/4 electro-diesel has an ibex and was rebuilt in 2002.
802: Murmeltier
The 802 in the 1980s, above Lago Bianco.
The number 802 Gem 4/4 electro-diesel has a marmot and was rebuilt in 2003.
Gem 4/4
4.8.6.13. Sequential link types
Some documents form part of a sequence of documents.
A sequence of documents is one where each document can have a previous
sibling and a next sibling. A document with no previous sibling is the
start of its sequence, a document with no next sibling is the end of its
sequence.
A document may be part of multiple sequences.
4.8.6.13.1. Link type "next"
The next keyword may be used with link, a, and area elements. This keyword
creates a hyperlink.
The next keyword indicates that the document is part of a sequence, and
that the link is leading to the document that is the next logical document
in the sequence.
4.8.6.13.2. Link type "prev"
The prev keyword may be used with link, a, and area elements. This keyword
creates a hyperlink.
The prev keyword indicates that the document is part of a sequence, and
that the link is leading to the document that is the previous logical
document in the sequence.
Synonyms: For historical reasons, user agents must also treat the keyword
"previous" like the prev keyword.
4.8.6.14. Other link types
Extensions to the predefined set of link types may be registered in the
HTML link extensions section of the microformats wiki existing-rel-values
page [MFREL], or filed as an issue on this specification.
Proposed extension types should be specified with the following
information:
Keyword
The actual value being defined. The value should not be
confusingly similar to any other defined value (e.g., differing
only in case).
If the value contains a U+003A COLON character (:), it must also
be an absolute URL.
Effect on... link
One of the following:
Not allowed
The keyword must not be specified on link elements.
Hyperlink
The keyword may be specified on a link element; it
creates a hyperlink.
External Resource
The keyword may be specified on a link element; it
creates an external resource link.
Effect on... a and area
One of the following:
Not allowed
The keyword must not be specified on a and area
elements.
Hyperlink
The keyword may be specified on a and area elements;
it creates a hyperlink.
External Resource
The keyword may be specified on a and area elements;
it creates an external resource link.
Hyperlink Annotation
The keyword may be specified on a and area elements;
it annotates other hyperlinks created by the element.
Brief description
A short non-normative description of what the keyword’s meaning
is.
Specification
A link to a more detailed description of the keyword’s semantics
and requirements. It could be another page on the Wiki, or a link
to an external page.
Synonyms
A list of other keyword values that have exactly the same
processing requirements. Authors should not use the values defined
to be synonyms, they are only intended to allow user agents to
support legacy content. Anyone may remove synonyms that are not
used in practice; only names that need to be processed as synonyms
for compatibility with legacy content are to be registered in this
way.
Status
One of the following:
Proposed
The keyword has not received wide peer review and
approval. Someone has proposed it and is, or soon
will be, using it.
Ratified
The keyword has received wide peer review and
approval. It has a specification that unambiguously
defines how to handle pages that use the keyword,
including when they use it in incorrect ways.
Discontinued
The keyword has received wide peer review and it has
been found wanting. Existing pages are using this
keyword, but new pages should avoid it. The "brief
description" and "specification" entries will give
details of what authors should use instead, if
anything.
If a keyword is found to be redundant with existing values, it
should be removed and listed as a synonym for the existing value.
If a keyword is registered in the "proposed" state for a period of
a month or more without being used or specified, then it may be
removed from the registry.
If a keyword is added with the "proposed" status and found to be
redundant with existing values, it should be removed and listed as
a synonym for the existing value. If a keyword is added with the
"proposed" status and found to be harmful, then it should be
changed to "discontinued" status.
Anyone can change the status at any time, but should only do so in
accordance with the definitions above.
Conformance checkers may use the information given on the microformats
wiki existing-rel-values page to establish if a value is allowed or not:
values defined in this specification or marked as "proposed" or "ratified"
must be accepted when used on the elements for which they apply as
described in the "Effect on..." field, whereas values marked as
"discontinued" or values not containing a U+003A COLON character but not
listed in either this specification or on the aforementioned page must be
reported as invalid. The remaining values must be accepted as valid if
they are absolute URLs containing US-ASCII characters only and rejected
otherwise. Conformance checkers may cache this information (e.g., for
performance reasons or to avoid the use of unreliable network
connectivity).
Note: Even URL-valued link types are compared ASCII-case-insensitively.
Validators might choose to warn about characters U+0041 (LATIN CAPITAL
LETTER A) through U+005A (LATIN CAPITAL LETTER Z) (inclusive) in the
pre-case-folded form of link types that contain a colon.
When an author uses a new type not defined by either this specification or
the Wiki page, conformance checkers should offer to add the value to the
Wiki, with the details described above, with the "proposed" status.
Types defined as extensions in the microformats wiki existing-rel-values
page with the status "proposed" or "ratified" may be used with the rel
attribute on link, a, and area elements in accordance to the "Effect
on..." field. [MFREL]
4.9. Tabular data
4.9.1. The table element
Categories:
Flow content.
Palpable content.
Contexts in which this element can be used:
Where flow content is expected.
Content model:
In this order: optionally a caption element, followed by zero or
more colgroup elements, followed optionally by a thead element,
followed by either zero or more tbody elements or one or more tr
elements, followed optionally by a tfoot element, optionally
intermixed with one or more script-supporting elements.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
border
Allowed ARIA role attribute values:
table role (default - do not set), Any other role value.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
interface HTMLTableElement : HTMLElement {
attribute HTMLTableCaptionElement? caption;
HTMLTableCaptionElement createCaption();
void deleteCaption();
attribute HTMLTableSectionElement? tHead;
HTMLTableSectionElement createTHead();
void deleteTHead();
attribute HTMLTableSectionElement? tFoot;
HTMLTableSectionElement createTFoot();
void deleteTFoot();
[SameObject] readonly attribute HTMLCollection tBodies;
HTMLTableSectionElement createTBody();
[SameObject] readonly attribute HTMLCollection rows;
HTMLTableRowElement insertRow(optional long index = -1);
void deleteRow(long index);
};
The table element represents data with more than one dimension, in the
form of a table.
The table element takes part in the table model. Tables have rows,
columns, and cells given by their descendants. The rows and columns form a
grid; a table’s cells must completely cover that grid without overlap.
Precise rules for determining whether this conformance requirement is met
are described in the description of the table model.
Authors are encouraged to provide information describing how to interpret
complex tables. Guidance on how to provide such information is given
below.
Tables should not be used as layout aids.
Historically, many Web authors have tables in HTML as a way to control
their page layout making it difficult to extract tabular data from such
documents.
In particular, users of accessibility tools, like screen readers, are
likely to find it very difficult to navigate pages with tables used for
layout.
If a table is to be used for layout it must be marked with the attribute
role="presentation" for a user agent to properly represent the table to an
assistive technology and to properly convey the intent of the author to
tools that wish to extract tabular data from the document.
There are a variety of alternatives to using HTML tables for layout,
primarily using CSS positioning and the CSS table model. [CSS-2015]
The border content attribute may be specified on a table element to
explicitly indicate that the table element is not being used for layout
purposes. If specified, the attribute’s value must either be the empty
string or the value "1". The attribute is used by certain user agents as
an indication that borders should be drawn around cells of the table.
----------------------------------------------------------------------
Tables can be complicated to understand and navigate. To help users with
this, user agents should clearly delineate cells in a table from each
other, unless the user agent has classified the table as a layout table.
Authors and implementors are encouraged to consider using some of the
table design techniques described below to make tables easier to navigate
for users.
User agents, especially those that do table analysis on arbitrary content,
are encouraged to find heuristics to determine which tables actually
contain data and which are merely being used for layout. This
specification does not define a precise heuristic, but the following are
suggested as possible indicators:
Feature Indication
The use of the role attribute with Probably a layout table
the value presentation
The use of the border attribute with Probably a layout table
the non-conforming value 0
The use of the non-conforming
cellspacing and cellpadding Probably a layout table
attributes with the value 0
The use of caption, thead, or th Probably a non-layout table
elements
The use of the headers and scope Probably a non-layout table
attributes
The use of the border attribute with Probably a non-layout table
a value other than 0
Explicit visible borders set using Probably a non-layout table
CSS
The use of the non-conforming Not a good indicator (both layout and
summary attribute non-layout tables have historically
been given this attribute)
It is quite possible that the above suggestions are wrong. Implementors
are urged to provide feedback elaborating on their experiences with trying
to create a layout table detection heuristic.
If a table element has a (non-conforming) summary attribute, and the user
agent has not classified the table as a layout table, the user agent may
report the contents of that attribute to the user.
----------------------------------------------------------------------
table . caption [ = value ]
Returns the table’s caption element.
Can be set, to replace the caption element.
caption = table . createCaption()
Ensures the table has a caption element, and returns it.
table . deleteCaption()
Ensures the table does not have a caption element.
table . tHead [ = value ]
Returns the table’s thead element.
Can be set, to replace the thead element. If the new value is not
a thead element, throws a HierarchyRequestError exception.
thead = table . createTHead()
Ensures the table has a thead element, and returns it.
table . deleteTHead()
Ensures the table does not have a thead element.
table . tFoot [ = value ]
Returns the table’s tfoot element.
Can be set, to replace the tfoot element. If the new value is not
a tfoot element, throws a HierarchyRequestError exception.
tfoot = table . createTFoot()
Ensures the table has a tfoot element, and returns it.
table . deleteTFoot()
Ensures the table does not have a tfoot element.
table . tBodies
Returns an HTMLCollection of the tbody elements of the table.
tbody = table . createTBody()
Creates a tbody element, inserts it into the table, and returns
it.
table . rows
Returns an HTMLCollection of the tr elements of the table.
tr = table . insertRow( [ index ] )
Creates a tr element, along with a tbody if required, inserts them
into the table at the position given by the argument, and returns
the tr.
The position is relative to the rows in the table. The index -1,
which is the default if the argument is omitted, is equivalent to
inserting at the end of the table.
If the given position is less than -1 or greater than the number
of rows, throws an IndexSizeError exception.
table . deleteRow(index)
Removes the tr element with the given position in the table.
The position is relative to the rows in the table. The index -1 is
equivalent to deleting the last row of the table.
If the given position is less than -1 or greater than the index of
the last row, or if there are no rows, throws an IndexSizeError
exception.
The caption IDL attribute must return, on getting, the first caption
element child of the table element, if any, or null otherwise. On setting,
the first caption element child of the table element, if any, must be
removed, and the new value, if not null, must be inserted as the first
node of the table element.
The createCaption() method must return the first caption element child of
the table element, if any; otherwise a new caption element must be
created, inserted as the first node of the table element, and then
returned.
The deleteCaption() method must remove the first caption element child of
the table element, if any.
The tHead IDL attribute must return, on getting, the first thead element
child of the table element, if any, or null otherwise. On setting, if the
new value is null or a thead element, the first thead element child of the
table element, if any, must be removed, and the new value, if not null,
must be inserted immediately before the first element in the table element
that is neither a caption element nor a colgroup element, if any, or at
the end of the table if there are no such elements. If the new value is
neither null nor a thead element, then a HierarchyRequestError DOM
exception must be thrown instead.
The createTHead() method must return the first thead element child of the
table element, if any; otherwise a new thead element must be created and
inserted immediately before the first element in the table element that is
neither a caption element nor a colgroup element, if any, or at the end of
the table if there are no such elements, and then that new element must be
returned.
The deleteTHead() method must remove the first thead element child of the
table element, if any.
The tFoot IDL attribute must return, on getting, the first tfoot element
child of the table element, if any, or null otherwise. On setting, if the
new value is null or a tfoot element, the first tfoot element child of the
table element, if any, must be removed, and the new value, if not null,
must be inserted at the end of the table. If the new value is neither null
nor a tfoot element, then a HierarchyRequestError DOM exception must be
thrown instead.
The createTFoot() method must return the first tfoot element child of the
table element, if any; otherwise a new tfoot element must be created and
inserted at the end of the table, and then that new element must be
returned.
The deleteTFoot() method must remove the first tfoot element child of the
table element, if any.
The tBodies attribute must return an HTMLCollection rooted at the table
node, whose filter matches only tbody elements that are children of the
table element.
The createTBody() method must create a new tbody element, insert it
immediately after the last tbody element child in the table element, if
any, or at the end of the table element if the table element has no tbody
element children, and then must return the new tbody element.
The rows attribute must return an HTMLCollection rooted at the table node,
whose filter matches only tr elements that are either children of the
table element, or children of thead, tbody, or tfoot elements that are
themselves children of the table element. The elements in the collection
must be ordered such that those elements whose parent is a thead are
included first, in tree order, followed by those elements whose parent is
either a table or tbody element, again in tree order, followed finally by
those elements whose parent is a tfoot element, still in tree order.
The behavior of the insertRow(index) method depends on the state of the
table. When it is called, the method must act as required by the first
item in the following list of conditions that describes the state of the
table and the index argument:
If index is less than -1 or greater than the number of elements in rows
collection:
The method must throw an IndexSizeError exception.
If the rows collection has zero elements in it, and the table has no tbody
elements in it:
The method must create a tbody element, then create a tr element,
then append the tr element to the tbody element, then append the
tbody element to the table element, and finally return the tr
element.
If the rows collection has zero elements in it:
The method must create a tr element, append it to the last tbody
element in the table, and return the tr element.
If index is -1 or equal to the number of items in rows collection:
The method must create a tr element, and append it to the parent
of the last tr element in the rows collection. Then, the newly
created tr element must be returned.
Otherwise:
The method must create a tr element, insert it immediately before
the indexth tr element in the rows collection, in the same parent,
and finally must return the newly created tr element.
When the deleteRow(index) method is called, the user agent must run the
following steps:
1. If index is equal to -1, then index must be set to the number of items
in the rows collection, minus one.
2. Now, if index is less than zero, or greater than or equal to the
number of elements in the rows collection, the method must instead
throw an IndexSizeError exception, and these steps must be aborted.
3. Otherwise, the method must remove the indexth element in the rows
collection from its parent.
Here is an example of a table being used to mark up a Sudoku puzzle.
Observe the lack of headers, which are not necessary in such a table.
Today’s Sudoku
1 3 6 4 7 9
2 9 1
7 6
2 4 3 9 8
5 9 7 1
6 5 2
7
9 8 2 5
4.9.1.1. Techniques for describing tables
For tables that consist of more than just a grid of cells with headers in
the first row and headers in the first column, and for any table in
general where the reader might have difficulty understanding the content,
authors should include explanatory information introducing the table. This
information is useful for all users, but is especially useful for users
who cannot see the table, e.g., users of screen readers.
Such explanatory information should introduce the purpose of the table,
outline its basic cell structure, highlight any trends or patterns, and
generally teach the user how to use the table.
For instance, the following table:
Characteristics with positive and negative sides
Negative Characteristic Positive
Sad Mood Happy
Failing Grade Passing
...could benefit from a description explaining the way the table is laid
out, something like "Characteristics are given in the second column, with
the negative side in the left column and the positive side in the right
column".
There are a variety of ways to include this information, such as:
In prose, surrounding the table
In the following table, characteristics are
given in the second column, with the negative side in the left column and the positive
side in the right column.
Characteristics with positive and negative sides
Negative
Characteristic
Positive
Sad
Mood
Happy
Failing
Grade
Passing
In the example above the aria-describedby attribute is used to
explicitly associate the information with the table for assistive
technology users.
Next to the table, in the same figure
Characteristics are given in the second column, with the
negative side in the left column and the positive side in the right
column.
Characteristics with positive and negative sides
Negative
Characteristic
Positive
Sad
Mood
Happy
Failing
Grade
Passing
The figure in this example has been labeled by the table caption
using aria-labelledby.
Authors may also use other techniques, or combinations of the above
techniques, as appropriate.
Regardless of the method used to provide additional descriptive
information for a table, if a table needs a caption, authors should use a
caption element as it is the most robust method for providing an
accessible caption for a table.
The best option, of course, rather than writing a description explaining
the way the table is laid out, is to adjust the table such that no
explanation is needed.
In the case of the table used in the examples above, a simple
rearrangement of the table so that the headers are on the top and left
sides removes the need for an explanation as well as removing the need for
the use of headers attributes:
Characteristics with positive and negative sides
Characteristic
Negative
Positive
Mood
Sad
Happy
Grade
Failing
Passing
4.9.1.2. Techniques for table design
Good table design is key to making tables more readable and usable.
In visual media, providing column and row borders and alternating row
backgrounds can be very effective to make complicated tables more
readable.
For tables with large volumes of numeric content, using monospaced fonts
can help users see patterns, especially in situations where a user agent
does not render the borders. (Unfortunately, for historical reasons, not
rendering borders on tables is a common default.)
In speech media, table cells can be distinguished by reporting the
corresponding headers before reading the cell’s contents, and by allowing
users to navigate the table in a grid fashion, rather than serializing the
entire contents of the table in source order.
Authors are encouraged to use CSS to achieve these effects.
User agents are encouraged to render tables using these techniques
whenever the page does not use CSS and the table is not classified as a
layout table.
4.9.2. The caption element
Categories:
None.
Contexts in which this element can be used:
As the first element child of a table element.
Content model:
Flow content, but with no descendant table elements.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
DOM interface:
interface HTMLTableCaptionElement : HTMLElement {};
The caption element represents the title of the table that is its parent,
if it has a parent and that is a table element.
The caption element takes part in the table model.
When a table element is the only content in a figure element other than
the figcaption, the caption element should be omitted in favor of the
figcaption.
A caption can introduce context for a table, making it significantly
easier to understand.
Consider, for instance, the following table:
1 2 3 4 5 6
1 2 3 4 5 6 7
2 3 4 5 6 7 8
3 4 5 6 7 8 9
4 5 6 7 8 9 10
5 6 7 8 9 10 11
6 7 8 9 10 11 12
In the abstract, this table is not clear. However, with a caption giving
the table’s number (for reference in the main prose) and explaining its
use, it makes more sense:
Table 1.
This table shows the total score obtained from rolling two
six-sided dice. The first row represents the value of the first die,
the first column the value of the second die. The total is given in
the cell that corresponds to the values of the two dice.
This provides the user with more context:
Table 1. This table shows the total score obtained from rolling two
six-sided dice. The first row represents the value of the first die, the
first column the value of the second die. The total is given in the cell
that corresponds to the values of the two dice.
1 2 3 4 5 6
1 2 3 4 5 6 7
2 3 4 5 6 7 8
3 4 5 6 7 8 9
4 5 6 7 8 9 10
5 6 7 8 9 10 11
6 7 8 9 10 11 12
4.9.3. The colgroup element
Categories:
None.
Contexts in which this element can be used:
As a child of a table element, after any caption elements and
before any thead, tbody, tfoot, and tr elements.
Content model:
If the span attribute is present: Nothing.
If the span attribute is absent: Zero or more col and template
elements.
Tag omission in text/html:
A colgroup element’s start tag may be omitted if the first thing
inside the colgroup element is a col element, and if the element
is not immediately preceded by another colgroup element whose end
tag has been omitted. (It can’t be omitted if the element is
empty.)
Content attributes:
Global attributes
span - Number of columns spanned by the element
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
DOM interface:
interface HTMLTableColElement : HTMLElement {
attribute unsigned long span;
};
The colgroup element represents a group of one or more columns in the
table that is its parent, if it has a parent and that is a table element.
If the colgroup element contains no col elements, then the element may
have a span content attribute specified, whose value must be a valid
non-negative integer greater than zero.
The colgroup element and its span attribute take part in the table model.
The span IDL attribute must reflect the content attribute of the same
name. The value must be limited to only non-negative numbers greater than
zero.
4.9.4. The col element
Categories:
None.
Contexts in which this element can be used:
As a child of a colgroup element that doesn’t have a span
attribute.
Content model:
Nothing.
Tag omission in text/html:
No end tag.
Content attributes:
Global attributes
span
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
DOM interface:
HTMLTableColElement, same as for colgroup elements. This interface
defines one member, span.
If a col element has a parent and that is a colgroup element that itself
has a parent that is a table element, then the col element represents one
or more columns in the column group represented by that colgroup.
The element may have a span content attribute specified, whose value must
be a valid non-negative integer greater than zero.
The col element and its span attribute take part in the table model.
The span IDL attribute must reflect the content attribute of the same
name. The value must be limited to only non-negative numbers greater than
zero.
4.9.5. The tbody element
Categories:
None.
Contexts in which this element can be used:
As a child of a table element, after any caption, colgroup, and
thead elements, but only if there are no tr elements that are
children of the table element.
Content model:
Zero or more tr and script-supporting elements.
Tag omission in text/html:
A tbody element’s start tag may be omitted if the first thing
inside the tbody element is a tr element, and if the element is
not immediately preceded by a tbody, thead, or tfoot element whose
end tag has been omitted. (It can’t be omitted if the element is
empty.). A tbody element’s end tag may be omitted if the tbody
element is immediately followed by a tbody or tfoot element, or if
there is no more content in the parent element.
Content attributes:
Global attributes
rowgroup role (default - do not set), Any other role value.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the default or allowed roles.
DOM interface:
interface HTMLTableSectionElement : HTMLElement {
[SameObject] readonly attribute HTMLCollection rows;
HTMLElement insertRow(optional long index = -1);
void deleteRow(long index);
};
The HTMLTableSectionElement interface is also used for thead and
tfoot elements.
The tbody element represents a block of rows that consist of a body of
data for the parent table element, if the tbody element has a parent and
it is a table.
The tbody element takes part in the table model.
tbody . rows
Returns an HTMLCollection of the tr elements of the table section.
tr = tbody . insertRow( [ index ] )
Creates a tr element, inserts it into the table section at the
position given by the argument, and returns the tr.
The position is relative to the rows in the table section. The
index -1, which is the default if the argument is omitted, is
equivalent to inserting at the end of the table section.
If the given position is less than -1 or greater than the number
of rows, throws an IndexSizeError exception.
tbody . deleteRow(index)
Removes the tr element with the given position in the table
section.
The position is relative to the rows in the table section. The
index -1 is equivalent to deleting the last row of the table
section.
If the given position is less than -1 or greater than the index of
the last row, or if there are no rows, throws an IndexSizeError
exception.
The rows attribute must return an HTMLCollection rooted at the element,
whose filter matches only tr elements that are children of the element.
The insertRow(index) method must, when invoked on an element table
section, act as follows:
If index is less than -1 or greater than the number of elements in the
rows collection, the method must throw an IndexSizeError exception.
If index is -1 or equal to the number of items in the rows collection, the
method must create a tr element, append it to the element table section,
and return the newly created tr element.
Otherwise, the method must create a tr element, insert it as a child of
the table section element, immediately before the indexth tr element in
the rows collection, and finally must return the newly created tr element.
The deleteRow(index) method must, when invoked, act as follows:
If index is less than -1 or greater than the number of elements in the
rows collection, the method must throw an IndexSizeError exception.
If index is -1, remove the last element in the rows collection from its
parent.
Otherwise, remove the indexth element in the rows collection from its
parent.
4.9.6. The thead element
Categories:
None.
Contexts in which this element can be used:
As a child of a table element, after any caption, and colgroup
elements and before any tbody, tfoot, and tr elements, but only if
there are no other thead elements that are children of the table
element.
Content model:
Zero or more tr and script-supporting elements.
Tag omission in text/html:
A thead element’s end tag may be omitted if the thead element is
immediately followed by a tbody or tfoot element.
Content attributes:
Global attributes
rowgroup role (default - do not set), Any other role value.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the default or allowed roles.
DOM interface:
HTMLTableSectionElement, as defined for tbody elements.
The thead element represents the block of rows that consist of the column
labels (headers) for the parent table element, if the thead element has a
parent and it is a table.
The thead element takes part in the table model.
This example shows a thead element being used. Notice the use of the th
element to provide headers in the thead element:
4.9.7. The tfoot element
Categories:
None.
Contexts in which this element can be used:
As a child of a table element, after any caption, colgroup, thead,
tbody, and tr elements, but only if there are no other tfoot
elements that are children of the table element.
Content model:
Zero or more tr and script-supporting elements.
Tag omission in text/html:
A tfoot element’s end tag may be omitted if the tfoot element is
immediately followed by a tbody element, or if there is no more
content in the parent element.
Content attributes:
Global attributes
rowgroup role (default - do not set), Any other role value.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the default or allowed roles.
DOM interface:
HTMLTableSectionElement, as defined for tbody elements.
The tfoot element represents the block of rows that consist of the column
summaries (footers) for the parent table element, if the tfoot element has
a parent and it is a table.
The tfoot element takes part in the table model.
4.9.8. The tr element
Categories:
None.
Contexts in which this element can be used:
As a child of a thead element.
As a child of a tbody element.
As a child of a tfoot element.
As a child of a table element, after any caption, colgroup, and
thead elements, but only if there are no tbody elements that are
children of the table element.
Content model:
Zero or more td, th, and script-supporting elements.
Tag omission in text/html:
A tr element’s end tag may be omitted if the tr element is
immediately followed by another tr element, or if there is no more
content in the parent element.
Content attributes:
Global attributes
row role (default - do not set), Any other role value.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the default or allowed roles.
DOM interface:
interface HTMLTableRowElement : HTMLElement {
readonly attribute long rowIndex;
readonly attribute long sectionRowIndex;
[SameObject] readonly attribute HTMLCollection cells;
HTMLElement insertCell(optional long index = -1);
void deleteCell(long index);
};
The tr element represents a row of cells in a table.
The tr element takes part in the table model.
tr . rowIndex
Returns the position of the row in the table’s rows list.
Returns -1 if the element isn’t in a table.
tr . sectionRowIndex
Returns the position of the row in the table section’s rows list.
Returns -1 if the element isn’t in a table section.
tr . cells
Returns an HTMLCollection of the td and th elements of the row.
cell = tr . insertCell( [ index ] )
Creates a td element, inserts it into the table row at the
position given by the argument, and returns the td.
The position is relative to the cells in the row. The index -1,
which is the default if the argument is omitted, is equivalent to
inserting at the end of the row.
If the given position is less than -1 or greater than the number
of cells, throws an IndexSizeError exception.
tr . deleteCell(index)
Removes the td or th element with the given position in the row.
The position is relative to the cells in the row. The index -1 is
equivalent to deleting the last cell of the row.
If the given position is less than -1 or greater than the index of
the last cell, or if there are no cells, throws an IndexSizeError
exception.
The rowIndex attribute must, if the element has a parent table element, or
a parent tbody, thead, or tfoot element and a grandparent table element,
return the index of the tr element in that table element’s rows
collection. If there is no such table element, then the attribute must
return -1.
The sectionRowIndex attribute must, if the element has a parent table,
tbody, thead, or tfoot element, return the index of the tr element in the
parent element’s rows collection (for tables, that’s the
HTMLTableElement.rows collection; for table sections, that’s the
HTMLTableRowElement.rows collection). If there is no such parent element,
then the attribute must return -1.
The cells attribute must return an HTMLCollection rooted at the tr
element, whose filter matches only td and th elements that are children of
the tr element.
The insertCell(index) method must act as follows:
If index is less than -1 or greater than the number of elements in the
cells collection, the method must throw an IndexSizeError exception.
If index is equal to -1 or equal to the number of items in cells
collection, the method must create a td element, append it to the tr
element, and return the newly created td element.
Otherwise, the method must create a td element, insert it as a child of
the tr element, immediately before the indexth td or th element in the
cells collection, and finally must return the newly created td element.
The deleteCell(index) method must act as follows:
If index is less than -1 or greater than the number of elements in the
cells collection, the method must throw an IndexSizeError exception.
If index is -1, remove the last element in the cells collection from its
parent.
Otherwise, remove the indexth element in the cells collection from its
parent.
4.9.9. The td element
Categories:
Sectioning root.
Contexts in which this element can be used:
As a child of a tr element.
Content model:
Flow content.
Tag omission in text/html:
A td element’s end tag may be omitted if the td element is
immediately followed by a td or th element, or if there is no more
content in the parent element.
Content attributes:
Global attributes
colspan - Number of columns that the cell is to span
rowspan - Number of rows that the cell is to span
headers - The header cells for this cell
cell role (default - do not set), Any other role value.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the default or allowed roles.
DOM interface:
interface HTMLTableDataCellElement : HTMLTableCellElement {};
The td element represents a data cell in a table.
The td element and its colspan, rowspan, and headers attributes take part
in the table model.
User agents, especially in non-visual environments or where displaying the
table as a 2D grid is impractical, may give the user context for the cell
when rendering the contents of a cell; for instance, giving its position
in the table model, or listing the cell’s header cells (as determined by
the algorithm for assigning header cells). When a cell’s header cells are
being listed, user agents may use the value of abbr attributes on those
header cells, if any, instead of the contents of the header cells
themselves.
4.9.10. The th element
Categories:
None.
Contexts in which this element can be used:
As a child of a tr element.
Content model:
Flow content, but with no header, footer, sectioning content, or
heading content descendants
Tag omission in text/html:
A th element’s end tag may be omitted if the th element is
immediately followed by a td or th element, or if there is no more
content in the parent element.
Content attributes:
Global attributes
colspan - Number of columns that the cell is to span
rowspan - Number of rows that the cell is to span
headers - The headers for this cell
scope - Specifies which cells the header cell applies to
abbr - Alternative label to use for the header cell when
referencing the cell in other contexts
columnheader or rowheader role (default - do not set), Any other
role value.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the default or allowed roles.
DOM interface:
interface HTMLTableHeaderCellElement : HTMLTableCellElement {
attribute DOMString scope;
attribute DOMString abbr;
};
The th element represents a header cell in a table.
The th element may have a scope content attribute specified. The scope
attribute is an enumerated attribute with five states, four of which have
explicit keywords:
The row keyword, which maps to the row state
The row state means the header cell applies to some of the
subsequent cells in the same row(s).
The col keyword, which maps to the column state
The column state means the header cell applies to some of the
subsequent cells in the same column(s).
The rowgroup keyword, which maps to the row group state
The row group state means the header cell applies to all the
remaining cells in the row group. A th element’s scope attribute
must not be in the row group state if the element is not anchored
in a row group.
The colgroup keyword, which maps to the column group state
The colgroup group state means the header cell applies to all the
remaining cells in the column group. A th element’s scope
attribute must not be in the column group state if the element is
not anchored in a column group.
The auto state
The auto state makes the header cell apply to a set of cells
selected based on context.
The scope attribute’s missing value default is the auto state.
The th element may have an abbr content attribute specified. Its value
must be an alternative label for the header cell, to be used when
referencing the cell in other contexts (e.g., when describing the header
cells that apply to a data cell). It is typically an abbreviated form of
the full header cell, but can also be an expansion, or merely a different
phrasing.
The th element and its colspan, rowspan, headers, and scope attributes
take part in the table model.
The scope IDL attribute must reflect the content attribute of the same
name, limited to only known values.
The abbr IDL attribute must reflect the content attribute of the same
name.
The following example shows how the scope attribute’s rowgroup value
affects which data cells a header cell applies to.
Here is a markup fragment showing a table:
The tbody elements in this example identify the range of the row groups.
Measurement of legs and tails in Cats and English speakers
ID Measurement Average Maximum
Cats
93 Legs 3.5 4
10 Tails 1 1
English speakers
32 Legs 2.67 4
35 Tails 0.33 1
This would result in the following table:
Measurement of legs and tails in Cats and English speakers
ID Measurement Average Maximum
Cats
93 Legs 3.5 4
10 Tails 1 1
English speakers
32 Legs 2.67 4
35 Tails 0.33 1
The header cells in row 1 ("ID", "Measurement", "Average" and "Maximum")
each apply only to the cells in their column.
The header cells with a scope=rowgroup ("Cats" and 'English speakers')
apply to all the cells in their row group other than the cells (to their
left) in column 1:
The header "Cats" (row 2, column 2) applies to the headers "Legs" (row 3,
column 2) and "Tails" (row 4, column 2) and to the data cells in rows 2, 3
and 4 of the "Average" and "Maximum" columns.
The header 'English speakers' (row 5, column 2) applies to the headers
"Legs" (row 6, column 2) and "Tails" (row 7, column 2) and to the data
cells in rows 5, 6 and 7 of the "Average" and "Maximum" columns.
Each of the "Legs" and "Tails" header cells has a scope=row and therefore
apply to the data cells (to the right) in their row, from the "Average"
and "Maximum" columns.
Representation of the example table overlayed with arrows indicating which
cells each header applies to.
4.9.11. Attributes common to td and th elements
The td and th elements may have a colspan content attribute specified,
whose value must be a valid non-negative integer greater than zero.
The td and th elements may also have a rowspan content attribute
specified, whose value must be a valid non-negative integer. For this
attribute, the value zero means that the cell is to span all the remaining
rows in the row group.
These attributes give the number of columns and rows respectively that the
cell is to span. These attributes must not be used to overlap cells, as
described in the table model.
----------------------------------------------------------------------
The td and th element may have a headers content attribute specified. The
headers attribute, if specified, must contain a string consisting of an
unordered set of unique space-separated tokens that are case-sensitive,
each of which must have the value of an id of a th element taking part in
the same table as the td or th element (as defined by the table model).
A th element with id id is said to be directly targeted by all td and th
elements in the same table that have headers attributes whose values
include as one of their tokens the ID id. A th element A is said to be
targeted by a th or td element B if either A is directly targeted by B or
if there exists an element C that is itself targeted by the element B and
A is directly targeted by C.
A th element must not be targeted by itself.
The colspan, rowspan, and headers attributes take part in the table model.
----------------------------------------------------------------------
The td and th elements implement interfaces that inherit from the
HTMLTableCellElement interface:
interface HTMLTableCellElement : HTMLElement {
attribute unsigned long colSpan;
attribute unsigned long rowSpan;
[SameObject, PutForwards=value] readonly attribute DOMTokenList headers;
readonly attribute long cellIndex;
};
cell . cellIndex
Returns the position of the cell in the row’s cells list. This
does not necessarily correspond to the x-position of the cell in
the table, since earlier cells might cover multiple rows or
columns.
Returns -1 if the element isn’t in a row.
The colSpan IDL attribute must reflect the colspan content attribute. Its
default value is 1.
The rowSpan IDL attribute must reflect the rowspan content attribute. Its
default value is 1.
The headers IDL attribute must reflect the content attribute of the same
name.
The cellIndex IDL attribute must, if the element has a parent tr element,
return the index of the cell’s element in the parent element’s cells
collection. If there is no such parent element, then the attribute must
return -1.
4.9.12. Processing model
The various table elements and their content attributes together define
the table model.
A table consists of cells aligned on a two-dimensional grid of slots with
coordinates (x, y). The grid is finite, and is either empty or has one or
more slots. If the grid has one or more slots, then the x coordinates are
always in the range 0 ≤ x < x_width, and the y coordinates are always in
the range 0 ≤ y < y_height. If one or both of x_width and y_height are
zero, then the table is empty (has no slots). Tables correspond to table
elements.
A cell is a set of slots anchored at a slot (cell_x, cell_y), and with a
particular width and height such that the cell covers all the slots with
coordinates (x, y) where cell_x ≤ x < cell_x+width and
cell_y ≤ y < cell_y+height. Cells can either be data cells or header
cells. Data cells correspond to td elements, and header cells correspond
to th elements. Cells of both types can have zero or more associated
header cells.
It is possible, in certain error cases, for two cells to occupy the same
slot.
A row is a complete set of slots from x=0 to x=x_width-1, for a particular
value of y. Rows usually correspond to tr elements, though a row group can
have some implied rows at the end in some cases involving cells spanning
multiple rows.
A column is a complete set of slots from y=0 to y=y_height-1, for a
particular value of x. Columns can correspond to col elements. In the
absence of col elements, columns are implied.
A row group is a set of rows anchored at a slot (0, group_y) with a
particular height such that the row group covers all the slots with
coordinates (x, y) where 0 ≤ x < x_width and group_y ≤ y < group_y+height.
Row groups correspond to tbody, thead, and tfoot elements. Not every row
is necessarily in a row group.
A column group is a set of columns anchored at a slot (group_x, 0) with a
particular width such that the column group covers all the slots with
coordinates (x, y) where group_x ≤ x < group_x+width and 0 ≤ y < y_height.
Column groups correspond to colgroup elements. Not every column is
necessarily in a column group.
Row groups cannot overlap each other. Similarly, column groups cannot
overlap each other.
A cell cannot cover slots that are from two or more row groups. It is,
however, possible for a cell to be in multiple column groups. All the
slots that form part of one cell are part of zero or one row groups and
zero or more column groups.
In addition to cells, columns, rows, row groups, and column groups, tables
can have a caption element associated with them. This gives the table a
heading, or legend.
A table model error is an error with the data represented by table
elements and their descendants. Documents must not have table model
errors.
4.9.12.1. Forming a table
User agents must use the following algorithm to determine
* which elements correspond to which slots in a table associated with a
table element,
* the dimensions of the table (x_width and y_height), and
* if there are any table model errors .
The algorithm selects the first caption encountered and assigns it as
the caption for the table, and selects the first thead and processes
it. Until there is a thead, tfoot, tbody or tr element, it processes
any colgroup elements encountered, and any col children, to create
column groups. Finally, from the first thead, tfoot, tbody or tr
element encountered as a child of the table it processes those
elements, moving the first tfoot encountered to the end of the table
respectively.
1. Let x_width be zero.
2. Let y_height be zero.
3. Let table footer be null.
4. Let table header be null.
5. Let the table be the table represented by the table element. The
x_width and y_height variables give the table’s dimensions. The
table is initially empty.
6. If the table element has no children elements, then return the
table (which will be empty), and abort these steps.
7. Associate the first caption element child of the table element
with the table. If there are no such children, then it has no
associated caption element.
8. Let the current element be the first element child of the table
element.
If a step in this algorithm ever requires the current element to
be advanced to the next child of the table when there is no such
next child, then the user agent must jump to the step labeled
end, near the end of this algorithm.
9. While the current element is not one of the following elements,
advance the current element to the next child of the table:
* colgroup
* thead
* tbody
* tfoot
* tr
10. If the current element is a colgroup, follow these substeps:
1. Column groups: Process the current element according to the
appropriate case below:
If the current element has any col element children
Follow these steps:
1. Let x_start have the value of x_width.
2. Let the current column be the first col
element child of the colgroup element.
3. Columns: If the current column col element
has a span attribute, then parse its value
using the rules for parsing non-negative
integers.
If the result of parsing the value is not
an error or zero, then let span be that
value.
Otherwise, if the col element has no span
attribute, or if trying to parse the
attribute’s value resulted in an error or
zero, then let span be 1.
4. Increase x_width by span.
5. Let the last span columns in the table
correspond to the current column col
element.
6. If current column is not the last col
element child of the colgroup element,
then let the current column be the next
col element child of the colgroup element,
and return to the step labeled columns.
7. Let all the last columns in the table from
x=x_start to x=x_width-1 form a new column
group, anchored at the slot (x_start, 0),
with width x_width-x_start, corresponding
to the colgroup element.
If the current element has no col element children
1. If the colgroup element has a span
attribute, then parse its value using the
rules for parsing non-negative integers.
If the result of parsing the value is not
an error or zero, then let span be that
value.
Otherwise, if the colgroup element has no
span attribute, or if trying to parse the
attribute’s value resulted in an error or
zero, then let span be 1.
2. Increase x_width by span.
3. Let the last span columns in the table
form a new column group, anchored at the
slot (x_width-span, 0), with width span,
corresponding to the colgroup element.
2. Advance the current element to the next child of the table.
3. While the current element is not one of the following
elements, advance the current element to the next child of
the table:
* colgroup
* thead
* tbody
* tfoot
* tr
4. If the current element is a colgroup element, jump to the
step labeled column groups above.
11. Let y_current be zero.
12. Let the list of downward-growing cells be an empty list.
13. Rows: While the current element is not one of the following
elements, advance the current element to the next child of the
table:
* thead
* tbody
* tfoot
* tr
Run the algorithm for processing row groups for the first thead
child of the table.
14. If the current element is a tfoot and the value of table footer
is null, then run the following substeps:
1. let table footer be the current element;
2. advance the current element to the next child of the table,
and
3. return to the step labeled rows.
15. If the current element is a thead and the value of table header
is null, then run the following substeps:
1. let table header be the current element;
2. advance the current element to the next child of the table,
and
3. return to the step labeled rows.
16. If the current element is a tr then run the algorithm for
processing rows, advance the current element to the next child of
the table, and return to the step labeled rows.
17. Run the algorithm for ending a row group.
18. The current element is either a thead, tfoot, or a tbody.
Run the algorithm for processing row groups.
19. Advance the current element to the next child of the table.
20. Return to the step labeled rows.
21. End: run the algorithm for processing row groups to process table
footer.
22. If there exists a row or column in the table containing only
slots that do not have a cell anchored to them, then this is a
table model error.
23. Return the table.
The algorithm for processing row groups, which is invoked by the set
of steps above for processing thead, tbody, and tfoot elements, is:
1. Let y_start have the value of y_height.
2. For each tr element that is a child of the element being
processed, in tree order, run the algorithm for processing rows.
3. If y_height > y_start, then let all the last rows in the table
from y=y_start to y=y_height-1 form a new row group, anchored at
the slot with coordinate (0, y_start), with height
y_height-y_start, corresponding to the element being processed.
4. Run the algorithm for ending a row group.
The algorithm for ending a row group, which is invoked by the set of
steps above when starting and ending a block of rows, is:
1. While y_current is less than y_height, follow these steps:
1. Run the algorithm for growing downward-growing cells.
2. Increase y_current by 1.
2. Empty the list of downward-growing cells.
The algorithm for processing rows, which is invoked by the set of
steps above for processing tr elements, is:
1. If y_height is equal to y_current, then increase y_height by
1. (y_current is never greater than y_height.)
2. Let x_current be 0.
3. Run the algorithm for growing downward-growing cells.
4. If the tr element being processed has no td or th element
children, then increase y_current by 1, abort this set of steps,
and return to the algorithm above.
5. Let current cell be the first td or th element child in the tr
element being processed.
6. Cells: While x_current is less than x_width and the slot with
coordinate (x_current, y_current) already has a cell assigned to
it, increase x_current by 1.
7. If x_current is equal to x_width, increase x_width by 1.
(x_current is never greater than x_width.)
8. If the current cell has a colspan attribute, then parse that
attribute’s value, and let colspan be the result.
If parsing that value failed, or returned zero, or if the
attribute is absent, then let colspan be 1, instead.
9. If the current cell has a rowspan attribute, then parse that
attribute’s value, and let rowspan be the result.
If parsing that value failed or if the attribute is absent, then
let rowspan be 1, instead.
10. If rowspan is zero and the table element’s node document is not
set to quirks mode, then let cell grows downward be true, and set
rowspan to 1. Otherwise, let cell grows downward be false.
11. If x_width < x_current+colspan, then let x_width be
x_current+colspan.
12. If y_height < y_current+rowspan, then let y_height be
y_current+rowspan.
13. Let the slots with coordinates (x, y) such that
x_current ≤ x < x_current+colspan and
y_current ≤ y < y_current+rowspan be covered by a new cell c,
anchored at (x_current, y_current), which has width colspan and
height rowspan, corresponding to the current cell element.
If the current cell element is a th element, let this new cell c
be a header cell; otherwise, let it be a data cell.
To establish which header cells apply to the current cell
element, use the algorithm for assigning header cells described
in the next section.
If any of the slots involved already had a cell covering them,
then this is a table model error. Those slots now have two cells
overlapping.
14. If cell grows downward is true, then add the tuple {c, x_current,
colspan} to the list of downward-growing cells.
15. Increase x_current by colspan.
16. If current cell is the last td or th element child in the tr
element being processed, then increase y_current by 1, abort this
set of steps, and return to the algorithm above.
17. Let current cell be the next td or th element child in the tr
element being processed.
18. Return to the step labeled cells.
When the algorithms above require the user agent to run the algorithm
for growing downward-growing cells, the user agent must, for each
{cell, cell_x, width} tuple in the list of downward-growing cells, if
any, extend the cell cell so that it also covers the slots with
coordinates (x, y_current), where cell_x ≤ x < cell_x+width.
4.9.12.2. Forming relationships between data cells and header cells
Each cell can be assigned zero or more header cells. The algorithm for
assigning header cells to a cell principal cell is as follows.
1. Let header list be an empty list of cells.
2. Let (principal_x, principal_y) be the coordinate of the slot to
which the principal cell is anchored.
3. If the principal cell has a headers attribute specified
1. Take the value of the principal cell’s headers
attribute and split it on spaces, letting id
list be the list of tokens obtained.
2. For each token in the id list, if the first
element in the Document with an ID equal to the
token is a cell in the same table, and that
cell is not the principal cell, then add that
cell to header list.
If principal cell does not have a headers attribute
specified
1. Let principal_width be the width of the
principal cell.
2. Let principal_height be the height of the
principal cell.
3. For each value of y from principal_y to
principal_y+principal_height-1, run the
internal algorithm for scanning and assigning
header cells, with the principal cell, the
header list, the initial coordinate
(principal_x,y), and the increments Δx=-1 and
Δy=0.
4. For each value of x from principal_x to
principal_x+principal_width-1, run the internal
algorithm for scanning and assigning header
cells, with the principal cell, the header
list, the initial coordinate (x,principal_y),
and the increments Δx=0 and Δy=-1.
5. If the principal cell is anchored in a row
group, then add all header cells that are row
group headers and are anchored in the same row
group with an x-coordinate less than or equal
to principal_x+principal_width-1 and a
y-coordinate less than or equal to
principal_y+principal_height-1 to header list.
6. If the principal cell is anchored in a column
group, then add all header cells that are
column group headers and are anchored in the
same column group with an x-coordinate less
than or equal to principal_x+principal_width-1
and a y-coordinate less than or equal to
principal_y+principal_height-1 to header list.
4. Remove all the empty cells from the header list.
5. Remove any duplicates from the header list.
6. Remove principal cell from the header list if it is there.
7. Assign the headers in the header list to the principal cell.
The internal algorithm for scanning and assigning header cells, given
a principal cell, a header list, an initial coordinate (initial_x,
initial_y), and Δx and Δy increments, is as follows:
1. Let x equal initial_x.
2. Let y equal initial_y.
3. Let opaque headers be an empty list of cells.
4. If principal cell is a header cell
Let in header block be true, and let headers from
current header block be a list of cells containing
just the principal cell.
Otherwise
Let in header block be false and let headers from
current header block be an empty list of cells.
5. Loop: Increment x by Δx; increment y by Δy.
For each invocation of this algorithm, one of Δx and Δy will be
-1, and the other will be 0.
6. If either x or y is less than 0, then abort this internal
algorithm.
7. If there is no cell covering slot (x, y), or if there is more
than one cell covering slot (x, y), return to the substep labeled
loop.
8. Let current cell be the cell covering slot (x, y).
9. If current cell is a header cell
1. Set in header block to true.
2. Add current cell to headers from current header
block.
3. Let blocked be false.
4. If Δx is 0
If there are any cells in the
opaque headers list anchored with
the same x-coordinate as the
current cell, and with the same
width as current cell, then let
blocked be true.
If the current cell is not a
column header, then let blocked be
true.
If Δy is 0
If there are any cells in the
opaque headers list anchored with
the same y-coordinate as the
current cell, and with the same
height as current cell, then let
blocked be true.
If the current cell is not a row
header, then let blocked be true.
5. If blocked is false, then add the current cell
to the headers list.
If current cell is a data cell and in header block is true
Set in header block to false. Add all the cells in
headers from current header block to the opaque
headers list, and empty the headers from current
header block list.
10. Return to the step labeled loop.
A header cell anchored at the slot with coordinate (x, y) with width
width and height height is said to be a column header if any of the
following conditions are true:
* The cell’s scope attribute is in the column state, or
* The cell’s scope attribute is in the auto state, and there are no
data cells in any of the cells covering slots with x-coordinates
x .. x+width-1.
A header cell anchored at the slot with coordinate (x, y) with width
width and height height is said to be a row header if any of the
following conditions are true:
* The cell’s scope attribute is in the row state, or
* The cell’s scope attribute is in the auto state, the cell is not
a column header, and there are no data cells in any of the cells
covering slots with y-coordinates y .. y+height-1.
A header cell is said to be a column group header if its scope
attribute is in the column group state.
A header cell is said to be a row group header if its scope attribute
is in the row group state.
A cell is said to be an empty cell if it contains no elements and its
text content, if any, consists only of White_Space characters.
4.9.13. Examples
This section is non-normative.
The following shows how might one mark up the bottom part of table 45
of the Smithsonian physical tables, Volume 71:
Specification values: Steel , Castings ,
Ann. A.S.T.M. A27-16, Class B;* P max. 0.06; S max. 0.05.
Grade.
Yield Point.
Ultimate tensile strength
Per cent elong. 50.8mm or 2 in.
Per cent reduct. area.
kg/mm2
lb/in2
Hard
0.45 ultimate
56.2
80,000
15
20
Medium
0.45 ultimate
49.2
70,000
18
25
Soft
0.45 ultimate
42.2
60,000
22
30
This table could look like this:
Specification values: Steel, Castings, Ann. A.S.T.M. A27-16, Class B;*
P max. 0.06; S max. 0.05.
Ultimate tensile Per cent elong. 50.8 mm Per cent
Grade. Yield Point. strength or 2 in. reduct.
kg/mm^2 lb/in^2 area.
Hard 0.45 56.2 80,000 15 20
ultimate
Medium 0.45 49.2 70,000 18 25
ultimate
Soft 0.45 42.2 60,000 22 30
ultimate
----------------------------------------------------------------------
The following shows how one might mark up the gross margin table on
page 46 of Apple, Inc’s 10-K filing for fiscal year 2008:
2008
2007
2006
Net sales
$ 32,479
$ 24,006
$ 19,315
Cost of sales
21,334
15,852
13,717
Gross margin
$ 11,145
$ 8,154
$ 5,598
Gross margin percentage
34.3%
34.0%
29.0%
This table could look like this:
2008 2007 2006
Net sales $ 32,479 $ 24,006 $ 19,315
Cost of sales 21,334 15,852 13,717
Gross margin $ 11,145 $ 8,154 $ 5,598
Gross margin percentage 34.3% 34.0% 29.0%
----------------------------------------------------------------------
The following shows how one might mark up the operating expenses table
from lower on the same page of that document:
2008 2007 2006
Research and development
$ 1,109 $ 782 $ 712
Percentage of net sales
3.4% 3.3% 3.7%
Selling, general, and administrative
$ 3,761 $ 2,963 $ 2,433
Percentage of net sales
11.6% 12.3% 12.6%
This table could look like this:
2008 2007 2006
Research and development $ 1,109 $ 782 $ 712
Percentage of net sales 3.4% 3.3% 3.7%
Selling, general, and administrative $ 3,761 $ 2,963 $ 2,433
Percentage of net sales 11.6% 12.3% 12.6%
4.10. Forms
4.10.1. Introduction
This section is non-normative.
A form is a component of a Web page that has form controls, such as text
fields, buttons, checkboxes, range controls, or color pickers. A user can
interact with such a form, providing data that can then be sent to the
server for further processing (e.g., returning the results of a search or
calculation). No client-side scripting is needed in many cases, though an
API is available so that scripts can augment the user experience or use
forms for purposes other than submitting data to a server.
Writing a form consists of several steps, which can be performed in any
order: writing the user interface, implementing the server-side
processing, and configuring the user interface to communicate with the
server.
4.10.1.1. Writing a form’s user interface
This section is non-normative.
For the purposes of this brief introduction, we will create a pizza
ordering form.
Any form starts with a form element, inside which are placed the controls.
Most controls are represented by the input element, which by default
provides a one-line text field. To label a control, the label element is
used; the label text and the control itself go inside the label element.
Each area within a form is typically represented using a div element.
Putting this together, here is how one might ask for the customer’s name:
To let the user select the size of the pizza, we can use a set of radio
buttons. Radio buttons also use the input element, this time with a type
attribute with the value radio. To make the radio buttons work as a group,
they are given a common name using the name attribute. To group a batch of
controls together, such as, in this case, the radio buttons, one can use
the fieldset element. The title of such a group of controls is given by
the first element in the fieldset, which has to be a legend element.
Changes from the previous step are highlighted.
To pick toppings, we can use checkboxes. These use the input element with
a type attribute with the value checkbox:
The pizzeria for which this form is being written is always making
mistakes, so it needs a way to contact the customer. For this purpose, we
can use form controls specifically for telephone numbers (input elements
with their type attribute set to tel) and e-mail addresses (input elements
with their type attribute set to email):
We can use an input element with its type attribute set to time to ask for
a delivery time. Many of these form controls have attributes to control
exactly what values can be specified; in this case, three attributes of
particular interest are min, max, and step. These set the minimum time,
the maximum time, and the interval between allowed values (in seconds).
This pizzeria only delivers between 11am and 9pm, and doesn’t promise
anything better than 15 minute increments, which we can mark up as
follows:
The textarea element can be used to provide a free-form text field. In
this instance, we are going to use it to provide a space for the customer
to give delivery instructions:
Finally, to make the form submittable we use the button element:
4.10.1.2. Implementing the server-side processing for a form
This section is non-normative.
The exact details for writing a server-side processor are out of scope for
this specification. For the purposes of this introduction, we will assume
that the script at https://pizza.example.com/order.cgi is configured to
accept submissions using the application/x-www-form-urlencoded format,
expecting the following parameters sent in an HTTP POST body:
custname
Customer’s name
custtel
Customer’s telephone number
custemail
Customer’s e-mail address
size
The pizza size, either small, medium, or large
topping
A topping, specified once for each selected topping, with the
allowed values being bacon, cheese, onion, and mushroom
delivery
The requested delivery time
comments
The delivery instructions
4.10.1.3. Configuring a form to communicate with a server
This section is non-normative.
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 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.
For each form control you want submitted, you then have to give a name
that will be used to refer to the data in the submission. We already
specified the name for the group of radio buttons; the same attribute
(name) also specifies the submission name. Radio buttons can be
distinguished from each other in the submission by giving them different
values, using the value attribute.
Multiple controls can have the same name; for example, here we give all
the checkboxes the same name, and the server distinguishes which checkbox
was checked by seeing which values are submitted with that name — like the
radio buttons, they are also given unique values with the value attribute.
Given the settings in the previous section, this all becomes:
There is no particular significance to the way some of the attributes have
their values quoted and others don’t. The HTML syntax allows a variety of
equally valid ways to specify attributes, as discussed in §8 The HTML
syntax.
For example, if the customer entered "Denise Lawrence" as their name,
"555-321-8642" as their telephone number, did not specify an e-mail
address, asked for a medium-sized pizza, selected the Extra Cheese and
Mushroom toppings, entered a delivery time of 7pm, and left the delivery
instructions text field blank, the user agent would submit the following
to the online Web service:
custname=Denise+Lawrence&custtel=555-321-8642&custemail=&size=medium&topping=cheese&topping=mushroom&delivery=19%3A00&comments=
4.10.1.4. Client-side form validation
This section is non-normative.
Forms can be annotated in such a way that the user agent will check the
user’s input before the form is submitted. The server still has to verify
the input is valid (since hostile users can easily bypass the form
validation), but it allows the user to avoid the wait incurred by having
the server be the sole checker of the user’s input.
The simplest annotation is the required attribute, which can be specified
on input elements to indicate that the form is not to be submitted until a
value is given. By adding this attribute to the customer name, pizza size,
and delivery time fields, we allow the user agent to notify the user when
the user submits the form without filling in those fields:
It is also possible to limit the length of the input, using the maxlength
attribute. By adding this to the textarea element, we can limit users to
1000 characters, preventing them from writing huge essays to the busy
delivery drivers instead of staying focused and to the point:
When a form is submitted, invalid events are fired at each form control
that is invalid, and then at the form element itself. This can be useful
for displaying a summary of the problems with the form, since typically
the browser itself will only report one problem at a time.
4.10.1.5. Enabling client-side automatic filling of form controls
This section is non-normative.
Some browsers attempt to aid the user by automatically filling form
controls rather than having the user reenter their information each time.
For example, a field asking for the user’s telephone number can be
automatically filled with the user’s phone number.
To help the user agent with this, the autocomplete attribute can be used
to describe the field’s purpose. In the case of this form, we have three
fields that can be usefully annotated in this way: the information about
who the pizza is to be delivered to. Adding this information looks like
this:
4.10.1.6. The difference between the field type, the autofill field name,
and the input modality
This section is non-normative.
The type and autocomplete attributes can seem confusingly similar. For
instance, in all three cases, the string "email" is a valid value. This
section attempts to illustrate the difference between the three attributes
and provides advice suggesting how to use them.
The type attribute on input elements decides what kind of control the user
agent will use to expose the field. Choosing between different values of
this attribute is the same choice as choosing whether to use an input
element, a textarea element, a select element, etc.
The autocomplete attribute, in contrast, describes what the value that the
user will enter actually represents. Choosing between different values of
this attribute is the same choice as choosing what the label for the
element will be.
First, consider telephone numbers. If a page is asking for a telephone
number from the user, the right form control to use is Your phone number:
Recipient’s phone number:
Please enter complete phone numbers including the country code prefix, as in "+1 555 123 4567".
But if the site only supports British customers and recipients, it might
instead look like this (notice the use of tel-national rather than tel):
Your phone number:
Recipient’s phone number:
Please enter complete UK phone numbers, as in "(01632) 960 123".
Now, consider a person’s preferred languages. The right autocomplete value
is language. However, there could be a number of different form controls
used for the purpose: a free text field (), radio buttons (Where?
If a label element has interactive content other than its labeled control,
the activation behavior of the label element for events targeted at those
interactive content descendants and any descendants of those must be to do
nothing.
In the following example, clicking on the link does not toggle the
checkbox, even if the platform normally toggles a checkbox when clicking
on a label. Instead, clicking the link triggers the normal activation
behavior of following the link.
the terms and conditions I agree to the terms and conditions Terms and Conditions )
The following example shows three form controls each with a label, two of
which have small text showing the right format for users to use.
Full name: Format: First Last
Age:
Post code: Format: AB12 3CD
label . control
Returns the form control that is associated with this element.
The htmlFor IDL attribute must reflect the for content attribute.
The control IDL attribute must return the label element’s labeled control,
if any, or null if there isn’t one.
----------------------------------------------------------------------
control . labels
Returns a NodeList of all the label elements that the form control
is associated with.
Labelable elements have a NodeList object associated with them that
represents the list of label elements, in tree order, whose labeled
control is the element in question. The labels IDL attribute of labelable
elements, on getting, must return that NodeList object.
4.10.5. The input element
Categories:
Flow content.
Phrasing content.
If the type attribute is not in the Hidden state: interactive
content.
If the type attribute is not in the Hidden state: listed,
labelable, submittable, resettable, and reassociateable
form-associated element.
If the type attribute is in the Hidden state: listed, submittable,
resettable, and reassociateable form-associated element.
If the type attribute is not in the Hidden state: Palpable
content.
Contexts in which this element can be used:
Where phrasing content is expected.
Content model:
Nothing.
Tag omission in text/html:
No end tag
Content attributes:
Global attributes
accept - Hint for expected file type in File Upload controls
alt - Replacement text for use when images are not available
autocomplete - Hint for form autofill feature
autofocus - Automatically focus the form control when the page is
loaded
checked - Whether the command or control is checked
dirname - Name of form field to use for sending the element’s
directionality in §4.10.21 Form submission
disabled - Whether the form control is disabled
form - Associates the control with a form element
formaction - URL to use for §4.10.21 Form submission
formenctype - Form data set encoding type to use for §4.10.21 Form
submission
formmethod - HTTP method to use for §4.10.21 Form submission
formnovalidate - Bypass form control validation for §4.10.21 Form
submission
formtarget - browsing context for §4.10.21 Form submission
height - Vertical dimension
list - List of autocomplete options
max - Maximum value
maxlength - Maximum length of value
min - Minimum value
minlength - Minimum length of value
multiple - Whether to allow multiple values
name - Name of form control to use for §4.10.21 Form submission
and in the form.elements API
pattern - Pattern to be matched by the form control’s value
placeholder - User-visible label to be placed within the form
control
readonly - Whether to allow the value to be edited by the user
required - Whether the control is required for §4.10.21 Form
submission
size - Size of the control
src - Address of the resource
step - Granularity to be matched by the form control’s value
type - Type of form control
value - Value of the form control
width - Horizontal dimension
Also, the title attribute has special semantics on this element
when used in conjunction with the pattern attribute.
Allowed ARIA role attribute values:
Depends upon state of the type attribute.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
interface HTMLInputElement : HTMLElement {
attribute DOMString accept;
attribute DOMString alt;
attribute DOMString autocomplete;
attribute boolean autofocus;
attribute boolean defaultChecked;
attribute boolean checked;
attribute DOMString dirName;
attribute boolean disabled;
readonly attribute HTMLFormElement? form;
readonly attribute FileList? files;
attribute DOMString formAction;
attribute DOMString formEnctype;
attribute DOMString formMethod;
attribute boolean formNoValidate;
attribute DOMString formTarget;
attribute unsigned long height;
attribute boolean indeterminate;
readonly attribute HTMLElement? list;
attribute DOMString max;
attribute long maxLength;
attribute DOMString min;
attribute long minLength;
attribute boolean multiple;
attribute DOMString name;
attribute DOMString pattern;
attribute DOMString placeholder;
attribute boolean readOnly;
attribute boolean _required;
attribute unsigned long size;
attribute DOMString src;
attribute DOMString step;
attribute DOMString type;
attribute DOMString defaultValue;
[TreatNullAs=EmptyString] attribute DOMString value;
attribute object? valueAsDate;
attribute unrestricted double valueAsNumber;
attribute unsigned long width;
void stepUp(optional long n = 1);
void stepDown(optional long n = 1);
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
[SameObject] readonly attribute NodeList labels;
void select();
attribute unsigned long? selectionStart;
attribute unsigned long? selectionEnd;
attribute DOMString? selectionDirection;
void setRangeText(DOMString replacement);
void setRangeText(DOMString replacement, unsigned long start, unsigned long end, optional SelectionMode selectionMode = "preserve");
void setSelectionRange(unsigned long start, unsigned long end, optional DOMString direction);
};
The input element represents a typed data field, usually with a form
control to allow the user to edit the data.
The type attribute controls the data type of the element. It is an
enumerated attribute. The data type is used to select the control to use
for the input. Some data types allow either a text field or combo box
control to be used, based on the absence or presence of a list attribute
on the element. The following table lists the keywords and states for the
attribute — the keywords in the left column map to the state, data type
and control(s) in the cells on the same row.
Keyword State Data type Control type
hidden Hidden An arbitrary string n/a
text Text Text with no line breaks A text field or
combo box
search Search Text with no line breaks Search field or
combo box
tel Telephone Text with no line breaks A text field or
combo box
url URL An absolute URL A text field or
combo box
email E-mail An e-mail address or list A text field or
of e-mail addresses combo box
Text with no line breaks A text field
password Password (sensitive information) that obscures
data entry
date Date A date (year, month, day) A date control
with no time zone
A date consisting of a year
month Month and a month with no time A month control
zone
A date consisting of a
week Week week-year number and a week A week control
number with no time zone
A time (hour, minute,
time Time seconds, fractional A time control
seconds) with no time zone
A date and time (year,
Local Date and month, day, hour, minute, A date and time
datetime-local Time second, fraction of a control
second) with no timezone
offset
A text field or
number Number A numerical value combo box or
spinner control
A numerical value, with the
range Range extra semantic that the A slider control
exact value is not or similar
important
An sRGB color with 8-bit
color Color red, green, and blue A color well
components
A set of zero or more
checkbox Checkbox values from a predefined A checkbox
list
radio Radio Button An enumerated value A radio button
Zero or more files each A label and a
file File Upload with a MIME type and button
optionally a file name
An enumerated value, with
the extra semantic that it
submit Submit Button must be the last value A button
selected and initiates form
submission
A coordinate, relative to a
particular image’s size, Either a
image Image Button with the extra semantic clickable image,
that it must be the last or a button
value selected and
initiates form submission
reset Reset Button n/a A button
button Button n/a A button
The missing value default is the Text state.
Which of the accept, alt, autocomplete, checked, dirname, formaction,
formenctype, formmethod, formnovalidate, formtarget, height, list, max,
maxlength, min, minlength, multiple, pattern, placeholder, readonly,
required, size, src, step, and width content attributes, the checked,
files, valueAsDate, valueAsNumber, and list IDL attributes, the select()
method, the selectionStart, selectionEnd, and selectionDirection, IDL
attributes, the setRangeText() and setSelectionRange() methods, the
stepUp() and stepDown() methods, and the input and change events apply to
an input element depends on the state of its type attribute. The
subsections that define each type also clearly define in normative
"bookkeeping" sections which of these feature apply, and which do not
apply, to each type. The behavior of these features depends on whether
they apply or not, as defined in their various sections (q.v. for Content
attributes, for APIs, for events).
The following table is non-normative and summarizes which of those content
attributes, IDL attributes, methods, and events apply to each state:
Local
Date
and Checkbox, Reset
Hidden Text, URL, E-mail Password Time, Number Range Color Radio File Submit Image Button,
Search Telephone Date, Button Upload Button Button Button
Month,
Week,
Time
Content attributes
accept · · · · · · · · · · Yes · · ·
alt · · · · · · · · · · · · Yes ·
autocomplete · Yes Yes Yes Yes Yes Yes Yes Yes · · · · ·
checked · · · · · · · · · Yes · · · ·
dirname · Yes · · · · · · · · · · · ·
formaction · · · · · · · · · · · Yes Yes ·
formenctype · · · · · · · · · · · Yes Yes ·
formmethod · · · · · · · · · · · Yes Yes ·
formnovalidate · · · · · · · · · · · Yes Yes ·
formtarget · · · · · · · · · · · Yes Yes ·
height · · · · · · · · · · · · Yes ·
list · Yes Yes Yes · Yes Yes Yes Yes · · · · ·
max · · · · · Yes Yes Yes · · · · · ·
maxlength · Yes Yes Yes Yes · · · · · · · · ·
min · · · · · Yes Yes Yes · · · · · ·
minlength · Yes Yes Yes Yes · · · · · · · · ·
multiple · · · Yes · · · · · · Yes · · ·
pattern · Yes Yes Yes Yes · · · · · · · · ·
placeholder · Yes Yes Yes Yes · Yes · · · · · · ·
readonly · Yes Yes Yes Yes Yes Yes · · · · · · ·
required · Yes Yes Yes Yes Yes Yes · · Yes Yes · · ·
size · Yes Yes Yes Yes · · · · · · · · ·
src · · · · · · · · · · · · Yes ·
step · · · · · Yes Yes Yes · · · · · ·
width · · · · · · · · · · · · Yes ·
IDL attributes and methods
checked · · · · · · · · · Yes · · · ·
files · · · · · · · · · · Yes · · ·
value default value value value value value value value value default/on filename default default default
valueAsDate · · · · · Yes · · · · · · · ·
valueAsNumber · · · · · Yes Yes Yes · · · · · ·
list · Yes Yes Yes · Yes Yes Yes Yes · · · · ·
select() · Yes Yes† Yes Yes† Yes† Yes† · Yes† · Yes† · · ·
selectionStart · Yes Yes · Yes · · · · · · · · ·
selectionEnd · Yes Yes · Yes · · · · · · · · ·
selectionDirection · Yes Yes · Yes · · · · · · · · ·
setRangeText() · Yes Yes · Yes · · · · · · · · ·
setSelectionRange() · Yes Yes · Yes · · · · · · · · ·
stepDown() · · · · · Yes Yes Yes · · · · · ·
stepUp() · · · · · Yes Yes Yes · · · · · ·
Events
input event · Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes · · ·
change event · Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes · · ·
† If the control has no text field, the select() method results in a
no-op, with no "InvalidStateError" DOMException.
Some states of the type attribute define a value sanitization algorithm.
Each input element has a value, which is exposed by the value IDL
attribute. Some states define an algorithm to convert a string to a
number, an algorithm to convert a number to a string, an algorithm to
convert a string to a Date object, and an algorithm to convert a Date
object to a string, which are used by max, min, step, valueAsDate,
valueAsNumber, stepDown(), and stepUp().
Each input element has a boolean dirty value flag. The dirty value flag
must be initially set to false when the element is created, and must be
set to true whenever the user interacts with the control in a way that
changes the value. (It is also set to true when the value is
programmatically changed, as described in the definition of the value IDL
attribute.)
The value content attribute gives the default value of the input element.
When the value content attribute is added, set, or removed, if the
control’s dirty value flag is false, the user agent must set the value of
the element to the value of the value content attribute, if there is one,
or the empty string otherwise, and then run the current value sanitization
algorithm, if one is defined.
Each input element has a checkedness, which is exposed by the checked IDL
attribute.
Each input element has a boolean dirty checkedness flag. When it is true,
the element is said to have a dirty checkedness. The dirty checkedness
flag must be initially set to false when the element is created, and must
be set to true whenever the user interacts with the control in a way that
changes the checkedness.
The checked content attribute is a boolean attribute that gives the
default checkedness of the input element. When the checked content
attribute is added, if the control does not have dirty checkedness, the
user agent must set the checkedness of the element to true; when the
checked content attribute is removed, if the control does not have dirty
checkedness, the user agent must set the checkedness of the element to
false.
The reset algorithm for input elements is to set the dirty value flag and
dirty checkedness flag back to false, set the value of the element to the
value of the value content attribute, if there is one, or the empty string
otherwise, set the checkedness of the element to true if the element has a
checked content attribute and false if it does not, empty the list of
selected files, and then invoke the value sanitization algorithm, if the
type attribute’s current state defines one.
Each input element can be mutable. Except where otherwise specified, an
input element is always mutable. Similarly, except where otherwise
specified, the user agent should not allow the user to modify the
element’s value or checkedness.
When an input element is disabled, it is not mutable.
The readonly attribute can also in some cases (e.g., for the Date state,
but not the Checkbox state) stop an input element from being mutable.
The cloning steps for input elements must propagate the value, dirty value
flag, checkedness, and dirty checkedness flag from the node being cloned
to the copy.
----------------------------------------------------------------------
When an input element is first created, the element’s rendering and
behavior must be set to the rendering and behavior defined for the type
attribute’s state, and the value sanitization algorithm, if one is defined
for the type attribute’s state, must be invoked.
When an input element’s type attribute changes state, the user agent must
run the following steps:
1. If the previous state of the element’s type attribute put the value
IDL attribute in the value mode, and the element’s value is not the
empty string, and the new state of the element’s type attribute puts
the value IDL attribute in either the default mode or the default/on
mode, then set the element’s value content attribute to the element’s
value.
2. Otherwise, if the previous state of the element’s type attribute put
the value IDL attribute in any mode other than the value mode, and the
new state of the element’s type attribute puts the value IDL attribute
in the value mode, then set the value of the element to the value of
the value content attribute, if there is one, or the empty string
otherwise, and then set the control’s dirty value flag to false.
3. Otherwise, if the previous state of the element’s type attribute put
the value IDL attribute in any mode other than the filename mode, and
the new state of the element’s type attribute puts the value IDL
attribute in the filename mode, then set the value of the element to
the empty string.
4. Update the element’s rendering and behavior to the new state’s.
5. Signal a type change for the element. (The Radio Button state uses
this, in particular.)
6. Invoke the value sanitization algorithm, if one is defined for the
type attribute’s new state.
----------------------------------------------------------------------
The name attribute represents the element’s name. The dirname attribute
controls how the element’s directionality is submitted. The disabled
attribute is used to make the control non-interactive and to prevent its
value from being submitted. The form attribute is used to explicitly
associate the input element with its form owner. The autofocus attribute
controls focus. The autocomplete attribute controls how the user agent
provides autofill behavior.
The indeterminate IDL attribute must initially be set to false. On
getting, it must return the last value it was set to. On setting, it must
be set to the new value. It has no effect except for changing the
appearance of checkbox controls.
The accept, alt, max, min, multiple, pattern, placeholder, required, size,
src, and step IDL attributes must reflect the respective content
attributes of the same name. The dirName IDL attribute must reflect the
dirname content attribute. The readOnly IDL attribute must reflect the
readonly content attribute. The defaultChecked IDL attribute must reflect
the checked content attribute. The defaultValue IDL attribute must reflect
the value content attribute.
The type IDL attribute must reflect the respective content attribute of
the same name, limited to only known values. The maxLength IDL attribute
must reflect the maxlength content attribute, limited to only non-negative
numbers. The minLength IDL attribute must reflect the minlength content
attribute, limited to only non-negative numbers.
The IDL attributes width and height must return the rendered width and
height of the image, in CSS pixels, if an image is being rendered, and is
being rendered to a visual medium; or else the intrinsic width and height
of the image, in CSS pixels, if an image is available but not being
rendered to a visual medium; or else 0, if no image is available. When the
input element’s type attribute is not in the Image Button state, then no
image is available. [CSS-2015]
On setting, they must act as if they reflected the respective content
attributes of the same name.
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 select(), selectionStart, selectionEnd,
selectionDirection, setRangeText(), and setSelectionRange() methods and
IDL attributes expose the element’s text selection. The autofocus,
disabled, form, and name IDL attributes are part of the element’s forms
API.
4.10.5.1. States of the type attribute
4.10.5.1.1. Hidden state (type=hidden)
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
When an input element’s type attribute is in the Hidden state, the rules
in this section apply.
The input element represents a value that is not intended to be examined
or manipulated by the user.
Constraint validation: If an input element’s type attribute is in the
Hidden state, it is barred from constraint validation.
If the name attribute is present and has a value that is a case-sensitive
match for the string "_charset_", then the element’s value attribute must
be omitted.
The value IDL attribute applies to this element and is in mode default.
The following content attributes must not be specified and do not apply to
the element: accept, alt, autocomplete, checked, dirname, formaction,
formenctype, formmethod, formnovalidate, formtarget, height, list, max,
maxlength, min, minlength, multiple, pattern, placeholder, readonly,
required, size, src, step, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, list, selectionStart, selectionEnd, selectionDirection,
valueAsDate, and valueAsNumber IDL attributes; select(), setRangeText(),
setSelectionRange(), stepDown(), and stepUp() methods.
The input and change events do not apply.
4.10.5.1.2. Text (type=text) state and Search state (type=search)
Allowed ARIA role attribute values:
textbox, searchbox with no list attribute (default - do not set)
or with a list attribute: combobox (default - do not set).
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
When an input element’s type attribute is in the Text state or the Search
state, the rules in this section apply.
The input element represents a one line plain text edit control for the
element’s value.
The difference between the Text state and the Search state is primarily
stylistic: on platforms where search fields are distinguished from regular
text fields, the Search state might result in an appearance consistent
with the platform’s search fields rather than appearing like a regular
text field.
If the element is mutable, its value should be editable by the user. User
agents must not allow users to insert U+000A LINE FEED (LF) or U+000D
CARRIAGE RETURN (CR) characters into the element’s value.
If the element is mutable, the user agent should allow the user to change
the writing direction of the element, setting it either to a left-to-right
writing direction or a right-to-left writing direction. If the user does
so, the user agent must then run the following steps:
1. Set the element’s dir attribute to "ltr" if the user selected a
left-to-right writing direction, and "rtl" if the user selected a
right-to-left writing direction.
2. Queue a task to fire a simple event that bubbles named input at the
input element.
The value attribute, if specified, must have a value that contains no
U+000A LINE FEED (LF) or U+000D CARRIAGE RETURN (CR) characters.
The value sanitization algorithm is as follows: Strip line breaks from the
value.
The following common input element content attributes, IDL attributes, and
methods apply to the element: autocomplete, dirname, list, maxlength,
minlength, pattern, placeholder, readonly, required, and size content
attributes; list, selectionStart, selectionEnd, selectionDirection, and
value IDL attributes; select(), setRangeText(), and setSelectionRange()
methods.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, formaction, formenctype, formmethod,
formnovalidate, formtarget, height, max, min, multiple, src, step, and
width.
The following IDL attributes and methods do not apply to the element:
checked, files, valueAsDate, and valueAsNumber IDL attributes; stepDown()
and stepUp() methods.
4.10.5.1.3. Telephone state (type=tel)
Allowed ARIA role attribute values:
textbox with no list attribute (default - do not set) or with a
list attribute: combobox (default - do not set).
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
When an input element’s type attribute is in the Telephone state, the
rules in this section apply.
The input element represents a control for editing a telephone number
given in the element’s value.
If the element is mutable, its value should be editable by the user. User
agents may change the spacing and, with care, the punctuation of values
that the user enters. User agents must not allow users to insert U+000A
LINE FEED (LF) or U+000D CARRIAGE RETURN (CR) characters into the
element’s value.
The value attribute, if specified, must have a value that contains no
U+000A LINE FEED (LF) or U+000D CARRIAGE RETURN (CR) characters.
The value sanitization algorithm is as follows: Strip line breaks from the
value.
Unlike the URL and E-mail types, the Telephone type does not enforce a
particular syntax. This is intentional; in practice, telephone number
fields tend to be free-form fields, because there are a wide variety of
valid phone numbers. Systems that need to enforce a particular format are
encouraged to use the pattern attribute or the setCustomValidity() method
to hook into the client-side validation mechanism.
The following common input element content attributes, IDL attributes, and
methods apply to the element: autocomplete, list, maxlength, minlength,
pattern, placeholder, readonly, required, and size content attributes;
list, selectionStart, selectionEnd, selectionDirection, and value IDL
attributes; select(), setRangeText(), and setSelectionRange() methods.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, max, min, multiple, src,
step, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, valueAsDate, and valueAsNumber IDL attributes; stepDown()
and stepUp() methods.
4.10.5.1.4. URL state (type=url)
Allowed ARIA role attribute values:
textbox with no list attribute (default - do not set) or with a
list attribute: combobox (default - do not set).
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
When an input element’s type attribute is in the URL state, the rules in
this section apply.
The input element represents a control for editing a single absolute URL
given in the element’s value.
If the element is mutable, the user agent should allow the user to change
the URL represented by its value. User agents may allow the user to set
the value to a string that is not a valid absolute URL, but may also or
instead automatically escape characters entered by the user so that the
value is always a valid absolute URL (even if that isn’t the actual value
seen and edited by the user in the interface). User agents should allow
the user to set the value to the empty string. User agents must not allow
users to insert U+000A LINE FEED (LF) or U+000D CARRIAGE RETURN (CR)
characters into the value.
The value attribute, if specified and not empty, must have a value that is
a valid URL potentially surrounded by spaces that is also an absolute URL.
The value sanitization algorithm is as follows: Strip line breaks from the
value, then strip leading and trailing white space from the value.
Constraint validation: While the value of the element is neither the empty
string nor a valid absolute URL, the element is suffering from a type
mismatch.
The following common input element content attributes, IDL attributes, and
methods apply to the element: autocomplete, list, maxlength, minlength,
pattern, placeholder, readonly, required, and size content attributes;
list, selectionStart, selectionEnd, selectionDirection, and value IDL
attributes; select(), setRangeText(), and setSelectionRange() methods.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, max, min, multiple, src,
step, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, valueAsDate, and valueAsNumber IDL attributes; stepDown()
and stepUp() methods.
If a document contained the following markup:
...and the user had typed "www.w3", and the user agent had also found that
the user had visited https://www.w3.org/Consortium/#membership and
https://www.w3.org/TR/XForms/ in the recent past, then the rendering might
look like this:
A text box with an icon on the left followed by the text "www.w3" and a
cursor, with a drop down button on the right hand side; with, below, a
drop down box containing a list of six URLs on the left, with the first
four having grayed out labels on the right; and a scroll bar to the right
of the drop down box, indicating further values are available.
The first four URLs in this sample consist of the four URLs in the
author-specified list that match the text the user has entered, sorted in
some user agent-defined manner (maybe by how frequently the user refers to
those URLs). Note how the user agent is using the knowledge that the
values are URLs to allow the user to omit the scheme part and perform
intelligent matching on the domain name.
The last two URLs (and probably many more, given the scrollbar’s
indications of more values being available) are the matches from the user
agent’s session history data. This data is not made available to the page
DOM. In this particular case, the user agent has no titles to provide for
those values.
4.10.5.1.5. E-mail state (type=email)
Allowed ARIA role attribute values:
textbox with no list attribute (default - do not set) or with a
list attribute: combobox (default - do not set).
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
When an input element’s type attribute is in the E-mail state, the rules
in this section apply.
User agents may transform the values for display and editing.
User agents should convert punycode in the domain labels of the value to
Internationalized Domain Names in the display, and vice versa.
User agents should allow the user to set the value to a string that is not
a valid e-mail address or valid e-mail address list.
User agents must not allow users to insert U+000A LINE FEED (LF) or U+000D
CARRIAGE RETURN (CR) characters into the value.
Some aspects of how the E-mail state operates depend on whether the
multiple attribute is present.
When the multiple attribute is not specified on the element
The input element represents a control for editing an e-mail
address given in the element’s value.
If the element is mutable, the user agent should allow the user to
change the e-mail address represented by its value, including
setting the value to the empty string.
The user agent should act in a manner consistent with expecting
the user to provide a single e-mail address.
Constraint validation: While the user interface is representing
input that the user agent cannot convert to punycode, the control
is suffering from bad input.
The value attribute, if specified and not empty, must have a value
that is a single valid e-mail address.
The value sanitization algorithm is as follows: Strip line breaks
from the value, then strip leading and trailing white space from
the value.
Constraint validation: While the value of the element is neither
the empty string nor a single valid e-mail address, the element is
suffering from a type mismatch.
When the multiple attribute is specified on the element
The input element represents a control for adding, removing, and
editing a list of e-mail addresses given in the element’s values.
If the element is mutable, the user agent should allow the user to
add, remove, and edit the e-mail addresses represented by its
values, including removing all addresses and setting the value to
the empty string.
User agents may allow the user to set any individual value in the
list of values to a string that is not a valid e-mail address, but
must not allow users to set any individual value to a string
containing U+002C COMMA (,) as well as the U+000A LINE FEED (LF),
or U+000D CARRIAGE RETURN (CR) characters.
Constraint validation: While the user interface describes a
situation where an individual value contains a U+002C COMMA (,) or
is representing input that the user agent cannot convert to
punycode, the control is suffering from bad input.
Whenever the user changes the element’s values, the user agent
must run the following steps:
1. Let latest values be a copy of the element’s values.
2. Strip leading and trailing white space from each value in
latest values.
3. Let the element’s value be the result of concatenating all
the values in latest values, separating each value from the
next by a single U+002C COMMA character (,), maintaining the
list’s order.
The value attribute, if specified, must have a value that is a
valid e-mail address list.
The value sanitization algorithm is as follows:
1. Split on commas the element’s value, strip leading and
trailing white space from each resulting token, if any, and
let the element’s values be the (possibly empty) resulting
list of (possibly empty) tokens, maintaining the original
order.
2. Let the element’s value be the result of concatenating the
element’s values, separating each value from the next by a
single U+002C COMMA character (,), maintaining the list’s
order.
Constraint validation: While the value of the element is not a
valid e-mail address list, the element is suffering from a type
mismatch.
When the multiple attribute is set or removed, the user agent must run the
value sanitization algorithm.
A valid e-mail address is a string that matches the email production of
the following ABNF, the character set for which is Unicode. This ABNF
implements the extensions described in RFC 1123. [ABNF] [RFC5322]
[RFC1034] [RFC1123]
email = 1*( atext / "." ) "@" label *( "." label )
label = let-dig [ [ ldh-str ] let-dig ]
; limited to a length of 63 characters by RFC 1034 section 3.5
atext = ALPHA / DIGIT / ; Printable US-ASCII characters not including "specials".
"!" / "#" / ;
"$" / "%" / ; This is as defined in RFC 5322 section 3.2.3
"&" / "'" /
"*" / "+" / "-" / "/" / "=" / "?" /
"^" / "_" / "`" / "{" / "|" / "}" / "~"
let-dig = ALPHA / DIGIT ; defined in RFC 1034 section 3.5
ldh-str = let-dig / "-" ; defined in RFC 1034 section 3.5
This requirement is a willful violation of RFC 5322.
This syntax allows e-mail addresses with Internationalised Domain Names
using punycode, such as example@xn--d1acpjx3f.xn--p1ai. A user agent
should represent that in the user interface as example@яндекс.рф
This syntax does not allow valid internationalised email addresses, such
as 我買@屋企.香港. See also Issue 845.
The following JavaScript- and Perl-compatible regular expression is an
implementation of the above definition.
/^[a-zA-Z0-9.!#$%&'*+\/=?^_`{|}~-]+@[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(?:\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*$/
A valid e-mail address list is a set of comma-separated tokens, where each
token is itself a valid e-mail address. To obtain the list of tokens from
a valid e-mail address list, an implementation must split the string on
commas.
The following common input element content attributes, IDL attributes, and
methods apply to the element: autocomplete, list, maxlength, minlength,
multiple, pattern, placeholder, readonly, required, and size content
attributes; list and value IDL attributes; select() method.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, max, min, src, step, and
width.
The following IDL attributes and methods do not apply to the element:
checked, files, selectionStart, selectionEnd, selectionDirection,
valueAsDate, and valueAsNumber IDL attributes; select(), setRangeText(),
setSelectionRange(), stepDown() and stepUp() methods.
4.10.5.1.6. Password state (type=password)
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
When an input element’s type attribute is in the Password state, the rules
in this section apply.
The input element represents a one line plain text edit control for the
element’s value. The user agent should obscure the value so that people
other than the user cannot see it.
If the element is mutable, its value should be editable by the user. User
agents must not allow users to insert U+000A LINE FEED (LF) or U+000D
CARRIAGE RETURN (CR) characters into the value.
The value attribute, if specified, must have a value that contains no
U+000A LINE FEED (LF) or U+000D CARRIAGE RETURN (CR) characters.
The value sanitization algorithm is as follows: Strip line breaks from the
value.
The following common input element content attributes, IDL attributes, and
methods apply to the element: autocomplete, maxlength, minlength, pattern,
placeholder, readonly, required, and size content attributes;
selectionStart, selectionEnd, selectionDirection, and value IDL
attributes; select(), setRangeText(), and setSelectionRange() methods.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, list, max, min, multiple,
src, step, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, list, valueAsDate, and valueAsNumber IDL attributes;
stepDown() and stepUp() methods.
4.10.5.1.7. Date state (type=date)
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
When an input element’s type attribute is in the Date state, the rules in
this section apply.
The input element represents a control for setting the element’s value to
a string representing a specific date.
date values represent a "floating" time and do not include time zone
information. Care is needed when converting values of this type to or from
date data types in JavaScript and other programming languages. In many
cases, an implicit time-of-day and time zone are used to create a global
("incremental") time (an integer value that represents the offset from
some arbitrary epoch time). Processing or conversion of these values,
particularly across time zones, can change the value of the date itself.
[TIMEZONE]
If the element is mutable, the user agent should allow the user to change
the date represented by its value, as obtained by parsing a date from it.
User agents must not allow the user to set the value to a non-empty string
that is not a valid date string. If the user agent provides a user
interface for selecting a date, then the value must be set to a valid date
string representing the user’s selection. User agents should allow the
user to set the value to the empty string.
Constraint validation: While the user interface describes input that the
user agent cannot convert to a valid date string, the control is suffering
from bad input.
See §4.10.1.7 Date, time, and number formats for a discussion of the
difference between the input format and submission format for date, time,
and number form controls, and the implementation notes regarding
localization of form controls.
The value attribute, if specified and not empty, must have a value that is
a valid date string.
The value sanitization algorithm is as follows: If the value of the
element is not a valid date string, then set it to the empty string
instead.
The min attribute, if specified, must have a value that is a valid date
string. The max attribute, if specified, must have a value that is a valid
date string.
The step attribute is expressed in days. The step scale factor is
86,400,000 (which converts the days to milliseconds, which is the base
unit of comparison for the conversion algorithms below). The default step
is 1 day.
When the element is suffering from a step mismatch, the user agent may
round the element’s value to the nearest date for which the element would
not suffer from a step mismatch.
The algorithm to convert a string to a number, given a string input, is as
follows: If parsing a date from input results in an error, then return an
error; otherwise, return the number of milliseconds elapsed from midnight
UTC on the morning of 1970-01-01 (the time represented by the value
"1970-01-01T00:00:00.0Z") to midnight UTC on the morning of the parsed
date, ignoring leap seconds.
The algorithm to convert a number to a string, given a number input, is as
follows: Return a valid date string that represents the date that, in UTC,
is current input milliseconds after midnight UTC on the morning of
1970-01-01 (the time represented by the value "1970-01-01T00:00:00.0Z").
The algorithm to convert a string to a Date object, given a string input,
is as follows: If parsing a date from input results in an error, then
return an error; otherwise, return a new Date object representing midnight
UTC on the morning of the parsed date.
The algorithm to convert a Date object to a string, given a Date object
input, is as follows: Return a valid date string that represents the date
current at the time represented by input in the UTC time zone.
See the note on historical dates in the Local Date and Time state section.
The following common input element content attributes, IDL attributes, and
methods apply to the element: autocomplete, list, max, min, readonly,
required, and step content attributes; list, value, valueAsDate, and
valueAsNumber IDL attributes; select(), stepDown(), and stepUp() methods.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, maxlength, minlength,
multiple, pattern, placeholder, size, src, and width.
The following IDL attributes and methods do not apply to the element:
checked, selectionStart, selectionEnd, and selectionDirection IDL
attributes; setRangeText(), and setSelectionRange() methods.
4.10.5.1.8. Month state (type=month)
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
When an input element’s type attribute is in the Month state, the rules in
this section apply.
The input element represents a control for setting the element’s value to
a string representing a specific month.
If the element is mutable, the user agent should allow the user to change
the month represented by its value, as obtained by parsing a month from
it. User agents must not allow the user to set the value to a non-empty
string that is not a valid month string. If the user agent provides a user
interface for selecting a month, then the value must be set to a valid
month string representing the user’s selection. User agents should allow
the user to set the value to the empty string.
Constraint validation: While the user interface describes input that the
user agent cannot convert to a valid month string, the control is
suffering from bad input.
See §4.10.1.7 Date, time, and number formats for a discussion of the
difference between the input format and submission format for date, time,
and number form controls, and the implementation notes regarding
localization of form controls.
The value attribute, if specified and not empty, must have a value that is
a valid month string.
The value sanitization algorithm is as follows: If the value of the
element is not a valid month string, then set it to the empty string
instead.
The min attribute, if specified, must have a value that is a valid month
string. The max attribute, if specified, must have a value that is a valid
month string.
The step attribute is expressed in months. The step scale factor is 1
(units of whole months are the base unit of comparison for the conversion
algorithms below). The default step is 1 month.
When the element is suffering from a step mismatch, the user agent may
round the element’s value to the nearest month for which the element would
not suffer from a step mismatch.
The algorithm to convert a string to a number, given a string input, is as
follows: If parsing a month from input results in an error, then return an
error; otherwise, return the number of months between January 1970 and the
parsed month.
The algorithm to convert a number to a string, given a number input, is as
follows: Return a valid month string that represents the month that has
input months between it and January 1970.
The algorithm to convert a string to a Date object, given a string input,
is as follows: If parsing a month from input results in an error, then
return an error; otherwise, return a new Date object representing midnight
UTC on the morning of the first day of the parsed month.
The algorithm to convert a Date object to a string, given a Date object
input, is as follows: Return a valid month string that represents the
month current at the time represented by input in the UTC time zone.
The following common input element content attributes, IDL attributes, and
methods apply to the element: autocomplete, list, max, min, readonly,
required, and step content attributes; list, value, valueAsDate, and
valueAsNumber IDL attributes; select(), stepDown(), and stepUp() methods.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, maxlength, minlength,
multiple, pattern, placeholder, size, src, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, selectionStart, selectionEnd, and selectionDirection IDL
attributes; setRangeText(), and setSelectionRange() methods.
4.10.5.1.9. Week state (type=week)
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
When an input element’s type attribute is in the Week state, the rules in
this section apply.
The input element represents a control for setting the element’s value to
a string representing a specific week beginning on a Monday, at midnight
UTC.
If the element is mutable, the user agent should allow the user to change
the week represented by its value, as obtained by parsing a week from it.
User agents must not allow the user to set the value to a non-empty string
that is not a valid week string. If the user agent provides a user
interface for selecting a week, then the value must be set to a valid week
string representing the user’s selection. User agents should allow the
user to set the value to the empty string.
Constraint validation: While the user interface describes input that the
user agent cannot convert to a valid week string, the control is suffering
from bad input.
See §4.10.1.7 Date, time, and number formats for a discussion of the
difference between the input format and submission format for date, time,
and number form controls, and the implementation notes regarding
localization of form controls.
The value attribute, if specified and not empty, must have a value that is
a valid week string.
The value sanitization algorithm is as follows: If the value of the
element is not a valid week string, then set it to the empty string
instead.
The min attribute, if specified, must have a value that is a valid week
string. The max attribute, if specified, must have a value that is a valid
week string.
The step attribute is expressed in weeks. The step scale factor is
604,800,000 (which converts the weeks to milliseconds, which is the base
unit of comparison for the conversion algorithms below). The default step
is 1 week. The default step base is -259,200,000 (the start of week
1970-W01 which is the Monday 3 days before 1970-01-01).
When the element is suffering from a step mismatch, the user agent may
round the element’s value to the nearest week for which the element would
not suffer from a step mismatch.
The algorithm to convert a string to a number, given a string input, is as
follows: If parsing a week string from input results in an error, then
return an error; otherwise, return the number of milliseconds elapsed from
midnight UTC on the morning of 1970-01-01 (the time represented by the
value "1970-01-01T00:00:00.0Z") to midnight UTC on the morning of the
Monday of the parsed week, ignoring leap seconds.
The algorithm to convert a number to a string, given a number input, is as
follows: Return a valid week string that represents the week that, in UTC,
is current input milliseconds after midnight UTC on the morning of
1970-01-01 (the time represented by the value "1970-01-01T00:00:00.0Z").
The algorithm to convert a string to a Date object, given a string input,
is as follows: If parsing a week from input results in an error, then
return an error; otherwise, return a new Date object representing midnight
UTC on the morning of the Monday of the parsed week.
The algorithm to convert a Date object to a string, given a Date object
input, is as follows: Return a valid week string that represents the week
current at the time represented by input in the UTC time zone.
The following common input element content attributes, IDL attributes, and
methods apply to the element: autocomplete, list, max, min, readonly,
required, and step content attributes; list, value, valueAsDate, and
valueAsNumber IDL attributes; select(), stepDown(), and stepUp() methods.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, maxlength, minlength,
multiple, pattern, placeholder, size, src, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, selectionStart, selectionEnd, and selectionDirection IDL
attributes; setRangeText(), and setSelectionRange() methods.
4.10.5.1.10. Time state (type=time)
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
When an input element’s type attribute is in the Time state, the rules in
this section apply.
The input element represents a control for setting the element’s value to
a string representing a specific time.
If the element is mutable, the user agent should allow the user to change
the time represented by its value, as obtained by parsing a time from it.
User agents must not allow the user to set the value to a non-empty string
that is not a valid time string. If the user agent provides a user
interface for selecting a time, then the value must be set to a valid time
string representing the user’s selection. User agents should allow the
user to set the value to the empty string.
Constraint validation: While the user interface describes input that the
user agent cannot convert to a valid time string, the control is suffering
from bad input.
See §4.10.1.7 Date, time, and number formats for a discussion of the
difference between the input format and submission format for date, time,
and number form controls, and the implementation notes regarding
localization of form controls.
The value attribute, if specified and not empty, must have a value that is
a valid time string.
The value sanitization algorithm is as follows: If the value of the
element is not a valid time string, then set it to the empty string
instead.
The form control has a periodic domain.
The min attribute, if specified, must have a value that is a valid time
string. The max attribute, if specified, must have a value that is a valid
time string.
The step attribute is expressed in seconds. The step scale factor is 1000
(which converts the seconds to milliseconds, which is the base unit of
comparison for the conversion algorithms below). The default step is 60
seconds.
When the element is suffering from a step mismatch, the user agent may
round the element’s value to the nearest time for which the element would
not suffer from a step mismatch.
The algorithm to convert a string to a number, given a string input, is as
follows: If parsing a time from input results in an error, then return an
error; otherwise, return the number of milliseconds elapsed from midnight
to the parsed time on a day with no time changes.
The algorithm to convert a number to a string, given a number input, is as
follows: Return a valid time string that represents the time that is input
milliseconds after midnight on a day with no time changes.
The algorithm to convert a string to a Date object, given a string input,
is as follows: If parsing a time from input results in an error, then
return an error; otherwise, return a new Date object representing the
parsed time in UTC on 1970-01-01.
The algorithm to convert a Date object to a string, given a Date object
input, is as follows: Return a valid time string that represents the UTC
time component that is represented by input.
The following common input element content attributes, IDL attributes, and
methods apply to the element: autocomplete, list, max, min, readonly,
required, and step content attributes; list, value, valueAsDate, and
valueAsNumber IDL attributes; select(), stepDown(), and stepUp() methods.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, maxlength, minlength,
multiple, pattern, placeholder, size, src, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, selectionStart, selectionEnd, and selectionDirection IDL
attributes; setRangeText(), and setSelectionRange() methods.
4.10.5.1.11. Local Date and Time state (type=datetime-local)
When an input element’s type attribute is in the Local Date and Time
state, the rules in this section apply.
The input element represents a control for setting the element’s value to
a string representing a Local Date and Time, with no time-zone offset
information.
If the element is mutable, the user agent should allow the user to change
the date and time represented by its value, as obtained by parsing a date
and time from it. User agents must not allow the user to set the value to
a non-empty string that is not a valid normalized global date and time
string. If the user agent provides a user interface for selecting a Local
Date and Time, then the value must be set to a valid normalized global
date and time string representing the user’s selection. User agents should
allow the user to set the value to the empty string.
Constraint validation: While the user interface describes input that the
user agent cannot convert to a valid normalized global date and time
string, the control is suffering from bad input.
The Local Date and Time state and other date-related states are not useful
for vague values, and are only useful for dates ranging from recent
history through a few thousand years. For example, "one millisecond after
the big bang", "the Ides of March, 44BC", "the early part of the Jurassic
period", or "a winter around 250 BCE", and many other expressions of time
cannot be sensibly expressed in HTML form states.
For the input of dates before the introduction of the Gregorian calendar,
authors are encouraged to not use the Local Date and Time state (and the
other date- and time-related states described in subsequent sections), as
user agents are not required to support converting dates and times from
earlier periods to the Gregorian calendar, and asking users to do so
manually puts an undue burden on users. (This is complicated by the manner
in which the Gregorian calendar was phased in, which occurred at different
times in different countries, ranging from partway through the 16th
century all the way to early in the 20th.) Instead, authors are encouraged
to provide fine-grained input controls using the select element and input
elements with the Number state.
See §4.10.1.7 Date, time, and number formats for a discussion of the
difference between the input format and submission format for date, time,
and number form controls, and the implementation notes regarding
localization of form controls.
Applications need to use care when working with datetime-local values,
since most date time objects (in languages such as JavaScript or
server-side languages such as Java) use incremental time values tied to
the UTC time zone. Implicit conversion of a floating time value to an
incremental time can cause the actual value used to be different from user
expectations. For more information, refer to: Working with Time Zones
§floating
The value attribute, if specified and not empty, must have a value that is
a valid floating date and time string.
The value sanitization algorithm is as follows: If the value of the
element is a valid floating date and time string, then set it to a valid
normalized floating date and time string representing the same date and
time; otherwise, set it to the empty string instead.
The min attribute, if specified, must have a value that is a valid
floating date and time string. The max attribute, if specified, must have
a value that is a valid floating date and time string.
The step attribute is expressed in seconds. The step scale factor is 1000
(which converts the seconds to milliseconds, which is the base unit of
comparison for the conversion algorithms below). The default step is 60
seconds.
When the element is suffering from a step mismatch, the user agent may
round the element’s value to the nearest floating date and time for which
the element would not suffer from a step mismatch.
The algorithm to convert a string to a number, given a string input, is as
follows: If parsing a date and time from input results in an error, then
return an error; otherwise, return the number of milliseconds elapsed from
midnight on the morning of 1970-01-01 (the time represented by the value
"1970-01-01T00:00:00.0") to the parsed floating date and time, ignoring
leap seconds.
The algorithm to convert a number to a string, given a number input, is as
follows: Return a valid normalized floating date and time string that
represents the date and time that is input milliseconds after midnight on
the morning of 1970-01-01 (the time represented by the value
"1970-01-01T00:00:00.0").
The following common input element content attributes, IDL attributes, and
methods apply to the element: autocomplete, list, max, min, readonly,
required, and step content attributes; list, value, and valueAsNumber IDL
attributes; select(), stepDown(), and stepUp() methods.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, maxlength, minlength,
multiple, pattern, placeholder, size, src, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, selectionStart, selectionEnd, selectionDirection, and
valueAsDate IDL attributes; setRangeText(), and setSelectionRange()
methods.
The following example shows part of a flight booking application. The
application uses an input element with its type attribute set to
datetime-local, and it then interprets the given date and time in the time
zone of the selected airport.
Destination
Airport:
Departure time:
4.10.5.1.12. Number state (type=number)
Allowed ARIA role attribute values:
spinbutton (default - do not set).
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
When an input element’s type attribute is in the Number state, the rules
in this section apply.
The input element represents a control for setting the element’s value to
a string representing a number.
If the element is mutable, the user agent should allow the user to change
the number represented by its value, as obtained from applying the rules
for parsing floating-point number values to it. User agents must not allow
the user to set the value to a non-empty string that is not a valid
floating-point number. If the user agent provides a user interface for
selecting a number, then the value must be set to the best representation
of the number representing the user’s selection as a floating-point
number. User agents should allow the user to set the value to the empty
string.
Constraint validation: While the user interface describes input that the
user agent cannot convert to a valid floating-point number, the control is
suffering from bad input.
This specification does not define what user interface user agents are to
use; user agent vendors are encouraged to consider what would best serve
their users' needs. For example, when displaying a page in the Persian or
Arabic languages, a form might support Persian and Arabic style numeric
input (converting it to the format required for submission as described
above). Similarly, a user agent showing a page in a French locale might
display the value with apostrophes between thousands and commas before the
decimals, and allow the user to enter a value in that manner, internally
converting it to the submission format described above.
See §4.10.1.7 Date, time, and number formats for a discussion of the
difference between the input format and submission format for date, time,
and number form controls, and the implementation notes regarding
localization of form controls.
The value attribute, if specified and not empty, must have a value that is
a valid floating-point number.
The value sanitization algorithm is as follows: If the value of the
element is not a valid floating-point number, then set it to the empty
string instead.
The min attribute, if specified, must have a value that is a valid
floating-point number. The max attribute, if specified, must have a value
that is a valid floating-point number.
The step scale factor is 1. The default step is 1 (allowing only integers
to be selected by the user, unless the step base has a non-integer value).
When the element is suffering from a step mismatch, the user agent may
round the element’s value to the nearest number for which the element
would not suffer from a step mismatch. If there are two such numbers, user
agents are encouraged to pick the one nearest positive infinity.
The algorithm to convert a string to a number, given a string input, is as
follows: If applying the rules for parsing floating-point number values to
input results in an error, then return an error; otherwise, return the
resulting number.
The algorithm to convert a number to a string, given a number input, is as
follows: Return a valid floating-point number that represents input.
The following common input element content attributes, IDL attributes, and
methods apply to the element: autocomplete, list, max, min, placeholder,
readonly, required, and step content attributes; list, value, and
valueAsNumber IDL attributes; select(), stepDown(), and stepUp() methods.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, maxlength, minlength,
multiple, pattern, size, src, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, selectionStart, selectionEnd, selectionDirection, and
valueAsDate IDL attributes; setRangeText(), and setSelectionRange()
methods.
Here is an example of using a numeric input control:
How much do you want to charge? $
As described above, a user agent might support numeric input in the user’s
local format, converting it to the format required for submission as
described above. This might include handling grouping separators (as in
"872,000,000,000") and various decimal separators (such as "3,99" vs
"3.99") or using local digits (such as those in Arabic, Devanagari,
Persian, and Thai).
The type=number state is not appropriate for input that happens to only
consist of numbers but isn’t strictly speaking a number. For example, it
would be inappropriate for credit card numbers or US postal codes. A
simple way of determining whether to use type=number is to consider
whether it would make sense for the input control to have a spinbox
interface (e.g., with "up" and "down" arrows). Getting a credit card
number wrong by 1 in the last digit isn’t a minor mistake, it’s as wrong
as getting every digit incorrect. So it would not make sense for the user
to select a credit card number using "up" and "down" buttons. When a
spinbox interface is not appropriate, type=text is probably the right
choice (possibly with a pattern attribute).
4.10.5.1.13. Range state (type=range)
Allowed ARIA role attribute values:
slider (default - do not set).
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
When an input element’s type attribute is in the Range state, the rules in
this section apply.
The input element represents a control for setting the element’s value to
a string representing a number, but with the caveat that the exact value
is not important, letting user agents provide a simpler interface than
they do for the Number state.
If the element is mutable, the user agent should allow the user to change
the number represented by its value, as obtained from applying the rules
for parsing floating-point number values to it. User agents must not allow
the user to set the value to a string that is not a valid floating-point
number. If the user agent provides a user interface for selecting a
number, then the value must be set to a best representation of the number
representing the user’s selection as a floating-point number. User agents
must not allow the user to set the value to the empty string.
Constraint validation: While the user interface describes input that the
user agent cannot convert to a valid floating-point number, the control is
suffering from bad input.
The value attribute, if specified, must have a value that is a valid
floating-point number.
The value sanitization algorithm is as follows: If the value of the
element is not a valid floating-point number, then set it to the best
representation, as a floating-point number, of the default value.
The default value is the minimum plus half the difference between the
minimum and the maximum, unless the maximum is less than the minimum, in
which case the default value is the minimum.
When the element is suffering from an underflow, the user agent must set
the element’s value to the best representation, as a floating-point
number, of the minimum.
When the element is suffering from an overflow, if the maximum is not less
than the minimum, the user agent must set the element’s value to a valid
floating-point number that represents the maximum.
When the element is suffering from a step mismatch, the user agent must
round the element’s value to the nearest number for which the element
would not suffer from a step mismatch, and which is greater than or equal
to the minimum, and, if the maximum is not less than the minimum, which is
less than or equal to the maximum, if there is a number that matches these
constraints. If two numbers match these constraints, then user agents must
use the one nearest to positive infinity.
For example, the markup
results in a range
control whose initial value is 60.
Here is an example of a range control using an autocomplete list with the
list attribute. This could be useful if there are values along the full
range of the control that are especially important, such as preconfigured
light levels or typical speed limits in a range control used as a speed
control. The following markup fragment:
...with the following style sheet applied:
input { height: 75px; width: 49px; background: #D5CCBB; color: black; }
...might render as:
A vertical slider control whose primary color is black and whose
background color is beige, with the slider having five tick marks, one
long one at each extremity, and three short ones clustered around the
midpoint.
Note how the user agent determined the orientation of the control from the
ratio of the style-sheet-specified height and width properties. The colors
were similarly derived from the style sheet. The tick marks, however, were
derived from the markup. In particular, the step attribute has not
affected the placement of tick marks, the user agent deciding to only use
the author-specified completion values and then adding longer tick marks
at the extremes.
Note also how the invalid value ++50 was completely ignored.
For another example, consider the following markup fragment:
With styles that make the control draw vertically, it might look as
follows:
A vertical slider control with two tick marks, one near the top labeled
'High', and one near the bottom labeled 'Low'.
In this state, the range and step constraints are enforced even during
user input, and there is no way to set the value to the empty string.
The min attribute, if specified, must have a value that is a valid
floating-point number. The default minimum is 0. The max attribute, if
specified, must have a value that is a valid floating-point number. The
default maximum is 100.
The step scale factor is 1. The default step is 1 (allowing only integers,
unless the min attribute has a non-integer value).
The algorithm to convert a string to a number, given a string input, is as
follows: If applying the rules for parsing floating-point number values to
input results in an error, then return an error; otherwise, return the
resulting number.
The algorithm to convert a number to a string, given a number input, is as
follows: Return the best representation, as a floating-point number, of
input.
The following common input element content attributes, IDL attributes, and
methods apply to the element: autocomplete, list, max, min, multiple, and
step content attributes; list, value, and valueAsNumber IDL attributes;
stepDown() and stepUp() methods.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, maxlength, minlength,
pattern, placeholder, readonly, required, size, src, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, selectionStart, selectionEnd, selectionDirection, and
valueAsDate IDL attributes; select(), setRangeText(), and
setSelectionRange() methods.
4.10.5.1.14. Color state (type=color)
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
When an input element’s type attribute is in the Color state, the rules in
this section apply.
The input element represents a color well control, for setting the
element’s value to a string representing a simple color.
In this state, there is always a color picked, and there is no way to set
the value to the empty string.
If the element is mutable, the user agent should allow the user to change
the color represented by its value, as obtained from applying the rules
for parsing simple color values to it. User agents must not allow the user
to set the value to a string that is not a valid lowercase simple color.
If the user agent provides a user interface for selecting a color, then
the value must be set to the result of using the rules for serializing
simple color values to the user’s selection. User agents must not allow
the user to set the value to the empty string.
Constraint validation: While the user interface describes input that the
user agent cannot convert to a valid lowercase simple color, the control
is suffering from bad input.
The value attribute, if specified and not empty, must have a value that is
a valid simple color.
The value sanitization algorithm is as follows: If the value of the
element is a valid simple color, then set it to the value of the element
in ASCII lowercase; otherwise, set it to the string "#000000".
The following common input element content attributes and IDL attributes
apply to the element: autocomplete and list content attributes; list and
value IDL attributes; select() method.
The value IDL attribute is in mode value.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, max, maxlength, min,
minlength, multiple, pattern, placeholder, readonly, required, size, src,
step, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, selectionStart, selectionEnd, selectionDirection,
valueAsDate, and valueAsNumber IDL attributes; setRangeText(),
setSelectionRange(), stepDown(), and stepUp() methods.
4.10.5.1.15. Checkbox state (type=checkbox)
Allowed ARIA role attribute values:
checkbox (default - do not set), option or switch.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
When an input element’s type attribute is in the Checkbox state, the rules
in this section apply.
The input element represents a two-state control that represents the
element’s checkedness state. If the element’s checkedness state is true,
the control represents a positive selection, and if it is false, a
negative selection. If the element’s indeterminate IDL attribute is set to
true, then the control’s selection should be obscured as if the control
was in a third, indeterminate, state.
The control is never a true tri-state control, even if the element’s
indeterminate IDL attribute is set to true. The indeterminate IDL
attribute only gives the appearance of a third state.
If the element is mutable, then: The pre-click activation steps consist of
setting the element’s checkedness to its opposite value (i.e., true if it
is false, false if it is true), and of setting the element’s indeterminate
IDL attribute to false. The canceled activation steps consist of setting
the checkedness and the element’s indeterminate IDL attribute back to the
values they had before the pre-click activation steps were run. The
activation behavior is to fire a simple event that bubbles named input at
the element and then fire a simple event that bubbles named change at the
element.
If the element is not mutable, it has no activation behavior.
Constraint validation: If the element is required and its checkedness is
false, then the element is suffering from being missing.
input . indeterminate [ = value ]
When set, overrides the rendering of checkbox controls so that the
current value is not visible.
The following common input element content attributes and IDL attributes
apply to the element: checked, and required content attributes; checked
and value IDL attributes.
The value IDL attribute is in mode default/on.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, autocomplete, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, list, max, maxlength, min,
minlength, multiple, pattern, placeholder, readonly, size, src, step, and
width.
The following IDL attributes and methods do not apply to the element:
files, list, selectionStart, selectionEnd, selectionDirection,
valueAsDate, and valueAsNumber IDL attributes; select(), setRangeText(),
setSelectionRange(), stepDown(), and stepUp() methods.
4.10.5.1.16. Radio Button state (type=radio)
Allowed ARIA role attribute values:
radio (default - do not set).
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
When an input element’s type attribute is in the Radio Button state, the
rules in this section apply.
The input element represents a control that, when used in conjunction with
other input elements, forms a radio button group in which only one control
can have its checkedness state set to true. If the element’s checkedness
state is true, the control represents the selected control in the group,
and if it is false, it indicates a control in the group that is not
selected.
The radio button group that contains an input element a also contains all
the other input elements b that fulfill all of the following conditions:
* The input element b’s type attribute is in the Radio Button state.
* Either a and b have the same form owner, or they both have no form
owner.
* Both a and b are in the same tree.
* They both have a name attribute, their name attributes are not empty,
and the value of a’s name attribute is a compatibility caseless match
for the value of b’s name attribute.
A document must not contain an input element whose radio button group
contains only that element.
When any of the following phenomena occur, if the element’s checkedness
state is true after the occurrence, the checkedness state of all the other
elements in the same radio button group must be set to false:
* The element’s checkedness state is set to true (for whatever reason).
* The element’s name attribute is set, changed, or removed.
* The element’s form owner changes.
* A type change is signalled for the element.
If the element R is mutable, then: The pre-click activation steps for R
consist of getting a reference to the element in R’s radio button group
that has its checkedness set to true, if any, and then setting R’s
checkedness to true. The canceled activation steps for R consist of
checking if the element to which a reference was obtained in the pre-click
activation steps, if any, is still in what is now R’s radio button group,
if it still has one, and if so, setting that element’s checkedness to
true; or else, if there was no such element, or that element is no longer
in R’s radio button group, or if R no longer has a radio button group,
setting R’s checkedness to false. The activation behavior for R is to fire
a simple event that bubbles named input at R and then fire a simple event
that bubbles named change at R.
If the element is not mutable, it has no activation behavior.
Constraint validation: If an element in the radio button group is
required, and all of the input elements in the radio button group have a
checkedness that is false, then the element is suffering from being
missing.
If none of the radio buttons in a radio button group are checked when they
are inserted into the document, then they will all be initially unchecked
in the interface, until such time as one of them is checked (either by the
user or by script).
The following common input element content attributes and IDL attributes
apply to the element: checked and required content attributes; checked and
value IDL attributes.
The value IDL attribute is in mode default/on.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: accept, alt, autocomplete, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, list, max, maxlength, min,
minlength, multiple, pattern, placeholder, readonly, size, src, step, and
width.
The following IDL attributes and methods do not apply to the element:
files, list, selectionStart, selectionEnd, selectionDirection,
valueAsDate, and valueAsNumber IDL attributes; select(), setRangeText(),
setSelectionRange(), stepDown(), and stepUp() methods.
4.10.5.1.17. File Upload state (type=file)
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
When an input element’s type attribute is in the File Upload state, the
rules in this section apply.
The input element represents a list of selected files, each file
consisting of a file name, a file type, and a file body (the contents of
the file).
File names must not contain path components, even in the case that a user
has selected an entire directory hierarchy or multiple files with the same
name from different directories. Path components, for the purposes of the
File Upload state, are those parts of file names that are separated by
U+005C REVERSE SOLIDUS character (\) characters.
Unless the multiple attribute is set, there must be no more than one file
in the list of selected files.
If the element is mutable, then the element’s activation behavior is to
run the following steps:
1. If the algorithm is not allowed to show a popup, then abort these
steps without doing anything else.
2. Return, but continue running these steps in parallel.
3. Optionally, wait until any prior execution of this algorithm has
terminated.
4. Display a prompt to the user requesting that the user specify some
files. If the multiple attribute is not set, there must be no more
than one file selected; otherwise, any number may be selected. Files
can be from the filesystem or created on the fly, e.g., a picture
taken from a camera connected to the user’s device.
5. Wait for the user to have made their selection.
6. Queue a task to first update the element’s selected files so that it
represents the user’s selection, then fire a simple event that bubbles
named input at the input element, and finally fire a simple event that
bubbles named change at the input element.
If the element is mutable, the user agent should allow the user to change
the files on the list in other ways also, e.g., adding or removing files
by drag-and-drop. When the user does so, the user agent must queue a task
to first update the element’s selected files so that it represents the
user’s new selection, then fire a simple event that bubbles named input at
the input element, and finally fire a simple event that bubbles named
change at the input element.
If the element is not mutable, it has no activation behavior and the user
agent must not allow the user to change the element’s selection.
Constraint validation: If the element is required and the list of selected
files is empty, then the element is suffering from being missing.
----------------------------------------------------------------------
The accept attribute may be specified to provide user agents with a hint
of what file types will be accepted.
If specified, the attribute must consist of a set of comma-separated
tokens, each of which must be an ASCII case-insensitive match for one of
the following:
The string "audio/*"
Indicates that sound files are accepted.
The string "video/*"
Indicates that video files are accepted.
The string "image/*"
Indicates that image files are accepted.
A valid MIME type with no parameters
Indicates that files of the specified type are accepted.
A string whose first character is a U+002E FULL STOP character (.)
Indicates that files with the specified file extension are
accepted.
The tokens must not be ASCII case-insensitive matches for any of the other
tokens (i.e., duplicates are not allowed). To obtain the list of tokens
from the attribute, the user agent must split the attribute value on
commas.
User agents may use the value of this attribute to display a more
appropriate user interface than a generic file picker. For instance, given
the value image/*, a user agent could offer the user the option of using a
local camera or selecting a photograph from their photo collection; given
the value audio/*, a user agent could offer the user the option of
recording a clip using a headset microphone.
User agents should prevent the user from selecting files that are not
accepted by one (or more) of these tokens.
Authors are encouraged to specify both any MIME types and any
corresponding extensions when looking for data in a specific format.
For example, consider an application that converts Microsoft Word
documents to Open Document Format files. Since Microsoft Word documents
are described with a wide variety of MIME types and extensions, the site
can list several, as follows:
The name of the file you picked is: (none)
----------------------------------------------------------------------
The following common input element content attributes and IDL attributes
apply to the element: accept, multiple, and required content attributes;
files and value IDL attributes; select() method.
The value IDL attribute is in mode filename.
The input and change events apply.
The following content attributes must not be specified and do not apply to
the element: alt, autocomplete, checked, dirname, formaction, formenctype,
formmethod, formnovalidate, formtarget, height, list, max, maxlength, min,
minlength, pattern, placeholder, readonly, size, src, step, and width.
The element’s value attribute must be omitted.
The following IDL attributes and methods do not apply to the element:
checked, list, selectionStart, selectionEnd, selectionDirection,
valueAsDate, and valueAsNumber IDL attributes; setRangeText(),
setSelectionRange(), stepDown(), and stepUp() methods.
4.10.5.1.18. Submit Button state (type=submit)
Allowed ARIA role attribute values:
button (default - do not set).
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
When an input element’s type attribute is in the Submit Button state, the
rules in this section apply.
The input element represents a button that, when activated, submits the
form. If the element has a value attribute, the button’s label must be the
value of that attribute; otherwise, it must be an implementation-defined
string that means "Submit" or some such. The element is a button,
specifically a submit button. (This is a fingerprinting vector.)
Since the default label is implementation-defined, and the width of the
button typically depends on the button’s label, the button’s width can
leak a few bits of fingerprintable information. These bits are likely to
be strongly correlated to the identity of the user agent and the user’s
locale.
If the element is mutable, then the element’s activation behavior is as
follows: if the element has a form owner, and the element’s node document
is fully active, submit the form owner from the input element; otherwise,
do nothing.
If the element is not mutable, it has no activation behavior.
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 following common input element content attributes and IDL attributes
apply to the element: formaction, formenctype, formmethod, formnovalidate,
and formtarget content attributes; value IDL attribute.
The value IDL attribute is in mode default.
The following content attributes must not be specified and do not apply to
the element: accept, alt, autocomplete, checked, dirname, height, list,
max, maxlength, min, minlength, multiple, pattern, placeholder, readonly,
required, size, src, step, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, list, selectionStart, selectionEnd, selectionDirection,
valueAsDate, and valueAsNumber IDL attributes; select(), setRangeText(),
setSelectionRange(), stepDown(), and stepUp() methods.
The input and change events do not apply.
4.10.5.1.19. Image Button state (type=image)
Allowed ARIA role attribute values:
button (default - do not set), link, or radio.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
When an input element’s type attribute is in the Image Button state, the
rules in this section apply.
The input element represents either an image from which a user can select
a coordinate and submit the form, or alternatively a button from which the
user can submit the form. The element is a button, specifically a Submit
Button.
The coordinate is sent to the server during form submission by sending two
entries for the element, derived from the name of the control but with
".x" and ".y" appended to the name with the x and y components of the
coordinate respectively.
----------------------------------------------------------------------
The image is given by the src attribute. The src attribute must be
present, and must contain a valid non-empty URL potentially surrounded by
spaces referencing a non-interactive, optionally animated, image resource
that is neither paged nor scripted.
When any of the these events occur
* the input element’s type attribute is first set to the Image Button
state (possibly when the element is first created), and the src
attribute is present
* the input element’s type attribute is changed back to the Image Button
state, and the src attribute is present, and its value has changed
since the last time the type attribute was in the Image Button state
* the input element’s type attribute is in the Image Button state, and
the src attribute is set or changed
then unless the user agent cannot support images, or its support for
images has been disabled, or the user agent only fetches images on demand,
or the src attribute’s value is the empty string, the user agent must
parse the value of the src attribute value, relative to the element’s node
document, and if that is successful, run these substeps:
1. Let request be a new request whose URL is the resulting URL string,
client is the element’s node document’s Window object’s environment
settings object, type is "image", destination is "subresource",
omit-Origin-header flag is set, credentials mode is "include", and
whose use-URL-credentials flag is set.
2. Fetch request.
Fetching the image must delay the load event of the element’s node
document until the task that is queued by the networking task source once
the resource has been fetched (defined below) has been run.
If the image was successfully obtained, with no network errors, and the
image’s type is a supported image type, and the image is a valid image of
that type, then the image is said to be available. If this is true before
the image is completely downloaded, each task that is queued by the
networking task source while the image is being fetched must update the
presentation of the image appropriately.
The user agent should apply the image sniffing rules to determine the type
of the image, with the image’s associated Content-Type headers giving the
official type. If these rules are not applied, then the type of the image
must be the type given by the image’s associated Content-Type headers.
User agents must not support non-image resources with the input element.
User agents must not run executable code embedded in the image resource.
User agents must only display the first page of a multipage resource. User
agents must not allow the resource to act in an interactive fashion, but
should honor any animation in the resource.
The task that is queued by the networking task source once the resource
has been fetched, must, if the download was successful and the image is
available, queue a task to fire a simple event named load at the input
element; and otherwise, if the fetching process fails without a response
from the remote server, or completes but the image is not a valid or
supported image, queue a task to fire a simple event named error on the
input element.
----------------------------------------------------------------------
The alt attribute provides the textual label for the button for users and
user agents who cannot use the image. The alt attribute must be present,
and must contain a non-empty string giving the label that would be
appropriate for an equivalent button if the image was unavailable.
The input element supports dimension attributes.
----------------------------------------------------------------------
If the src attribute is set, and the image is available and the user agent
is configured to display that image, then: The element represents a
control for selecting a coordinate from the image specified by the src
attribute; if the element is mutable, the user agent should allow the user
to select this coordinate, and the element’s activation behavior is as
follows: if the element has a form owner, and the element’s node document
is fully active, take the user’s selected coordinate, and submit the input
element’s form owner from the input element. If the user activates the
control without explicitly selecting a coordinate, then the coordinate
(0,0) must be assumed.
Otherwise, the element represents a submit button whose label is given by
the value of the alt attribute; if the element is mutable, then the
element’s activation behavior is as follows: if the element has a form
owner, and the element’s node document is fully active, set the selected
coordinate to (0,0), and submit the input element’s form owner from the
input element.
In either case, if the element is mutable but has no form owner or the
element’s node document is not fully active, then its activation behavior
must be to do nothing. If the element is not mutable, it has no activation
behavior.
The selected coordinate must consist of an x-component and a y-component.
The coordinates represent the position relative to the edge of the image,
with the coordinate space having the positive x direction to the right,
and the positive y direction downwards.
The x-component must be a valid integer representing a number x in the
range -(border_left+padding_left) ≤ x ≤ width+border_right+padding_right,
where width is the rendered width of the image, border_left is the width
of the border on the left of the image, padding_left is the width of the
padding on the left of the image, border_right is the width of the border
on the right of the image, and padding_right is the width of the padding
on the right of the image, with all dimensions given in CSS pixels.
The y-component must be a valid integer representing a number y in the
range -(border_top+padding_top) ≤ y ≤ height+border_bottom+padding_bottom,
where height is the rendered height of the image, border_top is the width
of the border above the image, padding_top is the width of the padding
above the image, border_bottom is the width of the border below the image,
and padding_bottom is the width of the padding below the image, with all
dimensions given in CSS pixels.
Where a border or padding is missing, its width is zero CSS pixels.
----------------------------------------------------------------------
The formaction, formenctype, formmethod, formnovalidate, and formtarget
attributes are attributes for form submission.
image . width [ = value ]
image . height [ = value ]
These attributes return the actual rendered dimensions of the
image, or zero if the dimensions are not known.
They can be set, to change the corresponding content attributes.
The following common input element content attributes and IDL attributes
apply to the element: alt, formaction, formenctype, formmethod,
formnovalidate, formtarget, height, src, and width content attributes;
value IDL attribute.
The value IDL attribute is in mode default.
The following content attributes must not be specified and do not apply to
the element: accept, autocomplete, checked, dirname, list, max, maxlength,
min, minlength, multiple, pattern, placeholder, readonly, required, size,
and step.
The element’s value attribute must be omitted.
The following IDL attributes and methods do not apply to the element:
checked, files, list, selectionStart, selectionEnd, selectionDirection,
valueAsDate, and valueAsNumber IDL attributes; select(), setRangeText(),
setSelectionRange(), stepDown(), and stepUp() methods.
The input and change events do not apply.
Many aspects of this state’s behavior are similar to the behavior of the
img element. Readers are encouraged to read that section, where many of
the same requirements are described in more detail.
Take the following form:
If the user clicked on the image at coordinate (127,40) then the URL used
to submit the form would be "process.cgi?where.x=127&where.y=40".
(In this example, it’s assumed that for users who don’t see the map, and
who instead just see a button labeled "Show location list", clicking the
button will cause the server to show a list of locations to pick from
instead of the map.)
4.10.5.1.20. Reset Button state (type=reset)
Allowed ARIA role attribute values:
button (default - do not set).
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
When an input element’s type attribute is in the Reset Button state, the
rules in this section apply.
The input element represents a button that, when activated, resets the
form. If the element has a value attribute, the button’s label must be the
value of that attribute; otherwise, it must be an implementation-defined
string that means "Reset" or some such. The element is a button. (This is
a fingerprinting vector.)
Since the default label is implementation-defined, and the width of the
button typically depends on the button’s label, the button’s width can
leak a few bits of fingerprintable information. These bits are likely to
be strongly correlated to the identity of the user agent and the user’s
locale.
If the element is mutable, then the element’s activation behavior, if the
element has a form owner and the element’s node document is fully active,
is to reset the form owner; otherwise, it is to do nothing.
If the element is not mutable, it has no activation behavior.
Constraint validation: The element is barred from constraint validation.
The value IDL attribute applies to this element and is in mode default.
The following content attributes must not be specified and do not apply to
the element: accept, alt, autocomplete, checked, dirname, formaction,
formenctype, formmethod, formnovalidate, formtarget, height, list, max,
maxlength, min, minlength, multiple, pattern, placeholder, readonly,
required, size, src, step, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, list, selectionStart, selectionEnd, selectionDirection,
valueAsDate, and valueAsNumber IDL attributes; select(), setRangeText(),
setSelectionRange(), stepDown(), and stepUp() methods.
The input and change events do not apply.
4.10.5.1.21. Button state (type=button)
Allowed ARIA role attribute values:
button (default - do not set), link, radio or switch.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
When an input element’s type attribute is in the Button state, the rules
in this section apply.
The input element represents a button with no default behavior. A label
for the button must be provided in the value attribute, though it may be
the empty string. If the element has a value attribute, the button’s label
must be the value of that attribute; otherwise, it must be the empty
string. The element is a button.
If the element is mutable, the element’s activation behavior is to do
nothing.
If the element is not mutable, it has no activation behavior.
Constraint validation: The element is barred from constraint validation.
The value IDL attribute applies to this element and is in mode default.
The following content attributes must not be specified and do not apply to
the element: accept, alt, autocomplete, checked, dirname, formaction,
formenctype, formmethod, formnovalidate, formtarget, height, list, max,
maxlength, min, minlength, multiple, pattern, placeholder, readonly,
required, size, src, step, and width.
The following IDL attributes and methods do not apply to the element:
checked, files, list, selectionStart, selectionEnd, selectionDirection,
valueAsDate, and valueAsNumber IDL attributes; select(), setRangeText(),
setSelectionRange(), stepDown(), and stepUp() methods.
The input and change events do not apply.
4.10.5.2. Implementation notes regarding localization of form controls
This section is non-normative.
The formats shown to the user in date, time, and number controls is
independent of the format used for form submission.
Browsers should use user interfaces that present locale-affected formats
such as dates, times, and numbers according to the conventions of either
the locale implied by the input element’s language or the user’s preferred
locale. Using the page’s locale will ensure consistency with page-provided
data.
For example, it would be confusing to users if an American English page
claimed that a Cirque De Soleil show was going to be showing on 02/03, but
their browser, configured to use the British English locale, only showed
the date 03/02 in the ticket purchase date picker. Using the page’s locale
would at least ensure that the date was presented in the same format
everywhere. (There’s still a risk that the user would end up arriving a
month late, of course, but there’s only so much that can be done about
such cultural differences...)
4.10.5.3. Common input element attributes
These attributes only apply to an input element if its type attribute is
in a state whose definition declares that the attribute applies. When an
attribute doesn’t apply to an input element, user agents must ignore the
attribute, regardless of the requirements and definitions below.
4.10.5.3.1. The maxlength and minlength attributes
The maxlength attribute, when it applies, is a form control maxlength
attribute controlled by the input element’s dirty value flag.
The minlength attribute, when it applies, is a form control minlength
attribute controlled by the input element’s dirty value flag.
If the input element has a maximum allowed value length, then the
code-unit length of the value of the element’s value attribute must be
equal to or less than the element’s maximum allowed value length.
The following extract shows how a messaging client’s text entry could be
arbitrarily restricted to a fixed number of characters, thus forcing any
conversation through this medium to be terse and discouraging intelligent
discourse.
What are you doing?
Here, a password is given a minimum length:
Username:
Password:
4.10.5.3.2. The size attribute
The size attribute gives the number of characters that, in a visual
rendering, the user agent is to allow the user to see while editing the
element’s value.
The size attribute, if specified, must have a value that is a valid
non-negative integer greater than zero.
If the attribute is present, then its value must be parsed using the rules
for parsing non-negative integers, and if the result is a number greater
than zero, then the user agent should ensure that at least that many
characters are visible.
The size IDL attribute is limited to only non-negative numbers greater
than zero and has a default value of 20.
4.10.5.3.3. The readonly attribute
The readonly attribute is a boolean attribute that controls whether or not
the user can edit the form control. When specified, the element is not
mutable.
Constraint validation: If the readonly attribute is specified on an input
element, the element is barred from constraint validation.
The difference between disabled and readonly is that read-only controls
are still focusable, so the user can still select the text and interact
with it, whereas disabled controls are entirely non-interactive. Only text
controls can be made read-only.
In the following example, the existing product identifiers cannot be
modified, but they are still displayed as part of the form, for
consistency with the row representing a new product (where the identifier
is not yet filled in).
4.10.5.3.4. The required attribute
The required attribute is a boolean attribute. When specified, the element
is required.
Constraint validation: If the element is required, and its value IDL
attribute applies and is in the mode value, and the element is mutable,
and the element’s value is the empty string, then the element is suffering
from being missing.
The following form has two required fields, one for an e-mail address and
one for a password. It also has a third field that is only considered
valid if the user types the same password in the password field and this
third field.
Create new account
For radio buttons, the required attribute is satisfied if any of the radio
buttons in the group is selected. Thus, in the following example, any of
the radio buttons can be checked, not just the one marked as required:
Did the movie pass the Bechdel test?
To avoid confusion as to whether a radio button group is required or not,
authors are encouraged to specify the attribute on all the radio buttons
in a group. Indeed, in general, authors are encouraged to avoid having
radio button groups that do not have any initially checked controls in the
first place, as this is a state that the user cannot return to, and is
therefore generally considered a poor user interface.
4.10.5.3.5. The multiple attribute
The multiple attribute is a boolean attribute that indicates whether the
user is to be allowed to specify more than one value.
The following extract shows how an e-mail client’s "Cc" field could accept
multiple e-mail addresses.
Cc:
If the user had, amongst many friends in their user contacts database, two
friends "Arthur Dent" (with address "art@example.net") and "Adam Josh"
(with address "adamjosh@example.net"), then, after the user has typed "a",
the user agent might suggest these two e-mail addresses to the user.
Form control group containing 'Send', 'Save now' and 'Discard' buttons, a
'To:' combo box with an 'a' displayed in the text box and 2 list items
below.
The page could also link in the user’s contacts database from the site:
Cc:
...
Suppose the user had entered "bob@example.net" into this text field, and
then started typing a second e-mail address starting with "a". The user
agent might show both the two friends mentioned earlier, as well as the
"astrophy" and "astronomy" values given in the datalist element.
Form control group containing 'send', 'save now' and 'discard' buttons
and a 'To:' combo box with 'bob@example.net,a' displayed in the text box
and 4 list items below.
The following extract shows how an e-mail client’s "Attachments" field
could accept multiple files for upload.
Attachments:
4.10.5.3.6. The pattern attribute
The pattern attribute specifies a regular expression against which the
control’s value, or, when the multiple attribute applies and is set, the
control’s values, are to be checked.
If specified, the attribute’s value must match the JavaScript Pattern
production. [ECMA-262]
If an input element has a pattern attribute specified, and the attribute’s
value, when compiled as a JavaScript regular expression with only the "u"
flag specified, compiles successfully, then the resulting regular
expression is the element’s compiled pattern regular expression. If the
element has no such attribute, or if the value doesn’t compile
successfully, then the element has no compiled pattern regular expression.
[ECMA-262]
If the value doesn’t compile successfully, user agents are encouraged to
log this fact in a developer console, to aid debugging.
Constraint validation: If the element’s value is not the empty string, and
either the element’s multiple attribute is not specified or it does not
apply to the input element given its type attribute’s current state, and
the element has a compiled pattern regular expression but that regular
expression does not match the entirety of the element’s value, then the
element is suffering from a pattern mismatch.
Constraint validation: If the element’s value is not the empty string, and
the element’s multiple attribute is specified and applies to the input
element, and the element has a compiled pattern regular expression but
that regular expression does not match the entirety of each of the
element’s values, then the element is suffering from a pattern mismatch.
The compiled pattern regular expression, when matched against a string,
must have its start anchored to the start of the string and its end
anchored to the end of the string.
This implies that the regular expression language used for this attribute
is the same as that used in JavaScript, except that the pattern attribute
is matched against the entire value, not just any subset (somewhat as if
it implied a ^(?: at the start of the pattern and a )$ at the end).
When an input element has a pattern attribute specified, authors should
provide a description of the pattern in text near the control. Authors may
also include a title attribute to give a description of the pattern. User
agents may use the contents of this attribute, if it is present, when
informing the user that the pattern is not matched, or at any other
suitable time, such as in a tooltip or read out by assistive technology
when the control gains focus.
Relying on the title attribute for the visual display of text content is
currently discouraged as many user agents do not expose the attribute in
an accessible manner as required by this specification (e.g., requiring a
pointing device such as a mouse to cause a tooltip to appear, which
excludes keyboard-only users and touch-only users, such as anyone with a
modern phone or tablet).
For example, the following snippet:
Part number:
...could cause the user agent to display an alert such as:
A part number is a digit followed by three uppercase letters.You cannot submit this form when the field is incorrect.
When a control has a pattern attribute, the title attribute, if used, must
describe the pattern. Additional information could also be included, so
long as it assists the user in filling in the control. Otherwise,
assistive technology would be impaired.
For instance, if the title attribute contained the caption of the control,
assistive technology could end up saying something like The text you have
entered does not match the required pattern. Birthday, which is not
useful.
user agents may still show the title in non-error situations (for example,
as a tooltip when hovering over the control), so authors should be careful
not to word titles as if an error has necessarily occurred.
4.10.5.3.7. The min and max attributes
Some form controls can have explicit constraints applied limiting the
allowed range of values that the user can provide. Normally, such a range
would be linear and continuous. A form control can have a periodic domain,
however, in which case the form control’s broadest possible range is
finite, and authors can specify explicit ranges within it that span the
boundaries.
Specifically, the broadest range of a type=time control is midnight to
midnight (24 hours), and authors can set both continuous linear ranges
(such as 9pm to 11pm) and discontinuous ranges spanning midnight (such as
11pm to 1am).
The min and max attributes indicate the allowed range of values for the
element.
Their syntax is defined by the section that defines the type attribute’s
current state.
If the element has a min attribute, and the result of applying the
algorithm to convert a string to a number to the value of the min
attribute is a number, then that number is the element’s minimum;
otherwise, if the type attribute’s current state defines a default
minimum, then that is the minimum; otherwise, the element has no minimum.
The min attribute also defines the step base.
If the element has a max attribute, and the result of applying the
algorithm to convert a string to a number to the value of the max
attribute is a number, then that number is the element’s maximum;
otherwise, if the type attribute’s current state defines a default
maximum, then that is the maximum; otherwise, the element has no maximum.
If the element does not have a periodic domain, the max attribute’s value
(the maximum) must not be less than the min attribute’s value (its
minimum).
If an element that does not have a periodic domain has a maximum that is
less than its minimum, then so long as the element has a value, it will
either be suffering from an underflow or suffering from an overflow.
An element has a reversed range if it has a periodic domain and its
maximum is less than its minimum.
An element has range limitations if it has a defined minimum or a defined
maximum.
How these range limitations apply depends on whether the element has a
multiple attribute.
If the element does not have a multiple attribute specified or if the
multiple attribute does not apply
Constraint validation: When the element has a minimum and does not
have a reversed range, and the result of applying the algorithm to
convert a string to a number to the string given by the element’s
value is a number, and the number obtained from that algorithm is
less than the minimum, the element is suffering from an underflow.
Constraint validation: When the element has a maximum and does not
have a reversed range, and the result of applying the algorithm to
convert a string to a number to the string given by the element’s
value is a number, and the number obtained from that algorithm is
more than the maximum, the element is suffering from an overflow.
Constraint validation: When an element has a reversed range, and
the result of applying the algorithm to convert a string to a
number to the string given by the element’s value is a number, and
the number obtained from that algorithm is more than the maximum
and less than the minimum, the element is simultaneously suffering
from an underflow and suffering from an overflow.
If the element does have a multiple attribute specified and the multiple
attribute does apply
Constraint validation: When the element has a minimum, and the
result of applying the algorithm to convert a string to a number
to any of the strings in the element’s values is a number that is
less than the minimum, the element is suffering from an underflow.
Constraint validation: When the element has a maximum, and the
result of applying the algorithm to convert a string to a number
to any of the strings in the element’s values is a number that is
more than the maximum, the element is suffering from an overflow.
The following date control limits input to dates that are before the
1980s:
Homepage:
Other URLs from the user’s history might show also; this is up to the user
agent.
This example demonstrates how to design a form that uses the
autocompletion list feature while still degrading usefully in legacy user
agents.
If the autocompletion list is merely an aid, and is not important to the
content, then simply using a datalist element with children option
elements is enough. To prevent the values from being rendered in legacy
user agents, they need to be placed inside the value attribute instead of
inline.
Enter a breed:
However, if the values need to be shown in legacy user agents, then
fallback content can be placed inside the datalist element, as follows:
Enter a breed:
or select one from the list:
(none selected)
Abyssinian
Alpaca
The fallback content will only be shown in user agents that don’t support
datalist. The options, on the other hand, will be detected by all user
agents, even though they are not children of the datalist element.
Note that if an option element used in a datalist is selected, it will be
selected by default by legacy user agents (because it affects the select),
but it will not have any effect on the input element in user agents that
support datalist.
4.10.5.3.10. The placeholder attribute
The placeholder attribute represents a short hint (a word or short phrase)
intended to aid the user with data entry when the control has no value. A
hint could be a sample value or a brief description of the expected
format. The attribute, if specified, must have a value that contains no
U+000A LINE FEED (LF) or U+000D CARRIAGE RETURN (CR) characters.
The placeholder attribute should not be used as a replacement for a label.
For a longer hint or other advisory text, place the text next to the
control.
Use of the placeholder attribute as a replacement for a label can reduce
the accessibility and usability of the control for a range of users
including older users and users with cognitive, mobility, fine motor skill
or vision impairments. While the hint given by the control’s label is
shown at all times, the short hint given in the placeholder attribute is
only shown before the user enters a value. Furthermore, placeholder text
may be mistaken for a pre-filled value, and as commonly implemented the
default color of the placeholder text provides insufficient contrast and
the lack of a separate visible label reduces the size of the hit region
available for setting focus on the control.
User agents should present this hint to the user, after having stripped
line breaks from it, when the element’s value is the empty string,
especially if the control is not focused.
If a user agent normally doesn’t show this hint to the user when the
control is focused, then the user agent should nonetheless show the hint
for the control if it was focused as a result of the autofocus attribute,
since in that case the user will not have had an opportunity to examine
the control before focusing it.
Here is an example of a mail configuration user interface that uses the
placeholder attribute:
Mail Account
Name:
Address:
Password:
Description:
In situations where the control’s content has one directionality but the
placeholder needs to have a different directionality, Unicode’s
bidirectional-algorithm formatting characters can be used in the attribute
value:
Show hint
4.10.7. The select element
Categories:
Flow content.
Phrasing content.
Interactive content.
listed, labelable, submittable, resettable, and reassociateable
form-associated element.
Palpable content.
Contexts in which this element can be used:
Where phrasing content is expected.
Content model:
Zero or more option, optgroup, and script-supporting elements.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
autocomplete - Hint for form autofill feature
autofocus - Automatically focus the form control when the page is
loaded
disabled - Whether the form control is disabled
form - Associates the control with a form element
multiple - Whether to allow multiple values
name - Name of form control to use for §4.10.21 Form submission
and in the form.elements API
required - Whether the control is required for §4.10.21 Form
submission
size - Size of the control
Allowed ARIA role attribute values:
(with NO multiple attribute and NO size attribute having value
greater than 1) combobox or (with a multiple attribute or a size
attribute having value greater than 1) listbox otherwise None.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
interface HTMLSelectElement : HTMLElement {
attribute DOMString autocomplete;
attribute boolean autofocus;
attribute boolean disabled;
readonly attribute HTMLFormElement? form;
attribute boolean multiple;
attribute DOMString name;
attribute boolean _required;
attribute unsigned long size;
readonly attribute DOMString type;
[SameObject] readonly attribute HTMLOptionsCollection options;
attribute unsigned long length;
getter Element? item(unsigned long index);
HTMLOptionElement? namedItem(DOMString name);
void add((HTMLOptionElement or HTMLOptGroupElement) element, optional (HTMLElement or long)? before = null);
void remove(); // ChildNode overload
void remove(long index);
setter void (unsigned long index, HTMLOptionElement? option);
[SameObject] readonly attribute HTMLCollection selectedOptions;
attribute long selectedIndex;
attribute DOMString value;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
[SameObject] readonly attribute NodeList labels;
};
The select element represents a control for selecting amongst a set of
options.
The multiple attribute is a boolean attribute. If the attribute is
present, then the select element represents a control for selecting zero
or more options from the list of options. If the attribute is absent, then
the select element represents a control for selecting a single option from
the list of options.
The size attribute gives the number of options to show to the user. The
size attribute, if specified, must have a value that is a valid
non-negative integer greater than zero.
The display size of a select element is the result of applying the rules
for parsing non-negative integers to the value of element’s size
attribute, if it has one and parsing it is successful. If applying those
rules to the attribute’s value is not successful, or if the size attribute
is absent, then the element’s display size is 4 if the element’s multiple
content attribute is present, and 1 otherwise.
The list of options for a select element consists of all the option
element children of the select element, and all the option element
children of all the optgroup element children of the select element, in
tree order.
The required attribute is a boolean attribute. When specified, the user
will be required to select a value before submitting the form.
If a select element has a required attribute specified, does not have a
multiple attribute specified, and has a display size of 1; and if the
value of the first option element in the select element’s list of options
(if any) is the empty string, and that option element’s parent node is the
select element (and not an optgroup element), then that option is the
select element’s placeholder label option.
If a select element has a required attribute specified, does not have a
multiple attribute specified, and has a display size of 1, then the select
element must have a placeholder label option.
In practice, the requirement stated in the paragraph above can only apply
when a select element does not have a sizes attribute with a value greater
than 1.
Constraint validation: If the element has its required attribute
specified, and either none of the option elements in the select element’s
list of options have their selectedness set to true, or the only option
element in the select element’s list of options with its selectedness set
to true is the placeholder label option, then the element is suffering
from being missing.
If the multiple attribute is absent, and the element is not disabled, then
the user agent should allow the user to pick an option element in its list
of options that is itself not disabled. Upon this option element being
picked (either through a click, or through unfocusing the element after
changing its value, or through any other mechanism), and before the
relevant user interaction event is queued (e.g., before the click event),
the user agent must set the selectedness of the picked option element to
true, set its dirtiness to true, and then send select update
notifications.
If the multiple attribute is absent, whenever an option element in the
select element’s list of options has its selectedness set to true, and
whenever an option element with its selectedness set to true is added to
the select element’s list of options, the user agent must set the
selectedness of all the other option elements in its list of options to
false.
If the multiple attribute is absent and the element’s display size is
greater than 1, then the user agent should also allow the user to request
that the option whose selectedness is true, if any, be unselected. Upon
this request being conveyed to the user agent, and before the relevant
user interaction event is queued (e.g., before the click event), the user
agent must set the selectedness of that option element to false, set its
dirtiness to true, and then send select update notifications.
If nodes are inserted or nodes are removed causing the list of options to
gain or lose one or more option elements, or if an option element in the
list of options asks for a reset, then, if the select element’s multiple
attribute is absent, the user agent must run the first applicable set of
steps from the following list:
If the select element’s display size is 1, and no option elements in the
select element’s list of options have their selectedness set to true
Set the selectedness of the first option element in the list of
options in tree order that is not disabled, if any, to true.
If two or more option elements in the select element’s list of options
have their selectedness set to true
Set the selectedness of all but the last option element with its
selectedness set to true in the list of options in tree order to
false.
If the multiple attribute is present, and the element is not disabled,
then the user agent should allow the user to toggle the selectedness of
the option elements in its list of options that are themselves not
disabled. Upon such an element being toggled (either through a click, or
any other mechanism), and before the relevant user interaction event is
queued (e.g., before a related click event), the selectedness of the
option element must be changed (from true to false or false to true), the
dirtiness of the element must be set to true, and the user agent must send
select update notifications.
When the user agent is to send select update notifications, queue a task
to first fire a simple event that bubbles named input at the select
element, and then fire a simple event that bubbles named change at the
select element, using the user interaction task source as the task source.
If the JavaScript execution context stack was not empty when the user
agent was to send select update notifications, then the resulting input
and change events must not be trusted.
The reset algorithm for select elements is to go through all the option
elements in the element’s list of options, set their selectedness to true
if the option element has a selected attribute, and false otherwise, set
their dirtiness to false, and then have the option elements ask for a
reset.
The form attribute is used to explicitly associate the select 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 autofocus attribute controls
focus. The autocomplete attribute controls how the user agent provides
autofill behavior.
A select element that is not disabled is mutable.
select . type
Returns "select-multiple" if the element has a multiple attribute,
and "select-one" otherwise.
select . options
Returns an HTMLOptionsCollection of the list of options.
select . length [ = value ]
Returns the number of elements in the list of options.
When set to a smaller number, truncates the number of option
elements in the select.
When set to a greater number, adds new blank option elements to
the select.
element = select . item(index)
select[index]
Returns the item with index index from the list of options. The
items are sorted in tree order.
element = select . namedItem(name)
Returns the first item with ID or name name from the list of
options.
Returns null if no element with that ID could be found.
select . add(element [, before ] )
Inserts element before the node given by before.
The before argument can be a number, in which case element is
inserted before the item with that number, or an element from the
list of options, in which case element is inserted before that
element.
If before is omitted, null, or a number out of range, then element
will be added at the end of the list.
This method will throw a HierarchyRequestError exception if
element is an ancestor of the element into which it is to be
inserted.
select . selectedOptions
Returns an HTMLCollection of the list of options that are
selected.
select . selectedIndex [ = value ]
Returns the index of the first selected item, if any, or -1 if
there is no selected item.
Can be set, to change the selection.
select . value [ = value ]
Returns the value of the first selected item, if any, or the empty
string if there is no selected item.
Can be set, to change the selection.
The type IDL attribute, on getting, must return the string "select-one" if
the multiple attribute is absent, and the string "select-multiple" if the
multiple attribute is present.
The options IDL attribute must return an HTMLOptionsCollection rooted at
the select node, whose filter matches the elements in the list of options.
The options collection is also mirrored on the HTMLSelectElement object.
The supported property indices at any instant are the indices supported by
the object returned by the options attribute at that instant.
The length IDL attribute must return the number of nodes represented by
the options collection. On setting, it must act like the attribute of the
same name on the options collection.
The item(index) method must return the value returned by the method of the
same name on the options collection, when invoked with the same argument.
The namedItem(name) method must return the value returned by the method of
the same name on the options collection, when invoked with the same
argument.
When the user agent is to set the value of a new indexed property for a
given property index index to a new value value, it must instead set the
value of a new indexed property with the given property index index to the
new value value on the options collection.
Similarly, the add() method must act like its namesake method on that same
options collection.
The remove() method must act like its namesake method on that same options
collection when it has arguments, and like its namesake method on the
ChildNode interface implemented by the HTMLSelectElement ancestor
interface Element when it has no arguments.
The selectedOptions IDL attribute must return an HTMLCollection rooted at
the select node, whose filter matches the elements in the list of options
that have their selectedness set to true.
The selectedIndex IDL attribute, on getting, must return the index of the
first option element in the list of options in tree order that has its
selectedness set to true, if any. If there isn’t one, then it must return
-1.
On setting, the selectedIndex attribute must set the selectedness of all
the option elements in the list of options to false, and then the option
element in the list of options whose index is the given new value, if any,
must have its selectedness set to true and its dirtiness set to true.
This can result in no element having a selectedness set to true even in
the case of the select element having no multiple attribute and a display
size of 1.
The value IDL attribute, on getting, must return the value of the first
option element in the list of options in tree order that has its
selectedness set to true, if any. If there isn’t one, then it must return
the empty string.
On setting, the value attribute must set the selectedness of all the
option elements in the list of options to false, and then the first option
element in the list of options, in tree order, whose value is equal to the
given new value, if any, must have its selectedness set to true and its
dirtiness set to true.
This can result in no element having a selectedness set to true even in
the case of the select element having no multiple attribute and a display
size of 1.
The multiple, required, and size IDL attributes must reflect the
respective content attributes of the same name. The size IDL attribute has
a default value of zero.
For historical reasons, the default value of the size IDL attribute does
not return the actual size used, which, in the absence of the size content
attribute, is either 1 or 4 depending on the presence of the multiple
attribute.
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 autofocus, disabled, form, and name IDL
attributes are part of the element’s forms API.
The following example shows how a select element can be used to offer the
user with a set of options from which the user can select a single option.
The default option is preselected.
Select unit type:
Miner
Puffer
Snipey
Max
Firebot
When there is no default option, a value that provides instructions or a
hint (placeholder option) can be used instead:
Select unit type
Miner
Puffer
Snipey
Max
Firebot
Here, the user is offered a set of options from which he can select any
number. By default, all five options are selected.
Select unit types to enable on this map:
Miner
Puffer
Snipey
Max
Firebot
Sometimes, a user has to select one or more items. This example shows such
an interface.
Select the songs from that you would like on your Act II Mix Tape:
It Sucks to Be Me (Reprize)
There is Life Outside Your Apartment
The More You Ruv Someone
Schadenfreude
I Wish I Could Go Back to College
The Money Song
School for Monsters
The Money Song (Reprize)
There’s a Fine, Fine Line (Reprize)
What Do You Do With a B.A. in English? (Reprize)
For Now
4.10.8. The datalist element
Categories:
Flow content.
Phrasing content.
Contexts in which this element can be used:
Where phrasing content is expected.
Content model:
Either: phrasing content.
Or: Zero or more option and script-supporting elements.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
Allowed ARIA role attribute values:
listbox (default - do not set).
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
interface HTMLDataListElement : HTMLElement {
[SameObject] readonly attribute HTMLCollection options;
};
The datalist element represents a set of option elements that represent
predefined options for other controls. In the rendering, the datalist
element represents nothing and it, along with its children, should be
hidden.
The datalist element can be used in two ways. In the simplest case, the
datalist element has just option element children.
Sex:
In the more elaborate case, the datalist element can be given contents
that are to be displayed for down-level clients that don’t support
datalist. In this case, the option elements are provided inside a select
element inside the datalist element.
Sex:
or select from the list:
Female
Male
The datalist element is hooked up to an input element using the list
attribute on the input element.
Each option element that is a descendant of the datalist element, that is
not disabled, and whose value is a string that isn’t the empty string,
represents a suggestion. Each suggestion has a value and a label.
datalist . options
Returns an HTMLCollection of the option elements of the datalist
element.
The options IDL attribute must return an HTMLCollection rooted at the
datalist node, whose filter matches option elements.
Constraint validation: If an element has a datalist element ancestor, it
is barred from constraint validation.
4.10.9. The optgroup element
Categories:
None.
Contexts in which this element can be used:
As a child of a select element.
Content model:
Zero or more option and script-supporting elements.
Tag omission in text/html:
An optgroup element’s end tag may be omitted if the optgroup
element is immediately followed by another optgroup element, or if
there is no more content in the parent element.
Content attributes:
Global attributes
disabled - Whether the form control is disabled
label - User-visible label
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
DOM interface:
interface HTMLOptGroupElement : HTMLElement {
attribute boolean disabled;
attribute DOMString label;
};
The optgroup element represents a group of option elements with a common
label.
The element’s group of option elements consists of the option elements
that are children of the optgroup element.
When showing option elements in select elements, user agents should show
the option elements of such groups as being related to each other and
separate from other option elements.
The disabled content attribute is a boolean attribute and can be used to
disable a group of option elements together.
The label content attribute must be specified. Its value gives the name of
the group, for the purposes of the user interface. User agents should use
this attribute’s value when labeling the group of option elements in a
select element.
The disabled and label IDL attributes must reflect the respective content
attributes of the same name.
There is no way to select an optgroup element. Only option elements can be
selected. An optgroup element merely provides a label for a group of
option elements.
The following snippet shows how a set of lessons from three courses could
be offered in a select drop-down widget:
4.10.10. The option element
Categories:
None.
Contexts in which this element can be used:
As a child of a select element.
As a child of a datalist element.
As a child of an optgroup element.
Content model:
If the element has a label attribute and a value attribute:
Nothing.
If the element has a label attribute but no value attribute: Text.
If the element has no label attribute: and is not a child of a
datalist element: Text that is not inter-element white space.
If the element has no label attribute and is a child of a datalist
element: Text.
Tag omission in text/html:
An option element’s end tag may be omitted if the option element
is immediately followed by another option element, or if it is
immediately followed by an optgroup element, or if there is no
more content in the parent element.
Content attributes:
Global attributes
disabled - Whether the form control is disabled
label - User-visible label
selected - Whether the option is selected by default
value - Value to be used for §4.10.21 Form submission
Allowed ARIA role attribute values:
option (default - do not set) or separator.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
[NamedConstructor=Option(optional DOMString text = "", optional DOMString value, optional boolean defaultSelected = false, optional boolean selected = false)]
interface HTMLOptionElement : HTMLElement {
attribute boolean disabled;
readonly attribute HTMLFormElement? form;
attribute DOMString label;
attribute boolean defaultSelected;
attribute boolean selected;
attribute DOMString value;
attribute DOMString text;
readonly attribute long index;
};
The option element represents an option in a select element or as part of
a list of suggestions in a datalist element.
In certain circumstances described in the definition of the select
element, an option element can be a select element’s placeholder label
option. A placeholder label option does not represent an actual option,
but instead represents a label for the select control.
The disabled content attribute is a boolean attribute. An option element
is disabled if its disabled attribute is present or if it is a child of an
optgroup element whose disabled attribute is present.
An option element that is disabled must prevent any click events that are
queued on the user interaction task source from being dispatched on the
element.
The label content attribute provides a label for the element. The label of
an option element is the value of the label content attribute, if there is
one and its value is not the empty string, or, otherwise, the value of the
element’s text IDL attribute if its value is not the empty string.
The label content attribute, if specified, must not be empty.
The value content attribute provides a value for element. The value of an
option element is the value of the value content attribute, if there is
one, or, if there is not, the value of the element’s text IDL attribute
(which may be the empty string).
The selected content attribute is a boolean attribute. It represents the
default selectedness of the element.
The dirtiness of an option element is a boolean state, initially false. It
controls whether adding or removing the selected content attribute has any
effect.
The selectedness of an option element is a boolean state, initially false.
Except where otherwise specified, when the element is created, its
selectedness must be set to true if the element has a selected attribute.
Whenever an option element’s selected attribute is added, if its dirtiness
is false, its selectedness must be set to true. Whenever an option
element’s selected attribute is removed, if its dirtiness is false, its
selectedness must be set to false.
The Option() constructor, when called with three or fewer arguments,
overrides the initial state of the selectedness state to always be false
even if the third argument is true (implying that a selected attribute is
to be set). The fourth argument can be used to explicitly set the initial
selectedness state when using the constructor.
A select element whose multiple attribute is not specified must not have
more than one descendant option element with its selected attribute set.
An option element’s index is the number of option elements that are in the
same list of options but that come before it in tree order. If the option
element is not in a list of options, then the option element’s index is
zero.
option . selected
Returns true if the element is selected, and false otherwise.
Can be set, to override the current state of the element.
option . index
Returns the index of the element in its select element’s options
list.
option . form
Returns the element’s form element, if any, or null otherwise.
option . text
Same as textContent, except that spaces are collapsed and script
elements are skipped.
option = new Option()( [ text [, value [, defaultSelected [, selected ] ]
] ] )
Returns a new option element.
The text argument sets the contents of the element.
The value argument sets the value attribute.
The defaultSelected argument sets the selected attribute.
The selected argument sets whether or not the element is selected.
If it is omitted, even if the defaultSelected argument is true,
the element is not selected.
The disabled IDL attribute must reflect the content attribute of the same
name. The defaultSelected IDL attribute must reflect the selected content
attribute.
The label IDL attribute, on getting, if there is a label content
attribute, must return that attribute’s value; otherwise, it must return
the element’s label. On setting, the element’s label content attribute
must be set to the new value.
The value IDL attribute, on getting, must return the element’s value. On
setting, the element’s value content attribute must be set to the new
value.
The selected IDL attribute, on getting, must return true if the element’s
selectedness is true, and false otherwise. On setting, it must set the
element’s selectedness to the new value, set its dirtiness to true, and
then cause the element to ask for a reset.
The index IDL attribute must return the element’s index.
The text IDL attribute, on getting, must return the result of stripping
and collapsing white space from the child text content of the option
element, in tree order, excluding any that are descendants of descendants
of the option element that are themselves script elements in the HTML
namespace or script elements in the SVG namespace.
On setting, the text attribute must act as if the textContent IDL
attribute on the element had been set to the new value.
The form IDL attribute’s behavior depends on whether the option element is
in a select element or not. If the option has a select element as its
parent, or has an optgroup element as its parent and that optgroup element
has a select element as its parent, then the form IDL attribute must
return the same value as the form IDL attribute on that select element.
Otherwise, it must return null.
A constructor is provided for creating HTMLOptionElement objects (in
addition to the factory methods from DOM such as createElement()):
Option(text, value, defaultSelected, selected). When invoked as a
constructor, it must return a new HTMLOptionElement object (a new option
element). If the first argument is not the empty string, the new object
must have as its only child a Text node whose data is the value of that
argument. Otherwise, it must have no children. If the value argument is
present, the new object must have a value attribute set with the value of
the argument as its value. If the defaultSelected argument is true, the
new object must have a selected attribute set with no value. If the
selected argument is true, the new object must have its selectedness set
to true; otherwise the selectedness must be set to false, even if the
defaultSelected argument is true. The element’s node document must be the
active document of the browsing context of the Window object on which the
interface object of the invoked constructor is found.
4.10.11. The textarea element
Categories:
Flow content.
Phrasing content.
Interactive content.
listed, labelable, submittable, resettable, and reassociateable
form-associated element.
Palpable content.
Contexts in which this element can be used:
Where phrasing content is expected.
Content model:
Text.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
autocomplete - Hint for form autofill feature
autofocus - Automatically focus the form control when the page is
loaded
cols - Maximum number of characters per line
dirname - Name of form field to use for sending the element’s
directionality in §4.10.21 Form submission
disabled - Whether the form control is disabled
form - Associates the control with a form element
maxlength - Maximum length of value
minlength - Minimum length of value
name - Name of form control to use for §4.10.21 Form submission
and in the form.elements API
placeholder - User-visible label to be placed within the form
control
readonly - Whether to allow the value to be edited by the user
required - Whether the control is required for §4.10.21 Form
submission
rows - Number of lines to show
wrap - How the value of the form control is to be wrapped for
§4.10.21 Form submission
Allowed ARIA role attribute values:
textbox with the aria-multiline property set to "true" (default -
do not set).
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
interface HTMLTextAreaElement : HTMLElement {
attribute DOMString autocomplete;
attribute boolean autofocus;
attribute unsigned long cols;
attribute DOMString dirName;
attribute boolean disabled;
readonly attribute HTMLFormElement? form;
attribute long maxLength;
attribute long minLength;
attribute DOMString name;
attribute DOMString placeholder;
attribute boolean readOnly;
attribute boolean _required;
attribute unsigned long rows;
attribute DOMString wrap;
readonly attribute DOMString type;
attribute DOMString defaultValue;
[TreatNullAs=EmptyString] attribute DOMString value;
readonly attribute unsigned long textLength;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
[SameObject] readonly attribute NodeList labels;
void select();
attribute unsigned long? selectionStart;
attribute unsigned long? selectionEnd;
attribute DOMString? selectionDirection;
void setRangeText(DOMString replacement);
void setRangeText(DOMString replacement, unsigned long start, unsigned long end, optional SelectionMode selectionMode = "preserve");
void setSelectionRange(unsigned long start, unsigned long end, optional DOMString direction);
};
The textarea element represents a multiline plain text edit control for
the element’s raw value. The contents of the control represent the
control’s default value.
The raw value of a textarea control must be initially the empty string.
This element has rendering requirements involving the bidirectional
algorithm.
The readonly attribute is a boolean attribute used to control whether the
text can be edited by the user or not.
In this example, a text field is marked read-only because it represents a
read-only file:
Filename: /etc/bash.bashrc
Constraint validation: If the readonly attribute is specified on a
textarea element, the element is barred from constraint validation.
A textarea element is mutable if it is neither disabled nor has a readonly
attribute specified.
When a textarea is mutable, its raw value should be editable by the user:
the user agent should allow the user to edit, insert, and remove text, and
to insert and remove line breaks in the form of U+000A LINE FEED (LF)
characters. Any time the user causes the element’s raw value to change,
the user agent must queue a task to fire a simple event that bubbles named
input at the textarea element. User agents may wait for a suitable break
in the user’s interaction before queuing the task; for example, a user
agent could wait for the user to have not hit a key for 100ms, so as to
only fire the event when the user pauses, instead of continuously for each
keystroke.
A textarea element has a dirty value flag, which must be initially set to
false, and must be set to true whenever the user interacts with the
control in a way that changes the raw value.
When the textarea element’s textContent IDL attribute changes value, if
the element’s dirty value flag is false, then the element’s raw value must
be set to the value of the element’s textContent IDL attribute.
The reset algorithm for textarea elements is to set the dirty value flag
back to false, and set the element’s raw value to the value of the
element’s textContent IDL attribute.
When a textarea element is popped off the stack of open elements of an
HTML parser or XML parser, then the user agent must invoke the element’s
reset algorithm.
If the element is mutable, the user agent should allow the user to change
the writing direction of the element, setting it either to a left-to-right
writing direction or a right-to-left writing direction. If the user does
so, the user agent must then run the following steps:
1. Set the element’s dir attribute to "ltr" if the user selected a
left-to-right writing direction, and "rtl" if the user selected a
right-to-left writing direction.
2. Queue a task to fire a simple event that bubbles named input at the
textarea element.
The cols attribute specifies the expected maximum number of characters per
line. If the cols attribute is specified, its value must be a valid
non-negative integer greater than zero. If applying the rules for parsing
non-negative integers to the attribute’s value results in a number greater
than zero, then the element’s character width is that value; otherwise, it
is 20.
The user agent may use the textarea element’s character width as a hint to
the user as to how many characters the server prefers per line (e.g., for
visual user agents by making the width of the control be that many
characters). In visual renderings, the user agent should wrap the user’s
input in the rendering so that each line is no wider than this number of
characters.
The rows attribute specifies the number of lines to show. If the rows
attribute is specified, its value must be a valid non-negative integer
greater than zero. If applying the rules for parsing non-negative integers
to the attribute’s value results in a number greater than zero, then the
element’s character height is that value; otherwise, it is 2.
Visual user agents should set the height of the control to the number of
lines given by character height.
The wrap attribute is an enumerated attribute with two keywords and
states: the soft keyword which maps to the Soft state, and the hard
keyword which maps to the Hard state. The missing value default is the
Soft state.
The Soft state indicates that the text in the textarea is not to be
wrapped when it is submitted (though it can still be wrapped in the
rendering).
The Hard state indicates that the text in the textarea is to have newlines
added by the user agent so that the text is wrapped when it is submitted.
If the element’s wrap attribute is in the Hard state, the cols attribute
must be specified.
For historical reasons, the element’s value is normalized in three
different ways for three different purposes. The raw value is the value as
it was originally set. It is not normalized. The API value is the value
used in the value IDL attribute. It is normalized so that line breaks use
U+000A LINE FEED (LF) characters. Finally, there is the value, as used in
form submission and other processing models in this specification. It is
normalized so that line breaks use U+000D CARRIAGE RETURN U+000A LINE FEED
(CRLF) character pairs, and in addition, if necessary given the element’s
wrap attribute, additional line breaks are inserted to wrap the text at
the given width.
The element’s API value is defined to be the element’s raw value with the
following transformation applied:
1. Replace every U+000D CARRIAGE RETURN U+000A LINE FEED (CRLF) character
pair from the raw value with a single U+000A LINE FEED (LF) character.
2. Replace every remaining U+000D CARRIAGE RETURN character from the raw
value with a single U+000A LINE FEED (LF) character.
The element’s value is defined to be the element’s raw value with the
textarea wrapping transformation applied. The textarea wrapping
transformation is the following algorithm, as applied to a string:
1. Replace every occurrence of a U+000D CARRIAGE RETURN (CR) character
not followed by a U+000A LINE FEED (LF) character, and every
occurrence of a U+000A LINE FEED (LF) character not preceded by a
U+000D CARRIAGE RETURN (CR) character, by a two-character string
consisting of a U+000D CARRIAGE RETURN U+000A LINE FEED (CRLF)
character pair.
2. If the element’s wrap attribute is in the Hard state, insert U+000D
CARRIAGE RETURN U+000A LINE FEED (CRLF) character pairs into the
string using a user agent-defined algorithm so that each line has no
more than character width characters. For the purposes of this
requirement, lines are delimited by the start of the string, the end
of the string, and U+000D CARRIAGE RETURN U+000A LINE FEED (CRLF)
character pairs.
The maxlength attribute is a form control maxlength attribute controlled
by the textarea element’s dirty value flag.
If the textarea element has a maximum allowed value length, then the
element’s children must be such that the code-unit length of the value of
the element’s textContent IDL attribute with the textarea wrapping
transformation applied is equal to or less than the element’s maximum
allowed value length.
The minlength attribute is a form control minlength attribute controlled
by the textarea element’s dirty value flag.
The required attribute is a boolean attribute. When specified, the user
will be required to enter a value before submitting the form.
Constraint validation: If the element has its required attribute
specified, and the element is mutable, and the element’s value is the
empty string, then the element is suffering from being missing.
The placeholder attribute represents a short hint (a word or short phrase)
intended to aid the user with data entry when the control has no value. A
hint could be a sample value or a brief description of the expected
format.
The placeholder attribute should not be used as a replacement for a label.
For a longer hint or other advisory text, place the text next to the
control.
Use of the placeholder attribute as a replacement for a label can reduce
the accessibility and usability of the control for a range of users
including older users and users with cognitive, mobility, fine motor skill
or vision impairments. While the hint given by the control’s label is
shown at all times, the short hint given in the placeholder attribute is
only shown before the user enters a value. Furthermore, placeholder text
may be mistaken for a pre-filled value, and as commonly implemented the
default color of the placeholder text provides insufficient contrast and
the lack of a separate visible label reduces the size of the hit region
available for setting focus on the control.
User agents should present this hint to the user when the element’s value
is the empty string and the control is not focused (e.g., by displaying it
inside a blank unfocused control). All U+000D CARRIAGE RETURN U+000A LINE
FEED character pairs (CRLF) in the hint, as well as all other U+000D
CARRIAGE RETURN (CR) and U+000A LINE FEED (LF) characters in the hint,
must be treated as line breaks when rendering the hint.
The name attribute represents the element’s name. The dirname attribute
controls how the element’s directionality is submitted. The disabled
attribute is used to make the control non-interactive and to prevent its
value from being submitted. The form attribute is used to explicitly
associate the textarea element with its form owner. The autofocus
attribute controls focus. The autocomplete attribute controls how the user
agent provides autofill behavior.
textarea . type
Returns the string "textarea".
textarea . value
Returns the current value of the element.
Can be set, to change the value.
The cols, placeholder, required, rows, and wrap attributes must reflect
the respective content attributes of the same name. The cols and rows
attributes are limited to only non-negative numbers greater than zero. The
cols attribute’s default value is 20. The rows attribute’s default value
is 2. The dirName IDL attribute must reflect the dirname content
attribute. The maxLength IDL attribute must reflect the maxlength content
attribute, limited to only non-negative numbers. The minLength IDL
attribute must reflect the minlength content attribute, limited to only
non-negative numbers. The readOnly IDL attribute must reflect the readonly
content attribute.
The type IDL attribute must return the value "textarea".
The defaultValue IDL attribute must act like the element’s textContent IDL
attribute.
The value attribute must, on getting, return the element’s API value; on
setting, it must set the element’s raw value to the new value, set the
element’s dirty value flag to true, and should then move the text entry
cursor position to the end of the text field, unselecting any selected
text and resetting the selection direction to none.
The textLength IDL attribute must return the code-unit length of the
element’s API value.
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 select(), selectionStart, selectionEnd,
selectionDirection, setRangeText(), and setSelectionRange() methods and
IDL attributes expose the element’s text selection. The autofocus,
disabled, form, and name IDL attributes are part of the element’s forms
API.
Here is an example of a textarea being used for unrestricted free-form
text input in a form:
If you have any comments, please let us know:
To specify a maximum length for the comments, one can use the maxlength
attribute:
If you have any short comments, please let us know:
To give a default value, text can be included inside the element:
If you have any comments, please let us know:
You can also give a minimum length. Here, a letter needs to be filled out
by the user; a template (which is shorter than the minimum length) is
provided, but is insufficient to submit the form:
A placeholder can be given as well, to suggest the basic form to the user,
without providing an explicit template:
To have the browser submit the directionality of the element along with
the value, the dirname attribute can be specified:
If you have any comments, please let us know (you may use either English or Hebrew for your comments):
4.10.12. The output element
Categories:
Flow content.
Phrasing content.
listed, labelable, resettable, and reassociateable form-associated
element.
Palpable content.
Contexts in which this element can be used:
Where phrasing content is expected.
Content model:
Phrasing content.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
for - Specifies controls from which the output was calculated
form - Associates the control with a form element
name - Name of form control to use for §4.10.21 Form submission
and in the form.elements API
Allowed ARIA role attribute values:
status (default - do not set), Any role value.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
interface HTMLOutputElement : HTMLElement {
[SameObject, PutForwards=value] readonly attribute DOMTokenList htmlFor;
readonly attribute HTMLFormElement? form;
attribute DOMString name;
readonly attribute DOMString type;
attribute DOMString defaultValue;
attribute DOMString value;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
[SameObject] readonly attribute NodeList labels;
};
The output element represents the result of a calculation performed by the
application, or the result of a user action.
This element can be contrasted with the samp element, which is the
appropriate element for quoting the output of other programs run
previously.
The for content attribute allows an explicit relationship to be made
between the result of a calculation and the elements that represent the
values that went into the calculation or that otherwise influenced the
calculation. The for attribute, if specified, must contain a string
consisting of an unordered set of unique space-separated tokens that are
case-sensitive, each of which must have the value of an ID of an element
in the same Document.
The form attribute is used to explicitly associate the output element with
its form owner. The name attribute represents the element’s name. The
output element is associated with a form so that it can be easily
referenced from the event handlers of form controls; the element’s value
itself is not submitted when the form is submitted.
The element has a value mode flag which is either value or default.
Initially, the value mode flag must be set to default.
The element also has a default value. Initially, the default value must be
the empty string.
When the value mode flag is in mode default, the contents of the element
represent both the value of the element and its default value. When the
value mode flag is in mode value, the contents of the element represent
the value of the element only, and the default value is only accessible
using the defaultValue IDL attribute.
Whenever the element’s descendants are changed in any way, if the value
mode flag is in mode default, the element’s default value must be set to
the value of the element’s textContent IDL attribute.
The reset algorithm for output elements is to set the element’s value mode
flag to default and then to set the element’s textContent IDL attribute to
the value of the element’s default value (thus replacing the element’s
child nodes).
output . value [ = value ]
Returns the element’s current value.
Can be set, to change the value.
output . defaultValue [ = value ]
Returns the element’s current default value.
Can be set, to change the default value.
output . type
Returns the string "output".
The value IDL attribute must act like the element’s textContent IDL
attribute, except that on setting, in addition, before the child nodes are
changed, the element’s value mode flag must be set to value.
The defaultValue IDL attribute, on getting, must return the element’s
default value. On setting, the attribute must set the element’s default
value, and, if the element’s value mode flag is in the mode default, set
the element’s textContent IDL attribute as well.
The type attribute must return the string "output".
The htmlFor IDL attribute must reflect the for content attribute.
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 form and name IDL attributes are part of
the element’s forms API.
A simple calculator could use output for its display of calculated
results:
In this example, an output element is used to report the results of a
calculation performed by a remote server, as they come in:
Task Progress
Progress: 0 %
(The updateProgress() method in this example would be called by some other
code on the page to update the actual progress bar as the task
progressed.)
The value and max attributes, when present, must have values that are
valid floating-point numbers. The value attribute, if present, must have a
value equal to or greater than zero, and less than or equal to the value
of the max attribute, if present, or 1.0, otherwise. The max attribute, if
present, must have a value greater than zero.
The progress element is the wrong element to use for something that is
just a gauge, as opposed to task progress. For instance, indicating disk
space usage using progress would be inappropriate. Instead, the meter
element is available for such use cases.
User agent requirements: If the value attribute is omitted, then the
progress bar is an indeterminate progress bar. Otherwise, it is a
determinate progress bar.
If the progress bar is a determinate progress bar and the element has a
max attribute, the user agent must parse the max attribute’s value
according to the rules for parsing floating-point number values. If this
does not result in an error, and if the parsed value is greater than zero,
then the maximum value of the progress bar is that value. Otherwise, if
the element has no max attribute, or if it has one but parsing it resulted
in an error, or if the parsed value was less than or equal to zero, then
the maximum value of the progress bar is 1.0.
If the progress bar is a determinate progress bar, user agents must parse
the value attribute’s value according to the rules for parsing
floating-point number values. If this does not result in an error, and if
the parsed value is less than the maximum value and greater than zero,
then the current value of the progress bar is that parsed value.
Otherwise, if the parsed value was greater than or equal to the maximum
value, then the current value of the progress bar is the maximum value of
the progress bar. Otherwise, if parsing the value attribute’s value
resulted in an error, or a number less than or equal to zero, then the
current value of the progress bar is zero.
user agent requirements for showing the progress bar: When representing a
progress element to the user, the user agent should indicate whether it is
a determinate or indeterminate progress bar, and in the former case,
should indicate the relative position of the current value relative to the
maximum value.
progress . position
For a determinate progress bar (one with known current and maximum
values), returns the result of dividing the current value by the
maximum value.
For an indeterminate progress bar, returns -1.
If the progress bar is an indeterminate progress bar, then the position
IDL attribute must return -1. Otherwise, it must return the result of
dividing the current value by the maximum value.
If the progress bar is an indeterminate progress bar, then the value IDL
attribute, on getting, must return 0. Otherwise, it must return the
current value. On setting, the given value must be converted to the best
representation of the number as a floating-point number and then the value
content attribute must be set to that string.
Setting the value IDL attribute to itself when the corresponding content
attribute is absent would change the progress bar from an indeterminate
progress bar to a determinate progress bar with no progress.
The max IDL attribute must reflect the content attribute of the same name,
limited to numbers greater than zero. The default value for max is 1.0.
The labels IDL attribute provides a list of the element’s labels.
4.10.14. The meter element
Categories:
Flow content.
Phrasing content.
Labelable element.
Palpable content.
Contexts in which this element can be used:
Where phrasing content is expected.
Content model:
Phrasing content, but there must be no meter element descendants.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
value - Current value of the element
min - Lower bound of range
max - Upper bound of range
low - High limit of low range
high - Low limit of high range
optimum - Optimum value in gauge
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
DOM interface:
interface HTMLMeterElement : HTMLElement {
attribute double value;
attribute double min;
attribute double max;
attribute double low;
attribute double high;
attribute double optimum;
[SameObject] readonly attribute NodeList labels;
};
The meter element represents a scalar measurement within a known range, or
a fractional value; for example disk usage, the relevance of a query
result, or the fraction of a voting population to have selected a
particular candidate.
This is also known as a gauge.
The meter element should not be used to indicate progress (as in a
progress bar). For that role, HTML provides a separate progress element.
The meter element also does not represent a scalar value of arbitrary
range — for example, it would be wrong to use this to report a weight, or
height, unless there is a known maximum value.
There are six attributes that determine the semantics of the gauge
represented by the element.
The min attribute specifies the lower bound of the range, and the max
attribute specifies the upper bound. The value attribute specifies the
value to have the gauge indicate as the "measured" value.
The other three attributes can be used to segment the gauge’s range into
"low", "medium", and "high" parts, and to indicate which part of the gauge
is the "optimum" part. The low attribute specifies the range that is
considered to be the "low" part, and the high attribute specifies the
range that is considered to be the "high" part. The optimum attribute
gives the position that is "optimum"; if that is higher than the "high"
value then this indicates that the higher the value, the better; if it’s
lower than the "low" mark then it indicates that lower values are better,
and naturally if it is in between then it indicates that neither high nor
low values are good.
Authoring requirements: The value attribute must be specified. The value,
min, low, high, max, and optimum attributes, when present, must have
values that are valid floating-point numbers.
In addition, the attributes' values are further constrained:
Let value be the value attribute’s number.
If the min attribute is specified, then let minimum be that attribute’s
value; otherwise, let it be zero.
If the max attribute is specified, then let maximum be that attribute’s
value; otherwise, let it be 1.0.
The following inequalities must hold, as applicable:
* minimum ≤ value ≤ maximum
* minimum ≤ low ≤ maximum (if low is specified)
* minimum ≤ high ≤ maximum (if high is specified)
* minimum ≤ optimum ≤ maximum (if optimum is specified)
* low ≤ high (if both low and high are specified)
If no minimum or maximum is specified, then the range is assumed to be
0..1, and the value thus has to be within that range.
Authors are encouraged to include a textual representation of the gauge’s
state in the element’s contents, for users of user agents that do not
support the meter element.
When used with microdata, the meter element’s value attribute provides the
element’s machine-readable value.
The following examples show three gauges that would all be three-quarters
full:
Storage space usage: 6 blocks used (out of 8 total)
Voter turnout: The grapefruit pie had a radius of 12cm and a height of 2cm .
Instead, one would either not include the meter element, or use the meter
element with a defined range to give the dimensions in context compared to
other pies:
The grapefruit pie had a radius of 12cm and a height of
2cm.
Radius: 12cm
Height: 2cm
There is no explicit way to specify units in the meter element, but the
units may be specified in the title attribute in free-form text.
The example above could be extended to mention the units:
Radius: 12cm
Height: 2cm
User agent requirements: User agents must parse the min, max, value, low,
high, and optimum attributes using the rules for parsing floating-point
number values.
User agents must then use all these numbers to obtain values for six
points on the gauge, as follows. (The order in which these are evaluated
is important, as some of the values refer to earlier ones.)
The minimum value
If the min attribute is specified and a value could be parsed out
of it, then the minimum value is that value. Otherwise, the
minimum value is zero.
The maximum value
If the max attribute is specified and a value could be parsed out
of it, then the candidate maximum value is that value. Otherwise,
the candidate maximum value is 1.0.
If the candidate maximum value is greater than or equal to the
minimum value, then the maximum value is the candidate maximum
value. Otherwise, the maximum value is the same as the minimum
value.
The actual value
If the value attribute is specified and a value could be parsed
out of it, then that value is the candidate actual value.
Otherwise, the candidate actual value is zero.
If the candidate actual value is less than the minimum value, then
the actual value is the minimum value.
Otherwise, if the candidate actual value is greater than the
maximum value, then the actual value is the maximum value.
Otherwise, the actual value is the candidate actual value.
The low boundary
If the low attribute is specified and a value could be parsed out
of it, then the candidate low boundary is that value. Otherwise,
the candidate low boundary is the same as the minimum value.
If the candidate low boundary is less than the minimum value, then
the low boundary is the minimum value.
Otherwise, if the candidate low boundary is greater than the
maximum value, then the low boundary is the maximum value.
Otherwise, the low boundary is the candidate low boundary.
The high boundary
If the high attribute is specified and a value could be parsed out
of it, then the candidate high boundary is that value. Otherwise,
the candidate high boundary is the same as the maximum value.
If the candidate high boundary is less than the low boundary, then
the high boundary is the low boundary.
Otherwise, if the candidate high boundary is greater than the
maximum value, then the high boundary is the maximum value.
Otherwise, the high boundary is the candidate high boundary.
The optimum point
If the optimum attribute is specified and a value could be parsed
out of it, then the candidate optimum point is that value.
Otherwise, the candidate optimum point is the midpoint between the
minimum value and the maximum value.
If the candidate optimum point is less than the minimum value,
then the optimum point is the minimum value.
Otherwise, if the candidate optimum point is greater than the
maximum value, then the optimum point is the maximum value.
Otherwise, the optimum point is the candidate optimum point.
All of which will result in the following inequalities all being true:
* minimum value ≤ actual value ≤ maximum value
* minimum value ≤ low boundary ≤ high boundary ≤ maximum value
* minimum value ≤ optimum point ≤ maximum value
user agent requirements for regions of the gauge: If the optimum point is
equal to the low boundary or the high boundary, or anywhere in between
them, then the region between the low and high boundaries of the gauge
must be treated as the optimum region, and the low and high parts, if any,
must be treated as suboptimal. Otherwise, if the optimum point is less
than the low boundary, then the region between the minimum value and the
low boundary must be treated as the optimum region, the region from the
low boundary up to the high boundary must be treated as a suboptimal
region, and the remaining region must be treated as an even less good
region. Finally, if the optimum point is higher than the high boundary,
then the situation is reversed; the region between the high boundary and
the maximum value must be treated as the optimum region, the region from
the high boundary down to the low boundary must be treated as a suboptimal
region, and the remaining region must be treated as an even less good
region.
user agent requirements for showing the gauge: When representing a meter
element to the user, the user agent should indicate the relative position
of the actual value to the minimum and maximum values, and the
relationship between the actual value and the three regions of the gauge.
The following markup:
Suggested groups
Hide suggested groups
Might be rendered as follows: With the elements rendered as inline
green bars of varying lengths.
User agents may combine the value of the title attribute and the other
attributes to provide context-sensitive help or inline text detailing the
actual values.
For example, the following snippet:
Disk usage: 170 261 928 bytes used
out of 233 257 824 bytes available
4.10.15. The fieldset element
Categories:
Flow content.
Sectioning root.
listed and reassociateable form-associated element.
Palpable content.
Contexts in which this element can be used:
Where flow content is expected.
Content model:
Optionally a legend element, followed by flow content.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
disabled - Whether the form control is disabled
form - Associates the control with a form element
name - Name of form control to use for §4.10.21 Form submission
and in the form.elements API
Allowed ARIA role attribute values:
group or presentation.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
interface HTMLFieldSetElement : HTMLElement {
attribute boolean disabled;
readonly attribute HTMLFormElement? form;
attribute DOMString name;
readonly attribute DOMString type;
[SameObject] readonly attribute HTMLCollection elements;
readonly attribute boolean willValidate;
[SameObject] readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
};
The fieldset element represents a set of form controls optionally grouped
under a common name.
The name of the group is given by the first legend element that is a child
of the fieldset element, if any. The remainder of the descendants form the
group.
The disabled attribute, when specified, causes all the form control
descendants of the fieldset element, excluding those that are descendants
of the fieldset element’s first legend element child, if any, to be
disabled.
A fieldset element is a disabled fieldset if it matches any of the
following conditions:
* Its disabled attribute is specified
* It is a descendant of another fieldset element whose disabled
attribute is specified, and is not a descendant of that fieldset
element’s first legend element child, if any.
The form attribute is used to explicitly associate the fieldset element
with its form owner. The name attribute represents the element’s name.
fieldset . type
Returns the string "fieldset".
fieldset . elements
Returns an HTMLCollection of the form controls in the element.
The disabled IDL attribute must reflect the content attribute of the same
name.
The type IDL attribute must return the string "fieldset".
The elements IDL attribute must return an HTMLCollection rooted at the
fieldset element, whose filter matches listed elements.
The willValidate, validity, and validationMessage attributes, and the
checkValidity(), reportValidity(), and setCustomValidity() methods, are
part of the constraint validation API. The form and name IDL attributes
are part of the element’s forms API.
This example shows a fieldset element being used to group a set of related
controls:
Display
Enhance contrast
The following snippet shows a fieldset with a checkbox in the legend that
controls whether or not the fieldset is enabled. The contents of the
fieldset consist of two required text fields and an optional year/month
control.
Name on card:
Card number:
Expiry date:
You can also nest fieldset elements. Here is an example expanding on the
previous one that does so:
Name on card:
Card number:
Card code:
In this example, if the outer "Use Club Card" checkbox is not checked,
everything inside the outer fieldset, including the two radio buttons in
the legends of the two nested fieldsets, will be disabled. However, if the
checkbox is checked, then the radio buttons will both be enabled and will
let you select which of the two inner fieldsets is to be enabled.
4.10.16. The legend element
Categories:
None.
Contexts in which this element can be used:
As the first child of a fieldset element.
Content model:
Phrasing content and headings (h1-h6 elements).
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
Global aria-* attributes
DOM interface:
interface HTMLLegendElement : HTMLElement {
readonly attribute HTMLFormElement? form;
};
The legend element represents a caption for the rest of the contents of
the legend element’s parent fieldset element, if any.
legend . form
Returns the element’s form element, if any, or null otherwise.
The form IDL attribute’s behavior depends on whether the legend element is
in a fieldset element or not. If the legend has a fieldset element as its
parent, then the form IDL attribute must return the same value as the form
IDL attribute on that fieldset element. Otherwise, it must return null.
4.10.17. Form control infrastructure
4.10.17.1. A form control value
Most form controls have a value and a checkedness. (The latter is only
used by input elements.) These are used to describe how the user interacts
with the control.
A control’s value is its internal state. As such, it might not match the
user’s current input.
For instance, if a user enters the word "three" into a numeric field that
expects digits, the user’s input would be the string "three" but the
control’s value would remain unchanged. Or, if a user enters the email
address " awesome@example.com" (with leading white space) into an email
field, the user’s input would be the string " awesome@example.com" but
the browser’s UI for email fields might translate that into a value of
"awesome@example.com" (without the leading white space).
To define the behavior of constraint validation in the face of the input
element’s multiple attribute, input elements can also have separately
defined values.
The select element does not have a value; the selectedness of its option
elements is what is used instead.
4.10.17.2. Mutability
A form control can be designated as mutable.
This determines (by means of definitions and requirements in this
specification that rely on whether an element is so designated) whether or
not the user can modify the value or checkedness of a form control, or
whether or not a control can be automatically prefilled.
4.10.17.3. Association of controls and forms
A form-associated element can have a relationship with a form element,
which is called the element’s form owner. If a form-associated element is
not associated with a form element, its form owner is said to be null.
A form-associated element is, by default, associated with its nearest
ancestor form element (as described below), but, if it is reassociateable,
may have a form attribute specified to override this.
This feature allows authors to work around the lack of support for nested
form elements.
If a reassociateable form-associated element has a form attribute
specified, then that attribute’s value must be the ID of a form element in
the element’s owner Document.
The rules in this section are complicated by the fact that although
conforming documents will never contain nested form elements, it is quite
possible (e.g., using a script that performs DOM manipulation) to generate
documents that have such nested elements. They are also complicated by
rules in the HTML parser that, for historical reasons, can result in a
form-associated element being associated with a form element that is not
its ancestor.
When a form-associated element is created, its form owner must be
initialized to null (no owner).
When a form-associated element is to be associated with a form, its form
owner must be set to that form.
When a form-associated element or one of its ancestors is inserted into a
Document, then the user agent must reset the form owner of that
form-associated element. The HTML parser overrides this requirement when
inserting form controls.
When an element changes its parent node resulting in a form-associated
element and its form owner (if any) no longer being in the same tree, then
the user agent must reset the form owner of that form-associated element.
When a reassociateable form-associated element’s form attribute is set,
changed, or removed, then the user agent must reset the form owner of that
element.
When a reassociateable form-associated element has a form attribute and
the ID of any of the elements in the Document changes, then the user agent
must reset the form owner of that form-associated element.
When a reassociateable form-associated element has a form attribute and an
element with an ID is inserted into or removed from the Document, then the
user agent must reset the form owner of that form-associated element.
When the user agent is to reset the form owner of a form-associated
element, it must run the following steps:
1. If the element’s form owner is not null, and either the element is not
reassociateable or its form content attribute is not present, and the
element’s form owner is its nearest form element ancestor after the
change to the ancestor chain, then do nothing, and abort these steps.
2. Let the element’s form owner be null.
3. If the element is reassociateable, has a form content attribute, and
is itself in a Document, then run these substeps:
1. If the first element in the Document to have an ID that is
case-sensitively equal to the element’s form content attribute’s
value is a form element, then associate the form-associated
element with that form element.
2. Abort the "reset the form owner" steps.
4. Otherwise, if the form-associated element in question has an ancestor
form element, then associate the form-associated element with the
nearest such ancestor form element.
5. Otherwise, the element is left unassociated.
In the following non-conforming snippet:
...
...
The form owner of "d" would be the inner nested form "c", while the form
owner of "e" would be the outer form "a".
This happens as follows: First, the "e" node gets associated with "c" in
the HTML parser. Then, the innerHTML algorithm moves the nodes from the
temporary document to the "b" element. At this point, the nodes see their
ancestor chain change, and thus all the "magic" associations done by the
parser are reset to normal ancestor associations.
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 tag.
element . form
Returns the element’s form owner.
Returns null if there isn’t one.
Reassociateable form-associated elements have a form IDL attribute, which,
on getting, must return the element’s form owner, or null if there isn’t
one.
4.10.18. Attributes common to form controls
4.10.18.1. Naming form controls: the name attribute
The name content attribute gives the name of the form control, as used in
§4.10.21 Form submission and in the form element’s elements object. If the
attribute is specified, its value must not be the empty string.
Any non-empty value for name is allowed, but the name "_charset_" is
special:
_charset_
This value, if used as the name of a Hidden control with no value
attribute, is automatically given a value during submission
consisting of the submission character encoding.
The name IDL attribute must reflect the name content attribute.
4.10.18.2. Submitting element directionality: the dirname attribute
The dirname attribute on a form control element enables the submission of
the directionality of the element, and gives the name of the field that
contains this value during §4.10.21 Form submission. If such an attribute
is specified, its value must not be the empty string.
In this example, a form contains a text field and a submission button:
When the user submits the form, the user agent includes three fields, one
called "comment", one called "comment.dir", and one called "mode"; so if
the user types "Hello", the submission body might be something like:
comment=Hello&comment.dir=ltr&mode=add
If the user manually switches to a right-to-left writing direction and
enters "مرحبا", the submission body might be something like:
comment=%D9%85%D8%B1%D8%AD%D8%A8%D8%A7&comment.dir=rtl&mode=add
4.10.18.3. Limiting user input length: the maxlength attribute
A form control maxlength attribute, controlled by a dirty value flag,
declares a limit on the number of characters a user can input.
If an element has its form control maxlength attribute specified, the
attribute’s value must be a valid non-negative integer. If the attribute
is specified and applying the rules for parsing non-negative integers to
its value results in a number, then that number is the element’s maximum
allowed value length. If the attribute is omitted or parsing its value
results in an error, then there is no maximum allowed value length.
Constraint validation: If an element has a maximum allowed value length,
its dirty value flag is true, its value was last changed by a user edit
(as opposed to a change made by a script), and the code-unit length of the
element’s value is greater than the element’s maximum allowed value
length, then the element is suffering from being too long.
User agents may prevent the user from causing the element’s value to be
set to a value whose code-unit length is greater than the element’s
maximum allowed value length.
In the case of textarea elements, this is the value, not the raw value, so
the textarea wrapping transformation is applied before the maximum allowed
value length is checked.
4.10.18.4. Setting minimum input length requirements: the minlength
attribute
A form control minlength attribute, controlled by a dirty value flag,
declares a lower bound on the number of characters a user can input.
The minlength attribute does not imply the required attribute. If the form
control has no required attribute, then the value can still be omitted;
the minlength attribute only kicks in once the user has entered a value at
all. If the empty string is not allowed, then the required attribute also
needs to be set.
If an element has its form control minlength attribute specified, the
attribute’s value must be a valid non-negative integer. If the attribute
is specified and applying the rules for parsing non-negative integers to
its value results in a number, then that number is the element’s minimum
allowed value length. If the attribute is omitted or parsing its value
results in an error, then there is no minimum allowed value length.
If an element has both a maximum allowed value length and a minimum
allowed value length, the minimum allowed value length must be smaller
than or equal to the maximum allowed value length.
Constraint validation: If an element has a minimum allowed value length,
its dirty value flag is true, its value was last changed by a user edit
(as opposed to a change made by a script), its value is not the empty
string, and the code-unit length of the element’s value is less than the
element’s minimum allowed value length, then the element is suffering from
being too short.
In this example, there are four text fields. The first is required, and
has to be at least 5 characters long. The other three are optional, but if
the user fills one in, the user has to enter at least 10 characters.
4.10.18.5. Enabling and disabling form controls: the disabled attribute
The disabled content attribute is a boolean attribute.
A form control is disabled if any of the following conditions are met:
1. The element is a button, input, select, or textarea element, and the
disabled attribute is specified on this element (regardless of its
value).
2. The element is a descendant of a fieldset element whose disabled
attribute is specified, and is not a descendant of that fieldset
element’s first legend element child, if any.
A form control that is disabled must prevent any click events that are
queued on the user interaction task source from being dispatched on the
element.
Constraint validation: If an element is disabled, it is barred from
constraint validation.
The disabled IDL attribute must reflect the disabled content attribute.
4.10.18.6. Form submission
Attributes for form submission can be specified both on form elements 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, enctype, method, novalidate, and target.
The corresponding attributes for form submission that may be specified on
submit buttons are formaction, formenctype, formmethod, formnovalidate,
and formtarget. When omitted, they default to the values given on the
corresponding attributes on the form element.
----------------------------------------------------------------------
The action and formaction content attributes, if specified, must have a
value that is a valid non-empty URL potentially surrounded by spaces.
The action of an element is the value of the element’s formaction
attribute, if the element is a Submit Button and has such an attribute, or
the value of its form owner’s action attribute, if it has one, or else the
empty string.
----------------------------------------------------------------------
The method and formmethod content attributes are enumerated attributes
with the following keywords and states:
* The keyword get, mapping to the state GET, indicating the HTTP GET
method.
* The keyword post, mapping to the state POST, indicating the HTTP POST
method.
* The keyword dialog, mapping to the state 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.
The invalid value default for these attributes is the GET state. The
missing value default for the method attribute is also the GET state.
(There is no missing value default for the formmethod attribute.)
The method of an element is one of those states. If the element is a
Submit Button and has a formmethod attribute, then the element’s method is
that attribute’s state; otherwise, it is the form owner’s method
attribute’s state.
Here the method attribute is used to explicitly specify the default value,
"get", so that the search query is submitted in the URL:
On the other hand, here the method attribute is used to specify the value
"post", so that the user’s message is submitted in the HTTP request’s
body:
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.
----------------------------------------------------------------------
The enctype and formenctype content attributes are enumerated attributes
with the following keywords and states:
* The "application/x-www-form-urlencoded" keyword and corresponding
state.
* The "multipart/form-data" keyword and corresponding state.
* The "text/plain" keyword and corresponding state.
The invalid value default for these attributes is the
application/x-www-form-urlencoded state. The missing value default for the
enctype attribute is also the application/x-www-form-urlencoded state.
(There is no missing value default for the formenctype attribute.)
The enctype of an element is one of those three states. If the element is
a Submit Button and has a formenctype attribute, then the element’s
enctype is that attribute’s state; otherwise, it is the form owner’s
enctype attribute’s state.
----------------------------------------------------------------------
The target and formtarget content attributes, if specified, must have
values that are valid browsing context names or keywords.
The target of an element is the value of the element’s formtarget
attribute, if the element is a Submit Button and has such an attribute; or
the value of its form owner’s target attribute, if it has such an
attribute; or, if the Document contains a base element with a target
attribute, then the value of the target attribute of the first such base
element; or, if there is no such element, the empty string.
----------------------------------------------------------------------
The novalidate and formnovalidate content attributes are boolean
attributes. If present, they indicate that the form is not to be validated
during submission.
The no-validate state of an element is true if the element is a Submit
Button and the element’s formnovalidate attribute is present, or if the
element’s form owner’s novalidate attribute is present, and false
otherwise.
This attribute is useful to include "save" buttons on forms that have
validation constraints, to allow users to save their progress even though
they haven’t fully entered the data in the form. The following example
shows a simple form that has two required fields. There are three buttons:
one to submit the form, which requires both fields to be filled in; one to
save the form so that the user can come back and fill it in later; and one
to cancel the form altogether.
----------------------------------------------------------------------
The action IDL attribute must reflect the content attribute of the same
name, except that on getting, when the content attribute is missing or its
value is the empty string, the document’s URL must be returned instead.
The target IDL attribute must reflect the content attribute of the same
name.
The method and enctype IDL attributes must reflect the respective content
attributes of the same name, limited to only known values.
The encoding IDL attribute must reflect the enctype content attribute,
limited to only known values.
The noValidate IDL attribute must reflect the novalidate content
attribute.
The formAction IDL attribute must reflect the formaction content
attribute, except that on getting, when the content attribute is missing
or its value is the empty string, the document’s URL must be returned
instead.
The formEnctype IDL attribute must reflect the formenctype content
attribute, limited to only known values.
The formMethod IDL attribute must reflect the formmethod content
attribute, limited to only known values.
The formNoValidate IDL attribute must reflect the formnovalidate content
attribute.
The formTarget IDL attribute must reflect the formtarget content
attribute.
4.10.18.6.1. Autofocusing a form control: the autofocus attribute
The autofocus content attribute allows the author to indicate that a
control is to be focused as soon as the page is loaded or as soon as the
dialog within which it finds itself is shown, allowing the user to just
start typing without having to manually focus the main control.
Use of the autofocus attribute can reduce usability and accessibility for
users. Users of assistive technology can be adversively affected, because
its use overrides the default behaviour of assistive technology to display
content at the top of a document in the viewport, or announce content from
the start of the document. Users with cognitive disabilities can also be
disorientated by unexpected focus movement upon page load.
User agents should provide a method for users to disable the autofocus
attribute behaviour.
The autofocus attribute is a boolean attribute.
An element’s nearest ancestor autofocus scoping document element is the
element itself if the element is a dialog element, or else is the
element’s nearest ancestor dialog element, if any, or else is the
element’s document element.
There must not be two elements with the same nearest ancestor autofocus
scoping document element that both have the autofocus attribute specified.
When an element with the autofocus attribute specified is inserted into a
document, user agents should run the following steps:
1. Let target be the element’s node document.
2. If target has no browsing context, abort these steps.
3. If target’s browsing context has no top-level browsing context (e.g.,
it is a nested browsing context with no parent browsing context),
abort these steps.
4. If target’s active sandboxing flag set has the sandboxed automatic
features browsing context flag, abort these steps.
5. If target’s origin is not the same as the origin of the node document
of the currently focused element in target’s top-level browsing
context, abort these steps.
6. If target’s origin is not the same as the origin of the active
document of target’s top-level browsing context, abort these steps.
7. If the user agent has already reached the last step of this list of
steps in response to an element being inserted into a Document whose
top-level browsing context’s active document is the same as target’s
top-level browsing context’s active document, abort these steps.
8. If the user has indicated (for example, by starting to type in a form
control) that he does not wish focus to be changed, then optionally
abort these steps.
9. Queue a task that runs the focusing steps for the element. User agents
may also change the scrolling position of the document, or perform
some other action that brings the element to the user’s attention. The
task source for this task is the user interaction task source.
This handles the automatic focusing during document load. The show() and
showModal() methods of dialog elements also processes the autofocus
attribute.
Focusing the control does not imply that the user agent must focus the
browser window if it has lost focus.
The autofocus IDL attribute must reflect the content attribute of the same
name.
In the following snippet, the text control would be focused when the
document was loaded.
Ship the blue gift to...
Address:
City:
Postal Code:
Ship the red gift to...
Address:
City:
Postal Code:
2. Optionally, a token that is an ASCII case-insensitive match for one of
the following strings:
* "shipping", meaning the field is part of the shipping address or
contact information
* "billing", meaning the field is part of the billing address or
contact information
3. Either of the following two options:
* A token that is an ASCII case-insensitive match for one of the
following autofill field names, excluding those that are
inappropriate for the control:
* "name"
* "honorific-prefix"
* "given-name"
* "additional-name"
* "family-name"
* "honorific-suffix"
* "nickname"
* "username"
* "new-password"
* "current-password"
* "organization-title"
* "organization"
* "street-address"
* "address-line1"
* "address-line2"
* "address-line3"
* "address-level4"
* "address-level3"
* "address-level2"
* "address-level1"
* "country"
* "country-name"
* "postal-code"
* "cc-name"
* "cc-given-name"
* "cc-additional-name"
* "cc-family-name"
* "cc-number"
* "cc-exp"
* "cc-exp-month"
* "cc-exp-year"
* "cc-csc"
* "cc-type"
* "transaction-currency"
* "transaction-amount"
* "language"
* "bday"
* "bday-day"
* "bday-month"
* "bday-year"
* "sex"
* "url"
* "photo"
(See the table below for descriptions of these values.)
* The following, in the given order:
1. Optionally, a token that is an ASCII case-insensitive match
for one of the following strings:
* "home", meaning the field is for contacting someone at
their residence
* "work", meaning the field is for contacting someone at
their workplace
* "mobile", meaning the field is for contacting someone
regardless of location
* "fax", meaning the field describes a fax machine’s
contact details
* "pager", meaning the field describes a pager’s or
beeper’s contact details
2. A token that is an ASCII case-insensitive match for one of
the following autofill field names, excluding those that are
inappropriate for the control:
* "tel"
* "tel-country-code"
* "tel-national"
* "tel-area-code"
* "tel-local"
* "tel-local-prefix"
* "tel-local-suffix"
* "tel-extension"
* "email"
* "impp"
(See the table below for descriptions of these values.)
As noted earlier, the meaning of the attribute and its keywords depends on
the mantle that the attribute is wearing.
When wearing the autofill expectation mantle...
The "off" keyword indicates either that the control’s input data
is particularly sensitive (for example the activation code for a
nuclear weapon); or that it is a value that will never be reused
(for example a one-time-key for a bank login) and the user will
therefore have to explicitly enter the data each time, instead of
being able to rely on the user agent to prefill the value for him;
or that the document provides its own autocomplete mechanism and
does not want the user agent to provide autocompletion values.
The "on" keyword indicates that the user agent is allowed to
provide the user with autocompletion values, but does not provide
any further information about what kind of data the user might be
expected to enter. User agents would have to use heuristics to
decide what autocompletion values to suggest.
The autofill field listed above indicate that the user agent is
allowed to provide the user with autocompletion values, and
specifies what kind of value is expected. The meaning of each such
keyword is described in the table below.
If the autocomplete attribute is omitted, the default value
corresponding to the state of the element’s form owner’s
autocomplete attribute is used instead (either "on" or "off"). If
there is no form owner, then the value "on" is used.
When wearing the autofill anchor mantle...
The autofill field listed above indicate that the value of the
particular kind of value specified is that value provided for this
element. The meaning of each such keyword is described in the
table below.
In this example the page has explicitly specified the currency and
amount of the transaction. The form requests a credit card and
other billing details. The user agent could use this information
to suggest a credit card that it knows has sufficient balance and
that supports the relevant currency.
The autofill field keywords relate to each other as described in the table
below. Each field name listed on a row of this table corresponds to the
meaning given in the cell for that row in the column labeled "Meaning".
Some fields correspond to subparts of other fields; for example, a credit
card expiry date can be expressed as one field giving both the month and
year of expiry ("cc-exp"), or as two fields, one giving the month
("cc-exp-month") and one the year ("cc-exp-year"). In such cases, the
names of the broader fields cover multiple rows, in which the narrower
fields are defined.
Generally, authors are encouraged to use the broader fields rather than
the narrower fields, as the narrower fields tend to expose Western biases.
For example, while it is common in some Western cultures to have a given
name and a family name, in that order (and thus often referred to as a
first name and a surname), many cultures put the family name first and the
given name second, and many others simply have one name (a mononym).
Having a single field is therefore more flexible.
Some fields are only appropriate for certain form controls. An autofill
field name is inappropriate for a control if the control does not belong
to the group listed for that autofill field in the fifth column of the
first row describing that autofill field in the table below. What controls
fall into each group is described below the table.
Field name Meaning Canonical Canonical Format Example Control
Format group
Free-form
"name" Full name text, no Sir Timothy John Berners-Lee, OM, KBE, FRS, FREng, FRSA Text
newlines
Prefix or title (e.g., "Mr.", Free-form
"honorific-prefix" "Ms.", "Dr.", "M^lle") text, no Sir Text
newlines
Given name (in some Western Free-form
"given-name" cultures, also known as the text, no Timothy Text
first name) newlines
Additional names (in some Free-form
"additional-name" Western cultures, also known text, no John Text
as middle names, forenames newlines
other than the first name)
Family name (in some Western Free-form
"family-name" cultures, also known as the text, no Berners-Lee Text
last name or surname) newlines
Suffix (e.g., "Jr.", "B.Sc.", Free-form
"honorific-suffix" "MBASW", "II") text, no OM, KBE, FRS, FREng, FRSA Text
newlines
Nickname, screen name, Free-form
"nickname" handle: a typically short text, no Tim Text
name used instead of the full newlines
name
Job title (e.g., "Software Free-form
"organization-title" Engineer", "Senior Vice text, no Professor Text
President", "Deputy Managing newlines
Director")
Free-form
"username" A username text, no timbl Text
newlines
A new password (e.g., when Free-form
"new-password" creating an account or text, no GUMFXbadyrS3 Password
changing a password) newlines
The current password for the Free-form
"current-password" account identified by the text, no qwerty Password
username field (e.g., when newlines
logging in)
Company name corresponding to
the person, address, or Free-form
"organization" contact information in the text, no World Wide Web Consortium Text
other fields associated with newlines
this field
"street-address" Street address (multiple Free-form text 32 Vassar Street Multiline
lines, newlines preserved) MIT Room 32-G524
Free-form
"address-line1" text, no 32 Vassar Street Text
newlines
Street address (one line per Free-form
"address-line2" field) text, no MIT Room 32-G524 Text
newlines
Free-form
"address-line3" text, no Text
newlines
The most fine-grained Free-form
"address-level4" administrative level, in text, no Text
addresses with four newlines
administrative levels
The third administrative Free-form
"address-level3" level, in addresses with text, no Text
three or more administrative newlines
levels
The second administrative
level, in addresses with two
or more administrative
levels; in the countries with Free-form
"address-level2" two administrative levels, text, no Cambridge Text
this would typically be the newlines
city, town, village, or other
locality within which the
relevant street address is
found
The broadest administrative
level in the address, i.e.,
the province within which the
locality is found; for Free-form
"address-level1" example, in the US, this text, no MA Text
would be the state; in newlines
Switzerland it would be the
canton; in the UK, the post
town
Valid ISO
"country" Country code 3166-1-alpha-2 US Text
country code
[ISO3166]
Free-form
text, no
"country-name" Country name newlines; US Text
derived from
country in
some cases
Postal code, post code, ZIP
code, CEDEX code (if CEDEX, Free-form
"postal-code" append "CEDEX", and the text, no 02139 Text
dissement, if relevant, to newlines
the address-level2 field)
Full name as given on the Free-form
"cc-name" payment instrument text, no Tim Berners-Lee Text
newlines
Given name as given on the Free-form
"cc-given-name" payment instrument (in some text, no Tim Text
Western cultures, also known newlines
as the first name)
Additional names given on the
payment instrument (in some Free-form
"cc-additional-name" Western cultures, also known text, no Text
as middle names, forenames newlines
other than the first name)
Family name given on the Free-form
"cc-family-name" payment instrument (in some text, no Berners-Lee Text
Western cultures, also known newlines
as the last name or surname)
Code identifying the payment
"cc-number" instrument (e.g., the credit ASCII digits 4114360123456785 Text
card number)
"cc-exp" Expiration date of the Valid month 2014-12 Month
payment instrument string
Month component of the valid integer
"cc-exp-month" expiration date of the in the range 12 Numeric
payment instrument 1..12
Year component of the valid integer
"cc-exp-year" expiration date of the greater than 2014 Numeric
payment instrument zero
Security code for the payment
instrument (also known as the
card security code (CSC),
"cc-csc" card validation code (CVC), ASCII digits 419 Text
card verification value
(CVV), signature panel code
(SPC), credit card ID (CCID),
etc)
Free-form
"cc-type" Type of payment instrument text, no Visa Text
newlines
The currency that the user ISO 4217
"transaction-currency" would prefer the transaction currency code GBP Text
to use [ISO4217]
The amount that the user Valid
"transaction-amount" would like for the floating-point 401.00 Numeric
transaction (e.g., when number
entering a bid or sale price)
Valid BCP 47
"language" Preferred language language tag en Text
[BCP47]
"bday" Birthday Valid date 1955-06-08 Date
string
valid integer
"bday-day" Day component of birthday in the range 8 Numeric
1..31
valid integer
"bday-month" Month component of birthday in the range 6 Numeric
1..12
valid integer
"bday-year" Year component of birthday greater than 1955 Numeric
zero
Gender identity (e.g., Free-form
"sex" Female, Fa’afafine) text, no Male Text
newlines
Home page or other Web page
corresponding to the company,
"url" person, address, or contact Valid URL https://www.w3.org/People/Berners-Lee/ URL
information in the other
fields associated with this
field
Photograph, icon, or other
image corresponding to the
"photo" company, person, address, or Valid URL https://www.w3.org/Press/Stock/Berners-Lee/2001-europaeum-eighth.jpg URL
contact information in the
other fields associated with
this field
ASCII digits
and U+0020
SPACE
"tel" Full telephone number, characters, +1 617 253 5702 Tel
including country code prefixed by a
U+002B PLUS
SIGN character
(+)
ASCII digits
Country code component of the prefixed by a
"tel-country-code" telephone number U+002B PLUS +1 Text
SIGN character
(+)
Telephone number without the ASCII digits
"tel-national" county code component, with a and U+0020 617 253 5702 Text
country-internal prefix SPACE
applied if applicable characters
Area code component of the
"tel-area-code" telephone number, with a ASCII digits 617 Text
country-internal prefix
applied if applicable
Telephone number without the
"tel-local" country code and area code ASCII digits 2535702 Text
components
First part of the component
of the telephone number that
"tel-local-prefix" follows the area code, when ASCII digits 253 Text
that component is split into
two components
Second part of the component
of the telephone number that
"tel-local-suffix" follows the area code, when ASCII digits 5702 Text
that component is split into
two components
"tel-extension" Telephone number internal ASCII digits 1000 Text
extension code
"email" E-mail address Valid e-mail timbl@w3.org E-mail
address
URL representing an instant
messaging protocol endpoint
"impp" (for example, Valid URL irc://example.org/timbl,isuser URL
"aim:goim?screenname=example"
or "xmpp:fred@example.net")
The groups correspond to controls as follows:
Text
input elements with a type attribute in the Hidden state
input elements with a type attribute in the Text state
input elements with a type attribute in the Search state
textarea elements
select elements
Multiline
input elements with a type attribute in the Hidden state
textarea elements
select elements
Password
input elements with a type attribute in the Hidden state
input elements with a type attribute in the Text state
input elements with a type attribute in the Search state
input elements with a type attribute in the Password state
textarea elements
select elements
URL
input elements with a type attribute in the Hidden state
input elements with a type attribute in the Text state
input elements with a type attribute in the Search state
input elements with a type attribute in the URL state
textarea elements
select elements
E-mail
input elements with a type attribute in the Hidden state
input elements with a type attribute in the Text state
input elements with a type attribute in the Search state
input elements with a type attribute in the E-mail state
textarea elements
select elements
Tel
input elements with a type attribute in the Hidden state
input elements with a type attribute in the Text state
input elements with a type attribute in the Search state
input elements with a type attribute in the Telephone state
textarea elements
select elements
Numeric
input elements with a type attribute in the Hidden state
input elements with a type attribute in the Text state
input elements with a type attribute in the Search state
input elements with a type attribute in the Number state
textarea elements
select elements
Month
input elements with a type attribute in the Hidden state
input elements with a type attribute in the Text state
input elements with a type attribute in the Search state
input elements with a type attribute in the Month state
textarea elements
select elements
Date
input elements with a type attribute in the Hidden state
input elements with a type attribute in the Text state
input elements with a type attribute in the Search state
input elements with a type attribute in the Date state
textarea elements
select elements
Address levels: The "address-level1" – "address-level4" fields are used to
describe the locality of the street address. Different locales have
different numbers of levels. For example, the US uses two levels (state
and town), the UK uses one or two depending on the address (the post town,
and in some cases the locality), and China can use three (province, city,
district). The "address-level1" field represents the widest administrative
division. Different locales order the fields in different ways; for
example, in the US the town (level 2) precedes the state (level 1); while
in Japan the prefecture (level 1) precedes the city (level 2) which
precedes the district (level 3). Authors are encouraged to provide forms
that are presented in a way that matches the country’s conventions
(hiding, showing, and rearranging fields accordingly as the user changes
the country).
4.10.18.7.2. Processing model
Each input element to which the autocomplete attribute applies, each
select element, and each textarea element, has an autofill hint set, an
autofill scope, an autofill field name, and an IDL-exposed autofill value.
The autofill field name specifies the specific kind of data expected in
the field, e.g., "street-address" or "cc-exp".
The autofill hint set identifies what address or contact information type
the user agent is to look at, e.g., "shipping fax" or "billing".
The autofill scope identifies the group of fields that are to be filled
with the information from the same source, and consists of the autofill
hint set with, if applicable, the "section-*" prefix, e.g., "billing",
"section-parent shipping", or "section-child shipping home".
These values are defined as the result of running the following algorithm:
1. If the element has no autocomplete attribute, then jump to the step
labeled default.
2. Let tokens be the result of splitting the attribute’s value on spaces.
3. If tokens is empty, then jump to the step labeled default.
4. Let index be the index of the last token in tokens.
5. If the indexth token in tokens is not an ASCII case-insensitive match
for one of the tokens given in the first column of the following
table, or if the number of tokens in tokens is greater than the
maximum number given in the cell in the second column of that token’s
row, then jump to the step labeled default. Otherwise, let field be
the string given in the cell of the first column of the matching row,
and let category be the value of the cell in the third column of that
same row.
Token Maximum number of tokens Category
"off" 1 Off
"on" 1 Automatic
"name" 3 Normal
"honorific-prefix" 3 Normal
"given-name" 3 Normal
"additional-name" 3 Normal
"family-name" 3 Normal
"honorific-suffix" 3 Normal
"nickname" 3 Normal
"organization-title" 3 Normal
"username" 3 Normal
"new-password" 3 Normal
"current-password" 3 Normal
"organization" 3 Normal
"street-address" 3 Normal
"address-line1" 3 Normal
"address-line2" 3 Normal
"address-line3" 3 Normal
"address-level4" 3 Normal
"address-level3" 3 Normal
"address-level2" 3 Normal
"address-level1" 3 Normal
"country" 3 Normal
"country-name" 3 Normal
"postal-code" 3 Normal
"cc-name" 3 Normal
"cc-given-name" 3 Normal
"cc-additional-name" 3 Normal
"cc-family-name" 3 Normal
"cc-number" 3 Normal
"cc-exp" 3 Normal
"cc-exp-month" 3 Normal
"cc-exp-year" 3 Normal
"cc-csc" 3 Normal
"cc-type" 3 Normal
"transaction-currency" 3 Normal
"transaction-amount" 3 Normal
"language" 3 Normal
"bday" 3 Normal
"bday-day" 3 Normal
"bday-month" 3 Normal
"bday-year" 3 Normal
"sex" 3 Normal
"url" 3 Normal
"photo" 3 Normal
"tel" 4 Contact
"tel-country-code" 4 Contact
"tel-national" 4 Contact
"tel-area-code" 4 Contact
"tel-local" 4 Contact
"tel-local-prefix" 4 Contact
"tel-local-suffix" 4 Contact
"tel-extension" 4 Contact
"email" 4 Contact
"impp" 4 Contact
6. If category is Off or Automatic but the element’s autocomplete
attribute is wearing the autofill anchor mantle, then jump to the step
labeled default.
7. If category is Off, let the element’s autofill field name be the
string "off", let its autofill hint set be empty, and let its
IDL-exposed autofill value be the string "off". Then, abort these
steps.
8. If category is Automatic, let the element’s autofill field name be the
string "on", let its autofill hint set be empty, and let its
IDL-exposed autofill value be the string "on". Then, abort these
steps.
9. Let scope tokens be an empty list.
10. Let hint tokens be an empty set.
11. Let IDL value have the same value as field.
12. If the indexth token in tokens is the first entry, then skip to the
step labeled done.
13. Decrement index by one.
14. If category is Contact and the indexth token in tokens is an ASCII
case-insensitive match for one of the strings in the following list,
then run the substeps that follow:
* "home"
* "work"
* "mobile"
* "fax"
* "pager"
The substeps are:
1. Let contact be the matching string from the list above.
2. Insert contact at the start of scope tokens.
3. Add contact to hint tokens.
4. Let IDL value be the concatenation of contact, a U+0020 SPACE
character, and the previous value of IDL value (which at this
point will always be field).
5. If the indexth entry in tokens is the first entry, then skip to
the step labeled done.
6. Decrement index by one.
15. If the indexth token in tokens is an ASCII case-insensitive match for
one of the strings in the following list, then run the substeps that
follow:
* "shipping"
* "billing"
The substeps are:
1. Let mode be the matching string from the list above.
2. Insert mode at the start of scope tokens.
3. Add mode to hint tokens.
4. Let IDL value be the concatenation of mode, a U+0020 SPACE
character, and the previous value of IDL value (which at this
point will either be field or the concatenation of contact, a
space, and field).
5. If the indexth entry in tokens is the first entry, then skip to
the step labeled done.
6. Decrement index by one.
16. If the indexth entry in tokens is not the first entry, then jump to
the step labeled default.
17. If the first eight characters of the indexth token in tokens are not
an ASCII case-insensitive match for the string "section-", then jump
to the step labeled default.
18. Let section be the indexth token in tokens, in ASCII lowercase.
19. Insert section at the start of scope tokens.
20. Let IDL value be the concatenation of section, a U+0020 SPACE
character, and the previous value of IDL value.
21. Done: Let the element’s autofill hint set be hint tokens.
22. Let the element’s autofill scope be scope tokens.
23. Let the element’s autofill field name be field.
24. Let the element’s IDL-exposed autofill value be IDL value.
25. Abort these steps.
26. Default: Let the element’s IDL-exposed autofill value be the empty
string, and its autofill hint set and autofill scope be empty.
27. If the element’s autocomplete attribute is wearing the autofill anchor
mantle, then let the element’s autofill field name be the empty string
and abort these steps.
28. Let form be the element’s form owner, if any, or null otherwise.
29. If form is not null and form’s autocomplete attribute is in the off
state, then let the element’s autofill field name be "off".
Otherwise, let the element’s autofill field name be "on".
----------------------------------------------------------------------
For the purposes of autofill, a control’s data depends on the kind of
control:
An input element with its type attribute in the E-mail state and with the
multiple attribute specified
The element’s values.
Any other input element
A textarea element
The element’s value.
A select element with its multiple attribute specified
The option elements in the select element’s list of options that
have their selectedness set to true.
Any other select element
The option element in the select element’s list of options that
has its selectedness set to true.
----------------------------------------------------------------------
How to process the autofill hint set, autofill scope, and autofill field
name depends on the mantle that the autocomplete attribute is wearing.
When wearing the autofill expectation mantle...
When an element’s autofill field name is "off", the user agent
should not remember the control’s data, and should not offer past
values to the user.
In addition, when an element’s autofill field name is "off",
values are reset when traversing the history.
Banks frequently do not want user agents to prefill login
information:
Account:
PIN:
When an element’s autofill field name is not "off", the user agent
may store the control’s data, and may offer previously stored
values to the user.
For example, suppose a user visits a page with this control:
Afghanistan
Albania
Algeria
Andorra
Angola
Antigua and Barbuda
Argentina
Armenia
Yemen
Zambia
Zimbabwe
This might render as follows:
A drop-down control with a long alphabetical list of countries.
Suppose that on the first visit to this page, the user selects
"Zambia". On the second visit, the user agent could duplicate the
entry for Zambia at the top of the list, so that the interface
instead looks like this:
The same drop-down control with the alphabetical list of
countries, but with Zambia as an entry at the top.
When the autofill field name is "on", the user agent should
attempt to use heuristics to determine the most appropriate values
to offer the user, e.g., based on the element’s name value, the
position of the element in the document’s DOM, what other fields
exist in the form, and so forth.
When the autofill field name is one of the names of the autofill
fields described above, the user agent should provide suggestions
that match the meaning of the field name as given in the table
earlier in this section. The autofill hint set should be used to
select amongst multiple possible suggestions.
For example, if a user once entered one address into fields that
used the "shipping" keyword, and another address into fields that
used the "billing" keyword, then in subsequent forms only the
first address would be suggested for form controls whose autofill
hint set contains the keyword "shipping". Both addresses might be
suggested, however, for address-related form controls whose
autofill hint set does not contain either keyword.
When wearing the autofill anchor mantle...
When the autofill field name is not the empty string, then the
user agent must act as if the user had specified the control’s
data for the given autofill hint set, autofill scope, and autofill
field name combination.
When the user agent autofills form controls, elements with the same form
owner and the same autofill scope must use data relating to the same
person, address, payment instrument, and contact details. When a user
agent autofills "country" and "country-name" fields with the same form
owner and autofill scope, and the user agent has a value for the country"
field(s), then the "country-name" field(s) must be filled using a
human-readable name for the same country. When a user agent fills in
multiple fields at once, all fields with the same autofill field name,
form owner and autofill scope must be filled with the same value.
Suppose a user agent knows of two phone numbers, +1 555 123 1234 and +1
555 666 7777. It would not be conforming for the user agent to fill a
field with autocomplete="shipping tel-local-prefix" with the value "123"
and another field in the same form with autocomplete="shipping
tel-local-suffix" with the value "7777". The only valid prefilled values
given the aforementioned information would be "123" and "1234", or "666"
and "7777", respectively.
Similarly, if a form for some reason contained both a "cc-exp" field and a
"cc-exp-month" field, and the user agent prefilled the form, then the
month component of the former would have to match the latter.
This requirement interacts with the autofill anchor mantle also. Consider
the following markup snippet:
The only value that a conforming user agent could suggest in the text
field is "TreePlate", the value given by the hidden input element.
The "section-*" tokens in the autofill scope are opaque; user agents must
not attempt to derive meaning from the precise values of these tokens.
For example, it would not be conforming if the user agent decided that it
should offer the address it knows to be the user’s daughter’s address for
"section-child" and the addresses it knows to be the user’s spouses'
addresses for "section-spouse".
The autocompletion mechanism must be implemented by the user agent acting
as if the user had modified the control’s data, and must be done at a time
where the element is mutable (e.g., just after the element has been
inserted into the document, or when the user agent stops parsing). User
agents must only prefill controls using values that the user could have
entered.
For example, if a select element only has option elements with values
"Steve" and "Rebecca", "Jay", and "Bob", and has an autofill field name
"given-name", but the user agent’s only idea for what to prefill the field
with is "Evan", then the user agent cannot prefill the field. It would not
be conforming to somehow set the select element to the value "Evan", since
the user could not have done so themselves.
A user agent prefilling a form control’s value must not cause that control
to suffer from a type mismatch, suffer from being too long, suffer from
being too short, suffer from an underflow, suffer from an overflow, suffer
from a step mismatch, or suffer from a pattern mismatch. Where possible
given the control’s constraints, user agents must use the format given as
canonical in the aforementioned table. Where it’s not possible for the
canonical format to be used, user agents should use heuristics to attempt
to convert values so that they can be used.
For example, if the user agent knows that the user’s middle name is
"Ines", and attempts to prefill a form control that looks like this:
recognizing
Jan that one of
Feb the strings
... (three
Jul July characters
Aug "Jul"
... followed by
a newline
and a space)
is a close
match for
the name of
the month
(July) in
one of the
user agent’s
supported
languages,
or through
some other
similar
mechanism.
User agent
converts
"July" to a
Feeling:
The validity IDL attribute must return a ValidityState object that
represents the validity states of the element. This object is live.
interface ValidityState {
readonly attribute boolean valueMissing;
readonly attribute boolean typeMismatch;
readonly attribute boolean patternMismatch;
readonly attribute boolean tooLong;
readonly attribute boolean tooShort;
readonly attribute boolean rangeUnderflow;
readonly attribute boolean rangeOverflow;
readonly attribute boolean stepMismatch;
readonly attribute boolean badInput;
readonly attribute boolean customError;
readonly attribute boolean valid;
};
A ValidityState object has the following attributes. On getting, they must
return true if the corresponding condition given in the following list is
true, and false otherwise.
valueMissing, of type boolean, readonly
The control is suffering from being missing.
typeMismatch, of type boolean, readonly
The control is suffering from a type mismatch.
patternMismatch, of type boolean, readonly
The control is suffering from a pattern mismatch.
tooLong, of type boolean, readonly
The control is suffering from being too long.
tooShort, of type boolean, readonly
The control is suffering from being too short.
rangeUnderflow, of type boolean, readonly
The control is suffering from an underflow.
rangeOverflow, of type boolean, readonly
The control is suffering from an overflow.
stepMismatch, of type boolean, readonly
The control is suffering from a step mismatch.
badInput, of type boolean, readonly
The control is suffering from bad input.
customError, of type boolean, readonly
The control is suffering from a custom error.
valid, of type boolean, readonly
None of the other conditions are true.
When the checkValidity() method is invoked, if the element is a candidate
for constraint validation and does not satisfy its constraints, the user
agent must fire a simple event named invalid that is cancelable (but in
this case has no default action) at the element and return false.
Otherwise, it must only return true without doing anything else.
When the reportValidity() method is invoked, if the element is a candidate
for constraint validation and does not satisfy its constraints, the user
agent must: fire a simple event named invalid that is cancelable at the
element, and if that event is not canceled, report the problems with the
constraints of that element to the user; then, return false. Otherwise, it
must only return true without doing anything else. When reporting the
problem with the constraints to the user, the user agent may run the
focusing steps for that element, and may change the scrolling position of
the document, or perform some other action that brings the element to the
user’s attention. User agents may report more than one constraint
violation, if the element suffers from multiple problems at once. If the
element is not being rendered, then the user agent may, instead of
notifying the user, report a script error.
The validationMessage attribute must return the empty string if the
element is not a candidate for constraint validation or if it is one but
it satisfies its constraints; otherwise, it must return a suitably
localized message that the user agent would show the user if this were the
only form control with a validity constraint problem. If the user agent
would not actually show a textual message in such a situation (e.g., it
would show a graphical cue instead), then the attribute must return a
suitably localized message that expresses (one or more of) the validity
constraint(s) that the control does not satisfy. If the element is a
candidate for constraint validation and is suffering from a custom error,
then the custom validity error message should be present in the return
value.
4.10.20.4. Security
Servers should not rely on client-side validation. Client-side validation
can be intentionally bypassed by hostile users, and unintentionally
bypassed by users of older user agents or automated tools that do not
implement these features. The constraint validation features are only
intended to improve the user experience, not to provide any kind of
security mechanism.
4.10.21. Form submission
4.10.21.1. Introduction
This section is non-normative.
When a form is submitted, the data in the form is converted into the
structure specified by the enctype, and then sent to the destination
specified by the action using the given method.
For example, take the following form:
If the user types in "cats" in the first field and "fur" in the second,
and then hits the submit button, then the user agent will load
/find.cgi?t=cats&q=fur.
On the other hand, consider this form:
Given the same user input, the result on submission is quite different:
the user agent instead does an HTTP POST to the given URL, with as the
entity body something like the following text:
------kYFrd4jNJEgCervEContent-Disposition: form-data; name="t"
cats
------kYFrd4jNJEgCervE
Content-Disposition: form-data; name="q"
fur
------kYFrd4jNJEgCervE--
4.10.21.2. Implicit submission
A form element’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 field is
focused implicitly submits the form), then doing so for a form whose
default button has a defined activation behavior must cause the user agent
to run synthetic click activation steps on that default button.
Consequently, if the default button is disabled, the form is not submitted
when such an implicit submission mechanism is used. (A button has no
activation behavior when disabled.)
There are pages on the Web that are only usable if there is a way to
implicitly submit forms, so user agents are strongly encouraged to support
this.
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 form element if it is an input element
whose form owner is that form element and whose type attribute is in one
of the following states: Text, Search, URL, Telephone, E-mail, Password,
Local Date and Time, Date, Month, Week, Time, Number
4.10.21.3. Form submission algorithm
When a form element 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 following steps:
1. Let form document be the form’s node document.
2. If form document has no associated browsing context or its active
sandboxing flag set has its sandboxed forms browsing context flag set,
then abort these steps without doing anything.
3. Let form browsing context be the browsing context of form document.
4. If the submitted from submit() method flag is not set, and the
submitter element’s no-validate state is false, then interactively
validate the constraints of form and examine the result: if the result
is negative (the constraint validation concluded that there were
invalid fields and probably informed the user of this) then fire a
simple event named invalid at the form element and then abort these
steps.
5. If the submitted from submit() method flag is not set, then fire a
simple event that bubbles and is cancelable named submit, at form. If
the event’s default action is prevented (i.e., if the event is
canceled) then abort these steps. Otherwise, continue (effectively the
default action is to perform the submission).
6. Let form data set be the result of constructing the form data set for
form in the context of submitter.
7. Let action be the submitter element’s action.
8. If action is the empty string, let action be the document’s URL of the
form document.
9. Parse the URL action, relative to the submitter element’s node
document. If this fails, abort these steps.
10. Let action be the resulting URL string.
11. Let action components be the resulting URL record.
12. Let scheme be the scheme of the resulting URL record.
13. Let enctype be the submitter element’s enctype.
14. Let method be the submitter element’s method.
15. Let target be the submitter element’s target.
16. If the user indicated a specific browsing context to use when
submitting the form, then let target browsing context be that browsing
context. Otherwise, apply the rules for choosing a browsing context
given a browsing context name using target as the name and form
browsing context as the context in which the algorithm is executed,
and let target browsing context be the resulting browsing context.
17. If target browsing context was created in the previous step, or,
alternatively, if the form document has not yet completely loaded and
the submitted from submit() method flag is set, then let replace be
true. Otherwise, let it be false.
18. If the value of method is dialog then jump to the submit dialog steps.
Otherwise, select the appropriate row in the table below based on the
value of scheme as given by the first cell of each row. Then, select
the appropriate cell on that row based on the value of method as given
in the first cell of each column. Then, jump to the steps named in
that cell and defined below the table.
GET POST
http Mutate action URL Submit as entity body
https Mutate action URL Submit as entity body
ftp Get action URL Get action URL
javascript Get action URL Get action URL
data Get action URL Post to data:
mailto Mail with headers Mail as body
If scheme is not one of those listed in this table, then the behavior
is not defined by this specification. User agents should, in the
absence of another specification defining this, act in a manner
analogous to that defined in this specification for similar schemes.
Each form element 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:
1. If the form has a non-null planned navigation, remove it from its
task queue.
2. Let the form's planned navigation be a new task that consists of
running the following steps:
1. Let the form's planned navigation be null.
2. Navigate target browsing context to destination. If replace
is true, then target browsing context must be navigated with
replacement enabled.
For the purposes of this task, target browsing context and
replace are the variables that were set up when the overall form
submission algorithm was run, with their values as they stood
when this planned navigation was queued.
3. Queue a task that is the form's new planned navigation.
The task source for this task is the DOM manipulation task
source.
The behaviors are as follows:
Mutate action URL
Let query be the result of encoding the form data set
using the application/x-www-form-urlencoded encoding
algorithm, interpreted as a US-ASCII string.
Set parsed action’s query component to query.
Let destination be a new URL formed by applying the URL
serializer algorithm to parsed action.
Plan to navigate to destination.
Submit as entity body
Let entity body be the result of encoding the form data
set using the appropriate form encoding algorithm.
Let MIME type be determined as follows:
If enctype is application/x-www-form-urlencoded
Let MIME type be
"application/x-www-form-urlencoded".
If enctype is multipart/form-data
Let MIME type be the concatenation of the
string "multipart/form-data;", a U+0020
SPACE character, the string "boundary=", and
the multipart/form-data boundary string
generated by the multipart/form-data
encoding algorithm.
If enctype is text/plain
Let MIME type be "text/plain".
Otherwise, plan to navigate to a new request whose URL is
action, method is method, header list consists of
Content-Type/MIME type, and body is entity body.
Get action URL
Plan to navigate to action.
The form data set is discarded.
Post to data:
Let data be the result of encoding the form data set
using the appropriate form encoding algorithm.
If action contains the string "%%%%" (four U+0025 PERCENT
SIGN characters), then percent encode all bytes in data
that, if interpreted as US-ASCII, are not characters in
the URL default encode set, and then, treating the result
as a US-ASCII string, UTF-8 percent encode all the U+0025
PERCENT SIGN characters in the resulting string and
replace the first occurrence of "%%%%" in action with the
resulting doubly-escaped string. [URL]
Otherwise, if action contains the string "%%" (two U+0025
PERCENT SIGN characters in a row, but not four), then
UTF-8 percent encode all characters in data that, if
interpreted as US-ASCII, are not characters in the URL
default encode set, and then, treating the result as a
US-ASCII string, replace the first occurrence of "%%" in
action with the resulting escaped string. [URL]
Plan to navigate to the potentially modified action
(which will be a data: URL).
Mail with headers
Let headers be the resulting encoding the form data set
using the application/x-www-form-urlencoded encoding
algorithm, interpreted as a US-ASCII string.
Replace occurrences of U+002B PLUS SIGN characters (+) in
headers with the string "%20".
Let destination consist of all the characters from the
first character in action to the character immediately
before the first U+003F QUESTION MARK character (?), if
any, or the end of the string if there are none.
Append a single U+003F QUESTION MARK character (?) to
destination.
Append headers to destination.
Plan to navigate to destination.
Mail as body
Let body be the resulting of encoding the form data set
using the appropriate form encoding algorithm and then
percent encoding all the bytes in the resulting byte
string that, when interpreted as US-ASCII, are not
characters in the URL default encode set. [URL]
Let destination have the same value as action.
If destination does not contain a U+003F QUESTION MARK
character (?), append a single U+003F QUESTION MARK
character (?) to destination. Otherwise, append a single
U+0026 AMPERSAND character (&).
Append the string "body=" to destination.
Append body, interpreted as a US-ASCII string, to
destination.
Plan to navigate to destination.
Submit dialog
Let subject be the nearest ancestor dialog element of
form, if any.
If there isn’t one, or if it does not have an open
attribute, do nothing. Otherwise, proceed as follows:
If submitter is an input element whose type attribute is
in the Image Button state, then let result be the string
formed by concatenating the selected coordinate’s
x-component, expressed as a base-ten number using ASCII
digits, a U+002C COMMA character (,), and the selected
coordinate’s y-component, expressed in the same way as
the x-component.
Otherwise, if submitter has a value, then let result be
that value.
Otherwise, there is no result.
Then, close the dialog subject. If there is a result, let
that be the return value.
The appropriate form encoding algorithm is determined as follows:
If enctype is application/x-www-form-urlencoded
Use the application/x-www-form-urlencoded encoding
algorithm.
If enctype is multipart/form-data
Use the multipart/form-data encoding algorithm.
If enctype is text/plain
Use the text/plain encoding algorithm.
4.10.21.4. Constructing the form data set
The algorithm to construct the form data set for a form form optionally in
the context of a submitter submitter is as follows. If not specified
otherwise, submitter is null.
1. Let controls be a list of all the submittable elements whose form
owner is form, in tree order.
2. Let the form data set be a list of name-value-type tuples, initially
empty.
3. Loop: For each element field in controls, in tree order, run the
following substeps:
1. If any of the following conditions are met, then skip these
substeps for this element:
* The field element has a datalist element ancestor.
* The field element is disabled.
* The field element is a button but it is not submitter.
* The field element is an input element whose type attribute
is in the Checkbox state and whose checkedness is false.
* The field element is an input element whose type attribute
is in the Radio Button state and whose checkedness is false.
* The field element is not an input element whose type
attribute is in the Image Button state, and either the field
element does not have a name attribute specified, or its
name attribute’s value is the empty string.
* The field element is an object element that is not using a
plugin.
Otherwise, process field as follows:
2. Let type be the value of the type IDL attribute of field.
3. If the field element is an input element whose type attribute is
in the Image Button state, then run these further nested
substeps:
1. If the field element has a name attribute specified and its
value is not the empty string, let name be that value
followed by a single U+002E FULL STOP character (.).
Otherwise, let name be the empty string.
2. Let name_x be the string consisting of the concatenation of
name and a single U+0078 LATIN SMALL LETTER X character (x).
3. Let name_y be the string consisting of the concatenation of
name and a single U+0079 LATIN SMALL LETTER Y character (y).
4. The field element is submitter, and before this algorithm
was invoked the user indicated a coordinate. Let x be the
x-component of the coordinate selected by the user, and let
y be the y-component of the coordinate selected by the user.
5. Append an entry to the form data set with the name name_x,
the value x, and the type type.
6. Append an entry to the form data set with the name name_y
and the value y, and the type type.
7. Skip the remaining substeps for this element: if there are
any more elements in controls, return to the top of the loop
step, otherwise, jump to the end step below.
4. Let name be the value of the field element’s name attribute.
5. If the field element is a select element, then for each option
element in the select element’s list of options whose
selectedness is true and that is not disabled, append an entry to
the form data set with the name as the name, the value of the
option element as the value, and type as the type.
6. Otherwise, if the field element is an input element whose type
attribute is in the Checkbox state or the Radio Button state,
then run these further nested substeps:
1. If the field element has a value attribute specified, then
let value be the value of that attribute; otherwise, let
value be the string "on".
2. Append an entry to the form data set with name as the name,
value as the value, and type as the type.
7. Otherwise, if the field element is an input element whose type
attribute is in the File Upload state, then for each file
selected in the input element, append an entry to the form data
set with the name as the name, the file (consisting of the name,
the type, and the body) as the value, and type as the type. If
there are no selected files, then append an entry to the form
data set with the name as the name, the empty string as the
value, and application/octet-stream as the type.
8. Otherwise, if the field element is an object element: try to
obtain a form submission value from the plugin, and if that is
successful, append an entry to the form data set with name as the
name, the returned form submission value as the value, and the
string "object" as the type.
9. Otherwise, append an entry to the form data set with name as the
name, the value of the field element as the value, and type as
the type.
10. If the element has a dirname attribute, and that attribute’s
value is not the empty string, then run these substeps:
1. Let dirname be the value of the element’s dirname attribute.
2. Let dir be the string "ltr" if the directionality of the
element is 'ltr', and "rtl" otherwise (i.e., when the
directionality of the element is 'rtl').
3. Append an entry to the form data set with dirname as the
name, dir as the value, and the string "direction" as the
type.
An element can only have a dirname attribute if it is a textarea
element or an input element whose type attribute is in either the
Text state or the Search state.
4. End: For the name of each entry in the form data set, and for the
value of each entry in the form data set whose type is not "file" or
"textarea", replace every occurrence of a U+000D CARRIAGE RETURN (CR)
character not followed by a U+000A LINE FEED (LF) character, and every
occurrence of a U+000A LINE FEED (LF) character not preceded by a
U+000D CARRIAGE RETURN (CR) character, by a two-character string
consisting of a U+000D CARRIAGE RETURN U+000A LINE FEED (CRLF)
character pair.
In the case of the value of textarea elements, this newline
normalization is already performed during the conversion of the
control’s raw value into the control’s value (which also performs any
necessary line wrapping). In the case of input elements type
attributes in the File Upload state, the value is not normalized.
5. Return the form data set.
4.10.21.5. Selecting a form submission encoding
If the user agent is to pick an encoding for a form, it must run the
following steps:
1. Let encoding be the document’s character encoding.
2. If the form element has an accept-charset attribute, set encoding to
the return value of running these substeps:
1. Let input be the value of the form element’s accept-charset
attribute.
2. Let candidate encoding labels be the result of splitting input on
spaces.
3. Let candidate encodings be an empty list of character encodings.
4. For each token in candidate encoding labels in turn (in the order
in which they were found in input), get an encoding for the token
and, if this does not result in failure, append the encoding to
candidate encodings.
5. If candidate encodings is empty, return UTF-8.
6. Return the first encoding in candidate encodings.
3. Return the result of getting an output encoding from encoding.
4.10.21.6. URL-encoded form data
See the WHATWG URL specification for details on
application/x-www-form-urlencoded. [URL]
The application/x-www-form-urlencoded encoding algorithm is as follows:
1. Let encoding be the result of picking an encoding for the form.
2. Let serialized be the result of running the
application/x-www-form-urlencoded serializer given form data set and
encoding.
3. Return the result of encoding serialized.
4.10.21.7. Multipart form data
The multipart/form-data encoding algorithm is as follows:
1. Let result be the empty string.
2. If the algorithm was invoked with an explicit character encoding, let
the selected character encoding be that encoding. (This algorithm is
used by other specifications, which provide an explicit character
encoding to avoid the dependency on the form element described in the
next paragraph.)
Otherwise, if the form element has an accept-charset attribute, let
the selected character encoding be the result of picking an encoding
for the form.
Otherwise, if the form element has no accept-charset attribute, but
the document’s character encoding is an ASCII-compatible encoding,
then that is the selected character encoding.
Otherwise, let the selected character encoding be UTF-8.
3. Let charset be the name of the selected character encoding.
4. For each entry in the form data set, perform these substeps:
1. If the entry’s name is "_charset_" and its type is "hidden",
replace its value with charset.
2. For each character in the entry’s name and value that cannot be
expressed using the selected character encoding, replace the
character by a string consisting of a U+0026 AMPERSAND character
(&), a U+0023 NUMBER SIGN character (#), one or more ASCII digits
representing the Unicode code point of the character in base ten,
and finally a U+003B SEMICOLON character (;).
5. Encode the (now mutated) form data set using the rules described by
RFC 7578, Returning Values from Forms: multipart/form-data, and return
the resulting byte stream. [RFC7578]
Each entry in the form data set is a field, the name of the entry is
the field name and the value of the entry is the field value.
The order of parts must be the same as the order of fields in the form
data set. Multiple entries with the same name must be treated as
distinct fields.
The parts of the generated multipart/form-data resource that
correspond to non-file fields must not have a Content-Type header
specified. Their names and values must be encoded using the character
encoding selected above.
File names included in the generated multipart/form-data resource (as
part of file fields) must use the character encoding selected above,
though the precise name may be approximated if necessary (e.g.,
newlines could be removed from file names, quotes could be changed to
"%22", and characters not expressible in the selected character
encoding could be replaced by other characters).
The boundary used by the user agent in generating the return value of
this algorithm is the multipart/form-data boundary string. (This value
is used to generate the MIME type of the form submission payload
generated by this algorithm.)
For details on how to interpret multipart/form-data payloads, see RFC
7578. [RFC7578]
4.10.21.8. Plain text form data
The text/plain encoding algorithm is as follows:
1. Let result be the empty string.
2. Let encoding be the result of picking an encoding for the form.
3. Let charset be the name of encoding.
4. If the entry’s name is "_charset_" and its type is "hidden", replace
its value with charset.
5. If the entry’s type is "file", replace its value with the file’s name
only.
6. For each entry in the form data set, perform these substeps:
1. Append the entry’s name to result.
2. Append a single U+003D EQUALS SIGN character (=) to result.
3. Append the entry’s value to result.
4. Append a U+000D CARRIAGE RETURN (CR) U+000A LINE FEED (LF)
character pair to result.
7. Return the result of encoding result using encoding.
Payloads using the text/plain format are intended to be human readable.
They are not reliably interpretable by computer, as the format is
ambiguous (for example, there is no way to distinguish a literal newline
in a value from the newline at the end of the value).
4.10.22. Resetting a form
When a form element form is reset, the user agent must fire a simple event
named reset, that bubbles and is cancelable, at form, and then, if that
event is not canceled, must invoke the reset algorithm of each resettable
element whose form owner is form.
When the reset algorithm is invoked by the reset() method, the reset event
fired by the reset algorithm must not be trusted.
Each resettable element defines its own reset algorithm. Changes made to
form controls as part of these algorithms do not count as changes caused
by the user (and thus, e.g., do not cause input events to fire).
4.11. Interactive elements
4.11.1. The details element
Categories:
Flow content.
Sectioning root.
Interactive content.
Palpable content.
Contexts in which this element can be used:
Where flow content is expected.
Content model:
One summary element followed by flow content.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
open - Whether the details are visible
Allowed ARIA role attribute values:
group role (default - do not set)
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the default role.
DOM interface:
interface HTMLDetailsElement : HTMLElement {
attribute boolean open;
};
The details element represents a disclosure widget from which the user can
obtain additional information or controls.
The details element is not appropriate for footnotes. Please see §4.13.5
Footnotes for details on how to mark up footnotes.
If the details element has a summary child element, then the first summary
child element represents the summary or legend of the details element. If
there is no summary child element, a user agent should provide its own
legend (e.g. in English "Details" or Spanish "Detalles").
The legend text should be presented in the language determined from the
computed language of the element, if available, rather than from the
locale of the browser/system.
The rest of the element’s contents represents the additional information
or controls.
The open content attribute is a boolean attribute. If present, it
indicates that both the summary and the additional information is to be
shown to the user. If the attribute is absent, only the summary is to be
shown.
When the element is created, if the attribute is absent, the additional
information should be hidden; if the attribute is present, that
information should be shown. Subsequently, if the attribute is removed,
then the information should be hidden; if the attribute is added, the
information should be shown.
The user agent should allow the user to request that the additional
information be shown or hidden. To honor a request for the details to be
shown, the user agent must set the open attribute on the element to the
empty string. To honor a request for the information to be hidden, the
user agent must remove the open attribute from the element.
This ability to request that additional information be shown or hidden may
simply be the activation behavior of the appropriate summary element, in
the case such an element exists. However, if no such element exists, user
agents can still provide this ability through some other user interface
affordance.
Whenever the open attribute is added to or removed from a details element,
the user agent must queue a task that runs the following steps, which are
known as the details notification task steps, for this details element:
1. If another task has been queued to run the details notification task
steps for this details element, then abort these steps.
When the open attribute is toggled several times in succession, these
steps essentially get coalesced so that only one event is fired.
2. Fire a simple event named toggle at the details element.
The task source for this task must be the DOM manipulation task source.
The open IDL attribute must reflect the open content attribute.
The following example shows the details element being used to hide
technical details in a progress report.
Copying "Really Achieving Your Childhood Dreams"
Copying...
Transfer rate: 452KB/s
Local filename: /home/rpausch/raycd.m4v
Remote filename: /var/www/lectures/raycd.m4v
Duration: 01:16:27
Color profile: SD (6-1-6)
Dimensions: 320×240
The following shows how a details element can be used to hide some
controls by default:
Name & Extension:
One could use this in conjunction with other details in a list to allow
the user to collapse a set of fields down to a small set of headings, with
the ability to open each one.
In these examples, the summary really just summarizes what the controls
can change, and not the actual values, which is less than ideal.
Because the open attribute is added and removed automatically as the user
interacts with the control, it can be used in CSS to style the element
differently based on its state. Here, a stylesheet is used to animate the
color of the summary when the element is opened or closed:
Automated Status: Operational
Velocity: 12m/s
Direction: North
4.11.2. The summary element
Categories:
None.
Contexts in which this element can be used:
As the first child of a details element.
Content model:
Either: phrasing content.
Or: one element of heading content.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
Allowed ARIA role attribute values:
button.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the allowed roles.
DOM interface:
Uses HTMLElement.
The first summary child element of a details element represents a summary,
caption, or legend for the rest of the contents of the parent details
element, if any.
The activation behavior of summary elements is to run the following steps:
1. If this summary element has no parent node, then abort these steps.
2. Let parent be this summary element’s parent node.
3. If parent is not a details element, then abort these steps.
4. If the open attribute is present on parent, then remove it. Otherwise,
set parent’s open attribute to the empty string.
This will then run the details notification task steps.
4.11.3. Commands
4.11.3.1. Facets
A command is the abstraction behind buttons, and links. Once a command is
defined, other parts of the interface can refer to the same command,
allowing many access points to a single feature to share facets such as
the Disabled State.
Commands are defined to have the following facets:
Label
The name of the command as seen by the user.
Access Key
A key combination selected by the user agent that triggers the
command. A command might not have an Access Key.
Hidden State
Whether the command is hidden or not.
Disabled State
Whether the command is relevant and can be triggered or not.
Action
The actual effect that triggering the command will have. This
could be a scripted event handler, a URL to which to navigate, or
a form submission.
User agents may expose the commands that match the following criteria:
* The Hidden State facet is false (visible)
* The element is in a Document that has an associated browsing context.
* Neither the element nor any of its ancestors has a hidden attribute
specified.
User agents are encouraged to do this especially for commands that have
Access Keys, as a way to advertise those keys to the user.
4.11.3.2. Using the a element to define a command
An a element with an href attribute defines a command.
The Label of the command is the string given by the element’s textContent
IDL attribute.
The Access Key of the command is the element’s assigned access key, if
any.
The Hidden State of the command is true (hidden) if the element has a
hidden attribute, and false otherwise.
The Disabled State facet of the command is true if the element or one of
its ancestors is inert, and false otherwise.
The Action of the command, if the element has a defined activation
behavior, is to run synthetic click activation steps on the element.
Otherwise, it is just to fire a click event at the element.
4.11.3.3. Using the button element to define a command
A button element always defines a command.
The Label, Access Key, Hidden State, and Action facets of the command are
determined as for a elements (see the previous section).
The Disabled State of the command is true if the element or one of its
ancestors is inert, or if the element’s disabled state is set, and false
otherwise.
4.11.3.4. Using the input element to define a command
An input element whose type attribute is in one of the Submit Button,
Reset Button, Image Button, Button, Radio Button, or Checkbox states
defines a command.
The Label of the command is determined as follows:
* If the type attribute is in one of the Submit Button, Reset Button,
Image Button, or Button states, then the Label is the string given by
the value attribute, if any, and a user agent-dependent,
locale-dependent value that the user agent uses to label the button
itself if the attribute is absent.
* Otherwise, if the element is a labeled control, then the Label is the
string given by the textContent of the first label element in tree
order whose labeled control is the element in question. (In DOM terms,
this is the string given by element.labels[0].textContent.)
* Otherwise, if the value attribute is present, then the Label is the
value of that attribute.
* Otherwise, the Label is the empty string.
The Access Key of the command is the element’s assigned access key, if
any.
The Hidden State of the command is true (hidden) if the element has a
hidden attribute, and false otherwise.
The Disabled State of the command is true if the element or one of its
ancestors is inert, or if the element’s disabled state is set, and false
otherwise.
The Action of the command, if the element has a defined activation
behavior, is to run synthetic click activation steps on the element.
Otherwise, it is just to fire a click event at the element.
4.11.3.5. Using the option element to define a command
An option element with an ancestor select element and either no value
attribute or a value attribute that is not the empty string defines a
command.
The Label of the command is the value of the option element’s label
attribute, if there is one, or else the value of option element’s
textContent IDL attribute, with leading and trailing white space stripped,
and with any sequences of two or more space characters replaced by a
single U+0020 SPACE character.
The Access Key of the command is the element’s assigned access key, if
any.
The Hidden State of the command is true (hidden) if the element has a
hidden attribute, and false otherwise.
The Disabled State of the command is true if the element is disabled, or
if its nearest ancestor select element is disabled, or if it or one of its
ancestors is inert, and false otherwise.
If the option’s nearest ancestor select element has a multiple attribute,
the Action of the command is to pick the option element. Otherwise, the
Action is to toggle the option element.
4.11.3.6. Using the accesskey attribute on a label element to define a
command
A label element that has an assigned access key and a labeled control and
whose labeled control defines a command, itself defines a command.
The Label of the command is the string given by the element’s textContent
IDL attribute.
The Access Key of the command is the element’s assigned access key.
The Hidden State, Disabled State, and Action facets of the command are the
same as the respective facets of the element’s labeled control.
4.11.3.7. Using the accesskey attribute on a legend element to define a
command
A legend element that has an assigned access key and is a child of a
fieldset element that has a descendant that is not a descendant of the
legend element and is neither a label element nor a legend element but
that defines a command, itself defines a command.
The Label of the command is the string given by the element’s textContent
IDL attribute.
The Access Key of the command is the element’s assigned access key.
The Hidden State, Disabled State, and Action facets of the command are the
same as the respective facets of the first element in tree order that is a
descendant of the parent of the legend element that defines a command but
is not a descendant of the legend element and is neither a label nor a
legend element.
4.11.3.8. Using the accesskey attribute to define a command on other
elements
An element that has an assigned access key defines a command.
If one of the earlier sections that define elements that define commands
define that this element defines a command, then that section applies to
this element, and this section does not. Otherwise, this section applies
to that element.
The Label of the command depends on the element. If the element is a
labeled control, the textContent of the first label element in tree order
whose labeled control is the element in question is the Label (in DOM
terms, this is the string given by element.labels[0].textContent).
Otherwise, the Label is the textContent of the element itself.
The Access Key of the command is the element’s assigned access key.
The Hidden State of the command is true (hidden) if the element has a
hidden attribute, and false otherwise.
The Disabled State of the command is true if the element or one of its
ancestors is inert, and false otherwise.
The Action of the command is to run the following steps:
1. Run the focusing steps for the element.
2. If the element has a defined activation behavior, run synthetic click
activation steps on the element.
3. Otherwise, if the element does not have a defined activation behavior,
fire a click event at the element.
4.11.4. The dialog element
Categories:
Flow content.
Sectioning root.
Contexts in which this element can be used:
Where flow content is expected.
Content model:
Flow content.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
open - Whether the dialog box is showing
Allowed ARIA role attribute values:
dialog (default - do not set) or alertdialog.
Allowed ARIA state and property attributes:
Global aria-* attributes
Any aria-* attributes applicable to the default or allowed roles.
DOM interface:
interface HTMLDialogElement : HTMLElement {
attribute boolean open;
attribute DOMString returnValue;
void show(optional (MouseEvent or Element) anchor);
void showModal(optional (MouseEvent or Element) anchor);
void close(optional DOMString returnValue);
};
The dialog element represents a part of an application that a user
interacts with to perform a task, for example a dialog box, inspector, or
window.
The open attribute is a boolean attribute. When specified, it indicates
that the dialog element is active and that the user can interact with it.
The following is an example of a modal dialog which provides a form for a
user to add coins to their wallet, as part of an online game.
...
Add to Wallet
How many gold coins do you want to add to your wallet?
You add coins at your own risk.
...
Add to Wallet Dialog
A dialog element without an open attribute specified should not be shown
to the user. This requirement may be implemented indirectly through the
style layer. For example, user agents that support the suggested default
rendering implement this requirement using the CSS rules described in §10
Rendering.
The tabindex attribute must not be specified on dialog elements.
dialog . show( [ anchor ] )
Displays the dialog element.
The argument, if provided, provides an anchor point to which the
element will be fixed.
dialog . showModal( [ anchor ] )
Displays the dialog element and makes it the top-most modal
dialog.
The argument, if provided, provides an anchor point to which the
element will be fixed.
This method honors the autofocus attribute.
dialog . close( [ result ] )
Closes the dialog element.
The argument, if provided, provides a return value.
dialog . returnValue [ = result ]
Returns the dialog’s return value.
Can be set, to update the return value.
When the show() method is invoked, the user agent must run the following
steps:
1. If the element already has an open attribute, then abort these steps.
2. Add an open attribute to the dialog element, whose value is the empty
string.
3. If the show() method was invoked with an argument, set up the position
of the dialog element, using that argument as the anchor. Otherwise,
set the dialog to the normal alignment mode.
4. Run the dialog focusing steps for the dialog element.
----------------------------------------------------------------------
Each Document has a stack of dialog elements known as the pending dialog
stack. When a Document is created, this stack must be initialized to be
empty.
When an element is added to the pending dialog stack, it must also be
added to the top layer. When an element is removed from the pending dialog
stack, it must be removed from the top layer. [FULLSCREEN]
When the showModal() method is invoked, the user agent must run the
following steps:
1. Let subject be the dialog element on which the method was invoked.
2. If subject already has an open attribute, then throw an
InvalidStateError exception and abort these steps.
3. If subject is not in a Document, then throw an InvalidStateError
exception and abort these steps.
4. Add an open attribute to subject, whose value is the empty string.
5. If the showModal() method was invoked with an argument, set up the
position of subject, using that argument as the anchor. Otherwise, set
the dialog to the centered alignment mode.
6. Let subject’s node document be blocked by the modal dialog subject.
7. Push subject onto subject’s node document’s pending dialog stack.
8. Run the dialog focusing steps for subject.
The dialog focusing steps for a dialog element subject are as follows:
1. If for some reason subject is not a control group owner at this point,
or if it is inert, abort these steps.
2. Let control be the first non-inert focusable area in subject’s control
group whose DOM anchor has an autofocus attribute specified.
If there isn’t one, then let control be the first non-inert focusable
area in subject’s control group.
If there isn’t one of those either, then let control be subject.
3. Run the focusing steps for control.
If at any time a dialog element is removed from a Document, then if that
dialog is in that Document’s pending dialog stack, the following steps
must be run:
1. Let subject be that dialog element and document be the Document from
which it is being removed.
2. Remove subject from document’s pending dialog stack.
3. If document’s pending dialog stack is not empty, then let document be
blocked by the modal dialog that is at the top of document’s pending
dialog stack. Otherwise, let document be no longer blocked by a modal
dialog at all.
When the close() method is invoked, the user agent must close the dialog
that the method was invoked on. If the method was invoked with an
argument, that argument must be used as the return value; otherwise, there
is no return value.
When a dialog element subject is to be closed, optionally with a return
value result, the user agent must run the following steps:
1. If subject does not have an open attribute, then abort these steps.
2. Remove subject’s open attribute.
3. If the argument result was provided, then set the returnValue
attribute to the value of result.
4. If subject is in its Document’s pending dialog stack, then run these
substeps:
1. Remove subject from that pending dialog stack.
2. If that pending dialog stack is not empty, then let subject’s
node document be blocked by the modal dialog that is at the top
of the pending dialog stack. Otherwise, let document be no longer
blocked by a modal dialog at all.
5. Queue a task to fire a simple event named close at subject.
The returnValue IDL attribute, on getting, must return the last value to
which it was set. On setting, it must be set to the new value. When the
element is created, it must be set to the empty string.
----------------------------------------------------------------------
Canceling dialogs: When a Document’s pending dialog stack is not empty,
user agents may provide a user interface that, upon activation, queues a
task to fire a simple event named cancel that is cancelable at the top
dialog element on the Document’s pending dialog stack. The default action
of this event must be to check if that element has an open attribute, and
if it does, close the dialog with no return value.
An example of such a UI mechanism would be the user pressing the "Escape"
key.
----------------------------------------------------------------------
All dialog elements are always in one of three modes: normal alignment,
centered alignment, and magic alignment. When a dialog element is created,
it must be placed in the normal alignment mode. In this mode, normal CSS
requirements apply to the element. The centered alignment mode is only
used for dialog elements that are in the top layer. [FULLSCREEN]
[CSS-2015]
When an element subject is placed in centered alignment mode, and when it
is in that mode and has new rendering boxes created, the user agent must
set up the element such that its top static position, for the purposes of
calculating the used value of the top property, is the value that would
place the element’s top margin edge as far from the top of the viewport as
the element’s bottom margin edge from the bottom of the viewport, if the
element’s height is less than the height of the viewport, and otherwise is
the value that would place the element’s top margin edge at the top of the
viewport.
If there is a dialog element with centered alignment and that is being
rendered when its browsing context changes viewport width (as measured in
CSS pixels), then the user agent must recreate the element’s boxes,
recalculating its top static position as in the previous paragraph.
This top static position of a dialog element with centered alignment must
remain the element’s top static position until its boxes are recreated.
(The element’s static position is only used in calculating the used value
of the top property in certain situations; it’s not used, for instance, to
position the element if its position property is set to static.)
When a user agent is to set up the position of an element subject using an
anchor anchor, it must run the following steps:
1. If anchor is a MouseEvent object, then run these substeps:
1. If anchor’s target element does not have a rendered box, or is in
a different document than subject, then let subject be in the
centered alignment mode, and abort the set up the position steps.
2. Let anchor element be an anonymous element rendered as a box with
zero height and width (so its margin and border boxes both just
form a point), positioned so that its top and left are at the
coordinate identified by the event, and whose properties all
compute to their initial values.
Otherwise, let anchor element be anchor.
2. Put subject in the magic alignment mode, aligned to anchor element.
While an element A has magic alignment, aligned to an element B, the
following requirements apply:
* If at any time either A or B cease having rendered boxes, A and B
cease being in the same Document, or B ceases being earlier than A in
tree order, then, if subject is in the pending dialog stack, let
subject’s mode become centered alignment, otherwise, let subject’s
mode become normal alignment.
* A’s position property must compute to the keyword 'absolute-anchored'
rather than whatever it would otherwise compute to (i.e., the position
property’s specified value is ignored).
The 'absolute-anchored' keyword’s requirements are described below.
* The anchor points for A and B are defined as per the appropriate entry
in the following list:
If the computed value of anchor-point is none on both A and B
The anchor points of A and B are the center points of
their respective first boxes' border boxes.
If the computed value of anchor-point is none on A and a specific
point on B
The anchor point of B is the point given by its
anchor-point property.
If the anchor point of B is the center point of B’s first
box’s border box, then A’s anchor point is the center
point of its first box’s margin box.
Otherwise, A’s anchor point is on one of its margin
edges. Consider four hypothetical half-infinite lines L1,
L2, L3, and L4 that each start in the center of B’s first
box’s border box, and that extend respectively through
the top left corner, top right corner, bottom right
corner, and bottom left corner of B’s first box’s border
box. A’s anchor point is determined by the location of
B’s anchor point relative to these four hypothetical
lines, as follows:
If the anchor point of B lies on L1 or L2, or inside the
area bounded by L1 and L2 that also contains the points
above B’s first box’s border box, then let A’s anchor
point be the horizontal center of A’s bottom margin edge.
Otherwise, if the anchor point of B lies on L3 or L4, or
inside the area bounded by L3 and L4 that also contains
the points below B’s first box’s border box, then let A’s
anchor point be the horizontal center of A’s top margin
edge.
Otherwise, if the anchor point of B lies inside the area
bounded by L4 and L1 that also contains the points to the
left of B’s first box’s border box, then let A’s anchor
point be the vertical center of A’s right margin edge.
Otherwise, the anchor point of B lies inside the area
bounded by L2 and L3 that also contains the points to the
right of B’s first box’s border box; let A’s anchor point
be the vertical center of A’s left margin edge.
If the computed value of anchor-point is a specific point on A
and none on B
The anchor point of A is the point given by its
anchor-point property.
If the anchor point of A is the center point of A’s first
box’s margin box, then B’s anchor point is the center
point of its first box’s border box.
Otherwise, B’s anchor point is on one of its border
edges. Consider four hypothetical half-infinite lines L1,
L2, L3, and L4 that each start in the center of A’s first
box’s margin box, and that extend respectively through
the top left corner, top right corner, bottom right
corner, and bottom left corner of A’s first box’s margin
box. B’s anchor point is determined by the location of
A’s anchor point relative to these four hypothetical
lines, as follows:
If the anchor point of A lies on L1 or L2, or inside the
area bounded by L1 and L2 that also contains the points
above A’s first box’s margin box, then let B’s anchor
point be the horizontal center of B’s bottom border edge.
Otherwise, if the anchor point of A lies on L3 or L4, or
inside the area bounded by L3 and L4 that also contains
the points below A’s first box’s margin box, then let B’s
anchor point be the horizontal center of B’s top border
edge.
Otherwise, if the anchor point of A lies inside the area
bounded by L4 and L1 that also contains the points to the
left of A’s first box’s margin box, then let B’s anchor
point be the vertical center of B’s right border edge.
Otherwise, the anchor point of A lies inside the area
bounded by L2 and L3 that also contains the points to the
right of A’s first box’s margin box; let B’s anchor point
be the vertical center of B’s left border edge.
If the computed value of anchor-point is a specific point on both
A and B
The anchor points of A and B are the points given by
their respective anchor-point properties.
The rules above generally use A’s margin box, but B’s border box. This
is because while A always has a margin box, and using the margin box
allows for the dialog to be positioned offset from the box it is
annotating, B sometimes does not have a margin box (e.g., if it is a
table-cell), or has a margin box whose position may be not entirely
clear (e.g., in the face of margin collapsing and clear handling of
in-flow blocks).
In cases where B does not have a border box but its border box is used
by the algorithm above, user agents must use its first box’s content
area instead. (This is in particular an issue with boxes in tables
that have border-collapse set to collapse.)
* When an element’s position property computes to 'absolute-anchored',
the float property does not apply and must compute to none, the
display property must compute to a value as described by the table in
the section of CSS 2.1 describing the relationships between display,
position, and float, and the element’s box must be positioned using
the rules for absolute positioning but with its static position set
such that if the box is positioned in its static position, its anchor
point is exactly aligned over the anchor point of the element to which
it is magically aligned. Elements aligned in this way are absolutely
positioned. For the purposes of determining the containing block of
other elements, the 'absolute-anchored' keyword must be treated like
the absolute keyword.
The trivial example of an element that does not have a rendered box is one
whose display property computes to none. However, there are many other
cases; e.g., table columns do not have boxes (their properties merely
affect other boxes).
If an element to which another element is anchored changes rendering, the
anchored element will be repositioned accordingly. (In other words, the
requirements above are live, they are not just calculated once per
anchored element.)
The 'absolute-anchored' keyword is not a keyword that can be specified in
CSS; the position property can only compute to this value if the dialog
element is positioned via the APIs described above.
User agents in visual interactive media should allow the user to pan the
viewport to access all parts of a dialog element’s border box, even if the
element is larger than the viewport and the viewport would otherwise not
have a scroll mechanism (e.g., because the viewport’s overflow property is
set to hidden).
----------------------------------------------------------------------
The open IDL attribute must reflect the open content attribute.
4.11.4.1. Anchor points
This section will eventually be moved to a CSS specification; it is
specified here only on an interim basis until an editor can be found to
own this.
Name: anchor-point
Value: [ none |
]
Initial: none
Applies to: all elements
Inherited: no
Percentages: refer to width or height of box; see prose
Media: visual
Computed value: The specified value, but with any lengths replaced by
their corresponding absolute length
Canonical order: per grammar
Animatable: no
The anchor-point property specifies a point to which dialog boxes are to
be aligned.
If the value is a , the anchor point is the point given by the
value, which must be interpreted relative to the element’s first rendered
box’s margin box. Percentages must be calculated relative to the element’s
first rendered box’s margin box (specifically, its width for the
horizontal position and its height for the vertical position).
[CSS-VALUES] [CSS-2015]
If the value is the keyword none, then no explicit anchor point is
defined. The user agent will pick an anchor point automatically if
necessary (as described in the definition of the open() method above).
4.12. Scripting
Scripts allow authors to add interactivity to their documents.
Authors are encouraged to use declarative alternatives to scripting where
possible, as declarative mechanisms are often more maintainable, and many
users disable scripting.
For example, instead of using script to show or hide a section to show
more details, the details element could be used.
Authors are also encouraged to make their applications degrade gracefully
in the absence of scripting support.
For example, if an author provides a link in a table header to dynamically
resort the table, the link could also be made to function without scripts
by requesting the sorted table from the server.
4.12.1. The script element
Categories:
Metadata content.
Flow content.
Phrasing content.
Script-supporting element.
Contexts in which this element can be used:
Where metadata content is expected.
Where phrasing content is expected.
Where script-supporting elements are expected.
Content model:
If there is no src attribute, depends on the value of the type
attribute, but must match script content restrictions.
If there is a src attribute, the element must be either empty or
contain only script documentation that also matches script content
restrictions.
Tag omission in text/html:
Neither tag is omissible
Content attributes:
Global attributes
src - Address of the resource
type - Type of embedded resource
charset - Character encoding of the external script resource
async - Execute script in parallel
defer - Defer script execution
crossorigin - How the element handles crossorigin requests
nonce - Cryptographic nonce used in Content Security Policy checks
[CSP3]
Allowed ARIA role attribute values:
None
Allowed ARIA state and property attributes:
None
DOM interface:
interface HTMLScriptElement : HTMLElement {
attribute DOMString src;
attribute DOMString type;
attribute DOMString charset;
attribute boolean async;
attribute boolean defer;
attribute DOMString? crossOrigin;
attribute DOMString text;
attribute DOMString nonce;
};
The script element allows authors to include dynamic script and data
blocks in their documents. The element does not represent content for the
user.
The type attribute allows customization of the type of script represented:
* Omitting the attribute, or setting it to a JavaScript MIME type, means
that the script is a classic script, to be interpreted according to
the JavaScript Script top-level production. Classic scripts are
affected by the charset, async, and defer attributes. Authors should
omit the attribute, instead of redundantly giving a JavaScript MIME
type.
* Setting the attribute to an ASCII case-insensitive match for the
string "module" means that the script is a module script, to be
interpreted according to the JavaScript Module top-level production.
Module scripts are not affected by the charset and defer attributes.
* Setting the attribute to any other value means that the script is a
data block, which is not processed. None of the script attributes
(except type itself) have any effect on data blocks. Authors must use
a valid MIME type that is not a JavaScript MIME type to denote data
blocks.
The requirement that data blocks must be denoted using a valid MIME type
is in place to avoid potential future collisions. If this specification
ever adds additional types of script, they will be triggered by setting
the type attribute to something which is not a MIME type, like how the
"module" value denotes module scripts. By using a valid MIME type now, you
ensure that your data block will not ever be reinterpreted as a different
script type, even in future user agents.
Classic scripts and module scripts may either be embedded inline or may be
imported from an external file using the src attribute, which if specified
gives the URL of the external script resource to use. If src is specified,
it must be a valid non-empty URL potentially surrounded by spaces. The
contents of inline script elements, or the external script resource, must
conform with the requirements of the JavaScript specification’s Script or
Module productions, for classic scripts and module scripts respectively.
[ECMA-262]
When used to include data blocks, the data must be embedded inline, the
format of the data must be given using the type attribute, and the
contents of the script element must conform to the requirements defined
for the format used. The src, charset, async, defer, crossorigin, and
nonce attributes must not be specified.
The charset attribute gives the character encoding of the external script
resource. The attribute must not be specified if the src attribute is not
present, or if the script is not a classic script. (Module scripts are
always interpreted as UTF-8.) If the attribute is set, its value must be
an ASCII case-insensitive match for one of the labels of an encoding, and
must specify the same encoding as the charset parameter of the
Content-Type metadata of the external file, if any. [ENCODING]
The async and defer attributes are boolean attributes that indicate how
the script should be executed. Classic scripts may specify defer or async;
module scripts may specify async.
There are several possible modes that can be selected using these
attributes, and depending on the script’s type.
For classic scripts, if the async attribute is present, then the classic
script will be fetched in parallel to parsing and evaluated as soon as it
is available (potentially before parsing completes). If the async
attribute is not present but the defer attribute is present, then the
classic script will be fetched in parallel and evaluated when the page has
finished parsing. If neither attribute is present, then the script is
fetched and evaluated immediately, blocking parsing until these are both
complete.
For module scripts, if the async attribute is present, then the module
script and all its dependencies will be fetched in parallel to parsing,
and the module script will be evaluated as soon as it is available
(potentially before parsing completes). Otherwise, the module script and
its dependencies will be fetched in parallel to parsing and evaluated when
the page has finished parsing. (The defer attribute has no effect on
module scripts.)
This is all summarized in the following schematic diagram:
With
The data in this case might be used by the script to generate the map of a
video game. The data doesn’t have to be used that way, though; maybe the
map data is actually embedded in other parts of the page’s markup, and the
data block here is just used by the site’s search engine to help users who
are looking for particular features in their game maps.
The following sample shows how a script element can be used to define a
function that is then used by other parts of the document, as part of a
classic script. It also shows how a script element can be used to invoke
script while the document is being parsed, in this case to initialize the
form’s output.
The following sample shows how a script element can be used to include an
external module script.
This module, and all its dependencies (expressed through JavaScript import
statements in the source file), will be fetched. Once the entire resulting
module tree has been imported, and the document has finished parsing, the
contents of app.js will be evaluated.
The following sample shows how a script element can be used to write an
inline module script that performs a number of substitutions on the
document’s text, in order to make for a more interesting reading
experience (e.g. on a news site): [XKCD-1288]
Some notable features gained by using a module script include the ability
to import functions from other JavaScript modules, strict mode by default,
and how top-level declarations do not introduce new properties onto the
global object. Also note that no matter where this script element appears
in the document, it will not be evaluated until both document parsing has
complete and its dependency (dom-utils.js) has been fetched and evaluated.
4.12.1.1. Processing model
A script element has several associated pieces of state.
The first is a flag indicating whether or not the script block has been
"already started". Initially, script elements must have this flag unset
(script blocks, when created, are not "already started"). The cloning
steps for script elements must set the "already started" flag on the copy
if it is set on the element being cloned.
The second is a flag indicating whether the element was "parser-inserted".
Initially, script elements must have this flag unset. It is set by the
HTML parser and the XML parser on script elements they insert and affects
the processing of those elements.
The third is a flag indicating whether the element will "non-blocking".
Initially, script elements must have this flag set. It is unset by the
HTML parser and the XML parser on script elements they insert. In
addition, whenever a script element whose "non-blocking" flag is set has
an async content attribute added, the element’s "non-blocking" flag must
be unset.
The fourth is a flag indicating whether or not the script block is "ready
to be parser-executed". Initially, script elements must have this flag
unset (script blocks, when created, are not "ready to be
parser-executed"). This flag is used only for elements that are also
"parser-inserted", to let the parser know when to execute the script.
The fifth is the script’s type, which is either "classic" or "module". It
is determined when the script is prepared, based on the type attribute of
the element at that time. Initially, script elements must have this flag
unset.
The sixth is a flag indicating whether or not the script is from an
external file. It is determined when the script is prepared, based on the
src attribute of the element at that time.
Finally, a script element has the script’s script, which is a script
resulting from preparing the element. This is set asynchronously after the
classic script or module tree is fetched. Once it is set, either to a
script in the case of success or to null in the case of failure, the
fetching algorithms will note that the script is ready, which can trigger
other actions. The user agent must delay the load event of the element’s
node document until the script is ready.
When a script element that is not marked as being "parser-inserted"
experiences one of the events listed in the following list, the user agent
must immediately prepare the script element:
* The script element gets inserted into a document, at the time the node
is inserted according to the DOM, after any other script elements
inserted at the same time that are earlier in the Document in tree
order.
* The script element is in a Document and a node or document fragment is
inserted into the script element, after any script elements inserted
at that time.
* The script element is in a Document and has a src attribute set where
previously the element had no such attribute.
To prepare a script, the user agent must act as follows:
1. If the script element is marked as having "already started", then the
user agent must abort these steps at this point. The script is not
executed.
2. If the element has its "parser-inserted" flag set, then set
was-parser-inserted to true and unset the element’s "parser-inserted"
flag. Otherwise, set was-parser-inserted to false.
This is done so that if parser-inserted script elements fail to run
when the parser tries to run them, e.g., because they are empty or
specify an unsupported scripting language, another script can later
mutate them and cause them to run again.
3. If was-parser-inserted is true and the element does not have an async
attribute, then set the element’s "non-blocking" flag to true.
This is done so that if a parser-inserted script element fails to run
when the parser tries to run it, but it is later executed after a
script dynamically updates it, it will execute in a non-blocking
fashion even if the async attribute isn’t set.
4. If the element has no src attribute, and its child nodes, if any,
consist only of comment nodes and empty Text nodes, then abort these
steps at this point. The script is not executed.
5. If the element is not in a Document, then the user agent must abort
these steps at this point. The script is not executed.
6. If either:
* the script element has a type attribute and its value is the
empty string, or
* the script element has no type attribute but it has a language
attribute and that attribute’s value is the empty string, or
* the script element has neither a type attribute nor a language
attribute, then
...let the script block’s type string for this script element be
"text/javascript".
Otherwise, if the script element has a type attribute, let the script
block’s type string for this script element be the value of that
attribute with any leading or trailing sequences of space characters
removed.
Otherwise, the element has a non-empty language attribute; let the
script block’s type string for this script element be the child text
content of the language attribute.
The language attribute is never conforming, and is always ignored if
there is a type attribute present.
Determine the script’s type as follows:
* If the script block’s type string is an ASCII case-insensitive
match for any JavaScript MIME type, the script’s type is
"classic".
* If the script block’s type string is an ASCII case-insensitive
match for the string "module", the script’s type is "module".
* If neither of the above conditions are true, then abort these
steps at this point. No script is executed.
7. If was-parser-inserted is true, then flag the element as
"parser-inserted" again, and set the element’s "non-blocking" flag to
false.
8. The user agent must set the element’s "already started" flag.
9. If the element is flagged as "parser-inserted", but the element’s node
document is not the Document of the parser that created the element,
then abort these steps.
10. If scripting is disabled for the script element, then abort these
steps at this point. The script is not executed.
The definition of scripting is disabled means that, amongst others,
the following scripts will not execute: scripts in XMLHttpRequest's
responseXML documents, scripts in DOMParser-created documents, scripts
in documents created by XSLTProcessor’s transformToDocument feature,
and scripts that are first inserted by a script into a Document that
was created using the createDocument() API. [XHR] [DOM-PARSING]
[XSLTP] [DOM41]
11. If the script element does not have a src content attribute, and the
Should element’s inline behavior be blocked by Content Security
Policy? algorithm returns "Blocked" when executed upon the script
element, "script", and the script element’s child text content, then
abort these steps. The script is not executed. [CSP3]
12. If the script element has an event attribute and a for attribute, and
the script’s type is "classic", then run these substeps:
1. Let for be the value of the for attribute.
2. Let event be the value of the event attribute.
3. Strip leading and trailing white space from event and for.
4. If for is not an ASCII case-insensitive match for the string
"window", then the user agent must abort these steps at this
point. The script is not executed.
5. If event is not an ASCII case-insensitive match for either the
string "onload" or the string "onload()", then the user agent
must abort these steps at this point. The script is not executed.
13. If the script element has a charset attribute, then let encoding be
the result of getting an encoding from the value of the charset
attribute.
If the script element does not have a charset attribute, or if getting
an encoding failed, let encoding be the same as the encoding of the
document itself.
If the script’s type is "module", this encoding will be ignored.
14. Let CORS setting be the current state of the element’s crossorigin
content attribute.
15. If the script element has a nonce attribute, then let cryptographic
nonce be that attribute’s value.
Otherwise, let cryptographic nonce be the empty string.
16. Let parser state be "parser-inserted" if the script element has been
flagged as "parser-inserted", and "not parser-inserted" otherwise.
17. Let settings be the element’s node document’s Window object’s
environment settings object.
18. If the element has a src content attribute, run these substeps:
1. Let src be the value of the element’s src attribute.
2. If src is the empty string, queue a task to fire a simple event
named error at the element, and abort these steps.
3. Set the element’s from an external file flag.
4. Parse src relative to the element’s node document.
5. If the previous step failed, queue a task to fire a simple event
named error at the element, and abort these steps.
Otherwise, let url be the resulting URL record.
6. Switch on the script’s type:
"classic"
Fetch a classic script given url, CORS setting,
cryptographic nonce, parser state, settings, and
encoding.
"module"
1. Let credentials mode be determined by switching
on CORS setting:
No CORS
"omit"
Anonymous
"same-origin"
Use Credentials
"include"
2. Fetch a module script tree given url,
credentials mode, cryptographic nonce, parser
state, "script", and settings.
When the chosen algorithm asynchronously completes, set the
script’s script to the result. At that time, the script is ready.
For performance reasons, user agents may start fetching the
classic script or module tree (as defined above) as the src
attribute is set, instead, in the hope that the element will be
inserted into the document (and that the crossorigin attribute
won’t change value in the meantime). Either way, once the element
is inserted into the document, the load must have started as
described in this step. If the UA performs such prefetching, but
the element is never inserted in the document, or the src
attribute is dynamically changed, or the crossorigin attribute is
dynamically changed, then the user agent will not execute the
script so obtained, and the fetching process will have been
effectively wasted.
19. If the element does not have a src content attribute, run these
substeps:
1. Let source text be the value of the text IDL attribute.
2. Switch on the script’s type:
"classic"
1. Let script be the result of creating a classic
script using source text and settings.
2. Set the script’s script to script.
3. The script is ready.
"module"
1. Let base URL be the script element’s node
document’s document base URL.
2. Let script be the result of creating a module
script using source text, settings, base URL,
and CORS setting.
3. If this returns null, set the script’s script
to null and abort these substeps; the script is
ready.
4. Fetch the descendants of script. When this
asynchronously completes, set the script’s
script to the result. At that time, the script
is ready.
20. Then, follow the first of the following options that describes the
situation:
the src defer async
script’s present? present? present? other conditions
type
element flagged
"classic" yes yes no as
"parser-inserted"
element flagged
"module" yes or no n/a no as
"parser-inserted"
Add the element to the end of the list of scripts that
will execute when the document has finished parsing
associated with the Document of the parser that created
the element.
When the the script is ready, set the element’s "ready to
be parser-executed" flag. The parser will handle
executing the script.
the src defer async
script’s present? present? present? other conditions
type
element flagged
"classic" yes no no as
"parser-inserted"
The element is the pending parsing-blocking script of the
Document of the parser that created the element. (There
can only be one such script per Document at a time.)
When the script is ready, set the element’s "ready to be
parser-executed" flag. The parser will handle executing
the script.
the src defer async
script’s present? present? present? other conditions
type
"non-blocking"
"classic" yes yes or no no flag not set on
element
"non-blocking"
"module" yes or no n/a no flag not set on
element
Add the element to the end of the list of scripts that
will execute in order as soon as possible associated with
the node document of the script element at the time the
prepare a script algorithm started.
When the script is ready, run the following steps:
1. If the element is not now the first element in the
list of scripts that will execute in order as soon
as possible to which it was added above, then mark
the element as ready but abort these steps without
executing the script yet.
2. Execution: Execute the script block corresponding to
the first script element in this list of scripts
that will execute in order as soon as possible.
3. Remove the first element from this list of scripts
that will execute in order as soon as possible.
4. If this list of scripts that will execute in order
as soon as possible is still not empty and the first
entry has already been marked as ready, then jump
back to the step labeled Execution.
the script’s src defer async other
type present? present? present? conditions
"classic" yes yes or no yes or no n/a
"module" yes or no n/a yes or no n/a
The element must be added to the set of scripts that will
execute as soon as possible of the node document of the
script element at the time the prepare a script algorithm
started.
When the script is ready, execute the script block and
then remove the element from the set of scripts that will
execute as soon as possible.
the src defer async
script’s present? present? present? other conditions
type
All of the following:
* element flagged
as
"parser-inserted"
* an XML parser or
an HTML parser
whose script
nesting level is
"classic" yes or yes or not greater than
or no no no one created the
"module" script
* the Document of
the XML parser or
HTML parser that
created the
script has a
style sheet that
is blocking
scripts
The element is the pending parsing-blocking script of the
Document of the parser that created the element. (There
can only be one such script per Document at a time.)
Set the element’s "ready to be parser-executed" flag. The
parser will handle executing the script.
Otherwise
Immediately execute the script block, even if other
scripts are already executing.
The pending parsing-blocking script of a Document is used by the
Document's parser(s).
If a script element that blocks a parser gets moved to another Document
before it would normally have stopped blocking that parser, it nonetheless
continues blocking that parser until the condition that causes it to be
blocking the parser no longer applies (e.g., if the script is a pending
parsing-blocking script because there was a style sheet that is blocking
scripts when it was parsed, but then the script is moved to another
Document before the style sheet loads, the script still blocks the parser
until the style sheets are all loaded, at which time the script executes
and the parser is unblocked).
When the user agent is required to execute a script block, it must run the
following steps:
1. If the element is flagged as "parser-inserted", but the element’s node
document is not the Document of the parser that created the element,
then abort these steps.
2. If the script’s script is null, fire a simple event named error at the
element, and abort these steps.
3. If the script is from an external file, or the script’s type is
"module", then increment the ignore-destructive-writes counter of the
script element’s node document. Let neutralized doc be that Document.
4. Let old script element be the value to which the script element’s node
document’s currentScript object was most recently set.
5. Switch on the script’s type:
"classic"
1. Set the script element’s node document’s
currentScript attribute to the script element.
This does not use the in a document check, as the
script element could have been removed from the
document prior to execution, and in that scenario
currentScript still needs to point to it.
2. Run the classic script given by the script’s script.
"module"
1. Set the script element’s node document’s
currentScript attribute to null.
2. Run the module script given by the script’s script.
6. Set the script element’s node document’s currentScript object to old
script element.
7. Decrement the ignore-destructive-writes counter of neutralized doc, if
it was incremented in the earlier step.
8. If the script’s type is "classic" and the script is from an external
file, fire a simple event named load at the script element.
Otherwise queue a task to fire a simple event named load at the script
element.
4.12.1.2. Scripting languages
A JavaScript MIME type is a MIME type string that is one of the following
and refers to JavaScript: [ECMA-262]
* application/ecmascript
* application/javascript
* application/x-ecmascript
* application/x-javascript
* text/ecmascript
* text/javascript
* text/javascript1.0
* text/javascript1.1
* text/javascript1.2
* text/javascript1.3
* text/javascript1.4
* text/javascript1.5
* text/jscript
* text/livescript
* text/x-ecmascript
* text/x-javascript
User agents must recognize all JavaScript MIME types.
User agents may support other MIME types for other languages, but must not
support other MIME types for the languages in the list above. User agents
are not required to support JavaScript. The processing model for languages
other than JavaScript is outside the scope of this specification.
The following MIME types (with or without parameters) must not be
interpreted as scripting languages:
* text/plain
* text/xml
* application/octet-stream
* application/xml
These types are explicitly listed here because they are poorly-defined
types that are nonetheless likely to be used as formats for data blocks,
and it would be problematic if they were suddenly to be interpreted as
script by a user agent.
When examining types to determine if they represent supported languages,
user agents must not ignore MIME parameters. Types are to be compared
including all parameters.
For example, types that include the charset parameter will not be
recognized as referencing any of the scripting languages listed above.
4.12.1.3. Restrictions for contents of script elements
The easiest and safest way to avoid the rather strange restrictions
described in this section is to always escape "<!--" as "<\!--",
"<script" as "<\script", and "</script" as "<\/script" when
these sequences appear in literals in scripts (e.g., in strings, regular
expressions, or comments), and to avoid writing code that uses such
constructs in expressions. Doing so avoids the pitfalls that the
restrictions in this section are prone to triggering: namely, that, for
historical reasons, parsing of script blocks in HTML is a strange and
exotic practice that acts unintuitively in the face of these sequences.
The textContent of a script element must match the script production in
the following ABNF, the character set for which is Unicode. [ABNF]
script = outer *( comment-open inner comment-close outer )
outer = < any string that doesn’t contain a substring that matches not-in-outer >
not-in-outer = comment-open
inner = < any string that doesn’t contain a substring that matches not-in-inner >
not-in-inner = comment-close / script-open
comment-open = ""
script-open = "<" s c r i p t tag-end
s = %x0053 ; U+0053 LATIN CAPITAL LETTER S
s =/ %x0073 ; U+0073 LATIN SMALL LETTER S
c = %x0043 ; U+0043 LATIN CAPITAL LETTER C
c =/ %x0063 ; U+0063 LATIN SMALL LETTER C
r = %x0052 ; U+0052 LATIN CAPITAL LETTER R
r =/ %x0072 ; U+0072 LATIN SMALL LETTER R
i = %x0049 ; U+0049 LATIN CAPITAL LETTER I
i =/ %x0069 ; U+0069 LATIN SMALL LETTER I
p = %x0050 ; U+0050 LATIN CAPITAL LETTER P
p =/ %x0070 ; U+0070 LATIN SMALL LETTER P
t = %x0054 ; U+0054 LATIN CAPITAL LETTER T
t =/ %x0074 ; U+0074 LATIN SMALL LETTER T
tag-end = %x0009 ; U+0009 CHARACTER TABULATION (tab)
tag-end =/ %x000A ; U+000A LINE FEED (LF)
tag-end =/ %x000C ; U+000C FORM FEED (FF)
tag-end =/ %x0020 ; U+0020 SPACE
tag-end =/ %x002F ; U+002F SOLIDUS (/)
tag-end =/ %x003E ; U+003E GREATER-THAN SIGN (>)
When a script element contains script documentation, there are further
restrictions on the contents of the element, as described in the section
below.
The following script illustrates this issue. Suppose you have a script
that contains a string, as in:
var example = 'Consider this string:
What is going on here is that for legacy reasons, "<!--" and
"<script" strings in script elements in HTML need to be balanced in
order for the parser to consider closing the block.
By escaping the problematic strings as mentioned at the top of this
section, the problem is avoided entirely:
It is possible for these sequences to naturally occur in script
expressions, as in the following examples:
if (x
The hidden attribute must not be used to hide content just from one
presentation — if something is marked hidden, it is hidden from all
presentations, including, for instance, screen readers.
Elements that are not themselves hidden must not hyperlink to elements
that are hidden. The for attributes of label and output elements that are
not themselves hidden must similarly not refer to elements that are
hidden. In both cases, such references would cause user confusion.
Elements and scripts may, however, refer to elements that are hidden in
other contexts.
For example, it would be incorrect to use the href attribute to link to a
section marked with the hidden attribute. If the content is not applicable
or relevant, then there is no reason to link to it.
It would be fine, however, to use the ARIA aria-describedby attribute to
refer to descriptions that are themselves hidden. While hiding the
descriptions implies that they are not useful alone, they could be written
in such a way that they are useful in the specific context of being
referenced from the images that they describe.
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 attribute.
Accessibility APIs are encouraged to provide a way to expose structured
content while marking it as hidden in the default view. Such content
should not be perceivable to users in the normal document flow in any
modality, whether using Assistive Technology (AT) or mainstream User
Agents.
When such features are available, User Agents may use them to expose the
full semantics of hidden elements to AT when appropriate, if such content
is referenced indirectly by an ID reference or valid hash-name reference.
This allows ATs to access the structure of these hidden elements upon user
request, while keeping the content hidden in all presentations of the
normal document flow. Authors who wish to prevent user-initiated viewing
of a hidden element should not reference the element with such a
mechanism.
Because some User Agents have flattened hidden content when exposing such
content to AT, authors should not reference hidden content which would
lose essential meaning when flattened.
Elements in a section hidden by the hidden attribute are still active,
e.g., scripts and form controls in such sections still execute and submit
respectively. Only their presentation to the user changes.
The hidden IDL attribute must reflect the content attribute of the same
name.
5.2. Inert subtrees
This section does not define or create any content attribute named
"inert". This section merely defines an abstract concept of inertness.
A node (in particular elements and text nodes) can be marked as inert.
When a node is inert, then the user agent must act as if the node was
absent for the purposes of targeting user interaction events, may ignore
the node for the purposes of text search user interfaces (commonly known
as "find in page"), and may prevent the user from selecting text in that
node. User agents should allow the user to override the restrictions on
search and text selection, however.
For example, consider a page that consists of just a single inert
paragraph positioned in the middle of a body. If a user moves their
pointing device from the body over to the inert paragraph and clicks on
the paragraph, no mouseover event would be fired, and the mousemove and
click events would be fired on the body element rather than the paragraph.
When a node is inert, it generally cannot be focused. Inert nodes that are
commands will also get disabled.
While a browsing context container is marked as inert, its nested browsing
context’s active document, and all nodes in that Document, must be marked
as inert.
An entire Document can be marked as blocked by a modal dialog subject.
While a Document is so marked, every node that is in the Document, with
the exception of the subject element and its descendants, must be marked
inert. (The elements excepted by this paragraph can additionally be marked
inert through other means; being part of a modal dialog does not "protect"
a node from being marked inert.)
Only one element at a time can mark a Document as being blocked by a modal
dialog. When a new dialog is made to block a Document, the previous
element, if any, stops blocking the Document.
The dialog element’s showModal() method makes use of this mechanism.
5.3. Activation
Certain elements in HTML have an activation behavior, which means that the
user can activate them. This triggers a sequence of events dependent on
the activation mechanism, and normally culminating in a click event, as
described below.
The user agent should allow the user to manually trigger elements that
have an activation behavior, for instance using keyboard or voice input,
or through mouse clicks. When the user triggers an element with a defined
activation behavior in a manner other than clicking it, the default action
of the interaction event must be to run synthetic click activation steps
on the element.
For accessibility, the keyboard’s Enter and Space keys are often used to
trigger an element’s activation behavior. [wai-aria-practices-1.1]
Each element has a click in progress flag, initially set to false.
When a user agent is to run synthetic click activation steps on an
element, the user agent must run the following steps:
1. If the element’s click in progress flag is set to true, then abort
these steps.
2. Set the click in progress flag on the element to true.
3. Run pre-click activation steps on the element.
4. Fire a click event at the element. If the run synthetic click
activation steps algorithm was invoked because the click() method was
invoked, then the isTrusted attribute must be initialized to false.
5. If this click event is not canceled, run post-click activation steps
on the element.
If the event is canceled, the user agent must run canceled activation
steps on the element instead.
6. Set the click in progress flag on the element to false.
When a pointing device is clicked, the user agent must run authentic click
activation steps instead of firing the click event. When a user agent is
to run authentic click activation steps for a given event event, it must
follow these steps:
1. Let target be the element designated by the user (the target of
event).
2. If target is a canvas element, run the canvas MouseEvent rerouting
steps. If this changes event’s target, then let target be the new
target.
3. Set the click in progress flag on target to true.
4. Let e be the nearest activatable element of target (defined below), if
any.
5. If there is an element e, run pre-click activation steps on it.
6. Dispatch event (the required click event) at target.
If there is an element e and the click event is not canceled, run
post-click activation steps on element e.
If there is an element e and the event is canceled, run canceled
activation steps on element e.
7. Set the click in progress flag on target to false.
The algorithms above don’t run for arbitrary synthetic events dispatched
by author script. The click() method can be used to make the run synthetic
click activation steps algorithm happen programmatically.
Click-focusing behavior (e.g., the focusing of a text field when user
clicks in one) typically happens before the click, when the mouse button
is first depressed, and is therefore not discussed here.
Given an element target, the nearest activatable element is the element
returned by the following algorithm:
1. If target has a defined activation behavior, then return target and
abort these steps.
2. If target has a parent element, then set target to that parent element
and return to the first step.
3. Otherwise, there is no nearest activatable element.
When a user agent is to run pre-click activation steps on an element, it
must run the pre-click activation steps defined for that element, if any.
When a user agent is to run canceled activation steps on an element, it
must run the canceled activation steps defined for that element, if any.
When a user agent is to run post-click activation steps on an element, it
must run the activation behavior defined for that element, if any.
Activation behaviors can refer to the click event that was fired by the
steps above leading up to this point.
element . click()
Acts as if the element was clicked.
The click() method must run the following steps:
1. If the element is a form control that is disabled, abort these steps.
2. Run synthetic click activation steps on the element.
5.4. Focus
5.4.1. Introduction
This section is non-normative.
An HTML user interface typically consists of multiple interactive widgets,
such as form controls, scrollable regions, links, dialog boxes, browser
tabs, and so forth. These widgets form a hierarchy, with some (e.g.,
browser tabs, dialog boxes) containing others (e.g., links, form
controls).
When interacting with an interface using a keyboard, key input is
channeled from the system, through the hierarchy of interactive widgets,
to an active widget, which is said to be focused.
Consider an HTML application running in a browser tab running in a
graphical environment. Suppose this application had a page with some text
fields and links, and was currently showing a modal dialog, which itself
had a text field and a button.
The hierarchy of focusable widgets, in this scenario, would include the
browser window, which would have, amongst its children, the browser tab
containing the HTML application. The tab itself would have as its children
the various links and text fields, as well as the dialog. The dialog
itself would have as its children the text field and the button.
If the widget with focus in this example was the text field in the dialog
box, then key input would be channeled from the graphical system to ① the
Web browser, then to ② the tab, then to ③ the dialog, and finally to ④ the
text field.
Keyboard events are always targeted at this focused element.
5.4.2. Data model
The term focusable area is used to refer to regions of the interface that
can become the target of keyboard input. Focusable areas can be elements,
parts of elements, or other regions managed by the user agent.
Each focusable area has a DOM anchor, which is a Node object that
represents the position of the focusable area in the DOM. (When the
focusable area is itself a Node, it is its own DOM anchor.) The DOM anchor
is used in some APIs as a substitute for the focusable area when there is
no other DOM object to represent the focusable area.
The following table describes what objects can be focusable areas. The
cells in the left column describe objects that can be focusable areas; the
cells in the right column describe the DOM anchors for those elements.
(The cells that span both columns are non-normative examples.)
Focusable area DOM anchor
Examples
Elements that have their tabindex focus flag set,
that are not actually disabled, that are not The element itself.
expressly inert, and that are either being rendered
or being used as relevant canvas fallback content.
iframe, (depending on platform conventions).
The shapes of area elements in an image map
associated with an img element that is being The img element.
rendered and is not expressly inert.
In the following example, the area element creates two shapes, one on each image. The DOM anchor
of the first shape is the first img element, and the DOM anchor of the second shape is the second
img element.
Activities |
Technical Reports |
Site Index |
About Consortium |
Contact
5.5.3. Processing model
An element’s assigned access key is a key combination derived from the
element’s accesskey content attribute, or assigned by the user agent,
optionally based on a user preference. Initially, an element must not have
an assigned access key.
Whenever an element’s accesskey attribute is set, changed, or removed, the
user agent must update the element’s assigned access key by running the
following steps:
1. If the element has no accesskey attribute, then skip to the fallback
step below.
2. The user agent may assign a key combination based on stored user
preferences as the element’s assigned access key and then abort these
steps.
3. Let value be the value of the accesskey attribute.
4. The user agent may strip content from value to reduce the length of
value to a single unicode code point.
5. If value is not a string of exactly one printable character, then the
user agent may abort these steps.
6. The user agent may assign a combination of a mix of zero or more
modifier keys and value as the element’s assigned access key and abort
these steps.
7. Fallback: Optionally, the user agent may assign a key combination of
its choosing as the element’s assigned access key and then abort these
steps.
8. If this step is reached, the element has no assigned access key.
Once a user agent has selected and assigned an access key for an element,
the user agent should not change the element’s assigned access key unless
the accesskey content attribute is changed or the element is moved to
another Document.
When the user presses the key combination corresponding to the assigned
access key for an element, if the element defines a command, the command’s
Hidden State facet is false (visible), the command’s Disabled State facet
is also false (enabled), the element is in a Document that has an
associated browsing context, and neither the element nor any of its
ancestors has a hidden attribute specified, then the user agent must
either focus the element, or trigger the Action of the command.
User agents might expose elements that have an accesskey attribute in
other ways as well, e.g., in a menu displayed in response to a specific
key combination, or with a user gesture.
----------------------------------------------------------------------
The accessKey IDL attribute must reflect the accesskey content attribute.
5.6. Editing
5.6.1. Making document regions editable: The contenteditable content
attribute
[NoInterfaceObject]
interface ElementContentEditable {
attribute DOMString contentEditable;
readonly attribute boolean isContentEditable;
};
The contenteditable content attribute is an enumerated attribute whose
keywords are the empty string, true, and false. The empty string and the
true keyword map to the true state. The false keyword maps to the false
state. In addition, there is a third state, the inherit state, which is
the missing value default (and the invalid value default).
The true state indicates that the element is editable. The inherit state
indicates that the element is editable if its parent is. The false state
indicates that the element is not editable.
element . contentEditable [ = value ]
Returns "true", "false", or "inherit", based on the state of the
contenteditable attribute.
Can be set, to change that state.
Throws a "SyntaxError" DOMException if the new value isn’t one of
those strings.
element . isContentEditable
Returns true if the element is editable; otherwise, returns false.
The contentEditable IDL attribute, on getting, must return the string
"true" if the content attribute is set to the true state, "false" if the
content attribute is set to the false state, and "inherit" otherwise. On
setting, if the new value is an ASCII case-insensitive match for the
string "inherit" then the content attribute must be removed, if the new
value is an ASCII case-insensitive match for the string "true" then the
content attribute must be set to the string "true", if the new value is an
ASCII case-insensitive match for the string "false" then the content
attribute must be set to the string "false", and otherwise the attribute
setter must throw a "SyntaxError" DOMException.
The isContentEditable IDL attribute, on getting, must return true if the
element is either an editing host or editable, and false otherwise.
5.6.2. Making entire documents editable: The designMode IDL attribute
Documents have a designMode, which can be either enabled or disabled.
document . designMode [ = value ]
Returns "on" if the document is editable, and "off" if it isn’t.
Can be set, to change the document’s current state. This focuses
the document and resets the selection in that document.
The designMode IDL attribute on the Document object takes two values, "on"
and "off". On setting, the new value must be compared in an ASCII
case-insensitive manner to these two values; if it matches the "on" value,
then designMode must be enabled, and if it matches the "off" value, then
designMode must be disabled. Other values must be ignored.
On getting, if designMode is enabled, the IDL attribute must return the
value "on"; otherwise it is disabled, and the attribute must return the
value "off".
The last state set must persist until the document is destroyed or the
state is changed. Initially, documents must have their designMode
disabled.
When the designMode changes from being disabled to being enabled, the user
agent must immediately reset the document’s active range’s start and end
boundary points to be at the start of the Document and then run the
focusing steps for the document element of the Document, if non-null.
5.6.3. Best practices for in-page editors
Authors are encouraged to set the white-space property on editing hosts
and on markup that was originally created through these editing mechanisms
to the value pre-wrap. Default HTML white space handling is not well
suited to WYSIWYG editing, and line wrapping will not work correctly in
some corner cases if white-space is left at its default value.
As an example of problems that occur if the default normal value is used
instead, consider the case of the user typing "yellow␣␣ball", with two
spaces (here represented by "␣") between the words. With the editing rules
in place for the default value of white-space (normal), the resulting
markup will either consist of "yellow ball" or "yellow ball";
i.e., there will be a non-breaking space between the two words in addition
to the regular space. This is necessary because the normal value for
white-space requires adjacent regular spaces to be collapsed together.
In the former case, "yellow⍽" might wrap to the next line ("⍽" being used
here to represent a non-breaking space) even though "yellow" alone might
fit at the end of the line; in the latter case, "⍽ball", if wrapped to the
start of the line, would have visible indentation from the non-breaking
space.
When white-space is set to pre-wrap, however, the editing rules will
instead simply put two regular spaces between the words, and should the
two words be split at the end of a line, the spaces would be neatly
removed from the rendering.
5.6.4. Editing APIs
The definition of the terms active range, editing host, and editable, the
user interface requirements of elements that are editing hosts or
editable, the execCommand(), queryCommandEnabled(),
queryCommandIndeterm(), queryCommandState(), queryCommandSupported(), and
queryCommandValue() methods, text selections, and the delete the selection
algorithm are defined in the HTML Editing APIs specification. The
interaction of editing and the undo/redo features in user agents is
defined by the UndoManager and DOM Transaction specification. [EDITING]
[UNDO]
5.6.5. Spelling and grammar checking
User agents can support the checking of spelling and grammar of editable
text, either in form controls (such as the value of textarea elements), or
in elements in an editing host (e.g., using contenteditable).
For each element, user agents must establish a default behavior, either
through defaults or through preferences expressed by the user. There are
three possible default behaviors for each element:
true-by-default
The element will be checked for spelling and grammar if its
contents are editable and spellchecking is not explicitly disabled
through the spellcheck attribute.
false-by-default
The element will never be checked for spelling and grammar unless
spellchecking is explicitly enabled through the spellcheck
attribute.
inherit-by-default
The element’s default behavior is the same as its parent
element’s. Elements that have no parent element cannot have this
as their default behavior.
----------------------------------------------------------------------
The spellcheck attribute is an enumerated attribute whose keywords are the
empty string, true and false. The empty string and the true keyword map to
the true state. The false keyword maps to the false state. In addition,
there is a third state, the default state, which is the missing value
default (and the invalid value default).
The true state indicates that the element is to have its spelling and
grammar checked. The default state indicates that the element is to act
according to a default behavior, possibly based on the parent element’s
own spellcheck state, as defined below. The false state indicates that the
element is not to be checked.
----------------------------------------------------------------------
element . spellcheck [ = value ]
Returns true if the element is to have its spelling and grammar
checked; otherwise, returns false.
Can be set, to override the default and set the spellcheck content
attribute.
element . forceSpellCheck()
Forces the user agent to report spelling and grammar errors on the
element (if checking is enabled), even if the user has never
focused the element. (If the method is not invoked, user agents
can hide errors in text that wasn’t just entered by the user.)
The spellcheck IDL attribute, on getting, must return true if the
element’s spellcheck content attribute is in the true state, or if the
element’s spellcheck content attribute is in the default state and the
element’s default behavior is true-by-default, or if the element’s
spellcheck content attribute is in the default state and the element’s
default behavior is inherit-by-default and the element’s parent element’s
spellcheck IDL attribute would return true; otherwise, if none of those
conditions applies, then the attribute must instead return false.
The spellcheck IDL attribute is not affected by user preferences that
override the spellcheck content attribute, and therefore might not reflect
the actual spellchecking state.
On setting, if the new value is true, then the element’s spellcheck
content attribute must be set to the literal string "true", otherwise it
must be set to the literal string "false".
----------------------------------------------------------------------
User agents must only consider the following pieces of text as checkable
for the purposes of this feature:
* The value of input elements whose type attributes are in the Text,
Search, URL, or E-mail states and that are mutable (i.e., that do not
have the readonly attribute specified and that are not disabled).
* The value of textarea elements that do not have a readonly attribute
and that are not disabled.
* Text in Text nodes that are children of editing hosts or editable
elements.
* Text in attributes of editable elements.
For text that is part of a Text node, the element with which the text is
associated is the element that is the immediate parent of the first
character of the word, sentence, or other piece of text. For text in
attributes, it is the attribute’s element. For the values of input and
textarea elements, it is the element itself.
To determine if a word, sentence, or other piece of text in an applicable
element (as defined above) is to have spelling- and grammar-checking
enabled, the user agent must use the following algorithm:
1. If the user has disabled the checking for this text, then the checking
is disabled.
2. Otherwise, if the user has forced the checking for this text to always
be enabled, then the checking is enabled.
3. Otherwise, if the element with which the text is associated has a
spellcheck content attribute, then: if that attribute is in the true
state, then checking is enabled; otherwise, if that attribute is in
the false state, then checking is disabled.
4. Otherwise, if there is an ancestor element with a spellcheck content
attribute that is not in the default state, then: if the nearest such
ancestor’s spellcheck content attribute is in the true state, then
checking is enabled; otherwise, checking is disabled.
5. Otherwise, if the element’s default behavior is true-by-default, then
checking is enabled.
6. Otherwise, if the element’s default behavior is false-by-default, then
checking is disabled.
7. Otherwise, if the element’s parent element has its checking enabled,
then checking is enabled.
8. Otherwise, checking is disabled.
If the checking is enabled for a word/sentence/text, the user agent should
indicate spelling and grammar errors in that text. User agents should take
into account the other semantics given in the document when suggesting
spelling and grammar corrections. User agents may use the language of the
element to determine what spelling and grammar rules to use, or may use
the user’s preferred language settings. user agents should use input
element attributes such as pattern to ensure that the resulting value is
valid, where possible.
If checking is disabled, the user agent should not indicate spelling or
grammar errors for that text.
Even when checking is enabled, user agents may opt to not report spelling
or grammar errors in text that the user agent deems the user has no
interest in having checked (e.g., text that was already present when the
page was loaded, or that the user did not type, or text in controls that
the user has not focused, or in parts of e-mail addresses that the user
agent is not confident were misspelt). The forceSpellCheck() method, when
invoked on an element, must override this behavior, forcing the user agent
to consider all spelling and grammar errors in text in that element for
which checking is enabled to be of interest to the user.
The element with ID "a" in the following example would be the one used to
determine if the word "Hello" is checked for spelling errors. In this
example, it would not be.
Hell o!
The element with ID "b" in the following example would have checking
enabled (the leading space character in the attribute’s value on the input
element causes the attribute to be ignored, so the ancestor’s value is
used instead, regardless of the default).
Name:
This specification does not define the user interface for spelling and
grammar checkers. A user agent could offer on-demand checking, could
perform continuous checking while the checking is enabled, or could use
other interfaces.
5.7. Drag and drop
This section defines an event-based drag-and-drop mechanism.
This specification does not define exactly what a drag-and-drop operation
actually is.
On a visual medium with a pointing device, a drag operation could be the
default action of a mousedown event that is followed by a series of
mousemove events, and the drop could be triggered by the mouse being
released.
When using an input modality other than a pointing device, users would
probably have to explicitly indicate their intention to perform a
drag-and-drop operation, stating what they wish to drag and where they
wish to drop it, respectively.
However it is implemented, drag-and-drop operations must have a starting
point (e.g., where the mouse was clicked, or the start of the selection or
element that was selected for the drag), may have any number of
intermediate steps (elements that the mouse moves over during a drag, or
elements that the user picks as possible drop points as he cycles through
possibilities), and must either have an end point (the element above which
the mouse button was released, or the element that was finally selected),
or be canceled. The end point must be the last element selected as a
possible drop point before the drop occurs (so if the operation is not
canceled, there must be at least one element in the middle step).
5.7.1. Introduction
This section is non-normative.
To make an element draggable is simple: give the element a draggable
attribute, and set an event listener for dragstart that stores the data
being dragged.
The event handler typically needs to check that it’s not a text selection
that is being dragged, and then needs to store data into the DataTransfer
object and set the allowed effects (copy, move, link, or some
combination).
For example:
What fruits do you like?
Apples
Oranges
Pears
----------------------------------------------------------------------
To accept a drop, the drop target has to listen to the drop event.
A drop target can handle the dragenter event (to report whether or not the
drop target is to accept the drop) and the dragover event (to specify what
feedback is to be shown to the user).
The drop event allows the actual drop to be performed. This event needs to
be canceled, so that the dropEffect attribute’s value can be used by the
source (otherwise it’s reset).
For example:
Drop your favorite fruits below:
----------------------------------------------------------------------
To remove the original element (the one that was dragged) from the
display, the dragend event can be used.
For our example here, that means updating the original markup to handle
that event:
What fruits do you like?
5.7.2. The drag data store
The data that underlies a drag-and-drop operation, known as the drag data
store, consists of the following information:
* A drag data store item list, which is a list of items representing the
dragged data, each consisting of the following information:
The drag data item kind
The kind of data:
Plain Unicode string
Text.
File
Binary data with a file name.
The drag data item type string
A Unicode string giving the type or format of the data,
generally given by a MIME type. Some values that are not
MIME types are special-cased for legacy reasons. The API
does not enforce the use of MIME types; other values can
be used as well. In all cases, however, the values are
all converted to ASCII lowercase by the API.
There is a limit of one Plain Unicode string item per
item type string.
The actual data
A Unicode or binary string, in some cases with a file
name (itself a Unicode string), as per the drag data item
kind.
The drag data store item list is ordered in the order that the items
were added to the list; most recently added last.
* The following information, used to generate the UI feedback during the
drag:
* User-agent-defined default feedback information, known as the
drag data store default feedback.
* Optionally, a bitmap image and the coordinate of a point within
that image, known as the drag data store bitmap and drag data
store hot spot coordinate.
* A drag data store mode, which is one of the following:
Read/write mode
For the dragstart event. New data can be added to the
drag data store.
Read-only mode
For the drop event. The list of items representing
dragged data can be read, including the data. No new data
can be added.
Protected mode
For all other events. The formats and kinds in the drag
data store list of items representing dragged data can be
enumerated, but the data itself is unavailable and no new
data can be added.
* A drag data store allowed effects state, which is a string.
When a drag data store is created, it must be initialized such that its
drag data store item list is empty, it has no drag data store default
feedback, it has no drag data store bitmap and drag data store hot spot
coordinate, its drag data store mode is protected mode, and its drag data
store allowed effects state is the string "uninitialized".
5.7.3. The DataTransfer interface
DataTransfer objects are used to expose the drag data store that underlies
a drag-and-drop operation.
interface DataTransfer {
attribute DOMString dropEffect;
attribute DOMString effectAllowed;
[SameObject] readonly attribute DataTransferItemList items;
void setDragImage(Element image, long x, long y);
/* old interface */
[SameObject] readonly attribute DOMString[] types;
DOMString getData(DOMString format);
void setData(DOMString format, DOMString data);
void clearData(optional DOMString format);
[SameObject] readonly attribute FileList files;
};
dataTransfer . dropEffect [ = value ]
Returns the kind of operation that is currently selected. If the
kind of operation isn’t one of those that is allowed by the
effectAllowed attribute, then the operation will fail.
Can be set, to change the selected operation.
The possible values are "none", "copy", "link", and "move".
dataTransfer . effectAllowed [ = value ]
Returns the kinds of operations that are to be allowed.
Can be set (during the dragstart event), to change the allowed
operations.
The possible values are "none", "copy", "copyLink", "copyMove",
"link", "linkMove", "move", "all", and "uninitialized",
dataTransfer . items
Returns a DataTransferItemList object, with the drag data.
dataTransfer . setDragImage(element, x, y)
Uses the given element to update the drag feedback, replacing any
previously specified feedback.
dataTransfer . types
Returns an array listing the formats that were set in the
dragstart event. In addition, if any files are being dragged, then
one of the types will be the string "Files".
data = dataTransfer . getData(format)
Returns the specified data. If there is no such data, returns the
empty string.
dataTransfer . setData(format, data)
Adds the specified data.
dataTransfer . clearData( [ format ] )
Removes the data of the specified formats. Removes all data if the
argument is omitted.
dataTransfer . files
Returns a FileList of the files being dragged, if any.
DataTransfer objects are used during the drag-and-drop events, and are
only valid while those events are being fired.
A DataTransfer object is associated with a drag data store while it is
valid.
The dropEffect attribute controls the drag-and-drop feedback that the user
is given during a drag-and-drop operation. When the DataTransfer object is
created, the dropEffect attribute is set to a string value. On getting, it
must return its current value. On setting, if the new value is one of
"none", "copy", "link", or "move", then the attribute’s current value must
be set to the new value. Other values must be ignored.
The effectAllowed attribute is used in the drag-and-drop processing model
to initialize the dropEffect attribute during the dragenter and dragover
events. When the DataTransfer object is created, the effectAllowed
attribute is set to a string value. On getting, it must return its current
value. On setting, if drag data store’s mode is the read/write mode and
the new value is one of "none", "copy", "copyLink", "copyMove", "link",
"linkMove", "move", "all", or "uninitialized", then the attribute’s
current value must be set to the new value. Otherwise it must be left
unchanged.
The items attribute must return a DataTransferItemList object associated
with the DataTransfer object.
The setDragImage(element, x, y) method must run the following steps:
1. If the DataTransfer object is no longer associated with a drag data
store, abort these steps. Nothing happens.
2. If the drag data store’s mode is not the read/write mode, abort these
steps. Nothing happens.
3. If the element argument is an img element, then set the drag data
store bitmap to the element’s image (at its intrinsic size);
otherwise, set the drag data store bitmap to an image generated from
the given element (the exact mechanism for doing so is not currently
specified).
4. Set the drag data store hot spot coordinate to the given x, y
coordinate.
The types attribute must return a live read only array giving the strings
that the following steps would produce.
1. Start with an empty list L.
2. If the DataTransfer object is no longer associated with a drag data
store, the array is empty. Abort these steps; return the empty list L.
3. For each item in the drag data store item list whose kind is Plain
Unicode string, add an entry to the list L consisting of the item’s
type string.
4. If there are any items in the drag data store item list whose kind is
File, then add an entry to the list L consisting of the string
"Files". (This value can be distinguished from the other values
because it is not lowercase.)
5. The strings produced by these steps are those in the list L.
The getData(format) method must run the following steps:
1. If the DataTransfer object is no longer associated with a drag data
store, return the empty string and abort these steps.
2. If the drag data store’s mode is the protected mode, return the empty
string and abort these steps.
3. Let format be the first argument, in ASCII lowercase.
4. Let convert-to-URL be false.
5. If format equals "text", change it to "text/plain".
6. If format equals "url", change it to "text/uri-list" and set
convert-to-URL to true.
7. If there is no item in the drag data store item list whose kind is
Plain Unicode string and whose type string is equal to format, return
the empty string and abort these steps.
8. Let result be the data of the item in the drag data store item list
whose kind is Plain Unicode string and whose type string is equal to
format.
9. If convert-to-URL is true, then parse result as appropriate for
text/uri-list data, and then set result to the first URL from the
list, if any, or the empty string otherwise. [RFC2483]
10. Return result.
The setData(format, data) method must run the following steps:
1. If the DataTransfer object is no longer associated with a drag data
store, abort these steps. Nothing happens.
2. If the drag data store’s mode is not the read/write mode, abort these
steps. Nothing happens.
3. Let format be the first argument, in ASCII lowercase.
4. If format equals "text", change it to "text/plain".
If format equals "url", change it to "text/uri-list".
5. Remove the item in the drag data store item list whose kind is Plain
Unicode string and whose type string is equal to format, if there is
one.
6. Add an item to the drag data store item list whose kind is Plain
Unicode string, whose type string is equal to format, and whose data
is the string given by the method’s second argument.
The clearData() method must run the following steps:
1. If the DataTransfer object is no longer associated with a drag data
store, abort these steps. Nothing happens.
2. If the drag data store’s mode is not the read/write mode, abort these
steps. Nothing happens.
3. If the method was called with no arguments, remove each item in the
drag data store item list whose kind is Plain Unicode string, and
abort these steps.
4. Let format be the first argument, in ASCII lowercase.
5. If format equals "text", change it to "text/plain".
If format equals "url", change it to "text/uri-list".
6. Remove the item in the drag data store item list whose kind is Plain
Unicode string and whose type string is equal to format, if there is
one.
The clearData() method does not affect whether any files were included in
the drag, so the types attribute’s list might still not be empty after
calling clearData() (it would still contain the "Files" string if any
files were included in the drag).
The files attribute must return a live FileList sequence consisting of
File objects representing the files found by the following steps.
Furthermore, for a given FileList object and a given underlying file, the
same File object must be used each time.
1. Start with an empty list L.
2. If the DataTransfer object is no longer associated with a drag data
store, the FileList is empty. Abort these steps; return the empty list
L.
3. If the drag data store’s mode is the protected mode, abort these
steps; return the empty list L.
4. For each item in the drag data store item list whose kind is File ,
add the item’s data (the file, in particular its name and contents, as
well as its type) to the list L.
5. The files found by these steps are those in the list L.
This version of the API does not expose the types of the files during the
drag.
5.7.3.1. The DataTransferItemList interface
Each DataTransfer object is associated with a DataTransferItemList object.
interface DataTransferItemList {
readonly attribute unsigned long length;
getter DataTransferItem (unsigned long index);
DataTransferItem? add(DOMString data, DOMString type);
DataTransferItem? add(File data);
void remove(unsigned long index);
void clear();
};
items . length
Returns the number of items in the drag data store.
items[index]
Returns the DataTransferItem object representing the indexth entry
in the drag data store.
items . remove(index)
Removes the indexth entry in the drag data store.
items . clear()
Removes all the entries in the drag data store.
items . add(data)
items . add(data, type)
Adds a new entry for the given data to the drag data store. If the
data is plain text then a type string has to be provided also.
While the DataTransferItemList object’s DataTransfer object is associated
with a drag data store, the DataTransferItemList object’s mode is the same
as the drag data store mode. When the DataTransferItemList object’s
DataTransfer object is not associated with a drag data store, the
DataTransferItemList object’s mode is the disabled mode. The drag data
store referenced in this section (which is used only when the
DataTransferItemList object is not in the disabled mode) is the drag data
store with which the DataTransferItemList object’s DataTransfer object is
associated.
The length attribute must return zero if the object is in the disabled
mode; otherwise it must return the number of items in the drag data store
item list.
When a DataTransferItemList object is not in the disabled mode, its
supported property indices are the numbers in the range 0 .. n-1, where n
is the number of items in the drag data store item list.
To determine the value of an indexed property i of a DataTransferItemList
object, the user agent must return a DataTransferItem object representing
the ith item in the drag data store. The same object must be returned each
time a particular item is obtained from this DataTransferItemList object.
The DataTransferItem object must be associated with the same DataTransfer
object as the DataTransferItemList object when it is first created.
The add() method must run the following steps:
1. If the DataTransferItemList object is not in the read/write mode,
return null and abort these steps.
2. Jump to the appropriate set of steps from the following list:
If the first argument to the method is a string
If there is already an item in the drag data store item
list whose kind is Plain Unicode string and whose type
string is equal to the value of the method’s second
argument, in ASCII lowercase, then throw a
NotSupportedError exception and abort these steps.
Otherwise, add an item to the drag data store item list
whose kind is Plain Unicode string, whose type string is
equal to the value of the method’s second argument, in
ASCII lowercase, and whose data is the string given by
the method’s first argument.
If the first argument to the method is a File
Add an item to the drag data store item list whose kind
is File, whose type string is the type of the File, in
ASCII lowercase, and whose data is the same as the File’s
data.
3. Determine the value of the indexed property corresponding to the newly
added item, and return that value (a newly created DataTransferItem
object).
The remove() method, when invoked with the argument i, must run these
steps:
1. If the DataTransferItemList object is not in the read/write mode,
throw an InvalidStateError exception and abort these steps.
2. Remove the ith item from the drag data store.
The clear() method, if the DataTransferItemList object is in the
read/write mode, must remove all the items from the drag data store.
Otherwise, it must do nothing.
5.7.3.2. The DataTransferItem interface
Each DataTransferItem object is associated with a DataTransfer object.
interface DataTransferItem {
readonly attribute DOMString kind;
readonly attribute DOMString type;
void getAsString(FunctionStringCallback? _callback);
File? getAsFile();
};
callback FunctionStringCallback = void (DOMString data);
item . kind
Returns the drag data item kind, one of: "string", "file".
item . type
Returns the drag data item type string.
item . getAsString(callback)
Invokes the callback with the string data as the argument, if the
drag data item kind is Plain Unicode string.
file = item . getAsFile()
Returns a File object, if the drag data item kind is File.
While the DataTransferItem object’s DataTransfer object is associated with
a drag data store and that drag data store’s drag data store item list
still contains the item that the DataTransferItem object represents, the
DataTransferItem object’s mode is the same as the drag data store mode.
When the DataTransferItem object’s DataTransfer object is not associated
with a drag data store, or if the item that the DataTransferItem object
represents has been removed from the relevant drag data store item list,
the DataTransferItem object’s mode is the disabled mode. The drag data
store referenced in this section (which is used only when the
DataTransferItem object is not in the disabled mode) is the drag data
store with which the DataTransferItem object’s DataTransfer object is
associated.
The kind attribute must return the empty string if the DataTransferItem
object is in the disabled mode; otherwise it must return the string given
in the cell from the second column of the following table from the row
whose cell in the first column contains the drag data item kind of the
item represented by the DataTransferItem object:
Kind String
Plain Unicode string "string"
File "file"
The type attribute must return the empty string if the DataTransferItem
object is in the disabled mode; otherwise it must return the drag data
item type string of the item represented by the DataTransferItem object.
The getAsString(callback) method must run the following steps:
1. If the callback is null, abort these steps.
2. If the DataTransferItem object is not in the read/write mode or the
read-only mode, abort these steps. The callback is never invoked.
3. If the drag data item kind is not Plain Unicode string, abort these
steps. The callback is never invoked.
4. Otherwise, queue a task to invoke callback, passing the actual data of
the item represented by the DataTransferItem object as the argument.
The getAsFile() method must run the following steps:
1. If the DataTransferItem object is not in the read/write mode or the
read-only mode, return null and abort these steps.
2. If the drag data item kind is not File, then return null and abort
these steps.
3. Return a new File object representing the actual data of the item
represented by the DataTransferItem object.
5.7.4. The DragEvent interface
The drag-and-drop processing model involves several events. They all use
the DragEvent interface.
[Constructor(DOMString type, optional DragEventInit eventInitDict)]
interface DragEvent : MouseEvent {
readonly attribute DataTransfer? dataTransfer;
};
dictionary DragEventInit : MouseEventInit {
DataTransfer? dataTransfer = null;
};
event . dataTransfer
Returns the DataTransfer object for the event.
Although, for consistency with other event interfaces, the DragEvent
interface has a constructor, it is not particularly useful. In particular,
there’s no way to create a useful DataTransfer object from script, as
DataTransfer objects have a processing and security model that is
coordinated by the browser during drag-and-drops.
The dataTransfer attribute of the DragEvent interface must return the
value it was initialized to. It represents the context information for the
event.
When a user agent is required to fire a DND event named e at an element,
using a particular drag data store, and optionally with a specific related
target, the user agent must run the following steps:
1. Let dataDragStoreWasChanged be false.
2. If no specific related target was provided, set related target to
null.
3. Let window be the Window object of the Document object of the
specified target element.
4. If e is dragstart, then set the data store mode to the read/write mode
and set dataDragStoreWasChanged to true.
If e is drop, set the drag data store mode to the read-only mode.
5. Let dataTransfer be a newly created DataTransfer object associated
with the given drag data store.
6. Set the effectAllowed attribute to the drag data store’s drag data
store allowed effects state.
7. Set the dropEffect attribute to "none" if e is dragstart, drag,
dragexit, or dragleave; to the value corresponding to the current drag
operation if e is drop or dragend; and to a value based on the
effectAllowed attribute’s value and the drag-and-drop source, as given
by the following table, otherwise (i.e., if e is dragenter or
dragover):
effectAllowed dropEffect
"none" "none"
"copy" "copy"
"copyLink" "copy", or, if appropriate,
"link"
"copyMove" "copy", or, if appropriate,
"move"
"all" "copy", or, if appropriate,
either "link" or "move"
"link" "link"
"linkMove" "link", or, if appropriate,
"move"
"move" "move"
"uninitialized" when what is being dragged "move", or, if appropriate,
is a selection from a text field either "copy" or "link"
"uninitialized" when what is being dragged "copy", or, if appropriate,
is a selection either "link" or "move"
"uninitialized" when what is being dragged "link", or, if appropriate,
is an a element with an href attribute either "copy" or "move"
Any other case "copy", or, if appropriate,
either "link" or "move"
Where the table above provides possibly appropriate alternatives, user
agents may instead use the listed alternative values if platform
conventions dictate that the user has requested those alternate
effects.
For example, Windows platform conventions are such that dragging while
holding the "alt" key indicates a preference for linking the data,
rather than moving or copying it. Therefore, on a Windows system, if
"link" is an option according to the table above while the "alt" key
is depressed, the user agent could select that instead of "copy" or
"move".
8. Create a trusted DragEvent object and initialize it to have the given
name e, to bubble, to be cancelable unless e is dragexit, dragleave,
or dragend, and to have the view attribute initialized to window, the
detail attribute initialized to zero, the mouse and key attributes
initialized according to the state of the input devices as they would
be for user interaction events, the relatedTarget attribute
initialized to related target, and the dataTransfer attribute
initialized to dataTransfer, the DataTransfer object created above.
If there is no relevant pointing device, the object must have its
screenX, screenY, clientX, clientY, and button attributes set to 0.
9. Dispatch the newly created DragEvent object at the specified target
element.
10. Set the drag data store allowed effects state to the current value of
dataTransfer’s effectAllowed attribute. (It can only have changed
value if e is dragstart.)
11. If dataDragStoreWasChanged is true, then set the drag data store mode
back to the protected mode.
12. Break the association between dataTransfer and the drag data store.
5.7.5. Drag-and-drop processing model
When the user attempts to begin a drag operation, the user agent must run
the following steps. User agents must act as if these steps were run even
if the drag actually started in another document or application and the
user agent was not aware that the drag was occurring until it intersected
with a document under the user agent’s purview.
1. Determine what is being dragged, as follows:
If the drag operation was invoked on a selection, then it is the
selection that is being dragged.
Otherwise, if the drag operation was invoked on a Document, it is the
first element, going up the ancestor chain, starting at the node that
the user tried to drag, that has the IDL attribute draggable set to
true. If there is no such element, then nothing is being dragged;
abort these steps, the drag-and-drop operation is never started.
Otherwise, the drag operation was invoked outside the user agent’s
purview. What is being dragged is defined by the document or
application where the drag was started.
img elements and a elements with an href attribute have their
draggable attribute set to true by default.
2. Create a drag data store. All the DND events fired subsequently by the
steps in this section must use this drag data store.
3. Establish which DOM node is the source node, as follows:
If it is a selection that is being dragged, then the source node is
the Text node that the user started the drag on (typically the Text
node that the user originally clicked). If the user did not specify a
particular node, for example if the user just told the user agent to
begin a drag of "the selection", then the source node is the first
Text node containing a part of the selection.
Otherwise, if it is an element that is being dragged, then the source
node is the element that is being dragged.
Otherwise, the source node is part of another document or application.
When this specification requires that an event be dispatched at the
source node in this case, the user agent must instead follow the
platform-specific conventions relevant to that situation.
Multiple events are fired on the source node during the course of the
drag-and-drop operation.
4. Determine the list of dragged nodes, as follows:
If it is a selection that is being dragged, then the list of dragged
nodes contains, in tree order, every node that is partially or
completely included in the selection (including all their ancestors).
Otherwise, the list of dragged nodes contains only the source node, if
any.
5. If it is a selection that is being dragged, then add an item to the
drag data store item list, with its properties set as follows:
The drag data item type string
"text/plain"
The drag data item kind
Plain Unicode string
The actual data
The text of the selection
Otherwise, if any files are being dragged, then add one item per file
to the drag data store item list, with their properties set as
follows:
The drag data item type string
The MIME type of the file, if known, or
"application/octet-stream" otherwise.
The drag data item kind
File
The actual data
The file’s contents and name.
Dragging files can currently only happen from outside a browsing
context, for example from a file system manager application.
If the drag initiated outside of the application, the user agent must
add items to the drag data store item list as appropriate for the data
being dragged, honoring platform conventions where appropriate;
however, if the platform conventions do not use MIME types to label
dragged data, the user agent must make a best-effort attempt to map
the types to MIME types, and, in any case, all the drag data item type
strings must be in ASCII lowercase.
User agents may also add one or more items representing the selection
or dragged element(s) in other forms, e.g., as HTML.
6. If the list of dragged nodes is not empty, then extract the microdata
from those nodes into a JSON form, and add one item to the drag data
store item list, with its properties set as follows:
The drag data item type string
application/microdata+json
The drag data item kind
Plain Unicode string
The actual data
The resulting JSON string.
7. Run the following substeps:
1. Let urls be an empty list of absolute URLs.
2. For each node in the list of dragged nodes:
If the node is an a element with an href attribute
Add to urls the result of parsing the element’s href
content attribute relative to the element’s node
document
If the node is an img element with a src attribute
Add to urls the result of parsing the element’s src
content attribute relative to the element’s node
document
3. If urls is still empty, abort these substeps.
4. Let url string be the result of concatenating the strings in
urls, in the order they were added, separated by a U+000D
CARRIAGE RETURN U+000A LINE FEED character pair (CRLF).
5. Add one item to the drag data store item list, with its
properties set as follows:
The drag data item type string
text/uri-list
The drag data item kind
Plain Unicode string
The actual data
url string
8. Update the drag data store default feedback as appropriate for the
user agent (if the user is dragging the selection, then the selection
would likely be the basis for this feedback; if the user is dragging
an element, then that element’s rendering would be used; if the drag
began outside the user agent, then the platform conventions for
determining the drag feedback should be used).
9. Fire a DND event named dragstart at the source node.
If the event is canceled, then the drag-and-drop operation should not
occur; abort these steps.
Since events with no event listeners registered are, almost by
definition, never canceled, drag-and-drop is always available to the
user if the author does not specifically prevent it.
10. Initiate the drag-and-drop operation in a manner consistent with
platform conventions, and as described below.
The drag-and-drop feedback must be generated from the first of the
following sources that is available:
1. The drag data store bitmap, if any. In this case, the drag data
store hot spot coordinate should be used as hints for where to
put the cursor relative to the resulting image. The values are
expressed as distances in CSS pixels from the left side and from
the top side of the image respectively. [CSS-2015]
2. The drag data store default feedback.
From the moment that the user agent is to initiate the drag-and-drop
operation, until the end of the drag-and-drop operation, device input
events (e.g., mouse and keyboard events) must be suppressed.
During the drag operation, the element directly indicated by the user as
the drop target is called the immediate user selection. (Only elements can
be selected by the user; other nodes must not be made available as drop
targets.) However, the immediate user selection is not necessarily the
current target element, which is the element currently selected for the
drop part of the drag-and-drop operation.
The immediate user selection changes as the user selects different
elements (either by pointing at them with a pointing device, or by
selecting them in some other way). The current target element changes when
the immediate user selection changes, based on the results of event
listeners in the document, as described below.
Both the current target element and the immediate user selection can be
null, which means no target element is selected. They can also both be
elements in other (DOM-based) documents, or other (non-Web) programs
altogether. (For example, a user could drag text to a word-processor.) The
current target element is initially null.
In addition, there is also a current drag operation, which can take on the
values "none", "copy", "link", and "move". Initially, it has the value
"none". It is updated by the user agent as described in the steps below.
User agents must, as soon as the drag operation is initiated and every
350ms (±200ms) thereafter for as long as the drag operation is ongoing,
queue a task to perform the following steps in sequence:
1. If the user agent is still performing the previous iteration of the
sequence (if any) when the next iteration becomes due, abort these
steps for this iteration (effectively "skipping missed frames" of the
drag-and-drop operation).
2. Fire a DND event named drag at the source node. If this event is
canceled, the user agent must set the current drag operation to "none"
(no drag operation).
3. If the drag event was not canceled and the user has not ended the
drag-and-drop operation, check the state of the drag-and-drop
operation, as follows:
1. If the user is indicating a different immediate user selection
than during the last iteration (or if this is the first
iteration), and if this immediate user selection is not the same
as the current target element, then fire a DND event named
dragexit at the current target element, and then update the
current target element as follows:
If the new immediate user selection is null
Set the current target element to null also.
If the new immediate user selection is in a non-DOM document
or application
Set the current target element to the immediate user
selection.
Otherwise
Fire a DND event named dragenter at the immediate
user selection.
If the event is canceled, then set the current
target element to the immediate user selection.
Otherwise, run the appropriate step from the
following list:
If the immediate user selection is a text field
(e.g., textarea, or an input element whose type
attribute is in the Text state) or an editing
host or editable element, and the drag data
store item list has an item with the drag data
item type string "text/plain" and the drag data
item kind Plain Unicode string
Set the current target element to the
immediate user selection anyway.
If the immediate user selection is the body
element
Leave the current target element
unchanged.
Otherwise
Fire a DND event named dragenter at the
body element, if there is one, or at
the Document object, if not. Then, set
the current target element to the body
element, regardless of whether that
event was canceled or not.
2. If the previous step caused the current target element to change,
and if the previous target element was not null or a part of a
non-DOM document, then fire a DND event named dragleave at the
previous target element, with the new current target element as
the specific related target.
3. If the current target element is a DOM element, then fire a DND
event named dragover at this current target element.
If the dragover event is not canceled, run the appropriate step
from the following list:
If the current target element is a text field (e.g.,
textarea, or an input element whose type attribute is in the
Text state) or an editing host or editable element, and the
drag data store item list has an item with the drag data
item type string "text/plain" and the drag data item kind
Plain Unicode string
Set the current drag operation to either "copy" or
"move", as appropriate given the platform
conventions.
Otherwise
Reset the current drag operation to "none".
Otherwise (if the dragover event is canceled), set the current
drag operation based on the values of the effectAllowed and
dropEffect attributes of the DragEvent object’s dataTransfer
object as they stood after the event dispatch finished, as per
the following table:
effectAllowed dropEffect Drag operation
"uninitialized", "copy", "copyLink", "copy" "copy"
"copyMove", or "all"
"uninitialized", "link", "copyLink", "link" "link"
"linkMove", or "all"
"uninitialized", "move", "copyMove", "move" "move"
"linkMove", or "all"
Any other case "none"
4. Otherwise, if the current target element is not a DOM element,
use platform-specific mechanisms to determine what drag operation
is being performed (none, copy, link, or move), and set the
current drag operation accordingly.
5. Update the drag feedback (e.g., the mouse cursor) to match the
current drag operation, as follows:
Drag operation Feedback
"copy" Data will be copied if dropped here.
"link" Data will be linked if dropped here.
"move" Data will be moved if dropped here.
"none" No operation allowed, dropping here will cancel
the drag-and-drop operation.
4. Otherwise, if the user ended the drag-and-drop operation (e.g., by
releasing the mouse button in a mouse-driven drag-and-drop interface),
or if the drag event was canceled, then this will be the last
iteration. Run the following steps, then stop the drag-and-drop
operation:
1. If the current drag operation is "none" (no drag operation), or,
if the user ended the drag-and-drop operation by canceling it
(e.g., by hitting the Escape key), or if the current target
element is null, then the drag operation failed. Run these
substeps:
1. Let dropped be false.
2. If the current target element is a DOM element, fire a DND
event named dragleave at it; otherwise, if it is not null,
use platform-specific conventions for drag cancelation.
3. Set the current drag operation to "none".
Otherwise, the drag operation might be a success; run these
substeps:
1. Let dropped be true.
2. If the current target element is a DOM element, fire a DND
event named drop at it; otherwise, use platform-specific
conventions for indicating a drop.
3. If the event is canceled, set the current drag operation to
the value of the dropEffect attribute of the DragEvent
object’s dataTransfer object as it stood after the event
dispatch finished.
Otherwise, the event is not canceled; perform the event’s
default action, which depends on the exact target as
follows:
If the current target element is a text field (e.g.,
textarea, or an input element whose type attribute is
in the Text state) or an editing host or editable
element, and the drag data store item list has an item
with the drag data item type string "text/plain" and
the drag data item kind Plain Unicode string
Insert the actual data of the first item in the
drag data store item list to have a drag data
item type string of "text/plain" and a drag
data item kind that is Plain Unicode string
into the text field or editing host or editable
element in a manner consistent with
platform-specific conventions (e.g., inserting
it at the current mouse cursor position, or
inserting it at the end of the field).
Otherwise
Reset the current drag operation to "none".
2. Fire a DND event named dragend at the source node.
3. Run the appropriate steps from the following list as the default
action of the dragend event:
If dropped is true, the current target element is a text
field (see below), the current drag operation is "move", and
the source of the drag-and-drop operation is a selection in
the DOM that is entirely contained within an editing host
Delete the selection.
If dropped is true, the current target element is a text
field (see below), the current drag operation is "move", and
the source of the drag-and-drop operation is a selection in
a text field
The user agent should delete the dragged selection
from the relevant text field.
If dropped is false or if the current drag operation is
"none"
The drag was canceled. If the platform conventions
dictate that this be represented to the user (e.g.,
by animating the dragged selection going back to the
source of the drag-and-drop operation), then do so.
Otherwise
The event has no default action.
For the purposes of this step, a text field is a textarea element
or an input element whose type attribute is in one of the Text,
Search, Telephone, URL, E-mail, Password, or Number states.
User agents are encouraged to consider how to react to drags near the edge
of scrollable regions. For example, if a user drags a link to the bottom
of the viewport on a long page, it might make sense to scroll the page so
that the user can drop the link lower on the page.
This model is independent of which Document object the nodes involved are
from; the events are fired as described above and the rest of the
processing model runs as described above, irrespective of how many
documents are involved in the operation.
5.7.6. Events summary
This section is non-normative.
The following events are involved in the drag-and-drop model.
Event Name Target Cancelable? Drag data dropEffect Default Action
store mode
Source Read/write Initiate the
dragstart node ✓ Cancelable mode "none" drag-and-drop
operation
Source Protected Continue the
drag node ✓ Cancelable mode "none" drag-and-drop
operation
Immediate Reject
user Based on immediate user
dragenter selection ✓ Cancelable Protected effectAllowed selection as
or the mode value potential
body target element
element
Previous Protected
dragexit target — mode "none" None
element
Previous Protected
dragleave target — mode "none" None
element
Current Based on Reset the
dragover target ✓ Cancelable Protected effectAllowed current drag
element mode value operation to
"none"
Current Read-only Current drag
drop target ✓ Cancelable mode operation Varies
element
dragend Source — Protected Current drag Varies
node mode operation
Not shown in the above table: all these events bubble, and the
effectAllowed attribute always has the value it had after the dragstart
event, defaulting to "uninitialized" in the dragstart event.
5.7.7. The draggable attribute
All HTML elements may have the draggable content attribute set. The
draggable attribute is an enumerated attribute. It has three states. The
first state is true and it has the keyword true. The second state is false
and it has the keyword false. The third state is auto; it has no keywords
but it is the missing value default.
The true state means the element is draggable; the false state means that
it is not. The auto state uses the default behavior of the user agent.
An element with a draggable attribute should also have a title attribute
that names the element for the purpose of non-visual interactions.
element . draggable [ = value ]
Returns true if the element is draggable; otherwise, returns
false.
Can be set, to override the default and set the draggable content
attribute.
The draggable IDL attribute, whose value depends on the content
attribute’s in the way described below, controls whether or not the
element is draggable. Generally, only text selections are draggable, but
elements whose draggable IDL attribute is true become draggable as well.
If an element’s draggable content attribute has the state true, the
draggable IDL attribute must return true.
Otherwise, if the element’s draggable content attribute has the state
false, the draggable IDL attribute must return false.
Otherwise, the element’s draggable content attribute has the state auto.
If the element is an img element, an object element that represents an
image, or an a element with an href content attribute, the draggable IDL
attribute must return true; otherwise, the draggable IDL attribute must
return false.
If the draggable IDL attribute is set to the value false, the draggable
content attribute must be set to the literal value "false". If the
draggable IDL attribute is set to the value true, the draggable content
attribute must be set to the literal value "true".
5.7.8. Security risks in the drag-and-drop model
User agents must not make the data added to the DataTransfer object during
the dragstart event available to scripts until the drop event, because
otherwise, if a user were to drag sensitive information from one document
to a second document, crossing a hostile third document in the process,
the hostile document could intercept the data.
For the same reason, user agents must consider a drop to be successful
only if the user specifically ended the drag operation — if any scripts
end the drag operation, it must be considered unsuccessful (canceled) and
the drop event must not be fired.
User agents should take care to not start drag-and-drop operations in
response to script actions. For example, in a mouse-and-window
environment, if a script moves a window while the user has his mouse
button depressed, the user agent would not consider that to start a drag.
This is important because otherwise user agents could cause data to be
dragged from sensitive sources and dropped into hostile documents without
the user’s consent.
User agents should filter potentially active (scripted) content (e.g.,
HTML) when it is dragged and when it is dropped, using a safelist of
known-safe features. Similarly, relative URLs should be turned into
absolute URLs to avoid references changing in unexpected ways. This
specification does not specify how this is performed.
Consider a hostile page providing some content and getting the user to
select and drag and drop (or indeed, copy and paste) that content to a
victim page’s contenteditable region. If the browser does not ensure that
only safe content is dragged, potentially unsafe content such as scripts
and event handlers in the selection, once dropped (or pasted) into the
victim site, get the privileges of the victim site. This would thus enable
a cross-site scripting attack.
6. Loading Web pages
This section describes features that apply most directly to Web browsers.
Having said that, except where specified otherwise, the requirements
defined in this section do apply to all user agents, whether they are Web
browsers or not.
6.1. Browsing contexts
A browsing context is an environment in which Document objects are
presented to the user.
A tab or window in a Web browser typically contains a browsing context, as
does an iframe or frames in a frameset.
A browsing context has a corresponding WindowProxy object.
A browsing context has a session history, which lists the Document objects
that the browsing context has presented, is presenting, or will present.
At any time, one Document in each browsing context is designated the
active document. A Document's browsing context is that browsing context
whose session history contains the Document, if any. (A Document created
using an API such as createDocument() has no browsing context.) Each
Document in a browsing context is associated with a Window object.
In general, there is a 1-to-1 mapping from the Window object to the
Document object. There are two exceptions. First, a Window can be reused
for the presentation of a second Document in the same browsing context,
such that the mapping is then 1-to-2. This occurs when a browsing context
is navigated from the initial about:blank Document to another, with
replacement enabled. Second, a Document can end up being reused for
several Window objects when the document.open() method is used, such that
the mapping is then many-to-1.
A Document does not necessarily have a browsing context associated with
it. In particular, data mining tools are likely to never instantiate
browsing contexts.
----------------------------------------------------------------------
A browsing context can have a creator browsing context, the browsing
context that was responsible for its creation. If a browsing context has a
parent browsing context, then that is its creator browsing context.
Otherwise, if the browsing context has an opener browsing context, then
that is its creator browsing context. Otherwise, the browsing context has
no creator browsing context.
If a browsing context context has a creator browsing context creator, it
also has the following properties. In what follows, let creator document
be creator’s active document at the time context is created:
creator origin
creator document’s origin
creator URL
creator document’s URL
creator base URL
creator document’s base URL
creator referrer policy
creator document’s referrer policy
creator context security
The result of executing Is environment settings object a secure
context? on creator document’s relevant settings object
To create a new browsing context:
1. Call the JavaScript InitializeHostDefinedRealm() abstract operation
with the following customizations:
* For the global object, create a new Window object window.
* For the global this value, create a new WindowProxy object
windowProxy, whose [[Window]] internal slot value is window.
The internal slot value is updated when navigations occur.
* Let realm execution context be the created JavaScript execution
context.
2. Set the new browsing context’s associated WindowProxy to windowProxy.
3. Let document be a new Document, whose URL is about:blank, which is
marked as being an HTML document, whose character encoding is UTF-8,
and which is both ready for post-load tasks and completely loaded
immediately.
4. Set the origin of document:
* If the new browsing context has a creator browsing context, then
the origin of document is the creator origin.
* Otherwise, the origin of document is a unique opaque origin
assigned when the new browsing context is created.
5. If the new browsing context has a creator browsing context, then set
document’s referrer to the creator URL.
6. Ensure that document has a single child html node, which itself has
two empty child nodes: a head element, and a body element.
7. Implement the sandboxing for document.
8. Add document to the new browsing context’s session history.
9. Set window’s associated Document to document.
10. Set up a browsing context environment settings object with realm
execution context.
6.1.1. Nested browsing contexts
Certain elements (for example, iframe elements) can instantiate further
browsing contexts. These are called nested browsing contexts. If a
browsing context P has a Document D with an element E that nests another
browsing context C inside it, then C is said to be nested through D, and E
is said to be the browsing context container of C. If the browsing context
container element E is in the Document D, then P is said to be the parent
browsing context of C and C is said to be a child browsing context of P.
Otherwise, the nested browsing context C has no parent browsing context.
A browsing context A is said to be an ancestor of a browsing context B if
there exists a browsing context A' that is a child browsing context of A
and that is itself an ancestor of B, or if the browsing context A is the
parent browsing context of B.
A browsing context that is not a nested browsing context has no parent
browsing context, and is the top-level browsing context of all the
browsing contexts for which it is an ancestor browsing context.
The transitive closure of parent browsing contexts for a nested browsing
context gives the list of ancestor browsing contexts.
The list of the descendant browsing contexts of a Document d is the
(ordered) list returned by the following algorithm:
1. Let list be an empty list.
2. For each child browsing context of d that is nested through an element
that is in the Document d, in the tree order of the elements nesting
those browsing contexts, run these substeps:
1. Append that child browsing context to the list list.
2. Append the list of the descendant browsing contexts of the active
document of that child browsing context to the list list.
3. Return the constructed list.
A Document is said to be fully active when it has a browsing context and
it is the active document of that browsing context, and either its
browsing context is a top-level browsing context, or it has a parent
browsing context and the Document through which it is nested is itself
fully active.
Because they are nested through an element, child browsing contexts are
always tied to a specific Document in their parent browsing context. User
agents must not allow the user to interact with child browsing contexts of
elements that are in Documents that are not themselves fully active.
A nested browsing context can be put into a delaying load events mode.
This is used when it is navigated, to delay the load event of the browsing
context container before the new Document is created.
The document family of a browsing context consists of the union of all the
Document objects in that browsing context’s session history and the
document families of all those Document objects. The document family of a
Document object consists of the union of all the document families of the
browsing contexts that are nested through the Document object.
The content document of a browsing context container container is the
result of the following algorithm:
1. If container’s nested browsing context is null, then return null.
2. Let context be container’s nested browsing context.
3. Let document be context’s active document.
4. If document’s origin and the origin specified by the current settings
object are not same origin-domain, then return null.
5. Return document.
6.1.1.1. Navigating nested browsing contexts in the DOM
window . top
Returns the WindowProxy for the top-level browsing context.
window . parent
Returns the WindowProxy for the parent browsing context.
window . frameElement
Returns the Element for the browsing context container.
Returns null if there isn’t one, and in cross-origin situations.
The top IDL attribute on the Window object of a Document in a browsing
context b must return the WindowProxy object of its top-level browsing
context (which would be its own WindowProxy object if it was a top-level
browsing context itself), if it has one, or its own WindowProxy object
otherwise (e.g., if it was a detached nested browsing context).
The parent IDL attribute on the Window object of a Document that has a
browsing context b must return the WindowProxy object of the parent
browsing context, if there is one (i.e., if b is a child browsing
context), or the WindowProxy object of the browsing context b itself,
otherwise (i.e., if it is a top-level browsing context or a detached
nested browsing context).
The frameElement IDL attribute, on getting, must run the following
algorithm:
1. Let d be the Window object’s associated Document.
2. Let context be d’s browsing context.
3. If context is not a nested browsing context, return null and abort
these steps.
4. Let container be context’s browsing context container.
5. If container’s node document’s origin is not same origin-domain with
the entry settings object’s origin, then return null and abort these
steps.
6. Return container.
6.1.2. Auxiliary browsing contexts
It is possible to create new browsing contexts that are related to a
top-level browsing context without being nested through an element. Such
browsing contexts are called auxiliary browsing contexts. Auxiliary
browsing contexts are always top-level browsing contexts.
An auxiliary browsing context has an opener browsing context, which is the
browsing context from which the auxiliary browsing context was created.
6.1.2.1. Navigating auxiliary browsing contexts in the DOM
The opener IDL attribute on the Window object, on getting, must return the
WindowProxy object of the browsing context from which the current browsing
context was created (its opener browsing context), if there is one, if it
is still available, and if the current browsing context has not disowned
its opener; otherwise, it must return null.
On setting the opener attribute, if the new value is null then the current
browsing context must disown its opener; if the new value is anything else
then the user agent must call the [[DefineOwnProperty]] internal method of
the Window object, passing the property name "opener" as the property key,
and the Property Descriptor { [[Value]]: value, [[Writable]]: true,
[[Enumerable]]: true, [[Configurable]]: true } as the property descriptor,
where value is the new value.
6.1.3. Security
A browsing context A is familiar with a second browsing context B if one
of the following conditions is true:
* Either the origin of the active document of A is the same as the
origin of the active document of B, or
* The browsing context A is a nested browsing context with a top-level
browsing context, and its top-level browsing context is B, or
* The browsing context B is an auxiliary browsing context and A is
familiar with B’s opener browsing context, or
* The browsing context B is not a top-level browsing context, but there
exists an ancestor browsing context of B whose active document has the
same origin as the active document of A (possibly in fact being A
itself).
The relationship "familiar with" may be used to decide the value of a
browsing context name, see the table in the following browsing context
names section for details.
----------------------------------------------------------------------
A browsing context A is allowed to navigate a second browsing context B if
the following algorithm terminates positively:
1. If A is not the same browsing context as B, and A is not one of the
ancestor browsing contexts of B, and B is not a top-level browsing
context, and A’s active document’s active sandboxing flag set has its
sandboxed navigation browsing context flag set, then abort these steps
negatively.
2. Otherwise, if B is a top-level browsing context, and is one of the
ancestor browsing contexts of A, and A’s active document’s active
sandboxing flag set has its sandboxed top-level navigation browsing
context flag set, then abort these steps negatively.
3. Otherwise, if B is a top-level browsing context, and is neither A nor
one of the ancestor browsing contexts of A, and A’s Document's active
sandboxing flag set has its sandboxed navigation browsing context flag
set, and A is not the one permitted sandboxed navigator of B, then
abort these steps negatively.
4. Otherwise, terminate positively!
----------------------------------------------------------------------
An element has a browsing context scope origin if its Document's browsing
context is a top-level browsing context or if all of its Document's
ancestor browsing contexts all have active documents whose origin are the
same origin as the element’s node document’s origin. If an element has a
browsing context scope origin, then its value is the origin of the
element’s node document.
6.1.4. Groupings of browsing contexts
Each browsing context is defined as having a list of one or more directly
reachable browsing contexts. These are:
* The browsing context itself.
* All the browsing context’s child browsing contexts.
* The browsing context’s parent browsing context.
* All the browsing contexts that have the browsing context as their
opener browsing context.
* The browsing context’s opener browsing context.
The transitive closure of all the browsing contexts that are directly
reachable browsing contexts forms a unit of related browsing contexts.
Each unit of related browsing contexts is then further divided into the
smallest number of groups such that every member of each group has an
active document with an origin that, through appropriate manipulation of
the document.domain attribute, could be made to be same origin-domain with
other members of the group, but could not be made the same as members of
any other group. Each such group is a unit of related similar-origin
browsing contexts.
There is also at most one event loop per unit of related similar-origin
browsing contexts (though several units of related similar-origin browsing
contexts can have a shared event loop).
6.1.5. Browsing context names
Browsing contexts can have a browsing context name. By default, a browsing
context has no name (its name is not set).
A valid browsing context name is any string with at least one character
that does not start with a U+005F LOW LINE character. (Names starting with
an underscore are reserved for special keywords.)
A valid browsing context name or keyword is any string that is either a
valid browsing context name or that is an ASCII case-insensitive match for
one of: _blank, _self, _parent, or _top.
These values have different meanings based on whether the page is
sandboxed or not, as summarized in the following (non-normative) table. In
this table, "current" means the browsing context that the link or script
is in, "parent" means the parent browsing context of the one the link or
script is in, "top" means the top-level browsing context of the one the
link or script is in, "new" means a new top-level browsing context or
auxiliary browsing context is to be created, subject to various user
preferences and user agent policies, "none" means that nothing will
happen, and "maybe new" means the same as "new" if the "allow-popups"
keyword is also specified on the sandbox attribute (or if the user
overrode the sandboxing), and the same as "none" otherwise.
Keyword Ordinary Effect in an iframe with...
effect sandbox="" sandbox="allow-top-navigation"
none specified, for
links and form current current current
submissions
empty string current current current
_blank new maybe new maybe new
_self current current current
_parent if there current current current
isn’t a parent
_parent if parent parent/top none parent/top
is also top
_parent if there is
one and it’s not parent none none
top
_top if top is current current current
current
_top if top is not top none top
current
name that doesn’t new maybe new maybe new
exist
name that exists specified specified specified descendant
and is a descendant descendant descendant
name that exists current current current
and is current
name that exists specified
and is an ancestor ancestor none specified ancestor/top
that is top
name that exists specified
and is an ancestor ancestor none none
that is not top
other name that
exists with common specified none none
top
name that exists
with different top,
if familiar and one specified specified specified
permitted sandboxed
navigator
name that exists
with different top,
if familiar but not specified none none
one permitted
sandboxed navigator
name that exists
with different top, new maybe new maybe new
not familiar
Most of the restrictions on sandboxed browsing contexts are applied by
other algorithms, e.g., the navigation algorithm, not the rules for
choosing a browsing context given a browsing context name given below.
----------------------------------------------------------------------
An algorithm is allowed to show a popup if any of the following conditions
is true:
* The task in which the algorithm is running is currently processing an
activation behavior whose click event was trusted.
* The task in which the algorithm is running is currently running the
event listener for a trusted event whose type is in the following
list:
* change
* click
* dblclick
* mouseup
* reset
* submit
* The task in which the algorithm is running was queued by an algorithm
that was allowed to show a popup, and the chain of such algorithms
started within a user-agent defined timeframe.
For example, if a user clicked a button, it might be acceptable for a
popup to result from that after 4 seconds, but it would likely not be
acceptable for a popup to result from that after 4 hours.
----------------------------------------------------------------------
The rules for choosing a browsing context given a browsing context name
are as follows. The rules assume that they are being applied in the
context of a browsing context, as part of the execution of a task.
1. If the given browsing context name is the empty string or _self, then
the chosen browsing context must be the current one.
2. If the given browsing context name is _parent, then the chosen
browsing context must be the parent browsing context of the current
one, unless there isn’t one, in which case the chosen browsing context
must be the current browsing context.
3. If the given browsing context name is _top, then the chosen browsing
context must be the top-level browsing context of the current one, if
there is one, or else the current browsing context.
4. If the given browsing context name is not _blank and there exists a
browsing context whose name is the same as the given browsing context
name, and the current browsing context is familiar with that browsing
context, and the user agent determines that the two browsing contexts
are related enough that it is ok if they reach each other, then that
browsing context must be the chosen one. If there are multiple
matching browsing contexts, the user agent should select one in some
arbitrary consistent manner, such as the most recently opened, most
recently focused, or more closely related.
5. Otherwise, a new browsing context is being requested, and what happens
depends on the user agent’s configuration and abilities — it is
determined by the rules given for the first applicable option from the
following list:
If the algorithm is not allowed to show a popup and the user
agent has been configured to not show popups (i.e., the user
agent has a "popup blocker" enabled)
There is no chosen browsing context. The user agent may
inform the user that a popup has been blocked.
If the current browsing context’s active document’s active
sandboxing flag set has the sandboxed auxiliary navigation
browsing context flag set.
Typically, there is no chosen browsing context.
The user agent may offer to create a new top-level
browsing context or reuse an existing top-level browsing
context. If the user picks one of those options, then the
designated browsing context must be the chosen one (the
browsing context’s name isn’t set to the given browsing
context name). The default behavior (if the user agent
doesn’t offer the option to the user, or if the user
declines to allow a browsing context to be used) must be
that there must not be a chosen browsing context.
If this case occurs, it means that an author has
explicitly sandboxed the document that is trying to open
a link.
If the user agent has been configured such that in this instance
it will create a new browsing context, and the browsing context
is being requested as part of following a hyperlink whose link
types include the noreferrer keyword
A new top-level browsing context must be created. If the
given browsing context name is not _blank, then the new
top-level browsing context’s name must be the given
browsing context name (otherwise, it has no name). The
chosen browsing context must be this new browsing
context. The creation of such a browsing context is a new
start for session storage.
If it is immediately navigated, then the navigation will
be done with replacement enabled.
If the user agent has been configured such that in this instance
it will create a new browsing context, and the noreferrer keyword
doesn’t apply
A new auxiliary browsing context must be created, with
the opener browsing context being the current one. If the
given browsing context name is not _blank, then the new
auxiliary browsing context’s name must be the given
browsing context name (otherwise, it has no name). The
chosen browsing context must be this new browsing
context.
If it is immediately navigated, then the navigation will
be done with replacement enabled.
If the user agent has been configured such that in this instance
it will reuse the current browsing context
The chosen browsing context is the current browsing
context.
If the user agent has been configured such that in this instance
it will not find a browsing context
There must not be a chosen browsing context.
User agent implementors are encouraged to provide a way for users to
configure the user agent to always reuse the current browsing context.
If the chosen browsing context picked above, if any, is a new browsing
context, then:
1. Let flagSet be the current browsing context’s active document’s
active sandboxing flag set.
2. If flagSet’s sandboxed navigation browsing context flag is set,
then the current browsing context must be set as the new browsing
context’s one permitted sandboxed navigator.
3. If flagSet’s sandbox propagates to auxiliary browsing contexts
flag is set, then all the flags that are set in flagSet must be
set in the new browsing context’s popup sandboxing flag set.
6.1.6. Script settings for browsing contexts
When the user agent is required to set up a browsing context environment
settings object, given a JavaScript execution context execution context,
it must run the following steps:
1. Let realm be the value of execution context’s Realm component.
2. Let window be realm’s global object.
3. Let url be a copy of the URL of the Document with which window is
associated.
4. Let settings object be a new environment settings object whose
algorithms are defined as follows:
The realm execution context
Return execution context.
The module map
Return the module map of the Document with which window
is currently associated.
The responsible browsing context
Return the browsing context with which window is
associated.
The responsible event loop
Return the event loop that is associated with the unit of
related similar-origin browsing contexts to which
window’s browsing context belongs.
The responsible document
Return the Document with which window is currently
associated.
The API URL character encoding
Return the current character encoding of the Document
with which window is currently associated.
The API base URL
Return the current base URL of the Document with which
window is currently associated.
The origin
Return the origin of the Document with which window is
currently associated.
The creation URL
Return url.
The HTTPS state
Return the HTTPS state of the Document with which window
is currently associated.
5. Set realm’s [[HostDefined]] field to settings object.
6. Return settings object.
6.2. Security infrastructure for Window, WindowProxy, and Location objects
Although typically objects cannot be accessed across origins, the web
platform would not be true to itself if it did not have some legacy
exceptions to that rule that the web depends upon.
6.2.1. Integration with IDL
When perform a security check is invoked, with a platformObject, realm,
identifier, and type, run these steps:
1. If platformObject is a Window or Location object, then:
1. Repeat for each e that is an element of
CrossOriginProperties(platformObject):
1. If SameValue(e.[[Property]], identifier) is true, then:
1. If type is "method" and e has neither [[NeedsGet]] nor
[[NeedsSet]], then return.
2. Otherwise, if type is "getter" and e.[[NeedsGet]] is
true, then return.
3. Otherwise, if type is "setter" and e.[[NeedsSet]] is
true, then return.
2. If IsPlatformObjectSameOrigin(platformObject) is false, then throw a
"SecurityError" DOMException.
6.2.2. Shared internal slot: [[CrossOriginPropertyDescriptorMap]]
Window and Location objects both have a
[[CrossOriginPropertyDescriptorMap]] internal slot, whose value is
initially an empty map.
The [[CrossOriginPropertyDescriptorMap]] internal slot contains a map with
entries whose keys are (currentOrigin, objectOrigin, propertyKey)-tuples
and values are property descriptors, as a memoization of what is visible
to scripts when currentOrigin inspects a Window or Location object from
objectOrigin. It is filled lazily by CrossOriginGetOwnPropertyHelper,
which consults it on future lookups.
User agents should allow a value held in the map to be garbage collected
along with its corresponding key when nothing holds a reference to any
part of the value. That is, as long as garbage collection is not
observable.
For example, with
const href = Object.getOwnPropertyDescriptor(crossOriginLocation, "href").set
the value and its corresponding key in the map cannot be garbage collected
as that would be observable.
User agents may have an optimization whereby they remove key-value pairs
from the map when document.domain is set. This is not observable as
document.domain cannot revisit an earlier value.
For example, setting document.domain to "example.com" on www.example.com
means user agents can remove all key-value pairs from the map where part
of the key is www.example.com, as that can never be part of the origin
again and therefore the corresponding value could never be retrieved from
the map.
6.2.3. Shared abstract operations
6.2.3.1. CrossOriginProperties ( O )
1. Assert: O is a Location or Window object.
2. If O is a Location object, then return
« {
[[Property]]: "href",
[[NeedsGet]]: false,
[[NeedsSet]]: true
},
{
[[Property]]: "replace"
} »
3. Let crossOriginWindowProperties be
« {
[[Property]]: "window",
[[NeedsGet]]: true,
[[NeedsSet]]: false
},
{
[[Property]]: "self",
[[NeedsGet]]: true,
[[NeedsSet]]: false
},
{
[[Property]]: "location",
[[NeedsGet]]: true,
[[NeedsSet]]: true
},
{
[[Property]]: "close"
},
{
[[Property]]: "closed",
[[NeedsGet]]: true,
[[NeedsSet]]: false
},
{
[[Property]]: "focus"
},
{
[[Property]]: "blur"
},
{
[[Property]]: "frames",
[[NeedsGet]]: true,
[[NeedsSet]]: false
},
{
[[Property]]: "length",
[[NeedsGet]]: true,
[[NeedsSet]]: false
},
{
[[Property]]: "top",
[[NeedsGet]]: true,
[[NeedsSet]]: false
},
{
[[Property]]: "opener",
[[NeedsGet]]: true,
[[NeedsSet]]: false
},
{
[[Property]]: "parent",
[[NeedsGet]]: true,
[[NeedsSet]]: false
},
{
[[Property]]: "postMessage"
} »
4. Repeat for each e that is an element of the child browsing context
name property set:
1. Add { [[Property]]: e } as the last element of
crossOriginWindowProperties.
5. Return crossOriginWindowProperties.
Indexed properties do not need to be safelisted as they are handled
directly by the WindowProxy object.
6.2.3.2. IsPlatformObjectSameOrigin ( O )
1. Return true if the current settings object’s origin is same
origin-domain with O’s relevant settings object’s origin, and false
otherwise.
6.2.3.3. CrossOriginGetOwnPropertyHelper ( O, P )
If this abstract operation returns undefined and there is no custom
behavior, the caller needs to throw a "SecurityError" DOMException.
1. If P is @@toStringTag, @@hasInstance, or @@isConcatSpreadable, then
return PropertyDescriptor { [[Value]]: undefined, [[Writable]]: false,
[[Enumerable]]: false, [[Configurable]]: true }.
2. Let crossOriginKey be a tuple consisting of the current settings
object’s origin's effective domain, O’s relevant settings object’s
origin's effective domain, and P.
3. Repeat for each e that is an element of CrossOriginProperties(O):
1. If SameValue(e.[[Property]], P) is true, then:
1. If the value of the [[CrossOriginPropertyDescriptorMap]]
internal slot of O contains an entry whose key is
crossOriginKey, then return that entry’s value.
2. Let originalDesc be OrdinaryGetOwnProperty(O, P).
3. Let crossOriginDesc be CrossOriginPropertyDescriptor(e,
originalDesc).
4. Create an entry in the value of the
[[CrossOriginPropertyDescriptorMap]] internal slot of O with
key crossOriginKey and value crossOriginDesc.
5. Return crossOriginDesc.
4. Return undefined.
6.2.3.3.1. CrossOriginPropertyDescriptor ( crossOriginProperty,
originalDesc )
1. If crossOriginProperty.[[NeedsGet]] and
crossOriginProperty.[[NeedsSet]] are absent, then:
1. Let value be originalDesc.[[Value]].
2. If IsCallable(value) is true, set value to
CrossOriginFunctionWrapper(true, value).
3. Return PropertyDescriptor{ [[Value]]: value, [[Enumerable]]:
false, [[Writable]]: false, [[Configurable]]: true }.
2. Otherwise:
1. Let crossOriginGet be
CrossOriginFunctionWrapper(crossOriginProperty.[[NeedsGet]],
originalDesc.[[Get]]).
2. Let crossOriginSet be
CrossOriginFunctionWrapper(crossOriginProperty.[[NeedsSet]],
originalDesc.[[Set]]).
3. Return PropertyDescriptor{ [[Get]]: crossOriginGet, [[Set]]:
crossOriginSet, [[Enumerable]]: false, [[Configurable]]: true }.
6.2.3.3.2. CrossOriginFunctionWrapper ( needsWrapping, functionToWrap )
1. If needsWrapping is false, then return undefined.
2. Return a new cross-origin wrapper function whose [[Wrapped]] internal
slot is functionToWrap.
A cross-origin wrapper function is an anonymous built-in function that has
a [[Wrapped]] internal slot.
When a cross-origin wrapper function F is called with a list of arguments
argumentsList, the following steps are taken:
1. Assert: F has a [[Wrapped]] internal slot that is a function.
2. Let wrappedFunction be the [[Wrapped]] internal slot of F.
3. Return Call(wrappedFunction, this, argumentsList).
Due to this being invoked from a different origin, a cross-origin wrapper
function will have a different value for Function.prototype from the
function being wrapped. This follows from how JavaScript creates anonymous
built-in functions.
6.2.3.4. CrossOriginGet ( O, P, Receiver )
1. Let desc be O.[[GetOwnProperty]](P).
2. Assert: desc is not undefined.
3. If IsDataDescriptor(desc) is true, then return desc.[[Value]].
4. Assert: IsAccessorDescriptor(desc) is true.
5. Let getter be desc.[[Get]].
6. If getter is undefined, throw a "SecurityError" DOMException.
7. Return Call(getter, Receiver).
6.2.3.5. CrossOriginSet ( O, P, V, Receiver )
1. Let desc be O.[[GetOwnProperty]](P).
2. Assert: desc is not undefined.
3. If IsAccessorDescriptor(desc) is true, then:
1. Let setter be desc.[[Set]].
2. If setter is undefined, return false.
3. Perform Call(setter, Receiver, «V»).
4. Return true.
4. Return false.
6.2.3.6. CrossOriginOwnPropertyKeys ( O )
1. Let keys be a new empty List.
2. Repeat for each e that is an element of CrossOriginProperties(O):
1. Add e.[[Property]] as the last element of keys.
3. Return keys.
6.3. The Window object
[PrimaryGlobal, LegacyUnenumerableNamedProperties]
/*sealed*/ interface Window : EventTarget {
// the current browsing context
[Unforgeable] readonly attribute WindowProxy window;
[Replaceable] readonly attribute WindowProxy self;
[Unforgeable] readonly attribute Document document;
attribute DOMString name;
[PutForwards=href, Unforgeable] readonly attribute Location location;
readonly attribute History history;
[Replaceable] readonly attribute BarProp locationbar;
[Replaceable] readonly attribute BarProp menubar;
[Replaceable] readonly attribute BarProp personalbar;
[Replaceable] readonly attribute BarProp scrollbars;
[Replaceable] readonly attribute BarProp statusbar;
[Replaceable] readonly attribute BarProp toolbar;
attribute DOMString status;
void close();
readonly attribute boolean closed;
void stop();
void focus();
void blur();
// other browsing contexts
[Replaceable] readonly attribute WindowProxy frames;
[Replaceable] readonly attribute unsigned long length;
[Unforgeable] readonly attribute WindowProxy top;
attribute any opener;
[Replaceable] readonly attribute WindowProxy parent;
readonly attribute Element? frameElement;
WindowProxy open(optional DOMString url = "about:blank", optional DOMString target = "_blank", [TreatNullAs=EmptyString] optional DOMString features = "", optional boolean replace = false);
getter WindowProxy (unsigned long index);
getter object (DOMString name);
// Since this is the global object, the IDL named getter adds a NamedPropertiesObject exotic
// object on the prototype chain. Indeed, this does not make the global object an exotic object.
// Indexed access is taken care of by the WindowProxy exotic object.
// the user agent
readonly attribute Navigator navigator;
// user prompts
void alert();
void alert(DOMString message);
boolean confirm(optional DOMString message = "");
DOMString? prompt(optional DOMString message = "", optional DOMString default = "");
void print();
unsigned long requestAnimationFrame(FrameRequestCallback callback);
void cancelAnimationFrame(unsigned long handle);
};
Window implements GlobalEventHandlers;
Window implements WindowEventHandlers;
callback FrameRequestCallback = void (DOMHighResTimeStamp time);
window . window
window . frames
window . self
These attributes all return window.
window . document
Returns the Document associated with window.
document . defaultView
Returns the Window object of the active document.
The window, frames, and self IDL attributes must all return the Window
object’s browsing context’s WindowProxy object.
The document IDL attribute must return the Window object’s newest Document
object.
The Document object associated with a Window object can change in exactly
one case: when the navigate algorithm initializes a new Document object
for the first page loaded in a browsing context. In that specific case,
the Window object of the original about:blank page is reused and gets a
new Document object.
The defaultView IDL attribute of the Document interface must return the
Document's browsing context’s WindowProxy object, if there is one, or null
otherwise.
----------------------------------------------------------------------
For historical reasons, Window objects must also have a writable,
configurable, non-enumerable property named HTMLDocument whose value is
the Document interface object.
6.3.1. APIs for creating and navigating browsing contexts by name
window = window . open( [ url [, target [, features [, replace ] ] ] ] )
Opens a window to show url (defaults to about:blank), and returns
it. The target argument gives the name of the new window. If a
window exists with that name already, it is reused. The replace
attribute, if true, means that whatever page is currently open in
that window will be removed from the window’s session history. The
features argument can be used to influence the rendering of the
new window.
window . name [ = value ]
Returns the name of the window.
Can be set, to change the name.
window . close()
Closes the window.
window . closed
Returns true if the window has been closed, false otherwise.
window . stop()
Cancels the document load.
The open() method on Window objects provides a mechanism for navigating an
existing browsing context or opening and navigating an auxiliary browsing
context.
When the method is invoked, the user agent must run the following steps:
1. Let entry settings be the entry settings object when the method was
invoked.
2. Let url be the first argument.
3. Let target be the second argument.
4. Let features be the third argument.
5. Let replace be the fourth argument.
6. Let source browsing context be the responsible browsing context
specified by entry settings.
7. If target is the empty string, let it be the string "_blank" instead.
8. If the user has indicated a preference for which browsing context to
navigate, follow these substeps:
1. Let target browsing context be the browsing context indicated by
the user.
2. If target browsing context is a new top-level browsing context,
let the source browsing context be set as target browsing
context’s one permitted sandboxed navigator.
For example, suppose there is a user agent that supports
control-clicking a link to open it in a new tab. If a user clicks in
that user agent on an element whose onclick handler uses the
window.open() API to open a page in an iframe, but, while doing so,
holds the control key down, the user agent could override the
selection of the target browsing context to instead target a new tab.
Otherwise, apply the rules for choosing a browsing context given a
browsing context name using target as the name and source browsing
context as the context in which the algorithm is executed. If this
results in there not being a chosen browsing context, then throw an
InvalidAccessError exception and abort these steps. Otherwise, let
target browsing context be the browsing context so obtained.
9. If target browsing context was just created, either as part of the
rules for choosing a browsing context given a browsing context name or
due to the user indicating a preference for navigating a new top-level
browsing context, then let new be true. Otherwise, let it be false.
10. Interpret features as defined in the CSSOM View specification.
[CSSOM-VIEW]
11. If url is the empty string, run the appropriate steps from the
following list:
If new is false
Jump to the step labeled end.
If new is true
Let resource be the URL "about:blank".
Otherwise, parse url relative to entry settings, and let resource be
the resulting URL record, if any. If the parse a URL algorithm failed,
then run one of the following two steps instead:
* Let resource be a resource representing an inline error page.
* If new is false, jump to the step labeled end, otherwise, let
resource be the URL "about:blank".
12. If resource is "about:blank" and new is true, queue a task to fire a
simple event named load at target browsing context’s Window object,
with target override set to target browsing context’s Window object’s
Document object.
Otherwise, navigate target browsing context to resource, with the
exceptions enabled flag set. If new is true, then replacement must be
enabled also. The source browsing context is source browsing context.
13. End:
1. If the result of splitting features on commas contains the token
"noopener", then disown target browsing context’s opener and
return null.
2. Otherwise, return the WindowProxy object of target browsing
context.
----------------------------------------------------------------------
The name attribute of the Window object must, on getting, return the
current name of the browsing context, if one is set, or the empty string
otherwise; and, on setting, set the name of the browsing context to the
new value.
The name gets reset when the browsing context is navigated to another
domain.
----------------------------------------------------------------------
The close() method on Window objects should, if all the following
conditions are met, close the browsing context A:
* The corresponding browsing context A is script-closable.
* The responsible browsing context specified by the incumbent settings
object is familiar with the browsing context A.
* The responsible browsing context specified by the incumbent settings
object is allowed to navigate the browsing context A.
A browsing context is script-closable if it is an auxiliary browsing
context that was created by a script (as opposed to by an action of the
user), or if it is a top-level browsing context whose session history
contains only one Document.
The closed attribute on Window objects must return true if the Window
object’s browsing context has been discarded, and false otherwise.
The stop() method on Window objects should, if there is an existing
attempt to navigate the browsing context and that attempt is not currently
running the unload a document algorithm, cancel that navigation; then, it
must abort the active document of the browsing context of the Window
object on which it was invoked.
6.3.2. Accessing other browsing contexts
window . length
Returns the number of child browsing contexts.
window[index]
Returns the indicated child browsing context.
The number of child browsing contexts of a Window object W is the number
of child browsing contexts that are nested through elements that are in a
Document that is the active document of the Window object’s associated
Document object’s browsing context.
The length IDL attribute’s getter must return the number of child browsing
contexts of this Window object.
Indexed access to child browsing contexts is defined through the
[[GetOwnProperty]] internal method of the WindowProxy object.
6.3.3. Named access on the Window object
window[name]
Returns the indicated element or collection of elements.
As a general rule, relying on this will lead to brittle code.
Which IDs end up mapping to this API can vary over time, as new
features are added to the Web platform, for example. Instead of
this, use document.getElementById() or document.querySelector().
The child browsing context name property set consists of the browsing
context names of any child browsing context of the active document whose
name is not the empty string, with duplicates omitted.
The Window interface supports named properties. The supported property
names at any moment consist of the following, in tree order, ignoring
later duplicates:
* the child browsing context name property set.
* the value of the name content attribute for all a, applet, area,
embed, form, frameset, img, and object elements in the active document
that have a non-empty name content attribute, and
* the value of the id content attribute of any HTML element in the
active document with a non-empty id content attribute.
To determine the value of a named property name when the Window object is
indexed for property retrieval, the user agent must return the value
obtained using the following steps:
1. Let objects be the list of named objects with the name name in the
active document.
There will be at least one such object, by definition.
2. If objects contains a nested browsing context, then return the
WindowProxy object of the nested browsing context corresponding to the
first browsing context container in tree order whose browsing context
is in objects, and abort these steps.
3. Otherwise, if objects has only one element, return that element and
abort these steps.
4. Otherwise return an HTMLCollection rooted at the Document node, whose
filter matches only named objects with the name name. (By definition,
these will all be elements.)
Named objects with the name name, for the purposes of the above algorithm,
are those that are either:
* child browsing contexts of the active document whose name is name,
* a, applet, area, embed, form, frameset, img, or object elements that
have a name content attribute whose value is name, or
* HTML elements that have an id content attribute whose value is name.
6.3.4. Garbage collection and browsing contexts
A browsing context has a strong reference to each of its Documents and its
WindowProxy object, and the user agent itself has a strong reference to
its top-level browsing contexts.
A Document has a strong reference to its Window object.
A Window object has a strong reference to its Document object through its
document attribute. Thus, references from other scripts to either of those
objects will keep both alive. Similarly, both Document and Window objects
have implied strong references to the WindowProxy object.
Each script has a strong reference to its settings object, and each
environment settings object has strong references to its global object,
responsible browsing context, and responsible document (if any).
When a browsing context is to discard a Document, the user agent must run
the following steps:
1. Set the Document's salvageable state to false.
2. Run any unloading document cleanup steps for the Document that are
defined by this specification and other applicable specifications.
3. Abort the Document.
4. Remove any tasks associated with the Document in any task source,
without running those tasks.
5. Discard all the child browsing contexts of the Document.
6. Lose the strong reference from the Document's browsing context to the
Document.
Whenever a Document object is discarded, it is also removed from the list
of the worker’s Documents of each worker whose list contains that
Document.
When a browsing context is discarded, the strong reference from the user
agent itself to the browsing context must be severed, and all the Document
objects for all the entries in the browsing context’s session history must
be discarded as well.
User agents may discard top-level browsing contexts at any time
(typically, in response to user requests, e.g., when a user force-closes a
window containing one or more top-level browsing contexts). Other browsing
contexts must be discarded once their WindowProxy object is eligible for
garbage collection.
6.3.5. Closing browsing contexts
When the user agent is required to close a browsing context, it must run
the following steps:
1. Let specified browsing context be the browsing context being closed.
2. Prompt to unload the active document of the specified browsing
context. If the user refused to allow the document to be unloaded,
then abort these steps.
3. Unload the active document of the specified browsing context with the
recycle parameter set to false.
4. Remove the specified browsing context from the user interface (e.g.,
close or hide its tab in a tabbed browser).
5. Discard the specified browsing context.
User agents should offer users the ability to arbitrarily close any
top-level browsing context.
6.3.6. Browser interface elements
To allow Web pages to integrate with Web browsers, certain Web browser
interface elements are exposed in a limited way to scripts in Web pages.
Each interface element is represented by a BarProp object:
interface BarProp {
readonly attribute boolean visible;
};
window . locationbar . visible
Returns true if the location bar is visible; otherwise, returns
false.
window . menubar . visible
Returns true if the menu bar is visible; otherwise, returns false.
window . personalbar . visible
Returns true if the personal bar is visible; otherwise, returns
false.
window . scrollbars . visible
Returns true if the scroll bars are visible; otherwise, returns
false.
window . statusbar . visible
Returns true if the status bar is visible; otherwise, returns
false.
window . toolbar . visible
Returns true if the toolbar is visible; otherwise, returns false.
The visible attribute, on getting, must return either true or a value
determined by the user agent to most accurately represent the visibility
state of the user interface element that the object represents, as
described below.
The following BarProp objects exist for each Document object in a browsing
context. Some of the user interface elements represented by these objects
might have no equivalent in some user agents; for those user agents,
except when otherwise specified, the object must act as if it was present
and visible (i.e., its visible attribute must return true).
The location bar BarProp object
Represents the user interface element that contains a control that
displays the URL of the active document, or some similar interface
concept.
The menu bar BarProp object
Represents the user interface element that contains a list of
commands in menu form, or some similar interface concept.
The personal bar BarProp object
Represents the user interface element that contains links to the
user’s favorite pages, or some similar interface concept.
The scrollbar BarProp object
Represents the user interface element that contains a scrolling
mechanism, or some similar interface concept.
The status bar BarProp object
Represents a user interface element found immediately below or
after the document, as appropriate for the user’s media, which
typically provides information about ongoing network activity or
information about elements that the user’s pointing device is
current indicating. If the user agent has no such user interface
element, then the object may act as if the corresponding user
interface element was absent (i.e., its visible attribute may
return false).
The toolbar BarProp object
Represents the user interface element found immediately above or
before the document, as appropriate for the user’s media, which
typically provides session history traversal controls (back and
forward buttons, reload buttons, etc). If the user agent has no
such user interface element, then the object may act as if the
corresponding user interface element was absent (i.e., its visible
attribute may return false).
The locationbar attribute must return the location bar BarProp object.
The menubar attribute must return the menu bar BarProp object.
The personalbar attribute must return the personal bar BarProp object.
The scrollbars attribute must return the scrollbar BarProp object.
The statusbar attribute must return the status bar BarProp object.
The toolbar attribute must return the toolbar BarProp object.
----------------------------------------------------------------------
For historical reasons, the status attribute on the Window object must, on
getting, return the last string it was set to, and on setting, must set
itself to the new value. When the Window object is created, the attribute
must be set to the empty string. It does not do anything else.
6.3.7. The WindowProxy object
A WindowProxy is an exotic object that wraps a Window ordinary object,
indirecting most operations through to the wrapped object. Each browsing
context has an associated WindowProxy object. When the browsing context is
navigated, the Window object wrapped by the browsing context’s associated
WindowProxy object is changed.
There is no WindowProxy interface object.
Every WindowProxy object has a [[Window]] internal slot representing the
wrapped Window object.
Although WindowProxy is named as a "proxy", it does not do polymorphic
dispatch on its target’s internal methods as a real proxy would, due to a
desire to reuse machinery between WindowProxy and Location objects. As
long as the Window object remains an ordinary object this is unobservable
and can be implemented either way.
In the following example, the variable x is set to the WindowProxy object
returned by the window accessor on the global object. All of the
expressions following the assignment return true, because the WindowProxy
object passes most operations through to the underlying ordinary Window
object.
var x = window;
x instanceof Window; // true
x === this; // true
6.3.7.1. The WindowProxy internal methods
The WindowProxy object internal methods are described in the subsections
below.
6.3.7.1.1. [[GetPrototypeOf]] ( )
1. Let W be the value of the [[Window]] internal slot of this.
2. If IsPlatformObjectSameOrigin(W) is true, then return !
OrdinaryGetPrototypeOf(W).
3. Return null.
6.3.7.1.2. [[SetPrototypeOf]] ( V )
1. Return false.
6.3.7.1.3. [[IsExtensible]] ( )
1. Return true.
6.3.7.1.4. [[PreventExtensions]] ( )
1. Return false.
6.3.7.1.5. [[GetOwnProperty]] ( P )
1. Let W be the value of the [[Window]] internal slot of this.
2. If P is an array index property name, then:
1. Let index be ToUint32(P).
2. Let maxProperties be the number of child browsing contexts of W.
3. Let value be undefined.
4. If maxProperties is greater than 0 and index is less than
maxProperties, then:
1. Set value to the WindowProxy object of the indexth child
browsing context of the Document that is nested through an
element that is in W’s Document, sorted in the order that
the elements nesting those browsing contexts were most
recently inserted into the Document, the WindowProxy object
of the most recently inserted browsing context container’s
nested browsing context being last.
5. Return PropertyDescriptor{ [[Value]]: value, [[Writable]]: false,
[[Enumerable]]: false, [[Configurable]]: true }.
3. If IsPlatformObjectSameOrigin(W) is true, then return
OrdinaryGetOwnProperty(W, P).
This violates JavaScript’s internal method invariants.
4. Let property be CrossOriginGetOwnPropertyHelper(W, P).
5. If property is not undefined, return property.
6. If property is undefined and P is in the child browsing context name
property set, then:
1. Let value be the WindowProxy object of the named object with the
name P.
2. Return PropertyDescriptor{ [[Value]]: value, [[Enumerable]]:
false, [[Writable]]: false, [[Configurable]]: true }.
7. Throw a "SecurityError" DOMException.
6.3.7.1.6. [[DefineOwnProperty]] ( P, Desc )
1. If P is an array index property name, return false.
2. Let W be the value of the [[Window]] internal slot of this.
3. If IsPlatformObjectSameOrigin(W) is true, then return
OrdinaryDefineOwnProperty(W, P, Desc).
See above about how this violates JavaScript’s internal method
invariants.
4. Return false.
6.3.7.1.7. [[Get]] ( P, Receiver )
1. Let W be the value of the [[Window]] internal slot of this.
2. If IsPlatformObjectSameOrigin(W) is true, then return
OrdinaryGet(this, P, Receiver).
3. Return ? CrossOriginGet(this, P, Receiver).
6.3.7.1.8. [[Set]] ( P, V, Receiver )
1. Let W be the value of the [[Window]] internal slot of this.
2. If IsPlatformObjectSameOrigin(W) is true, then return OrdinarySet(W,
this, Receiver).
3. Return CrossOriginSet(this, P, V, Receiver).
6.3.7.1.9. [[Delete]] ( P )
1. If P is an array index property name, return false.
2. Let W be the value of the [[Window]] internal slot of this.
3. If IsPlatformObjectSameOrigin(W) is true, then return
OrdinaryDelete(W, P).
4. Return false.
6.3.7.1.10. [[OwnPropertyKeys]] ( )
1. Let W be the value of the [[Window]] internal slot of this.
2. Let keys be a new empty List.
3. Let maxProperties be the number of child browsing contexts of W.
4. Let index be 0.
5. Repeat while index < maxProperties,
1. Add ! ToString(index) as the last element of keys.
2. Increment index by 1.
6. If IsPlatformObjectSameOrigin(W) is true, then return the
concatenation of keys and ! OrdinaryOwnPropertyKeys(W).
7. Return the concatenation of keys and ! CrossOriginOwnPropertyKeys(W).
6.4. Origin
Origins are the fundamental currency of the Web’s security model. Two
actors in the Web platform that share an origin are assumed to trust each
other and to have the same authority. Actors with differing origins are
considered potentially hostile versus each other, and are isolated from
each other to varying degrees.
For example, if Example Bank’s Web site, hosted at bank.example.com, tries
to examine the DOM of Example Charity’s Web site, hosted at
charity.example.org, a "SecurityError" DOMException will be raised.
----------------------------------------------------------------------
An origin is one of the following:
An opaque origin
An internal value, with no serialisation, for which the only
meaningful operation is testing for equality.
A tuple origin
A tuple consists of:
* A scheme (a scheme).
* A host (a host).
* A port (a port).
* A domain (null or a domain). Null unless stated otherwise.
Origins can be shared, e.g., among multiple Document objects. Furthermore,
origins are generally immutable. Only the domain of a tuple origin can be
changed, and only through the document.domain API.
The effective domain of an origin origin is computed as follows:
1. If origin is an opaque origin, then return origin.
2. If origin’s domain is non-null, then return origin’s domain.
3. Return origin’s host.
Various specification objects are defined to have an origin. These origins
are determined as follows:
For Document objects
If the Document's active sandboxing flag set has its
sandboxed origin browsing context flag set
If the Document was generated from a data: URL
A unique opaque origin is assigned when the Document
is created.
If the Document's URL's scheme is a network scheme
A copy of the Document's URL's origin assigned when
the Document is created.
The document.open() method can change the Document's
URL to "about:blank". Therefore the origin is
assigned when the Document is created.
If the Document is the initial "about:blank" document
The one it was assigned when its browsing context was
created.
If the Document is a non-initial "about:blank" document
The origin of the incumbent settings object when the
navigate algorithm was invoked, or, if no script was
involved, of the node document of the element that
initiated the navigation to that URL.
If the Document was created as part of the processing for
javascript: URLs
The origin of the active document of the browsing
context being navigated when the navigate algorithm
was invoked.
If the Document is an iframe srcdoc document
The origin of the Document's browsing context’s
browsing context container’s node document.
If the Document was obtained in some other manner (e.g., a
Document created using the createDocument() API, etc)
The default behavior as defined in the DOM
specification applies. [DOM41].
The origin is a unique opaque origin assigned when
the Document is created.
For images of img elements
If the image data is CORS-cross-origin
A unique opaque origin assigned when the image is
created.
If the image data is CORS-same-origin
The img element’s node document’s origin.
For audio and video elements
If the media data is CORS-cross-origin
A unique opaque origin assigned when the media data
is fetched.
If the media data is CORS-same-origin
The media element’s node document’s origin.
For fonts
For a downloadable Web font it is a copy of the origin of the URL
record used to obtain the font (after any redirects).
[CSS-FONTS-3] [CSS-FONT-LOADING-3]
For a locally installed system font it is the origin of the
Document in which that font is being used.
Other specifications can override the above definitions by themselves
specifying the origin of a particular Document object, image, media
element, or font.
----------------------------------------------------------------------
The Unicode serialization of an origin is the string obtained by applying
the following algorithm to the given origin origin:
1. If origin is an opaque origin, then return "null".
2. Let host be origin’s host.
3. Let unicodeHost be host if host is not a domain, and the result of
applying domain to Unicode to host otherwise.
4. Let unicodeOrigin be a new tuple origin consisting origin’s scheme,
unicodeHost, and origin’s port.
5. Return the ASCII serialization of an origin, given unicodeOrigin.
The name ASCII serialization of an origin is misleading, as it merely
serialises an origin, which are all ASCII by default due to the URL
parser.
The Unicode serialization of ("https", "xn--maraa-rta.example", null,
null) is "https://maraña.example".
The ASCII serialization of an origin is the string obtained by applying
the following algorithm to the given origin origin:
1. If origin is an opaque origin, then return "null".
2. Otherwise, let result be origin’s scheme.
3. Append "://" to result.
4. Append origin’s host, serialized, to result.
5. If origin’s port is non-null, append a U+003A COLON character (:), and
origin’s port, serialized, to result.
6. Return result.
Two origins A and B are said to be same origin if the following algorithm
returns true:
1. If A and B are the same opaque origin, then return true.
2. If A and B are both tuple origins, and their schemes, hosts, and ports
are identical, then return true.
3. Return false.
Two origins A and B are said to be same origin-domain if the following
algorithm returns true:
1. If A and B are the same opaque origin, then return true.
2. If A and B are both tuple origins, run these substeps:
1. If A and B’s schemes are identical, and their domains are
identical and non-null, then return true.
2. Otherwise, if A and B are same origin and their domains are
identical and null, then return true.
3. Return false.
The following table shows how A and B are related:
A B same same
origin origin-domain
("https", "example.org", null, ("https",
null) "example.org", null, ✅ ✅
null)
("https", "example.org", 314, ("https",
"example.org") "example.org", 420, ❌ ✅
"example.org")
("https", "example.org", null, ("https",
null) "example.org", null, ✅ ❌
"example.org")
("https", "example.org", null, ("http",
"example.org") "example.org", null, ❌ ❌
"example.org")
6.4.1. Relaxing the same-origin restriction
document . domain [ = domain ]
Returns the current domain used for security checks.
Can be set to a value that removes subdomains, to change the
origin's domain to allow pages on other subdomains of the same
domain (if they do the same thing) to access each other. (Can’t be
set in sandboxed iframes.)
The domain attribute’s getter must run these steps:
1. If this Document object does not have a browsing context, then return
the empty string.
2. Let effectiveDomain be this Document's origin's effective domain.
3. If effectiveDomain is an opaque origin, then return the empty string.
4. Return effectiveDomain, serialised.
The domain attribute on setting must run these steps:
1. If this Document object has no browsing context, throw a
"SecurityError" DOMException.
2. If this Document object’s active sandboxing flag set has its sandboxed
document.domain browsing context flag set, then throw a
"SecurityError" DOMException.
3. If the given value is the empty string, then throw a "SecurityError"
DOMException.
4. Let host be the result of parsing the given value.
5. If host is failure, then throw a "SecurityError" DOMException.
6. Let effectiveDomain be this Document object’s origin's effective
domain.
7. If host is not equal to effectiveDomain, then run these substeps:
1. If host or effectiveDomain is not a domain, then throw a
"SecurityError" DOMException.
This is meant to exclude hosts that are an IPv4 address or an
IPv6 address.
2. If host, prefixed by a U+002E FULL STOP (.), does not exactly
match the end of effectiveDomain, then throw a "SecurityError"
DOMException.
3. If host matches a suffix in the Public Suffix List, or, if host,
prefixed by a U+002E FULL STOP (.), matches the end of a suffix
in the Public Suffix List, then throw a "SecurityError"
DOMException. [PSL]
Suffixes must be compared after applying the host parser
algorithm. [URL]
8. Set origin’s domain to host.
The document.domain attribute is used to enable pages on different hosts
of a domain to access each others' DOMs.
Do not use the document.domain attribute when using shared hosting. If an
untrusted third party is able to host an HTTP server at the same IP
address but on a different port, then the same-origin protection that
normally protects two different sites on the same host will fail, as the
ports are ignored when comparing origins after the document.domain
attribute has been used.
6.5. Sandboxing
A sandboxing flag set is a set of zero or more of the following flags,
which are used to restrict the abilities that potentially untrusted
resources have:
The sandboxed navigation browsing context flag
This flag prevents content from navigating browsing contexts other
than the sandboxed browsing context itself (or browsing contexts
further nested inside it), auxiliary browsing contexts (which are
protected by the sandboxed auxiliary navigation browsing context
flag defined next), and the top-level browsing context (which is
protected by the sandboxed top-level navigation browsing context
flag defined below).
If the sandboxed auxiliary navigation browsing context flag is not
set, then in certain cases the restrictions nonetheless allow
popups (new top-level browsing contexts) to be opened. These
browsing contexts always have one permitted sandboxed navigator,
set when the browsing context is created, which allows the
browsing context that created them to actually navigate them.
(Otherwise, the sandboxed navigation browsing context flag would
prevent them from being navigated even if they were opened.)
The sandboxed auxiliary navigation browsing context flag
This flag prevents content from creating new auxiliary browsing
contexts, e.g., using the target attribute, the window.open()
method.
The sandboxed top-level navigation browsing context flag
This flag prevents content from navigating their top-level
browsing context and prevents content from closing their top-level
browsing context.
When the sandboxed top-level navigation browsing context flag is
not set, content can navigate its top-level browsing context, but
other browsing contexts are still protected by the sandboxed
navigation browsing context flag and possibly the sandboxed
auxiliary navigation browsing context flag.
The sandboxed plugins browsing context flag
This flag prevents content from instantiating plugins, whether
using the embed element, the object element, the applet element,
or through navigation of a nested browsing context, unless those
plugins can be secured.
The sandboxed origin browsing context flag
This flag forces content into a unique origin, thus preventing it
from accessing other content from the same origin.
This flag also prevents script from reading from or writing to the
document.cookie IDL attribute, and blocks access to localStorage.
[WEBSTORAGE]
The sandboxed forms browsing context flag
This flag blocks form submission.
The sandboxed pointer lock browsing context flag
This flag disables the Pointer Lock API. [POINTERLOCK]
The sandboxed scripts browsing context flag
This flag blocks script execution.
The sandboxed automatic features browsing context flag
This flag blocks features that trigger automatically, such as
automatically playing a video or automatically focusing a form
control.
The sandboxed storage area URLs flag
This flag prevents URL schemes that use storage areas from being
able to access the origin’s data.
The sandboxed fullscreen browsing context flag
This flag prevents content from using the requestFullscreen()
method.
The sandboxed document.domain browsing context flag
This flag prevents content from using the document.domain setter.
The sandbox propagates to auxiliary browsing contexts flag
This flag prevents content from escaping the sandbox by ensuring
that any auxiliary browsing context it creates inherits the
content’s active sandboxing flag set.
The sandboxed modals flag
This flag prevents content from using any of the following
features to produce modal dialogs:
* window.alert()
* window.confirm()
* window.print()
* window.prompt()
* the beforeunload event
The sandboxed presentation browsing context flag
This flag disables the Presentation API. [PRESENTATION-API]
When the user agent is to parse a sandboxing directive, given a string
input, a sandboxing flag set output, and optionally an allow fullscreen
flag, it must run the following steps:
1. Split input on spaces, to obtain tokens.
2. Let output be empty.
3. Add the following flags to output:
* The sandboxed navigation browsing context flag.
* The sandboxed auxiliary navigation browsing context flag, unless
tokens contains the allow-popups keyword.
* The sandboxed top-level navigation browsing context flag, unless
tokens contains the allow-top-navigation keyword.
* The sandboxed plugins browsing context flag.
* The sandboxed origin browsing context flag, unless the tokens
contains the allow-same-origin keyword.
The allow-same-origin keyword is intended for two cases.
First, it can be used to allow content from the same site to be
sandboxed to disable scripting, while still allowing access to
the DOM of the sandboxed content.
Second, it can be used to embed content from a third-party site,
sandboxed to prevent that site from opening pop-up windows, etc,
without preventing the embedded page from communicating back to
its originating site, using the database APIs to store data, etc.
* The sandboxed forms browsing context flag, unless tokens contains
the allow-forms keyword.
* The sandboxed pointer lock browsing context flag, unless tokens
contains the allow-pointer-lock keyword.
* The sandboxed scripts browsing context flag, unless tokens
contains the allow-scripts keyword.
* The sandboxed automatic features browsing context flag, unless
tokens contains the allow-scripts keyword (defined above).
This flag is relaxed by the same keyword as scripts, because when
scripts are enabled these features are trivially possible anyway,
and it would be unfortunate to force authors to use script to do
them when sandboxed rather than allowing them to use the
declarative features.
* The sandboxed storage area URLs flag.
* The sandboxed fullscreen browsing context flag, unless the allow
fullscreen flag was passed to the parse a sandboxing directive
flag.
* The sandboxed document.domain browsing context flag.
* The sandbox propagates to auxiliary browsing contexts flag,
unless tokens contains the allow-popups-to-escape-sandbox
keyword.
* The sandboxed modals flag, unless tokens contains the
allow-modals keyword.
* The sandboxed presentation browsing context flag, unless tokens
contains the allow-presentation keyword.
There is only one known native implementation of the
allow-presentation token (Chrome/Blink). Therefore this feature
should not be relied upon until it becomes interoperable.
----------------------------------------------------------------------
Every top-level browsing context has a popup sandboxing flag set, which is
a sandboxing flag set. When a browsing context is created, its popup
sandboxing flag set must be empty. It is populated by the rules for
choosing a browsing context given a browsing context name.
Every nested browsing context has an iframe sandboxing flag set, which is
a sandboxing flag set. Which flags in a nested browsing context’s iframe
sandboxing flag set are set at any particular time is determined by the
iframe element’s sandbox attribute.
Every Document has an active sandboxing flag set, which is a sandboxing
flag set. When the Document is created, its active sandboxing flag set
must be empty. It is populated by the navigation algorithm.
Every resource that is obtained by the navigation algorithm has a forced
sandboxing flag set, which is a sandboxing flag set. A resource by default
has no flags set in its forced sandboxing flag set, but other
specifications can define that certain flags are set.
In particular, the forced sandboxing flag set is used by the Content
Security Policy specification. [CSP3]
----------------------------------------------------------------------
When a user agent is to implement the sandboxing for a Document, it must
populate Document's active sandboxing flag set with the union of the flags
that are present in the following sandboxing flag sets at the time the
Document object is created:
* If the Document's browsing context is a top-level browsing context,
then: the flags set on the browsing context’s popup sandboxing flag
set.
* If the Document's browsing context is a nested browsing context, then:
the flags set on the browsing context’s iframe sandboxing flag set.
* If the Document's browsing context is a nested browsing context, then:
the flags set on the browsing context’s parent browsing context’s
active document’s active sandboxing flag set.
* The flags set on the Document's resource’s forced sandboxing flag set,
if it has one.
6.6. Session history and navigation
6.6.1. The session history of browsing contexts
The sequence of Documents in a browsing context is its session history.
Each browsing context, including nested browsing contexts, has a distinct
session history. A browsing context’s session history consists of a flat
list of session history entries. Each session history entry consists, at a
minimum, of a URL, and each entry may in addition have a serialized state,
a title, a Document object, form data, a scroll restoration mode, a scroll
position, and other information associated with it.
Each entry, when first created, has a Document. However, when a Document
is not active, it’s possible for it to be discarded to free resources. The
URL and other data in a session history entry is then used to bring a new
Document into being to take the place of the original, should the user
agent find itself having to reactivate that Document.
Titles associated with session history entries need not have any relation
with the current title of the Document. The title of a session history
entry is intended to explain the state of the document at that point, so
that the user can navigate the document’s history.
URLs without associated serialized state are added to the session history
as the user (or script) navigates from page to page.
----------------------------------------------------------------------
Each Document object in a browsing context’s session history is associated
with a unique History object which must all model the same underlying
session history.
The history attribute of the Window interface must return the object
implementing the History interface for that Window object’s newest
Document.
----------------------------------------------------------------------
Serialized state is a serialization (via StructuredSerializeForStorage) of
an object representing a user interface state. We sometimes informally
refer to "state objects", which are the objects representing user
interface state supplied by the author, or alternately the objects created
by deserializing (via StructuredDeserialize) serialized state.
Pages can add serialized state to the session history. These are then
deserialized and returned to the script when the user (or script) goes
back in the history, thus enabling authors to use the "navigation"
metaphor even in one-page applications.
Serialized state is intended to be used for two main purposes: first,
storing a preparsed description of the state in the URL so that in the
simple case an author doesn’t have to do the parsing (though one would
still need the parsing for handling URLs passed around by users, so it’s
only a minor optimization), and second, so that the author can store state
that one wouldn’t store in the URL because it only applies to the current
Document instance and it would have to be reconstructed if a new Document
were opened.
An example of the latter would be something like keeping track of the
precise coordinate from which a pop-up div was made to animate, so that if
the user goes back, it can be made to animate to the same location. Or
alternatively, it could be used to keep a pointer into a cache of data
that would be fetched from the server based on the information in the URL,
so that when going back and forward, the information doesn’t have to be
fetched again.
----------------------------------------------------------------------
At any point, one of the entries in the session history is the current
entry. This is the entry representing the active document of the browsing
context. Which entry is the current entry is changed by the algorithms
defined in this specification, e.g., during session history traversal.
The current entry is usually an entry for the URL of the Document.
However, it can also be one of the entries for serialized state added to
the history by that document.
An entry with persisted user state is one that also has user-agent defined
state. This specification does not specify what kind of state can be
stored.
For example, some user agents might want to persist the scroll position,
or the values of form controls.
User agents that persist the value of form controls are encouraged to also
persist their directionality (the value of the element’s dir attribute).
This prevents values from being displayed incorrectly after a history
traversal when the user had originally entered the values with an
explicit, non-default directionality.
An entry’s scroll restoration mode indicates whether the user agent should
restore the persisted scroll position (if any) when traversing to it. The
scroll restoration mode may be one of the following:
"auto"
The user agent is responsible for restoring the scroll position
upon navigation.
"manual"
The page is responsible for restoring the scroll position and the
user agent does not attempt to do so automatically
If unspecified, the scroll restoration mode of a new entry must be set to
"auto".
Entries that consist of serialized state share the same Document as the
entry for the page that was active when they were added.
Contiguous entries that differ just by fragment also share the same
Document.
All entries that share the same Document (and that are therefore merely
different states of one particular document) are contiguous by definition.
Each Document in a browsing context can also have a latest entry. This is
the entry for that Document to which the browsing context’s session
history was most recently traversed. When a Document is created, it
initially has no latest entry.
User agents may discard the Document objects of entries other than the
current entry that are not referenced from any script, reloading the pages
afresh when the user or script navigates back to such pages. This
specification does not specify when user agents should discard Document
objects and when they should cache them.
Entries that have had their Document objects discarded must, for the
purposes of the algorithms given below, act as if they had not. When the
user or script navigates back or forwards to a page which has no in-memory
DOM objects, any other entries that shared the same Document object with
it must share the new object as well.
6.6.2. The History interface
enum ScrollRestoration { "auto", "manual" };
interface History {
readonly attribute unsigned long length;
attribute ScrollRestoration scrollRestoration;
readonly attribute any state;
void go(optional long delta = 0);
void back();
void forward();
void pushState(any data, DOMString title, optional DOMString? url = null);
void replaceState(any data, DOMString title, optional DOMString? url = null);
};
window . history . length
Returns the number of entries in the joint session history.
window . history . scrollRestoration [ = value ]
Returns the scroll restoration mode of the current entry in the
session history.
Can be set, to change the scroll restoration mode of the current
entry in the session history.
window . history . state
Returns the current serialized state, deserialized into an object.
window . history . go( [ delta ] )
Goes back or forward the specified number of steps in the joint
session history.
A zero delta will reload the current page.
If the delta is out of range, does nothing.
window . history . back()
Goes back one step in the joint session history.
If there is no previous page, does nothing.
window . history . forward()
Goes forward one step in the joint session history.
If there is no next page, does nothing.
window . history . pushState(data, title [, url ] )
Pushes the given data onto the session history, with the given
title, and, if provided and not null, the given URL.
window . history . replaceState(data, title [, url ] )
Updates the current entry in the session history to have the given
data, title, and, if provided and not null, URL.
The joint session history of a top-level browsing context is the union of
all the session histories of all browsing contexts of all the fully active
Document objects that share that top-level browsing context, with all the
entries that are current entries in their respective session histories
removed except for the current entry of the joint session history.
The current entry of the joint session history is the entry that most
recently became a current entry in its session history.
Entries in the joint session history are ordered chronologically by the
time they were added to their respective session histories. Each entry has
an index; the earliest entry has index 0, and the subsequent entries are
numbered with consecutively increasing integers (1, 2, 3, etc).
Since each Document in a browsing context might have a different event
loop, the actual state of the joint session history can be somewhat
nebulous. For example, two sibling iframe elements could both traverse
from one unique origin to another at the same time, so their precise order
might not be well-defined; similarly, since they might only find out about
each other later, they might disagree about the length of the joint
session history.
The length attribute of the History interface, on getting, must return the
number of entries in the top-level browsing context’s joint session
history. If this History object is associated with a Document that is not
fully active, getting must instead throw a "SecurityError" DOMException.
The actual entries are not accessible from script.
The scrollRestoration attribute of the History interface, on getting, must
return the scroll restoration mode of the current entry in the session
history. On setting, the scroll restoration mode of the current entry in
the session history must be set to the new value. If this History object
is associated with a Document that is not fully active, both getting and
setting must instead throw a "SecurityError" DOMException.
The state attribute of the History interface, on getting, must return the
last value it was set to by the user agent. If this History object is
associated with a Document that is not fully active, getting must instead
throw a SecurityError DOMException. Initially, its value must be null.
When the go(delta) method is invoked, if delta is zero, the user agent
must act as if the location.reload() method was called instead. Otherwise,
the user agent must traverse the history by a delta whose value is delta
If this History object is associated with a Document that is not fully
active, invoking must instead throw a "SecurityError" DOMException.
When the back() method is invoked, the user agent must traverse the
history by a delta −1. If this History object is associated with a
Document that is not fully active, invoking must instead throw a
"SecurityError" DOMException.
When the forward()method is invoked, the user agent must traverse the
history by a delta +1. If this History object is associated with a
Document that is not fully active, invoking must instead throw a
"SecurityError" DOMException.
----------------------------------------------------------------------
Each top-level browsing context has a session history traversal queue,
initially empty, to which tasks can be added.
Each top-level browsing context, when created, must begin running the
following algorithm, known as the session history event loop for that
top-level browsing context, in parallel:
1. Wait until this top-level browsing context’s session history traversal
queue is not empty.
2. Pull the first task from this top-level browsing context’s session
history traversal queue, and execute it.
3. Return to the first step of this algorithm.
The session history event loop helps coordinate cross-browsing-context
transitions of the joint session history: since each browsing context
might, at any particular time, have a different event loop (this can
happen if the user agent has more than one event loop per unit of related
browsing contexts), transitions would otherwise have to involve
cross-event-loop synchronization.
----------------------------------------------------------------------
To traverse the history by a delta delta, the user agent must append a
task to this top-level browsing context’s session history traversal queue,
the task consisting of running the following steps:
1. If the index of the current entry of the joint session history plus
delta is less than zero or greater than or equal to the number of
items in the joint session history, then abort these steps.
2. Let specified entry be the entry in the joint session history whose
index is the sum of delta and the index of the current entry of the
joint session history.
3. Let specified browsing context be the browsing context of the
specified entry.
4. If the specified browsing context’s active document’s unload a
document algorithm is currently running, abort these steps.
5. Queue a task that consists of running the following substeps. The
relevant event loop is that of the specified browsing context’s active
document. The task source for the queued task is the history traversal
task source.
1. If there is an ongoing attempt to navigate specified browsing
context that has not yet matured (i.e., it has not passed the
point of making its Document the active document), then cancel
that attempt to navigate the browsing context.
2. If the specified browsing context’s active document is not the
same Document as the Document of the specified entry, then run
these substeps:
1. Prompt to unload the active document of the specified
browsing context. If the user refused to allow the document
to be unloaded, then abort these steps.
2. Unload the active document of the specified browsing context
with the recycle parameter set to false.
3. Traverse the history of the specified browsing context to the
specified entry.
When the user navigates through a browsing context, e.g., using a
browser’s back and forward buttons, the user agent must traverse the
history by a delta equivalent to the action specified by the user.
----------------------------------------------------------------------
The pushState() method adds a state object entry to the history.
The replaceState() method updates the state object, title, and optionally
the URL of the current entry in the history.
When either of these methods is invoked, the user agent must run the
following steps:
1. If this History object is associated with a Document that is not fully
active, throw a "SecurityError" DOMException.
2. Optionally, abort these steps. (For example, the user agent might
disallow calls to these methods that are invoked on a timer, or from
event listeners that are not triggered in response to a clear user
action, or that are invoked in rapid succession.)
3. Let targetRealm be this History object’s relevant settings object’s
Realm.
4. Let serializedData be a StructuredSerialize(data), targetRealm).
Rethrow any exceptions.
5. If the third argument is not null, run these substeps:
1. Parse the value of the third argument, relative to the entry
settings object.
2. If that fails, throw a "SecurityError" DOMException and abort
these steps.
3. Let new URL be the resulting URL record.
4. Compare new URL to the document’s URL. If any component of these
two URL records differ other than the path, query, and fragment
components, then throw a "SecurityError" DOMException and abort
these steps.
5. If the origin of new URL is not the same as the origin of the
responsible document specified by the entry settings object, and
either the path or query components of the two URL records
compared in the previous step differ, throw a "SecurityError"
DOMException and abort these steps. (This prevents sandboxed
content from spoofing other pages on the same origin.)
6. If the third argument is null, then let new URL be the URL of the
current entry.
7. If the method invoked was the pushState() method:
1. Remove all the entries in the browsing context’s session history
after the current entry. If the current entry is the last entry
in the session history, then no entries are removed.
This doesn’t necessarily have to affect the user agent’s user
interface.
2. Remove any tasks queued by the history traversal task source that
are associated with any Document objects in the top-level
browsing context’s document family.
3. If appropriate, update the current entry to reflect any state
that the user agent wishes to persist. The entry is then said to
be an entry with persisted user state.
4. Add a session history entry entry to the session history, after
the current entry, with serializedData as the serialized state,
the given title as the title, new URL as the URL of the entry,
and the scroll restoration mode of the current entry in the
session history as the scroll restoration mode.
5. Update the current entry to be this newly added entry.
Otherwise, if the method invoked was the replaceState() method:
1. Update the current entry in the session history so that
serializedData is the entry’s new serialized state, the given
title is the new title, and new URL is the entry’s new URL.
8. If the current entry in the session history represents a non-GET
request (e.g., it was the result of a POST submission) then update it
to instead represent a GET request.
9. Set the document’s URL to new URL.
Since this is neither a navigation of the browsing context nor a
history traversal, it does not cause a hashchange event to be fired.
10. Let targetRealm be this History object’s relevant settings object’s
Realm.
11. Let state be StructuredDeserialize(serializedData, targetRealm). If
this throws an exception, ignore the exception and set state to null.
12. Set history.state to state.
13. Let the latest entry of the Document of the current entry be the
current entry.
The title is purely advisory. User agents might use the title in the user
interface.
User agents may limit the number of state objects added to the session
history per page. If a page hits the user agent-defined limit, user agents
must remove the entry immediately after the first entry for that Document
object in the session history after having added the new entry. (Thus the
state history acts as a FIFO buffer for eviction, but as a LIFO buffer for
navigation.)
Consider a game where the user can navigate along a line, such that the
user is always at some coordinate, and such that the user can bookmark the
page corresponding to a particular coordinate, to return to it later.
A static page implementing the x=5 position in such a game could look like
the following:
Line Game - 5
You are at coordinate 5 on the line.
Advance to 6 or
retreat to 4 ?
The problem with such a system is that each time the user clicks, the
whole page has to be reloaded. Here instead is another way of doing it,
using script:
Line Game - 5
You are at coordinate 5 on the line.
Advance to 6 or
retreat to 4 ?
In systems without script, this still works like the previous example.
However, users that do have script support can now navigate much faster,
since there is no network access for the same experience. Furthermore,
contrary to the experience the user would have with just a naïve
script-based approach, bookmarking and navigating the session history
still work.
In the example above, the data argument to the pushState() method is the
same information as would be sent to the server, but in a more convenient
form, so that the script doesn’t have to parse the URL each time the user
navigates.
Applications might not use the same title for a session history entry as
the value of the document’s title element at that time. For example, here
is a simple page that shows a block in the title element. Clearly, when
navigating backwards to a previous state the user does not go back in
time, and therefore it would be inappropriate to put the time in the
session history title.
Line
Most applications want to use the same scroll restoration mode value for
all of their history entries. To achieve this they should set the
scrollRestoration attribute as soon as possible (e.g., in the first script
element in the document’s head element) to ensure that any entry added to
the history session gets the desired scroll restoration mode.
6.6.3. Implementation notes for session history
This section is non-normative.
The History interface is not meant to place restrictions on how
implementations represent the session history to the user.
For example, session history could be implemented in a tree-like manner,
with each page having multiple "forward" pages. This specification doesn’t
define how the linear list of pages in the history object are derived from
the actual session history as seen from the user’s perspective.
Similarly, a page containing two iframes has a history object distinct
from the iframes' history objects, despite the fact that typical Web
browsers present the user with just one "Back" button, with a session
history that interleaves the navigation of the two inner frames and the
outer page.
Security: It is suggested that to avoid letting a page "hijack" the
history navigation facilities of a UA by abusing pushState(), the UA
provide the user with a way to jump back to the previous page (rather than
just going back to the previous state). For example, the back button could
have a drop down showing just the pages in the session history, and not
showing any of the states. Similarly, an aural browser could have two
"back" commands, one that goes back to the previous state, and one that
jumps straight back to the previous page.
For both pushState() and replaceState(), user agents are encouraged to
prevent abuse of these APIs via too-frequent calls or over-large state
objects. As detailed above, the algorithm explicitly allows user agents to
ignore any such calls when appropriate.
6.6.4. The Location interface
Each Window object is associated with a unique instance of a Location
object, allocated when the Window object is created.
To create a Location object, run these steps:
1. Let location be a new Location platform object.
2. Perform ! location.[[DefineOwnProperty]]("toString", { [[Value]]:
%ObjProto_toString%, [[Writable]]: false, [[Enumerable]]: false,
[[Configurable]]: false }).
3. Perform ! location.[[DefineOwnProperty]]("toJSON", { [[Value]]:
undefined, [[Writable]]: false, [[Enumerable]]: false,
[[Configurable]]: false }).
4. Perform ! location.[[DefineOwnProperty]]("valueOf", { [[Value]]:
%ObjProto_valueOf%, [[Writable]]: false, [[Enumerable]]: false,
[[Configurable]]: false }).
5. Perform ! location.[[DefineOwnProperty]](@@toPrimitive, { [[Value]]:
undefined, [[Writable]]: false, [[Enumerable]]: false,
[[Configurable]]: false }).
6. Set the value of the [[DefaultProperties]] internal slot of location
to location.[[OwnPropertyKeys]]().
7. Return location.
document . location [ = value ]
window . location [ = value ]
Returns a Location object with the current page’s location.
Can be set, to navigate to another page.
The location attribute of the Document interface must return the Location
object for that Document object’s global object, if it has a browsing
context, and null otherwise.
The location attribute of the Window interface must return the Location
object for that Window object.
Location objects provide a representation of the URL of the active
document of their Document's browsing context, and allow the current entry
of the browsing context’s session history to be changed, by adding or
replacing entries in the history object.
interface Location {
[Unforgeable] stringifier attribute USVString href;
[Unforgeable] readonly attribute USVString origin;
[Unforgeable] attribute USVString protocol;
[Unforgeable] attribute USVString host;
[Unforgeable] attribute USVString hostname;
[Unforgeable] attribute USVString port;
[Unforgeable] attribute USVString pathname;
[Unforgeable] attribute USVString search;
[Unforgeable] attribute USVString hash;
[Unforgeable] void assign(USVString url);
[Unforgeable] void replace(USVString url);
[Unforgeable] void reload();
[Unforgeable, SameObject] readonly attribute USVString[] ancestorOrigins;
};
location . toString()
location . href
Returns the Location object’s URL.
Can be set, to navigate to the given URL.
location . origin
Returns the Location object’s URL’s origin.
location . protocol
Returns the Location object’s URL’s scheme.
Can be set, to navigate to the same URL with a changed scheme.
location . host
Returns the Location object’s URL’s host and port (if different
from the default port for the scheme).
Can be set, to navigate to the same URL with a changed host and
port.
location . hostname
Returns the Location object’s URL’s host.
Can be set, to navigate to the same URL with a changed host.
location . port
Returns the Location object’s URL’s port.
Can be set, to navigate to the same URL with a changed port.
location . pathname
Returns the Location object’s URL’s path.
Can be set, to navigate to the same URL with a changed path.
location . search
Returns the Location object’s URL’s query (includes leading "?" if
non-empty).
Can be set, to navigate to the same URL with a changed query
(ignores leading "?").
location . hash
Returns the Location object’s URL’s fragment (includes leading "#"
if non-empty).
Can be set, to navigate to the same URL with a changed fragment
(ignores leading "#").
location . assign(url)
Navigates to the given URL.
location . replace(url)
Removes the current page from the session history and navigates to
the given URL.
location . reload()
Reloads the current page.
location . ancestorOrigins
Returns an array whose values are the origins of the ancestor
browsing contexts, from the parent browsing context to the
top-level browsing context.
A Location object has an associated relevant Document, which is this
Location object’s associated Document object’s browsing context’s active
document.
A Location object has an associated url, which is this Location object’s
relevant Document’s URL.
A Location object has an associated ancestor origins array. When a
Location object is created, its ancestor origins array must be set to a
array created from the list of strings that the following steps would
produce:
1. Let output be an empty ordered list of strings.
2. Let current be the browsing context of the Document with which the
Location object is associated.
3. Loop: If current has no parent browsing context, jump to the step
labeled End.
4. Let current be current’s parent browsing context.
5. Append the Unicode serialization of current’s active document’s origin
to output as a new value.
6. Return to the step labeled Loop.
7. End: Return output.
A Location object has an associated Location-object-setter navigate
algorithm, which given a url, runs these steps:
1. If any of the following conditions are met, let replacement flag be
unset; otherwise, let it be set:
* This Location object’s relevant Document has completely loaded,
or
* In the task in which the algorithm is running, an activation
behavior is currently being processed whose click event was
trusted, or
* In the task in which the algorithm is running, the event listener
for a trusted click event is being handled.
2. Location-object navigate, given url and replacement flag.
To Location-object navigate, given a url and replacement flag, run these
steps:
1. The source browsing context is the responsible browsing context
specified by the incumbent settings object.
2. Navigate the browsing context to url, with the exceptions enabled flag
set. Rethrow any exceptions.
If the replacement flag is set or the browsing context’s session
history contains only one Document, and that was the about:blank
Document created when the browsing context was created, then the
navigation must be done with replacement enabled.
The href attribute’s getter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Return this Location object’s URL, serialized.
The href attribute’s setter must run these steps:
1. Parse the given value relative to the entry settings object. If that
failed, throw a TypeError exception.
2. Location-object-setter navigate to the resulting URL record.
The href attribute setter intentionally has no security check.
The origin attribute’s getter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Return the Unicode serialization of this Location object’s URL's
origin.
It returns the Unicode rather than the ASCII serialization for
compatibility with MessageEvent.
The protocol attribute’s getter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Return this Location object’s URL's scheme, followed by ":".
The protocol attribute’s setter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Let copyURL be a copy of this Location object’s URL.
3. Let possibleFailure be the result of basic URL parsing the given
value, followed by ":", with copyURL as url and scheme start state as
state override.
4. If possibleFailure is failure, throw a TypeError exception.
5. If copyURL’s scheme is not "http" or "https", terminate these steps.
6. Location-object-setter navigate to copyURL.
The host attribute’s getter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Let url be this Location object’s URL.
3. If url’s host is null, return the empty string.
4. If url’s port is null, return url’s host, serialized.
5. Return url’s host, serialized, followed by ":" and url’s port,
serialized.
The host attribute’s setter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Let copyURL be a copy of this Location object’s URL.
3. If copyURL’s non-relative flag is set, terminate these steps.
4. Basic URL parse the given value, with copyURL as url and host state as
state override.
5. Location-object-setter navigate to copyURL.
The hostname attribute’s getter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. If this Location object’s URL's host is null, return the empty string.
3. Return this Location object’s URL's host, serialized.
The hostname attribute’s setter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Let copyURL be a copy of this Location object’s URL.
3. If copyURL’s non-relative flag is set, terminate these steps.
4. Basic URL parse the given value, with copyURL as url and hostname
state as state override.
5. Location-object-setter navigate to copyURL.
The port attribute’s getter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. If this Location object’s URL's port is null, return the empty string.
3. Return this Location object’s URL's port, serialized.
The port attribute’s setter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Let copyURL be a copy of this Location object’s URL.
3. If copyURL’s host is null, copyURL’s non-relative flag is set, or
copyURL’s scheme is "file", terminate these steps.
4. Basic URL parse the given value, with copyURL as url and port state as
state override.
5. Location-object-setter navigate to copyURL.
The pathname attribute’s getter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Let url be this Location object’s URL.
3. If url’s non-relative flag is set, return the first string in url’s
path.
4. Return "/", followed by the strings in url’s path (including empty
strings), separated from each other by "/".
The pathname attribute’s setter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Let copyURL be a copy of this Location object’s URL.
3. If copyURL’s non-relative flag is set, terminate these steps.
4. Set copyURL’s path to the empty list.
5. Basic URL parse the given value, with copyURL as url and path start
state as state override.
6. Location-object-setter navigate to copyURL.
The search attribute’s getter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. If this Location object’s URL's query is either null or the empty
string, return the empty string.
3. Return "?", followed by this Location object’s URL's query.
The search attribute’s setter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Let copyURL be a copy of this Location object’s URL.
3. If the given value is the empty string, set copyURL’s query to null.
4. Otherwise, run these substeps:
1. Let input be the given value with a single leading "?" removed,
if any.
2. Set copyURL’s query to the empty string.
3. Basic URL parse input, with copyURL as url and query state as
state override, and the relevant Document’s document’s character
encoding as encoding override.
5. Location-object-setter navigate to copyURL.
The hash attribute’s getter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. If this Location object’s URL's fragment is either null or the empty
string, return the empty string.
3. Return "#", followed by this Location object’s URL's fragment.
The hash attribute’s setter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Let copyURL be a copy of this Location object’s URL.
3. If copyURL’s scheme is "javascript", terminate these steps.
4. Let input be the given value with a single leading "#" removed, if
any.
5. Set copyURL’s fragment to the empty string.
6. Basic URL parse input, with copyURL as url and fragment state as state
override.
7. Location-object-setter navigate to copyURL.
Unlike the equivalent API for the a and area elements, the hash
attribute’s setter does not special case the empty string to remain
compatible with deployed scripts.
----------------------------------------------------------------------
When the assign(url) method is invoked, the user agent must run the
following steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Parse url, relative to the entry settings object. If that failed,
throw a "SyntaxError" DOMException.
3. Location-object navigate to the resulting URL record.
When the replace(url) method is invoked, the user agent must run the
following steps:
1. Parse url, relative to the entry settings object. If that failed,
throw a "SyntaxError" DOMException.
2. Location-object navigate to the resulting URL record with the
replacement flag set.
The replace() method intentionally has no security check.
When the reload() method is invoked, the user agent must run the
appropriate steps from the following list:
If this Location object’s relevant Document’s origin is not same origin
with entry settings object’s origin
Throw a "SecurityError" DOMException.
If the currently executing task is the dispatch of a resize event in
response to the user resizing the browsing context
Repaint the browsing context and abort these steps.
If the browsing context’s active document is an iframe srcdoc document
Reprocess the iframe attributes of the browsing context’s browsing
context container.
If the browsing context’s active document has its reload override flag set
Perform an overridden reload, with the browsing context being
navigated as the responsible browsing context.
Otherwise
Navigate the browsing context to the document’s URL with the
exceptions enabled flag set and replacement enabled. The source
browsing context must be the browsing context being navigated.
This is a reload-triggered navigation. Rethrow any exceptions.
When a user requests that the active document of a browsing context be
reloaded through a user interface element, the user agent should navigate
the browsing context to the same resource as that Document, with
replacement enabled. In the case of non-idempotent methods (e.g., HTTP
POST), the user agent should prompt the user to confirm the operation
first, since otherwise transactions (e.g., purchases or database
modifications) could be repeated. User agents may allow the user to
explicitly override any caches when reloading. If browsing context’s
active document’s reload override flag is set, then the user agent may
instead perform an overridden reload rather than the navigation described
in this paragraph (with the browsing context being reloaded as the source
browsing context).
The ancestorOrigins attribute’s getter must run these steps:
1. If this Location object’s relevant Document’s origin is not same
origin-domain with the entry settings object’s origin, then throw a
"SecurityError" DOMException.
2. Otherwise, return this Location object’s ancestor origins array.
6.6.4.1. The Location internal methods
The Location object requires additional logic beyond IDL for security
purposes. The internal slot and internal methods Location objects must
implement are defined below.
Every Location object has a [[DefaultProperties]] internal slot
representing its own properties at time of its creation.
6.6.4.1.1. [[GetPrototypeOf]] ( )
1. If IsPlatformObjectSameOrigin(this) is true, then return !
OrdinaryGetPrototypeOf(this).
2. Return null.
6.6.4.1.2. [[SetPrototypeOf]] ( V )
1. Return false.
6.6.4.1.3. [[IsExtensible]] ( )
1. Return true.
6.6.4.1.4. [[PreventExtensions]] ( )
1. Return false.
6.6.4.1.5. [[GetOwnProperty]] ( P )
1. If IsPlatformObjectSameOrigin(this) is true, then:
1. Let desc be OrdinaryGetOwnProperty(this, P).
2. If the value of the [[DefaultProperties]] internal slot of this
contains P, then set desc.[[Configurable]] to true.
3. Return desc.
2. Let property be ! CrossOriginGetOwnPropertyHelper(this, P).
3. If property is not undefined, return property.
4. Throw a "SecurityError" DOMException.
6.6.4.1.6. [[DefineOwnProperty]] ( P, Desc )
1. If IsPlatformObjectSameOrigin(this) is true, then:
1. If the value of the [[DefaultProperties]] internal slot of this
contains P, then return false.
2. Return ? OrdinaryDefineOwnProperty(this, P, Desc).
2. Return false.
6.6.4.1.7. [[Get]] ( P, Receiver )
1. If IsPlatformObjectSameOrigin(this) is true, then return ?
OrdinaryGet(this, P, Receiver).
2. Return ? CrossOriginGet(this, P, Receiver).
6.6.4.1.8. [[Set]] ( P, V, Receiver )
1. If IsPlatformObjectSameOrigin(this) is true, then return ?
OrdinarySet(this, P, Receiver).
2. Return ? CrossOriginSet(this, P, V, Receiver).
6.6.4.1.9. [[Delete]] ( P )
1. If IsPlatformObjectSameOrigin(this) is true, then return ?
OrdinaryDelete(this, P).
2. Return false.
6.6.4.1.10. [[OwnPropertyKeys]] ( )
1. If IsPlatformObjectSameOrigin(this) is true, then return !
OrdinaryOwnPropertyKeys(this).
2. Return ! CrossOriginOwnPropertyKeys(this).
6.7. Browsing the Web
6.7.1. Navigating across documents
Certain actions cause the browsing context to navigate to a new resource.
A user agent may provide various ways for the user to explicitly cause a
browsing context to navigate, in addition to those defined in this
specification.
For example, following a hyperlink, §4.10.21 Form submission, and the
window.open() and location.assign() methods can all cause a browsing
context to navigate.
A resource has a URL, but that might not be the only information necessary
to identify it. For example, a form submission that uses HTTP POST would
also have the HTTP method and payload. Similarly, an iframe srcdoc
document needs to know the data it is to use.
Navigation always involves source browsing context, which is the browsing
context which was responsible for starting the navigation.
When a browsing context is navigated to a new resource, the user agent
must run the following steps:
1. If the source browsing context is not allowed to navigate the browsing
context being navigated, then abort these steps.
If these steps are aborted here, the user agent may instead offer to
open the new resource in a new top-level browsing context or in the
top-level browsing context of the source browsing context, at the
user’s option, in which case the user agent must navigate that
designated top-level browsing context to the new resource as if the
user had requested it independently.
Doing so, however, can be dangerous, as it means that the user is
overriding the author’s explicit request to sandbox the content.
If the navigate algorithm was invoked optionally with an exceptions
enabled flag, and it is aborted on this step, then in addition to
aborting this algorithm, the user agent must also throw a
"SecurityError" DOMException.
2. If there is a preexisting attempt to navigate the browsing context,
and the source browsing context is the same as the browsing context
being navigated, and that attempt is currently running the unload a
document algorithm, and the origin of the URL of the resource being
loaded in that navigation is not the same origin as the origin of the
URL of the resource being loaded in this navigation, then abort these
steps without affecting the preexisting attempt to navigate the
browsing context.
3. If a task queued by the traverse the history by a delta algorithm is
running the unload a document algorithm for the active document of the
browsing context being navigated, then abort these steps without
affecting the unload a document algorithm or the aforementioned
history traversal task.
4. If the prompt to unload a document algorithm is being run for the
active document of the browsing context being navigated, then abort
these steps without affecting the prompt to unload a document
algorithm.
5. Let gone async be false.
The handle redirects step later in this algorithm can in certain cases
jump back to the step labeled Fragments. Since, between those two
steps, this algorithm goes from operating immediately in the context
of the calling task to operating in parallel independent of the event
loop, some of the intervening steps need to be able to handle both
being run as part of a task and running in parallel. The gone async
flag is thus used to make these steps aware of which mode they are
operating in.
6. Fragments: If this is not a reload-triggered navigation: apply the URL
parser algorithm to the absolute URL of the new resource and the URL
of the active document of the browsing context being navigated; if all
the components of the resulting parsed URLs, ignoring any fragment
components, are identical, and the new resource is to be fetched using
GET, and the URL record of the new resource has a fragment component
that is not null (even if it is empty), then navigate to that fragment
and abort these steps.
7. If gone async is false, cancel any preexisting but not yet mature
attempt to navigate the browsing context, including canceling any
instances of the fetch algorithm started by those attempts. If one of
those attempts has already created and initialized a new Document
object, abort that Document also. (Navigation attempts that have
matured already have session history entries, and are therefore
handled during the update the session history with the new page
algorithm, later.)
8. If the new resource is to be handled using a mechanism that does not
affect the browsing context, e.g., ignoring the navigation request
altogether because the specified scheme is not one of the supported
protocols, then abort these steps and proceed with that mechanism
instead.
9. If gone async is false, prompt to unload the Document object. If the
user refused to allow the document to be unloaded, then abort these
steps.
If this instance of the navigation algorithm gets canceled while this
step is running, the prompt to unload a document algorithm must
nonetheless be run to completion.
10. If gone async is false, abort the active document of the browsing
context.
11. If the new resource is to be handled by displaying some sort of inline
content, e.g., an error message because the specified scheme is not
one of the supported protocols, or an inline prompt to allow the user
to select a registered handler for the given scheme, then display the
inline content and abort these steps.
In the case of a registered handler being used, the algorithm will be
reinvoked with a new URL to handle the request.
12. If the browsing context being navigated is a nested browsing context,
then put it in the delaying load events mode.
The user agent must take this nested browsing context out of the
delaying load events mode when this navigation algorithm later
matures, or when it terminates (whether due to having run all the
steps, or being canceled, or being aborted), whichever happens first.
13. This is the step that attempts to obtain the resource, if necessary.
Jump to the first appropriate substep:
If the resource has already been obtained (e.g., because it is
being used to populate an object element’s new child browsing
context)
Skip this step. The data is already available.
If the new resource is a URL whose scheme is javascript
Queue a task to run these "javascript: URL" steps,
associated with the active document of the browsing
context being navigated:
1. If the origin of the source browsing context is not
the same origin as the origin of the active document
of the browsing context being navigated, then let
result be undefined, and jump to the step labeled
process results below.
2. Let urlRecord be the result of running the URL
parser on the URL of the new resource.
3. Let script source be the empty string.
4. Append the first string of urlRecord’s path
component to script source.
5. If urlRecord’s query component is not null, then
first append a U+003F QUESTION MARK character (?) to
script source, and then append urlRecord’s query
component to script source.
6. If urlRecord’s fragment component is not null, then
first append a U+0023 NUMBER SIGN character (#) to
script source, and then append urlRecord’s fragment
component to script source.
7. Replace script source with the result of applying
the percent decode algorithm to script source.
8. Replace script source with the result of applying
the UTF-8 decode algorithm to script source.
9. Let address be the URL of the active document of the
browsing context being navigated.
10. Let settings be the relevant settings object of the
browsing context being navigated.
11. Let script be the result of creating a classic
script given script source and settings.
12. Let result be the result of running the classic
script script. If evaluation was unsuccessful, let
result be undefined instead. (The result will also
be undefined if scripting is disabled.)
13. Process results: If Type(result) is not String, then
the result of obtaining the resource for the URL is
a response whose status is 204.
Otherwise, the result of obtaining the resource for
the URL is a response whose header list consists of
Content-Type/text/html and whose body is result, and
whose HTTPS state is settings’s HTTPS state.
When it comes time to set the document’s address in
the navigation algorithm, use address as the
override URL.
The task source for this task is the DOM manipulation
task source.
So for example a javascript: URL in an href attribute of
an a element would only be evaluated when the link was
followed, while such a URL in the src attribute of an
iframe element would be evaluated in the context of the
iframe’s own nested browsing context when the iframe is
being set up; once evaluated, its return value (if it was
not void) would replace that browsing context’s Document,
thus also changing the Window object of that browsing
context.
Otherwise
1. Let request be the new resource.
2. If request is a URL, set request to a new request
whose URL is request.
3. Set request’s client to the source browsing
context’s active document’s Window object’s
environment settings object, target browsing context
to the browsing context being navigated, destination
to "document", mode to "navigate", credentials mode
to "include", use-URL-credentials flag, and redirect
mode to "manual".
4. Set request’s omit-Origin-header flag.
5. If request’s method is not GET, or, if the
navigation algorithm was invoked as a result of the
form submission algorithm, then if there is an
origin of the active document of the source browsing
context, unset request’s omit-Origin-header flag.
6. Otherwise, if the browsing context being navigated
is a child browsing context, and the browsing
context container of the browsing context being
navigated has a browsing context scope origin, set
request’s origin to that browsing context scope
origin and unset request’s omit-Origin-header flag.
7. Fetch request.
14. If gone async is false, return to whatever algorithm invoked the
navigation steps and continue running these steps in parallel.
15. Let gone async be true.
16. Wait for one or more bytes to be available or for the user agent to
establish that the resource in question is empty. During this time,
the user agent may allow the user to cancel this navigation attempt or
start other navigation attempts.
17. Handle redirects: If fetching the resource results in a redirect, and
either the URL of the target of the redirect has the same origin as
the original resource, or the resource is being obtained using the
POST method or a safe method (in HTTP terms), return to the step
labeled Fragments with the new resource, except that if the URL of the
target of the redirect does not have a fragment and the URL of the
resource that led to the redirect does, then the fragment of the
resource that led to the redirect must be propagated to the URL of the
target of the redirect.
So for instance, if the original URL was
"https://example.com/#!sample" and "https://example.com/" is found to
redirect to "https://example.com/", the URL of the new resource will
be "https://example.com/#!sample".
Otherwise, if fetching the resource results in a redirect but the URL
of the target of the redirect does not have the same origin as the
original resource and the resource is being obtained using a method
that is neither the POST method nor a safe method (in HTTP terms),
then abort these steps. The user agent may indicate to the user that
the navigation has been aborted for security reasons.
18. Resource handling: If the resource’s out-of-band metadata (e.g., HTTP
headers), not counting any type information (such as the Content-Type
HTTP header), requires some sort of processing that will not affect
the browsing context, then perform that processing and abort these
steps.
Such processing might be triggered by, amongst other things, the
following:
* HTTP status codes (e.g., 204 No Content or 205 Reset Content)
* Network errors (e.g., the network interface being unavailable)
* Cryptographic protocol failures (e.g., an incorrect TLS
certificate)
Responses with HTTP Content-Disposition headers specifying the
attachment disposition type must be handled as a download.
HTTP 401 responses that do not include a challenge recognized by the
user agent must be processed as if they had no challenge, e.g.,
rendering the entity body as if the response had been 200 OK.
User agents may show the entity body of an HTTP 401 response even when
the response does include a recognized challenge, with the option to
login being included in a non-modal fashion, to enable the information
provided by the server to be used by the user before authenticating.
Similarly, user agents should allow the user to authenticate (in a
non-modal fashion) against authentication challenges included in other
responses such as HTTP 200 OK responses, effectively allowing
resources to present HTTP login forms without requiring their use.
19. Let type be the computed type of the resource.
20. If the user agent has been configured to process resources of the
given type using some mechanism other than rendering the content in a
browsing context, then skip this step. Otherwise, if the type is one
of the following types, jump to the appropriate entry in the following
list, and process the resource as described there:
an HTML MIME type
Follow the steps given in the HTML document section, and
then, once they have completed, abort this navigate
algorithm.
an XML MIME type that is not an explicitly supported XML type
Follow the steps given in the XML document section. If
that section determines that the content is not to be
displayed as a generic XML document, then proceed to the
next step in this overall set of steps. Otherwise, once
the steps given in the XML document section have
completed, abort this navigate algorithm.
a JavaScript MIME type
a JSON MIME type that is not an explicitly supported JSON type
"text/css"
"text/plain"
"text/vtt"
Follow the steps given in the plain text file section,
and then, once they have completed, abort this navigate
algorithm.
"multipart/x-mixed-replace"
Follow the steps given in the §12.2
multipart/x-mixed-replace section, and then, once they
have completed, abort this navigate algorithm.
A supported image, video, or audio type
Follow the steps given in the media section, and then,
once they have completed, abort this navigate algorithm.
A type that will use an external application to render the
content in the browsing context
Follow the steps given in the plugin section, and then,
once they have completed, abort this navigate algorithm.
An explicitly supported XML type is one for which the user agent is
configured to use an external application to render the content
(either a plugin rendering directly in the browsing context, or a
separate application), or one for which the user agent has dedicated
processing rules (e.g., a Web browser with a built-in Atom feed viewer
would be said to explicitly support the application/atom+xml MIME
type), or one for which the user agent has a dedicated handler (e.g.,
one registered using registerContentHandler()).
The term JSON MIME type is used to refer to the MIME types
application/json, text/json, and any MIME type whose subtype ends with
the five characters "+json".
An explicitly supported JSON type is one for which the user agent is
configured to use an external application to render the content
(either a plugin rendering directly in the browsing context, or a
separate application), or one for which the user agent has dedicated
processing rules, or one for which the user agent has a dedicated
handler (e.g., one registered using registerContentHandler()).
Setting the document’s address: If there is no override URL, then any
Document created by these steps must have its URL set to the URL that
was originally to be fetched, ignoring any other data that was used to
obtain the resource. However, if there is an override URL, then any
Document created by these steps must have its URL set to that URL
instead.
An override URL is set when dereferencing a javascript: URL and when
performing an overridden reload.
Initializing a new Document object: when a Document is created as part
of the above steps, the user agent will be required to additionally
run the following algorithm after creating the new object:
1. If browsingContext’s only entry in its session history is the
about:blank Document that was added when browsingContext was
created, and navigation is occurring with replacement enabled,
and that Document has the same origin as the new Document, then
1. Let window be the Window object of that Document.
2. Change the document attribute of window to point to the new
Document.
2. Otherwise,
1. Call the JavaScript InitializeHostDefinedRealm() abstract
operation with the following customizations:
* For the global object, create a new Window object
window.
* For the global this value, use browsingContext’s
WindowProxy object.
* Let realm execution context be the created JavaScript
execution context.
* Do not obtain any source texts for scripts or modules.
2. Set up a browsing context environment settings object with
realm execution context, and let settings object be the
result.
3. Set window’s associated Document to the new Document.
3. Set browsingContext’s WindowProxy object’s [[Window]] internal
slot value to window.
4. Set the Document's HTTPS state to the HTTPS state of the resource
used to generate the document.
5. Set the Document's referrer policy to the result of parsing the
Referrer-Policy header of the response used to generate the
document. [REFERRERPOLICY]
6. Execute the Initialize a Document’s CSP list algorithm on the
Document object and the resource used to generate the document.
[CSP3]
7. Set the document’s referrer to the address of the resource from
which Request-URIs are obtained as determined when the fetch
algorithm obtained the resource, if that algorithm was used and
determined such a value; otherwise, set it to the empty string.
8. Implement the sandboxing for the Document.
9. If the active sandboxing flag set of the Document's browsing
context or any of its ancestor browsing contexts (if any) have
the sandboxed fullscreen browsing context flag set, then skip
this step.
If the Document's browsing context has a browsing context
container and either it is not an iframe element, or it does not
have the allowfullscreen attribute specified, or its Document
does not have the fullscreen enabled flag set, then also skip
this step.
Otherwise, set the Document's fullscreen enabled flag.
10. Non-document content: If, given type, the new resource is to be
handled by displaying some sort of inline content, e.g., a native
rendering of the content, an error message because the specified
type is not supported, or an inline prompt to allow the user to
select a registered handler for the given type, then display the
inline content, and then abort these steps.
In the case of a registered handler being used, the algorithm
will be reinvoked with a new URL to handle the request.
11. Otherwise, the document’s type is such that the resource will not
affect the browsing context, e.g., because the resource is to be
handed to an external application or because it is an unknown
type that will be processed as a download. Process the resource
appropriately.
When a resource is handled by passing its URL or data to an external
software package separate from the user agent (e.g., handing a mailto: URL
to a mail client, or a Word document to a word processor), user agents
should attempt to mitigate the risk that this is an attempt to exploit the
target software, e.g., by prompting the user to confirm that the source
browsing context’s active document’s origin is to be allowed to invoke the
specified software. In particular, if the navigate algorithm, when it was
invoked, was not allowed to show a popup, the user agent should not invoke
the external software package without prior user confirmation.
For example, there could be a vulnerability in the target software’s URL
handler which a hostile page would attempt to exploit by tricking a user
into clicking a link.
----------------------------------------------------------------------
Some of the sections below, to which the above algorithm defers in certain
cases, require the user agent to update the session history with the new
page. When a user agent is required to do this, it must queue a task
(associated with the Document object of the current entry, not the new
one) to run the following steps:
1. Unload the Document object of the current entry, with the recycle
parameter set to false.
If this instance of the navigation algorithm is canceled while this
step is running the unload a document algorithm, then the unload a
document algorithm must be allowed to run to completion, but this
instance of the navigation algorithm must not run beyond this step.
(In particular, for instance, the cancelation of this algorithm does
not abort any event dispatch or script execution occurring as part of
unloading the document or its descendants.)
2. If the navigation was initiated for entry update of an entry
1. Replace the Document of the entry being updated, and
any other entries that referenced the same document
as that entry, with the new Document.
2. Traverse the history to the new entry.
This can only happen if the entry being updated is not
the current entry, and can never happen with replacement
enabled. (It happens when the user tried to traverse to a
session history entry that no longer had a Document
object.)
Otherwise
1. Remove all the entries in the browsing context’s
session history after the current entry. If the
current entry is the last entry in the session
history, then no entries are removed.
This doesn’t necessarily have to affect the user
agent’s user interface.
2. Append a new entry at the end of the History object
representing the new resource and its Document
object, related state, and the default scroll
restoration mode of "auto".
3. Traverse the history to the new entry. If the
navigation was initiated with replacement enabled,
then the traversal must itself be initiated with
replacement enabled.
3. The navigation algorithm has now matured.
4. fragment loop: Spin the event loop for a user-agent-defined amount of
time, as desired by the user agent implementor. (This is intended to
allow the user agent to optimize the user experience in the face of
performance concerns.)
5. If the Document object has no parser, or its parser has stopped
parsing, or the user agent has reason to believe the user is no longer
interested in scrolling to the fragment, then abort these steps.
6. Scroll to the fragment given in the document’s URL. If this fails to
find an indicated part of the document, then return to the fragment
loop step.
The task source for this task is the networking task source.
6.7.2. Page load processing model for HTML files
When an HTML document is to be loaded in a browsing context, the user
agent must queue a task to create a Document object, mark it as being an
HTML document, set its content type to "text/html", initialize the
Document object, and finally create an HTML parser and associate it with
the Document. Each task that the networking task source places on the task
queue while fetching runs must then fill the parser’s input byte stream
with the fetched bytes and cause the HTML parser to perform the
appropriate processing of the input stream.
The input byte stream converts bytes into characters for use in the
tokenizer. This process relies, in part, on character encoding information
found in the real Content-Type metadata of the resource; the "computed
type" is not used for this purpose.
When no more bytes are available, the user agent must queue a task for the
parser to process the implied EOF character, which eventually causes a
load event to be fired.
After creating the Document object, but before any script execution,
certainly before the parser stops, the user agent must update the session
history with the new page.
The task source for the two tasks mentioned in this section must be the
networking task source.
6.7.3. Page load processing model for XML files
When faced with displaying an XML file inline, user agents must follow the
requirements defined in the XML and Namespaces in XML recommendations, RFC
7303, DOM, and other relevant specifications to create a Document object
and a corresponding XML parser. [XML] [XML-NAMES] [RFC7303] [DOM41]
At the time of writing, the XML specification community had not actually
yet specified how XML and the DOM interact.
After the Document is created, the user agent must initialize the Document
object.
The actual HTTP headers and other metadata, not the headers as mutated or
implied by the algorithms given in this specification, are the ones that
must be used when determining the character encoding according to the
rules given in the above specifications. Once the character encoding is
established, the document’s character encoding must be set to that
character encoding.
User agents may examine the namespace of the root Element node of this
Document object to perform namespace-based dispatch to alternative
processing tools, e.g., determining that the content is actually a
syndication feed and passing it to a feed handler. If such processing is
to take place, abort the steps in this section, and jump to the next step
(labeled non-document content) in the navigate steps above.
Otherwise, then, with the newly created Document, the user agent must
update the session history with the new page. User agents may do this
before the complete document has been parsed (thus achieving incremental
rendering), and must do this before any scripts are to be executed.
Error messages from the parse process (e.g., XML namespace well-formedness
errors) may be reported inline by mutating the Document.
6.7.4. Page load processing model for text files
When a plain text document is to be loaded in a browsing context, the user
agent must queue a task to create a Document object, mark it as being an
HTML document, set its content type to the computed MIME type of the
resource (type in the navigate algorithm), initialize the Document object,
create an HTML parser, associate it with the Document, act as if the
tokenizer had emitted a start tag token with the tag name "pre" followed
by a single U+000A LINE FEED (LF) character, and switch the HTML parser’s
tokenizer to the §8.2.4.5 PLAINTEXT state. Each task that the networking
task source places on the task queue while fetching runs must then fill
the parser’s input byte stream with the fetched bytes and cause the HTML
parser to perform the appropriate processing of the input stream.
The rules for how to convert the bytes of the plain text document into
actual characters, and the rules for actually rendering the text to the
user, are defined by the specifications for the computed MIME type of the
resource (type in the navigate algorithm).
The document’s character encoding must be set to the character encoding
used to decode the document.
When no more bytes are available, the user agent must queue a task for the
parser to process the implied EOF character, which eventually causes a
load event to be fired.
After creating the Document object, but potentially before the page has
finished parsing, the user agent must update the session history with the
new page.
User agents may add content to the head element of the Document, e.g., to
link to a style sheet, provide a script, give the document a title, etc.
In particular, if the user agent supports the Format=Flowed feature of
RFC3676 then the user agent would need to apply extra styling to cause the
text to wrap correctly and to handle the quoting feature. [RFC3676]
The task source for the two tasks mentioned in this section must be the
networking task source.
6.7.5. Page load processing model for multipart/x-mixed-replace resources
When a resource with the type multipart/x-mixed-replace is to be loaded in
a browsing context, the user agent must parse the resource using the rules
for multipart types. [RFC2046]
For each body part obtained from the resource, the user agent must run a
new instance of the navigate algorithm, starting from the resource
handling step, using the new body part as the resource being navigated,
with replacement enabled if a previous body part from the same resource
resulted in a Document object being created and initialized, and otherwise
using the same setup as the navigate attempt that caused this section to
be invoked in the first place.
For the purposes of algorithms processing these body parts as if they were
complete stand-alone resources, the user agent must act as if there were
no more bytes for those resources whenever the boundary following the body
part is reached.
Thus, load events (and for that matter unload events) do fire for each
body part loaded.
6.7.6. Page load processing model for media
When an image, video, or audio resource is to be loaded in a browsing
context, the user agent should create a Document object, mark it as being
an HTML document, set its content type to the computed MIME type of the
resource (type in the navigate algorithm), initialize the Document object,
append an html element to the Document, append a head element and a body
element to the html element, append an element host element for the media,
as described below, to the body element, and set the appropriate attribute
of the element host element, as described below, to the address of the
image, video, or audio resource.
The element host element to create for the media is the element given in
the table below in the second cell of the row whose first cell describes
the media. The appropriate attribute to set is the one given by the third
cell in that same row.
Type of media Element for the media Appropriate attribute
Image img src
Video video src
Audio audio src
Then, the user agent must act as if it had stopped parsing.
After creating the Document object, but potentially before the page has
finished fully loading, the user agent must update the session history
with the new page.
User agents may add content to the head element of the Document, or
attributes to the element host element, e.g., to link to a style sheet,
provide a script, give the document a title, make the media autoplay, etc.
6.7.7. Page load processing model for content that uses plugins
When a resource that requires an external resource to be rendered is to be
loaded in a browsing context, the user agent should create a Document
object, mark it as being an HTML document and mark it as being a plugin
document, set its content type to the computed MIME type of the resource
(type in the navigate algorithm), initialize the Document object, append
an html element to the Document, append a head element and a body element
to the html element, append an embed to the body element, and set the src
attribute of the embed element to the address of the resource.
The term plugin document is used by Content Security Policy as part of the
mechanism that ensures iframes can’t be used to evade plugin-types
directives. [CSP3]
Then, the user agent must act as if it had stopped parsing.
After creating the Document object, but potentially before the page has
finished fully loading, the user agent must update the session history
with the new page.
User agents may add content to the head element of the Document, or
attributes to the embed element, e.g., to link to a style sheet, to give
the document a title, etc.
If the Document's active sandboxing flag set has its sandboxed plugins
browsing context flag set, the synthesized embed element will fail to
render the content if the relevant plugin cannot be secured.
6.7.8. Page load processing model for inline content that doesn’t have a DOM
When the user agent is to display a user agent page inline in a browsing
context, the user agent should create a Document object, mark it as being
an HTML document, set its content type to "text/html", initialize the
Document object, and then either associate that Document with a custom
rendering that is not rendered using the normal Document rendering rules,
or mutate that Document until it represents the content the user agent
wants to render.
Once the page has been set up, the user agent must act as if it had
stopped parsing.
After creating the Document object, but potentially before the page has
been completely set up, the user agent must update the session history
with the new page.
6.7.9. Navigating to a fragment
When a user agent is supposed to navigate to a fragment, then the user
agent must run the following steps:
1. Remove all the entries in the browsing context’s session history after
the current entry. If the current entry is the last entry in the
session history, then no entries are removed.
This doesn’t necessarily have to affect the user agent’s user
interface.
2. Remove any tasks queued by the history traversal task source that are
associated with any Document objects in the top-level browsing
context’s document family.
3. Append a new entry at the end of the History object representing the
new resource and its Document object, related state, and current
history scroll restoration preference. Its URL must be set to the
address to which the user agent was navigating. The title must be left
unset.
4. Traverse the history to the new entry, with the non-blocking events
flag set. This will scroll to the fragment given in what is now the
document’s URL.
If the scrolling fails because the relevant ID has not yet been parsed,
then the original navigation algorithm will take care of the scrolling
instead, as the last few steps of its update the session history with the
new page algorithm.
----------------------------------------------------------------------
When the user agent is required to scroll to the fragment and the
indicated part of the document, if any, is being rendered, the user agent
must either change the scrolling position of the document using the
following algorithm, or perform some other action such that the indicated
part of the document is brought to the user’s attention. If there is no
indicated part, or if the indicated part is not being rendered, then the
user agent must do nothing. The aforementioned algorithm is as follows:
1. Let target be the indicated part of the document, as defined below.
2. If target is the top of the document, then scroll to the beginning of
the document for the Document, and abort these steps. [CSSOM-VIEW]
3. Use the scroll an element into view algorithm to scroll target into
view, with the align to top flag set. [CSSOM-VIEW]
4. Run the focusing steps for that element, with the Document's viewport
as the fallback target.
5. Move the sequential focus navigation starting point to target.
The indicated part of the document is the one that the fragment, if any,
identifies. The semantics of the fragment in terms of mapping it to a
specific DOM Node is defined by the specification that defines the MIME
type used by the Document (for example, the processing of fragment for XML
MIME types is the responsibility of RFC7303). [RFC7303]
For HTML documents (and HTML MIME types), the following processing model
must be followed to determine what the indicated part of the document is.
1. Apply the URL parser algorithm to the URL, and let fragid be the
fragment component of the resulting URL record.
2. If fragid is the empty string, then the indicated part of the document
is the top of the document; stop the algorithm here.
3. Let fragid bytes be the result of percent decoding fragid.
4. Let decoded fragid be the result of running UTF-8 decode without BOM
or fail on fragid bytes. If decoded fragid is failure, jump to the
step labeled no decoded fragid.
5. If there is an element in the DOM that has an ID exactly equal to
decoded fragid, then the first such element in tree order is the
indicated part of the document; stop the algorithm here.
6. No decoded fragid: If there is an a element in the DOM that has a name
attribute whose value is exactly equal to fragid (not decoded fragid),
then the first such element in tree order is the indicated part of the
document; stop the algorithm here.
7. If fragid is an ASCII case-insensitive match for the string top, then
the indicated part of the document is the top of the document; stop
the algorithm here.
8. Otherwise, there is no indicated part of the document.
For the purposes of the interaction of HTML with Selectors' :target
pseudo-class, the target element is the indicated part of the document, if
that is an element; otherwise there is no target element. [SELECTORS4]
The task source for the task mentioned in this section must be the DOM
manipulation task source.
6.7.10. History traversal
When a user agent is required to traverse the history to a specified
entry, optionally with replacement enabled, and optionally with the
non-blocking events flag set, the user agent must act as follows.
This algorithm is not just invoked when explicitly going back or forwards
in the session history — it is also invoked in other situations, for
example when navigating a browsing context, as part of updating the
session history with the new page.
1. If there is no longer a Document object for the entry in question,
navigate the browsing context to the resource for that entry to
perform an entry update of that entry, and abort these steps. The
"navigate" algorithm reinvokes this "traverse" algorithm to complete
the traversal, at which point there is a Document object and so this
step gets skipped. The navigation must be done using the same source
browsing context as was used the first time this entry was created.
(This can never happen with replacement enabled.)
If the resource was obtained using a non-idempotent action, for
example a POST form submission, or if the resource is no longer
available, for example because the computer is now offline and the
page wasn’t cached, navigating to it again might not be possible. In
this case, the navigation will result in a different page than
previously; for example, it might be an error message explaining the
problem or offering to resubmit the form.
2. If the current entry’s title was not set by the pushState() or
replaceState() methods, then set its title to the value returned by
the document.title IDL attribute.
3. If appropriate, update the current entry in the browsing context’s
Document object’s History object to reflect any state that the user
agent wishes to persist. The entry is then said to be an entry with
persisted user state.
4. If the specified entry has a different Document object than the
current entry, then run the following substeps:
1. Remove any tasks queued by the history traversal task source that
are associated with any Document objects in the top-level
browsing context’s document family.
2. If the origin of the Document of the specified entry is not the
same as the origin of the Document of the current entry, then run
the following sub-sub-steps:
1. The current browsing context name must be stored with all
the entries in the history that are associated with Document
objects with the same origin as the active document and that
are contiguous with the current entry.
2. If the browsing context is a top-level browsing context, but
not an auxiliary browsing context, then the browsing
context’s browsing context name must be unset.
3. Make the specified entry’s Document object the active document of
the browsing context.
4. If the specified entry has a browsing context name stored with
it, then run the following sub-sub-steps:
1. Set the browsing context’s browsing context name to the name
stored with the specified entry.
2. Clear any browsing context names stored with all entries in
the history that are associated with Document objects with
the same origin as the new active document and that are
contiguous with the specified entry.
5. If the specified entry’s Document has any form controls whose
autofill field name is "off", invoke the reset algorithm of each
of those elements.
6. If the current document readiness of the specified entry’s
Document is "complete", queue a task to run the following
sub-sub-steps:
1. If the Document's page showing flag is true, then abort this
task (i.e., don’t fire the event below).
2. Set the Document's page showing flag to true.
3. Run any session history document visibility change steps for
Document that are defined by other applicable
specifications.
This is specifically intended for use by the Page Visibility
specification. [PAGE-VISIBILITY]
4. Fire a trusted event with the name pageshow at the Window
object of that Document, with target override set to the
Document object, using the PageTransitionEvent interface,
with the persisted attribute initialized to true. This event
must not bubble, must not be cancelable, and has no default
action.
5. Set the document’s URL to the URL of the specified entry.
6. If the specified entry has a URL whose fragment differs from that of
the current entry’s when compared in a case-sensitive manner, and the
two share the same Document object, then let hash changed be true, and
let old URL be the URL of the current entry and new URL be the URL of
the specified entry. Otherwise, let hash changed be false.
7. If the traversal was initiated with replacement enabled, remove the
entry immediately before the specified entry in the session history.
8. If the specified entry is not an entry with persisted user state, but
its URL has a fragment, scroll to the fragment.
9. If the entry is an entry with persisted user state, the user agent may
restore persisted user state and update aspects of the document and
its rendering.
10. Let targetRealm be the current Realm Record.
11. If the entry is a serialized state entry, let state be
StructuredDeserialize(entry’s serialized state, targetRealm). If this
throws an exception, ignore the exception and let state be null.
12. Set history.state to state.
13. Let state changed be true if the Document of the specified entry has a
latest entry, and that entry is not the specified entry; otherwise let
it be false.
14. Let the latest entry of the Document of the specified entry be the
specified entry.
15. If the non-blocking events flag is not set, then run the following
steps immediately. Otherwise, the non-blocking events flag is set;
queue a task to run the following substeps instead.
1. If state changed is true, fire a trusted event with the name
popstate at the Window object of the Document, using the
PopStateEvent interface, with the state attribute initialized to
the value of state. This event must bubble but not be cancelable
and has no default action.
2. If hash changed is true, then fire a trusted event with the name
hashchange at the browsing context’s Window object, using the
HashChangeEvent interface, with the oldURL attribute initialized
to old URL and the newURL attribute initialized to new URL. This
event must bubble but not be cancelable and has no default
action.
16. The current entry is now the specified entry.
The task source for the tasks mentioned above is the DOM manipulation task
source.
6.7.10.1. Persisted user state restoration
When the user agent is to restore persisted user state from a history
entry, it must run the following steps immediately:
1. If the entry has a scroll restoration mode, let scrollRestoration be
that. Otherwise let scrollRestoration be "auto"
2. If scrollRestoration is "manual" the user agent should not restore the
scroll position for the document, otherwise, it may do so.
3. Optionally, update other aspects of the document and its rendering,
for instance values of form fields, that the user agent had previously
recorded.
This can even include updating the dir attribute of textarea elements or
input elements whose type attribute is in either the Text state or the
Search state, if the persisted state includes the directionality of user
input in such controls.
6.7.10.2. The PopStateEvent interface
[Constructor(DOMString type, optional PopStateEventInit eventInitDict), Exposed=(Window,Worker)]
interface PopStateEvent : Event {
readonly attribute any state;
};
dictionary PopStateEventInit : EventInit {
any state = null;
};
event . state
Returns a copy of the information that was provided to pushState()
or replaceState().
The state attribute must return the value it was initialized to. It
represents the context information for the event, or null, if the state
represented is the initial state of the Document.
6.7.10.3. The HashChangeEvent interface
[Constructor(DOMString type, optional HashChangeEventInit eventInitDict), Exposed=(Window,Worker)]
interface HashChangeEvent : Event {
readonly attribute USVString oldURL;
readonly attribute USVString newURL;
};
dictionary HashChangeEventInit : EventInit {
USVString oldURL = "";
USVString newURL = "";
};
event . oldURL
Returns the URL of the session history entry that was previously
current.
event . newURL
Returns the URL of the session history entry that is now current.
The oldURL attribute must return the value it was initialized to. It
represents context information for the event, specifically the URL of the
session history entry that was traversed from.
The newURL attribute must return the value it was initialized to. It
represents context information for the event, specifically the URL of the
session history entry that was traversed to.
6.7.10.4. The PageTransitionEvent interface
[Constructor(DOMString type, optional PageTransitionEventInit eventInitDict), Exposed=(Window,Worker)]
interface PageTransitionEvent : Event {
readonly attribute boolean persisted;
};
dictionary PageTransitionEventInit : EventInit {
boolean persisted = false;
};
event . persisted
For the pageshow event, returns false if the page is newly being
loaded (and the load event will fire). Otherwise, returns true.
For the pagehide event, returns false if the page is going away
for the last time. Otherwise, returns true, meaning that (if
nothing conspires to make the page unsalvageable) the page might
be reused if the user navigates back to this page.
Things that can cause the page to be unsalvageable include:
* document.open()
* Listening for beforeunload events
* Listening for unload events
* Having iframes that are not salvageable
* Active WebSocket objects
* Aborting a Document
The persisted attribute must return the value it was initialized to. It
represents the context information for the event.
6.7.11. Unloading documents
A Document has a salvageable state, which must initially be true, a fired
unload flag, which must initially be false, and a page showing flag, which
must initially be false. The page showing flag is used to ensure that
scripts receive pageshow and pagehide events in a consistent manner (e.g.,
that they never receive two pagehide events in a row without an
intervening pageshow, or vice versa).
Event loops have a termination nesting level counter, which must initially
be zero.
When a user agent is to prompt to unload a document, it must run the
following steps.
1. Increase the event loop’s termination nesting level by one.
2. Increase the Document's ignore-opens-during-unload counter by one.
3. Let event be a new trusted BeforeUnloadEvent event object with the
name beforeunload, which does not bubble but is cancelable.
4. Dispatch: Dispatch event at the Document's Window object.
5. Decrease the event loop’s termination nesting level by one.
6. If any event listeners were triggered by the earlier dispatch step,
then set the Document's salvageable state to false.
7. If the Document's active sandboxing flag set does not have its
sandboxed modals flag set, and the returnValue attribute of the event
object is not the empty string, or if the event was canceled, then the
user agent should ask the user to confirm that they wish to unload the
document.
The prompt shown by the user agent may include the string of the
returnValue attribute, or optionally truncated.
The user agent must pause while waiting for the user’s response.
If the user did not confirm the page navigation, then the user agent
refused to allow the document to be unloaded.
8. If this algorithm was invoked by another instance of the "prompt to
unload a document" algorithm (i.e., through the steps below that
invoke this algorithm for all descendant browsing contexts), then jump
to the step labeled end.
9. Let descendants be the list of the descendant browsing contexts of the
Document.
10. If descendants is not an empty list, then for each browsing context b
in descendants run the following substeps:
1. Prompt to unload the active document of the browsing context b.
If the user refused to allow the document to be unloaded, then
the user implicitly also refused to allow this document to be
unloaded; jump to the step labeled end.
2. If the salvageable state of the active document of the browsing
context b is false, then set the salvageable state of this
document to false also.
11. End: Decrease the Document's ignore-opens-during-unload counter by
one.
When a user agent is to unload a document, it must run the following
steps. These steps are passed an argument, recycle, which is either true
or false, indicating whether the Document object is going to be re-used.
(This is set by the document.open() method.)
1. Increase the event loop’s termination nesting level by one.
2. Increase the Document's ignore-opens-during-unload counter by one.
3. If the Document's page showing flag is false, then jump to the step
labeled unload event below (i.e., skip firing the pagehide event and
don’t rerun the unloading document visibility change steps).
4. Set the Document's page showing flag to false.
5. Fire a trusted event with the name pagehide at the Window object of
the Document, with target override set to the Document object, using
the PageTransitionEvent interface, with the persisted attribute
initialized to true if the Document object’s salvageable state is
true, and false otherwise. This event must not bubble, must not be
cancelable, and has no default action.
6. Run any unloading document visibility change steps for Document that
are defined by other applicable specifications.
This is specifically intended for use by the Page Visibility
specification. [PAGE-VISIBILITY]
7. Unload event: If the Document's fired unload flag is false, fire a
simple event named unload at the Document's Window object, with target
override set to the Document object.
8. Decrease the event loop’s termination nesting level by one.
9. If any event listeners were triggered by the earlier unload event
step, then set the Document object’s salvageable state to false and
set the Document's fired unload flag to true.
10. Run any unloading document cleanup steps for Document that are defined
by this specification and other applicable specifications.
11. If this algorithm was invoked by another instance of the "unload a
document" algorithm (i.e., by the steps below that invoke this
algorithm for all descendant browsing contexts), then jump to the step
labeled end.
12. Let descendants be the list of the descendant browsing contexts of the
Document.
13. If descendants is not an empty list, then for each browsing context b
in descendants run the following substeps:
1. Unload the active document of the browsing context b with the
recycle parameter set to false.
2. If the salvageable state of the active document of the browsing
context b is false, then set the salvageable state of this
document to false also.
14. If both the Document's salvageable state and recycle are false, then
the Document's browsing context must discard the Document.
15. End: Decrease the Document's ignore-opens-during-unload counter by
one.
This specification defines the following unloading document cleanup steps.
Other specifications can define more.
1. Make disappear any WebSocket objects that were created by the
WebSocket() constructor from the Document's Window object.
If this affected any WebSocket objects, then set Document's
salvageable state to false.
2. If the Document's salvageable state is false, forcibly close any
EventSource objects that whose constructor was invoked from the
Document's Window object.
3. If the Document's salvageable state is false, empty the Document's
Window’s list of active timers.
6.7.11.1. The BeforeUnloadEvent interface
interface BeforeUnloadEvent : Event {
attribute DOMString returnValue;
};
event . returnValue [ = value ]
Returns the current return value of the event (the message to show
the user).
Can be set, to update the message.
There are no BeforeUnloadEvent-specific initialization methods.
The returnValue attribute represents the message to show the user. When
the event is created, the attribute must be set to the empty string. On
getting, it must return the last value it was set to. On setting, the
attribute must be set to the new value.
6.7.12. Aborting a document load
If a Document is aborted, the user agent must run the following steps:
1. Abort the active documents of every child browsing context. If this
results in any of those Document objects having their salvageable
state set to false, then set this Document's salvageable state to
false also.
2. Cancel any instances of the fetch algorithm in the context of this
Document, discarding any tasks queued for them, and discarding any
further data received from the network for them. If this resulted in
any instances of the fetch algorithm being canceled or any queued
tasks or any network data getting discarded, then set the Document's
salvageable state to false.
3. If the Document has an active parser, then abort that parser and set
the Document's salvageable state to false.
User agents may allow users to explicitly invoke the abort a document
algorithm for a Document. If the user does so, then, if that Document is
an active document, the user agent should queue a task to fire a simple
event named abort at that Document's Window object before invoking the
abort algorithm.
6.7.13. Browser state
[NoInterfaceObject, Exposed=(Window, Worker)]
interface NavigatorOnLine {
readonly attribute boolean onLine;
};
window . navigator . onLine
Returns false if the user agent is definitely offline
(disconnected from the network). Returns true if the user agent
might be online.
The events online and offline are fired when the value of this
attribute changes.
The navigator.onLine attribute must return false if the user agent will
not contact the network when the user follows links or when a script
requests a remote page (or knows that such an attempt would fail), and
must return true otherwise.
When the value that would be returned by the navigator.onLine attribute of
a Window or WorkerGlobalScope changes from true to false, the user agent
must queue a task to fire a simple event named offline at the Window or
WorkerGlobalScope object.
On the other hand, when the value that would be returned by the
navigator.onLine attribute of a Window or WorkerGlobalScope changes from
false to true, the user agent must queue a task to fire a simple event
named online at the Window or WorkerGlobalScope object.
The task source for these tasks is the networking task source.
This attribute is inherently unreliable. A computer can be connected to a
network without having Internet access.
In this example, an indicator is updated as the browser goes online and
offline.
Online status
The network is: (state unknown)
7. Web application APIs
7.1. Scripting
7.1.1. Introduction
Various mechanisms can cause author-provided executable code to run in the
context of a document. These mechanisms include, but are probably not
limited to:
* Processing of script elements.
* Navigating to javascript: URLs.
* Event handlers, whether registered through the DOM using
addEventListener(), by explicit event handler content attributes, by
event handler IDL attributes, or otherwise.
* Processing of technologies like SVG that have their own scripting
features.
7.1.2. Enabling and disabling scripting
Scripting is enabled in a browsing context when all of the following
conditions are true:
* The user agent supports scripting.
* The user has not disabled scripting for this browsing context at this
time. (User agents may provide users with the option to disable
scripting globally, or in a finer-grained manner, e.g. on a per-origin
basis.)
* The browsing context’s active document’s active sandboxing flag set
does not have its sandboxed scripts browsing context flag set.
Scripting is disabled in a browsing context when any of the above
conditions are false (i.e., when scripting is not enabled).
----------------------------------------------------------------------
Scripting is enabled for a node if the node’s node document has a browsing
context, and scripting is enabled in that browsing context.
Scripting is disabled for a node if there is no such browsing context, or
if scripting is disabled in that browsing context.
7.1.3. Processing model
7.1.3.1. Definitions
A script is one of two possible structures. All scripts have:
A settings object
An environment settings object, containing various settings that
are shared with other scripts in the same context.
A classic script additionally has:
A Source text
A string containing a block of executable code to be evaluated as
a JavaScript Script.
Optionally, a muted errors flag
A flag which, if set, means that error information will not be
provided for errors in this script (used to mute errors for
cross-origin scripts, since that can leak private information).
A module script additionally has:
A module record
A Source Text Module Record representing the parsed module, ready
to be evaluated.
A base URL
A base URL used for resolving module specifiers when resolving a
module specifier. This will either be the URL from which the
script was obtained, for external module scripts, or the document
base URL of the containing document, for inline module scripts.
A credentials mode
A credentials mode used to fetch imported modules.
A cryptographic nonce
A cryptographic nonce used to fetch imported modules.
A parser state
The parser metadata used to fetch imported modules.
----------------------------------------------------------------------
An environment settings object specifies algorithms for obtaining the
following:
A realm execution context
A JavaScript execution context shared by all script elements that
use this settings object, i.e. all scripts in a given JavaScript
realm. When we run a classic script or run a module script, this
execution context becomes the top of the JavaScript execution
context stack, on top of which another execution context specific
to the script in question is pushed. (This setup ensures
ParseScript and ModuleEvaluation know which Realm to use.)
A module map
Used when importing JavaScript modules.
A responsible browsing context
A browsing context that is assigned responsibility for actions
taken by the scripts that use this environment settings object.
When a script creates and navigates a new top-level browsing
context, the opener attribute of the new browsing context’s Window
object will be set to the responsible browsing context’s
WindowProxy object.
A responsible event loop
An event loop that is used when it would not be immediately clear
what event loop to use.
A responsible document
A Document that is assigned responsibility for actions taken by
the scripts that use this environment settings object.
For example, the URL of the responsible document is used to set
the URL of the Document after it has been reset using open().
If the responsible event loop is not a browsing context event
loop, then the environment settings object has no responsible
document.
An API URL character encoding
A character encoding used to encode URLs by APIs called by scripts
that use this environment settings object.
An API base URL
An URL used by APIs called by scripts that use this environment
settings object to parse URLs.
An origin
An origin used in security checks.
A creation URL
An absolute URL representing the location of the resource with
which the environment settings object is associated. Note that
this URL might be distinct from the responsible document’s URL,
due to mechanisms such as history.pushState().
An HTTPS state
An HTTPS state value representing the security properties of the
network channel used to deliver the resource with which the
environment settings object is associated.
An referrer policy
The default referrer policy for fetches performed using this
environment settings object as a request client. [REFERRERPOLICY]
An environment settings object also has an outstanding rejected promises
weak set and an about-to-be-notified rejected promises list, used to track
unhandled promise rejections. The outstanding rejected promises weak set
must not create strong references to any of its members, and
implementations are free to limit its size, e.g., by removing old entries
from it when new ones are added.
7.1.3.2. Fetching scripts
The various script-fetching algorithms below have two hooks that may be
customized by their callers:
* Set up the request, which takes a request which it may modify before
the algorithm continues
* Process the response, which takes a response and must either return
true or false to indicate success or failure, respectively
Service Workers is an example of a specification that runs these
algorithms with its own options for the hooks. [SERVICE-WORKERS]
To fetch a classic script for a script element element, given a url, a
CORS setting, a cryptographic nonce, a parser state, a settings object,
and a character encoding, run these steps. The algorithm will
asynchronously complete with either null (on failure) or a new classic
script (on success).
1. Let request be the result of creating a potential-CORS request given
url and CORS setting.
2. Set request’s client to settings object, its type to "script", its
destination to "script", its cryptographic nonce metadata to
cryptographic nonce, and its parser metadata to parser state.
3. If the caller specified custom steps to set up the request, perform
them on request.
4. Fetch request.
5. Return from this algorithm, and run the remaining steps as part of the
fetch’s process response for the response response.
response can be either CORS-same-origin or CORS-cross-origin. This
only affects how error reporting happens.
6. If response’s type is "error", or response’s status is not an ok
status, asynchronously complete this algorithm with null, and abort
these steps.
7. If the caller specified custom steps to process the response, perform
them on response. If they return false, complete this algorithm with
null, and abort these steps.
8. If response’s Content-Type metadata, if any, specifies a character
encoding, and the user agent supports that encoding, then set
character encoding to that encoding (ignoring the passed-in value).
9. Let source text be the result of decoding response’s body to Unicode,
using character encoding as the fallback encoding.
The decode algorithm overrides character encoding if the file contains
a BOM.
10. Let script be the result of creating a classic script using source
text and settings object.
If response was CORS-cross-origin, then pass the muted errors flag to
the create a classic script algorithm as well.
11. Asynchronously complete this algorithm with script.
To fetch a classic worker script given a url, a referrer, a settings
object, and a destination, run these steps. The algorithm will
asynchronously complete with either null (on failure) or a new classic
script (on success).
1. Let request be a new request whose URL is url, client is settings
object, type is "script", destination is destination, referrer is
referrer, mode is "same-origin", credentials mode is "same-origin",
parser metadata is "not parser-inserted", and whose
use-URL-credentials flag is set.
2. If the caller specified custom steps to set up the request, perform
them on request.
3. Fetch request.
4. Return from this algorithm, and run the remaining steps as part of the
fetch’s process response for the response response.
5. If response’s type is "error", or response’s status is not an ok
status, asynchronously complete this algorithm with null, and abort
these steps.
6. If the caller specified custom steps to process the response, perform
them on response. If they return false, complete this algorithm with
null, and abort these steps.
7. Let source text be the result of UTF-8 decoding response’s body.
8. Let script be the result of creating a classic script using source
text and settings object.
9. Asynchronously complete this algorithm with script.
To fetch a module script tree given a url, a credentials mode, a
cryptographic nonce, a parser state, a destination, a fetch client
settings object, and an optional ancestor list, run these steps. The
algorithm will asynchronously complete with either null (on failure) or a
new module script (on success).
1. If ancestor list is not given, let it be an empty list.
2. If module map settings object is not given, let it be fetch client
settings object.
3. Fetch a single module script given url, credentials mode,
cryptographic nonce, parser state, destination, and module map
settings object. If the caller of this algorithm specified custom set
up the request or process the response steps, pass those along while
fetching a single module script.
4. Return from this algorithm and run the following steps when fetching a
single module script asynchronously completes with result:
5. If result is null, asynchronously complete this algorithm with null
and abort these steps.
6. Otherwise, result is a module script. Fetch the descendants of result
given destination and an ancestor list obtained by appending url to
ancestor list.
7. When fetching the descendants of a module script asynchronously
completes with descendants result, asynchronously complete this
algorithm with descendants result.
----------------------------------------------------------------------
The following algorithms are used when fetching a module script tree, and
are not meant to be used directly by other specifications (or by other
parts of this specification).
To fetch the descendants of a module script module script, given a
destination and an ancestor list, run these steps. The algorithm will
asynchronously complete with either null (on failure) or with module
script (on success).
1. Let record be module script’s module record.
2. If record.[[RequestedModules]] is empty, asynchronously complete this
algorithm with module script.
3. Let urls be a new empty list.
4. For each string requested of record.[[RequestedModules]]:
1. Let url be the result of resolving a module specifier given
module script and requested.
2. If the result is error:
1. Let error be a new TypeError exception.
2. Report the exception error for module script.
3. Abort this algorithm, and asynchronously complete it with
null.
3. Otherwise, if url is not in ancestor list, add url to urls.
5. For each url in urls, fetch a module script tree given url, module
script’s credentials mode, module script’s cryptographic nonce, module
script’s parser state, destination, module script’s settings object,
and ancestor list.
It is intentional that no custom set up the request or process the
response steps are passed along here. Those hooks only apply to the
top-level fetch at the root of the module script tree.
If any of the fetch a module script tree invocations asynchronously
complete with null, the user agent may terminate any or all of the
other fetches, and must then asynchronously complete this algorithm
with null.
Once all of the fetch a module script tree invocations asynchronously
complete with a module script, asynchronously complete this algorithm
with module script.
To fetch a single module script, given a url, a credentials mode, a
cryptographic nonce, a parser state, a destination, and a settings object,
run these steps. The algorithm will asynchronously complete with either
null (on failure) or a module script (on success).
1. Let module map be settings object’s module map.
2. If module map contains an entry with key url whose value is
"fetching", wait (in parallel) until that entry’s value changes, then
proceed to the next step.
3. If module map contains an entry with key url, asynchronously complete
this algorithm with that entry’s value, and abort these steps.
4. Create an entry in module map with key url and value "fetching".
5. Let request be a new request whose url is url, destination is
destination, type is "script", mode is "cors", credentials mode is
credentials mode, cryptographic nonce metadata is cryptographic nonce,
parser metadata is parser state and client is settings object.
6. If the caller specified custom steps to set up the request, perform
them on request.
7. Fetch request.
8. Return from this algorithm, and run the remaining steps as part of the
fetch’s process response for the response response.
response is always CORS-same-origin.
9. If any of the following conditions are met, set the value of the entry
in module map whose key is url to null, asynchronously complete this
algorithm with null, and abort these steps:
* response’s type is "error"
* response’s status is not an ok status
* The result of extracting a MIME type from response’s header list
(ignoring parameters) is not a JavaScript MIME type.
For historical reasons, fetching a classic script does not
include MIME type checking. In contrast, module scripts will fail
to load if they are not of a correct MIME type.
* The caller specified custom steps to process the response, which
when performed on response return false.
10. Let source text be the result of UTF-8 decoding response’s body.
11. Let module script be the result of creating a module script given
source text, settings object, response’s url, credentials mode, and
cryptographic nonce.
12. Set the value of the entry in module map whose key is url to module
script, and asynchronously complete this algorithm with module script.
It is intentional that the module map is keyed by the request URL,
whereas the base URL for the module script is set to the response URL.
The former is used to deduplicate fetches, while the latter is used
for URL resolution.
7.1.3.3. Creating scripts
To create a classic script, given some script source, an environment
settings object, and an optional muted errors flag:
1. Let script be a new classic script that this algorithm will
subsequently initialize.
2. Set script’s settings object to the environment settings object
provided.
3. If scripting is disabled for the given environment settings object’s
responsible browsing context, set script’s source text to the empty
string. Otherwise, set script’s source text to the supplied script
source.
4. If the muted errors flag was set, then set script’s muted errors flag.
5. Return script.
To create a module script, given some script source, an environment
settings object, a script base URL, a credentials mode, a cryptographic
nonce, and a parser state:
1. Let script be a new module script that this algorithm will
subsequently initialise.
2. Set script’s settings object to the environment settings object
provided.
3. Let realm be the provided environment settings object’s Realm.
4. If scripting is disabled for the given environment settings object’s
responsible browsing context, then let script source be the empty
string. Otherwise, let script source be the provided script source.
5. Let result be ParseModule(script source, realm, script).
6. If result is a List of errors, report the exception given by the first
element of result for script, return null, and abort these steps.
7. Set script’s module record to result.
8. Set script’s base URL to the script base URL provided.
9. Set script’s credentials mode to the credentials mode provided.
10. Set script’s cryptographic nonce to the cryptographic nonce provided.
11. Set script’s parser state to the parser state.
12. Return script.
7.1.3.4. Calling scripts
To run a classic script given a classic script s and an optional rethrow
errors flag:
1. Let settings be the settings object of s.
2. Check if we can run script with settings. If this returns "do not
run", then return undefined and abort these steps.
3. Let realm be settings’s Realm.
4. Prepare to run script with settings.
5. Let result be ParseScript(s’s source text, realm, s).
6. If result is a List of errors, set result to the first element of
result and go to the step labeled error.
7. Let evaluationStatus be ScriptEvaluation(result).
8. If evaluationStatus is an abrupt completion, set result to
evaluationStatus.[[value]] and go to the next step (labeled Error). If
evaluationStatus is a normal completion, or if ScriptEvaluation does
not complete because the user agent has aborted the running script,
skip to the step labeled Cleanup.
9. Error: At this point result must be an exception. Perform the
following steps:
1. If the rethrow errors flag is set and s’s muted errors flag is
not set, rethrow result.
2. If the rethrow errors flag is set and s’s muted errors flag is
set, throw a NetworkError exception.
3. If the rethrow errors flag is not set, report the exception given
by result for the script s.
10. Cleanup: Clean up after running script with settings.
11. If evaluationStatus exists and is a normal completion, return
evaluationStatus.[[value]]. Otherwise, script execution was
unsuccessful, either because an error occurred during parsing, or an
exception occurred during evaluation, or because it was aborted
prematurely.
To run a module script given a module script s:
1. Let settings be the settings object of s.
2. Check if we can run script with settings. If this returns "do not run"
then abort these steps.
3. Let record be s’s module record.
4. Let instantiationStatus be record.ModuleDeclarationInstantiation().
This step will recursively instantiate all of the module’s
dependencies.
5. If instantiationStatus is an abrupt completion, report the exception
given by instantiationStatus.[[Value]] for s and abort these steps.
6. Prepare to run script given settings.
7. Let evaluationStatus be record.ModuleEvaluation().
This step will recursively evaluate all of the module’s dependencies.
8. If evaluationStatus is an abrupt completion, report the exception
given by evaluationStatus.[[Value]] for s. (Do not perform this step
if ScriptEvaluation fails to complete as a result of the user agent
aborting the running script.)
9. Clean up after running script with settings.
The steps to check if we can run script with an environment settings
object settings are as follows. They return either "run" or "do not run".
1. If the global object specified by settings is a Window object whose
Document object is not fully active, then return "do not run" and
abort these steps.
2. If scripting is disabled for the responsible browsing context
specified by settings, then return "do not run" and abort these steps.
3. Return "run".
The steps to prepare to run script with an environment settings object
settings are as follows:
1. Increment settings’s realm execution context’s entrance counter by
one.
2. Push settings’s realm execution context onto the JavaScript execution
context stack; it is now the running JavaScript execution context.
The steps to clean up after running script with an environment settings
object settings are as follows:
1. Assert: settings’s realm execution context is the running JavaScript
execution context.
2. Decrement settings’s realm execution context’s entrance counter by
one.
3. Remove settings’s realm execution context from the JavaScript
execution context stack.
4. If the JavaScript execution context stack is now empty, run the global
script clean-up jobs. (These cannot run scripts.)
5. If the JavaScript execution context stack is now empty, perform a
microtask checkpoint. (If this runs scripts, these algorithms will be
invoked reentrantly.)
These algorithms are not invoked by one script directly calling another,
but they can be invoked reentrantly in an indirect manner, e.g., if a
script dispatches an event which has event listeners registered.
The running script is the script in the [[HostDefined]] field in the
ScriptOrModule component of the running JavaScript execution context.
Each unit of related similar-origin browsing contexts has a global script
clean-up jobs list, which must initially be empty. A global script
clean-up job cannot run scripts, and cannot be sensitive to the order in
which other clean-up jobs are executed. The File API uses this to release
blob: URLs. [FILEAPI]
When the user agent is to run the global script clean-up jobs, the user
agent must perform each of the jobs in the global script clean-up jobs
list and then empty the list.
7.1.3.5. Realms, settings objects, and global objects
A global object is a JavaScript object that is the [[GlobalObject]] field
of a JavaScript realm.
In this specification, all JavaScript realms are initialized with global
objects that are either Window or WorkerGlobalScope objects.
There is always a 1:1:1 mapping between JavaScript realms, global objects,
and environment settings objects:
* A JavaScript realm has a [[HostDefined]] field, which contains the
Realm’s settings object.
* A JavaScript realm has a [[GlobalObject]] field, which contains the
Realm’s global object.
* Each global object in this specification is created during the
initialization of a corresponding JavaScript realm, known as the
global object’s Realm.
* Each global object in this specification is created alongside a
corresponding environment settings object, known as its relevant
settings object.
* An environment settings object’s realm execution context’s Realm
component is the environment settings object’s Realm.
* An environment settings object’s Realm then has a [[GlobalObject]]
field, which contains the environment settings object’s global object.
When defining algorithm steps throughout this specification, it is often
important to indicate what JavaScript realm is to be used—or,
equivalently, what global object or environment settings object is to be
used. In general, there are at least four possibilities:
Entry
This corresponds to the script that initiated the currently
running script action: i.e., the function or script that the user
agent called into when it called into author code.
Incumbent
This corresponds to the most-recently-entered author function or
script on the stack.
Current
This corresponds to the currently-running function object,
including built-in user-agent functions which might not be
implemented as JavaScript. (It is derived from the current
JavaScript realm.)
Relevant
Every platform object has a relevant Realm. When writing
algorithms, the most prominent platform object whose relevant
Realm might be important is the this value of the
currently-running function object. In some cases, there can be
other important relevant Realms, such as those of any arguments.
Note how the entry, incumbent, and current concepts are usable without
qualification, whereas the relevant concept must be applied to a
particular platform object.
Consider the following pages, with a.html being loaded in a browser
window, b.html being loaded in an iframe as shown, and c.html and d.html
omitted (they can simply be empty documents):
Entry page
Hello
Incumbent page
Each page has its own browsing context, and thus its own JavaScript realm,
global object, and environment settings object.
When the print() method is called in response to pressing the button in
a.html, then:
* The entry Realm is that of a.html.
* The incumbent Realm is that of b.html.
* The current Realm is that of c.html (since it is the print() method
from c.html whose code is running).
* The relevant Realm of the object on which the print() method is being
called is that of d.html.
The incumbent and entry concepts should not be used by new specifications,
and we are considering whether we can remove almost all existing uses
Currently, the incumbent concept is used in some security checks, and the
entry concept is sometimes used to obtain, amongst other things, the API
base URL to parse a URL, used in scripts running in that unit of related
similar-origin browsing contexts.
In general, the current concept is what should be used by specifications
going forward. There is an important exception, however. If an algorithm
is creating an object that is to be persisted and returned multiple times
(instead of simply returned to author code right away, and never vended
again), it should use the relevant concept with regard to the object on
which the method in question is being executed. This prevents cross-realm
calls from causing an object to store objects created in the "wrong"
realm.
The navigator.getBattery() method creates promises in the relevant Realm
for the Navigator object on which it is invoked. This has the following
impact: [BATTERY-STATUS]
Relevant Realm demo: outer page
Relevant Realm demo: inner page
If the algorithm for the getBattery() method had instead used the current
Realm, all the results would be reversed. That is, after the first call to
getBattery() in outer.html, the Navigator object in inner.html would be
permanently storing a Promise object created in outer.html’s JavaScript
realm, and calls like that inside the hello() function would thus return a
promise from the "wrong" realm. Since this is undesirable, the algorithm
instead uses the relevant Realm, giving the sensible results indicated in
the comments above.
The rest of this section deals with formally defining the entry,
incumbent, current, and relevant concepts.
7.1.3.5.1. Entry
All realm execution contexts must contain, as part of their code
evaluation state, an entrance counter value, which is initially zero. In
the process of calling scripts, this value will be incremented and
decremented.
With this in hand, we define the entry execution context to be the most
recently pushed entry in the JavaScript execution context stack whose
entrance counter value is greater than zero. The entry Realm is the entry
execution context’s Realm component.
Then, the entry settings object is the environment settings object of the
entry Realm.
Similarly, the entry global object is the global object of the entry
Realm.
7.1.3.5.2. Incumbent
The incumbent settings object is determined as follows:
1. Let scriptOrModule be the result of JavaScript’s
GetActiveScriptOrModule() abstract operation.
2. If scriptOrModule is null, abort these steps; there is no incumbent
settings object.
3. Return the settings object of the script in scriptOrModule’s
[[HostDefined]] field.
Then, the incumbent Realm is the Realm of the incumbent settings object.
Similarly, the incumbent global object is the global object of the
incumbent settings object.
7.1.3.5.3. Current
The JavaScript specification defines the current Realm Record, sometimes
abbreviated to the "current Realm". [ECMA-262]
Then, the current settings object is the environment settings object of
the current Realm Record.
Similarly, the current global object is the global object of the current
Realm Record.
7.1.3.5.4. Relevant
The relevant settings object for a platform object is defined as follows:
If the object is a global object
Each global object in this specification is created alongside a
corresponding environment settings object; that is its relevant
settings object.
Otherwise
The relevant settings object for a non-global platform object o is
the environment settings object whose global object is the global
object of the global environment associated with o.
The "global environment associated with" concept is from the olden
days, before the modern JavaScript specification and its concept
of realms. We expect that as the Web IDL specification gets
updated, every platform object will have a Realm associated with
it, and this definition can be re-cast in those terms. [ECMA-262]
[WEBIDL]
Then, the relevant Realm for a platform object is the Realm of its
relevant settings object.
Similarly, the relevant global object for a platform object is the global
object of its relevant settings object.
7.1.3.6. Killing scripts
Although the JavaScript specification does not account for this
possibility, it’s sometimes necessary to abort a running script. This
causes any ScriptEvaluation or ModuleEvaluation to cease immediately,
emptying the JavaScript execution context stack without triggering any of
the normal mechanisms like finally blocks. [ECMA-262]
User agents may impose resource limitations on scripts, for example CPU
quotas, memory limits, total execution time limits, or bandwidth
limitations. When a script exceeds a limit, the user agent may either
throw a QuotaExceededError exception, abort the script without an
exception, prompt the user, or throttle script execution.
For example, the following script never terminates. A user agent could,
after waiting for a few seconds, prompt the user to either terminate the
script or let it continue.
User agents are encouraged to allow users to disable scripting whenever
the user is prompted either by a script (e.g., using the window.alert()
API) or because of a script’s actions (e.g., because it has exceeded a
time limit).
If scripting is disabled while a script is executing, the script should be
terminated immediately.
User agents may allow users to specifically disable scripts just for the
purposes of closing a browsing context.
For example, the prompt mentioned in the example above could also offer
the user with a mechanism to just close the page entirely, without running
any unload event handlers.
7.1.3.7. Integration with the JavaScript job queue
The JavaScript specification defines the JavaScript job and job queue
abstractions in order to specify certain invariants about how promise
operations execute with a clean JavaScript execution context stack and in
a certain order. However, as of the time of this writing the definition of
EnqueueJob in that specification are not sufficiently flexible to
integrate with HTML as a host environment. [ECMA-262]
This is not strictly true. It is in fact possible, by taking liberal
advantage of the many "implementation defined" sections of the algorithm,
to contort it to our purposes. However, the end result is a mass of messy
indirection and workarounds that essentially bypasses the job queue
infrastructure entirely, albeit in a way that is technically sanctioned
within the bounds of implementation-defined behavior. We do not take this
path, and instead introduce the following willful violation.
As such, user agents must instead use the following definition in place of
that in the JavaScript specification. These ensure that the promise jobs
enqueued by the JavaScript specification are properly integrated into the
user agent’s event loops.
7.1.3.7.1. EnqueueJob(queueName, job, arguments)
When the JavaScript specification says to call the EnqueueJob abstract
operation, the following algorithm must be used in place of JavaScript’s
EnqueueJob:
1. Assert: queueName is "PromiseJobs". ("ScriptJobs" must not be used by
user agents.)
2. Let settings be the settings object of job.[[Realm]]
3. Queue a microtask, on settings’s responsible event loop, to perform
the following steps:
1. Check if we can run script with settings. If this returns "do not
run" then abort these steps.
2. Prepare to run script with settings.
3. Let result be the result of performing the abstract operation
specified by job, using the elements of arguments as its
arguments.
4. Clean up after running script with settings.
5. If result is an abrupt completion, report the exception given by
result.[[Value]].
7.1.3.8. Integration with the JavaScript module system
The JavaScript specification defines a syntax for modules, as well as some
host-agnostic parts of their processing model. This specification defines
the rest of their processing model: how the module system is bootstrapped,
via the script element with type attribute set to "module", and how
modules are fetched, resolved, and executed. [ECMA-262]
Although the JavaScript specification speaks in terms of "scripts" versus
"modules", in general this specification speaks in terms of classic
scripts versus module scripts, since both of them use the script element.
A module map is a map of absolute URLs to values that are either a module
script, null, or a placeholder value "fetching". Module maps are used to
ensure that imported JavaScript modules are only fetched, parsed, and
evaluated once per Document or Worker.
To resolve a module specifier given a module script script and a string
specifier, perform the following steps. It will return either an absolute
URL or failure.
1. Apply the URL parser to specifier. If the result is not failure,
return the result.
2. If specifier does not start with the character U+002F SOLIDUS (/), the
two-character sequence U+002E FULL STOP, U+002F SOLIDUS (./), or the
three-character sequence U+002E FULL STOP, U+002E FULL STOP, U+002F
SOLIDUS (../), return failure and abort these steps.
This restriction is in place so that in the future we can allow custom
module loaders to give special meaning to "bare" import specifiers,
like import "jquery" or import "web/crypto". For now any such imports
will fail, instead of being treated as relative URLs.
3. Return the result of applying the URL parser to specifier with
script’s base URL as the base URL.
7.1.3.8.1. HostResolveImportedModule(referencingModule, specifier)
JavaScript contains an implementation-defined HostResolveImportedModule
abstract operation. User agents must use the following implementation:
[ECMA-262]
1. Let referencing module script be referencingModule.[[HostDefined]].
2. Let module map be referencing module script’s settings object’s module
map.
3. Let url be the result of resolving a module specifier given
referencing module script and specifier. If the result is failure,
throw a TypeError exception and abort these steps.
4. Let resolved module script be the value of the entry in module map
whose key is url. If no such entry exists, or if the value is null or
"fetching", throw a TypeError exception and abort these steps.
5. Return resolved module script’s module record.
7.1.3.9. Runtime script errors
When the user agent is required to report an error for a particular script
script with a particular position line:col, using a particular target
target, it must run these steps, after which the error is either handled
or not handled:
1. If target is in error reporting mode, then abort these steps; the
error is not handled.
2. Let target be in error reporting mode.
3. Let message be a user-agent-defined string describing the error in a
helpful manner.
4. Let error object be the object that represents the error: in the case
of an uncaught exception, that would be the object that was thrown; in
the case of a JavaScript error that would be an Error object. If there
is no corresponding object, then the null value must be used instead.
5. Let location be an absolute URL that corresponds to the resource from
which script was obtained.
The resource containing the script will typically be the file from
which the Document was parsed, e.g., for inline script elements or
event handler content attributes; or the JavaScript file that the
script was in, for external scripts. Even for dynamically-generated
scripts, user agents are strongly encouraged to attempt to keep track
of the original source of a script. For example, if an external script
uses the document.write() API to insert an inline script element
during parsing, the URL of the resource containing the script would
ideally be reported as being the external script, and the line number
might ideally be reported as the line with the document.write() call
or where the string passed to that call was first constructed.
Naturally, implementing this can be somewhat non-trivial.
User agents are similarly encouraged to keep careful track of the
original line numbers, even in the face of document.write() calls
mutating the document as it is parsed, or event handler content
attributes spanning multiple lines.
6. If script has muted errors, then set message to "Script error.", set
location to the empty string, set line and col to 0, and set error
object to null.
7. Let event be a new trusted ErrorEvent object that does not bubble but
is cancelable, and which has the event name error.
8. Initialize event’s message attribute to message.
9. Initialize event’s filename attribute to location.
10. Initialize event’s lineno attribute to line.
11. Initialize event’s colno attribute to col.
12. Initialize event’s error attribute to error object.
13. Dispatch event at target.
14. Let target no longer be in error reporting mode.
15. If event was canceled, then the error is handled. Otherwise, the error
is not handled.
Returning true cancels event per the event handler processing
algorithm.
7.1.3.9.1. Runtime script errors in documents
When the user agent is to report an exception E, the user agent must
report the error for the relevant script, with the problematic position
(line number and column number) in the resource containing the script,
using the global object specified by the script’s settings object as the
target. If the error is still not handled after this, then the error may
be reported to a developer console.
7.1.3.9.2. The ErrorEvent interface
[Constructor(DOMString type, optional ErrorEventInit eventInitDict), Exposed=(Window, Worker)]
interface ErrorEvent : Event {
readonly attribute DOMString message;
readonly attribute DOMString filename;
readonly attribute unsigned long lineno;
readonly attribute unsigned long colno;
readonly attribute any error;
};
dictionary ErrorEventInit : EventInit {
DOMString message = "";
DOMString filename = "";
unsigned long lineno = 0;
unsigned long colno = 0;
any error = null;
};
The message attribute must return the value it was initialized to. It
represents the error message.
The filename attribute must return the value it was initialized to. It
represents the absolute URL of the script in which the error originally
occurred.
The lineno attribute must return the value it was initialized to. It
represents the line number where the error occurred in the script.
The colno attribute must return the value it was initialized to. It
represents the column number where the error occurred in the script.
The error attribute must return the value it was initialized to. Where
appropriate, it is set to the object representing the error (e.g., the
exception object in the case of an uncaught DOM exception).
7.1.3.10. Unhandled promise rejections
In addition to synchronous runtime script errors, scripts may experience
asynchronous promise rejections, tracked via the unhandledrejection and
rejectionhandled events.
When the user agent is to notify about rejected promises on a given
environment settings object settings object, it must run these steps:
1. Let list be a copy of settings object’s about-to-be-notified rejected
promises list.
2. If list is empty, abort these steps.
3. Clear settings object’s about-to-be-notified rejected promises list.
4. Queue a task to run the following substep:
1. For each promise p in list:
1. If p’s [[PromiseIsHandled]] internal slot is true, continue
to the next iteration of the loop.
2. Let event be a new trusted PromiseRejectionEvent object that
does not bubble but is cancelable, and which has the event
name unhandledrejection.
3. Initialise event’s promise attribute to p.
4. Initialise event’s reason attribute to the value of p’s
[[PromiseResult]] internal slot.
5. Dispatch event at settings object’s global object.
6. If the event was canceled, then the promise rejection is
handled. Otherwise, the promise rejection is not handled.
7. If p’s [[PromiseIsHandled]] internal slot is false, add p to
settings object’s outstanding rejected promises weak set.
This algorithm results in promise rejections being marked as handled or
not handled. These concepts parallel handled and not handled script
errors. If a rejection is still not handled after this, then the rejection
may be reported to a developer console.
7.1.3.10.1. The HostPromiseRejectionTracker implementation
ECMAScript contains an implementation-defined
HostPromiseRejectionTracker(promise, operation) abstract operation. User
agents must use the following implementation: [ECMA-262]
1. Let script be the running script.
2. If script has muted errors, terminate these steps.
3. Let settings object be script’s settings object.
4. If operation is "reject",
1. Add promise to settings object’s about-to-be-notified rejected
promises list.
5. If operation is "handle",
1. If settings object’s about-to-be-notified rejected promises list
contains promise, remove promise from that list and abort these
steps.
2. If settings object’s outstanding rejected promises weak set does
not contain promise, abort these steps.
3. Remove promise from settings object’s outstanding rejected
promises weak set.
4. Queue a task to run the following steps:
1. Let event be a new trusted PromiseRejectionEvent object that
does not bubble and is not cancelable, and which has the
event name rejectionhandled.
2. Initialise event’s promise attribute to promise.
3. Initialise event’s reason attribute to the value of
promise’s [[PromiseResult]] internal slot.
4. Dispatch event at settings object’s global object.
7.1.3.10.2. The PromiseRejectionEvent interface
[Constructor(DOMString type, PromiseRejectionEventInit eventInitDict), Exposed=(Window,Worker)]
interface PromiseRejectionEvent : Event {
readonly attribute Promise promise;
readonly attribute any reason;
};
dictionary PromiseRejectionEventInit : EventInit {
required Promise promise;
any reason;
};
The promise attribute must return the value it was initialized to. It
represents the promise which this notification is about.
The reason attribute must return the value it was initialized to. It
represents the rejection reason for the promise.
7.1.3.11. HostEnsureCanCompileStrings(callerRealm, calleeRealm)
JavaScript contains an implementation-defined
HostEnsureCanCompileStrings(callerRealm, calleeRealm) abstract operation.
User agents must use the following implementation: [ECMA-262]
1. Perform ? EnsureCSPDoesNotBlockStringCompilation(callerRealm,
calleeRealm). [CSP3]
7.1.4. Event loops
7.1.4.1. Definitions
To coordinate events, user interaction, scripts, rendering, networking,
and so forth, user agents must use event loops as described in this
section. There are two kinds of event loops: those for browsing contexts,
and those for workers.
There must be at least one browsing context event loop per user agent, and
at most one per unit of related similar-origin browsing contexts.
When there is more than one event loop for a unit of related browsing
contexts, complications arise when a browsing context in that group is
navigated such that it switches from one unit of related similar-origin
browsing contexts to another. This specification does not currently
describe how to handle these complications.
A browsing context event loop always has at least one browsing context. If
such an event loop’s browsing contexts all go away, then the event loop
goes away as well. A browsing context always has an event loop
coordinating its activities.
Worker event loops are simpler: each worker has one event loop, and the
worker processing model manages the event loop’s lifetime.
----------------------------------------------------------------------
An event loop has one or more task queues. A task queue is an ordered list
of tasks, which are algorithms that are responsible for such work as:
Events
Dispatching an Event object at a particular EventTarget object is
often done by a dedicated task.
Not all events are dispatched using the task queue, many are
dispatched during other tasks.
Parsing
The HTML parser tokenizing one or more bytes, and then processing
any resulting tokens, is typically a task.
Callbacks
Calling a callback is often done by a dedicated task.
Using a resource
When an algorithm fetches a resource, if the fetching occurs in a
non-blocking fashion then the processing of the resource once some
or all of the resource is available is performed by a task.
Reacting to DOM manipulation
Some elements have tasks that trigger in response to DOM
manipulation, e.g., when that element is inserted into the
document.
Each task in a browsing context event loop is associated with a Document;
if the task was queued in the context of an element, then it is the
element’s node document; if the task was queued in the context of a
browsing context, then it is the browsing context’s active document at the
time the task was queued; if the task was queued by or for a script then
the document is the responsible document specified by the script’s
settings object.
A task is intended for a specific event loop: the event loop that is
handling tasks for the task’s associated Document or Worker.
When a user agent is to queue a task, it must add the given task to one of
the task queues of the relevant event loop.
Each task is defined as coming from a specific task source. All the tasks
from one particular task source and destined to a particular event loop
(e.g., the callbacks generated by timers of a Document, the events fired
for mouse movements over that Document, the tasks queued for the parser of
that Document) must always be added to the same task queue, but tasks from
different task sources may be placed in different task queues.
For example, a user agent could have one task queue for mouse and key
events (the user interaction task source), and another for everything
else. The user agent could then give keyboard and mouse events preference
over other tasks three quarters of the time, keeping the interface
responsive but not starving other task queues, and never processing events
from any one task source out of order.
Each event loop has a currently running task. Initially, this is null. It
is used to handle reentrancy. Each event loop also has a performing a
microtask checkpoint flag, which must initially be false. It is used to
prevent reentrant invocation of the perform a microtask checkpoint
algorithm.
7.1.4.2. Processing model
An event loop must continually run through the following steps for as long
as it exists:
1. Select the oldest task on one of the event loop’s task queues, if any,
ignoring, in the case of a browsing context event loop, tasks whose
associated Documents are not fully active. The user agent may pick any
task queue. If there is no task to select, then jump to the Microtasks
step below.
2. Set the event loop’s currently running task to the task selected in
the previous step.
3. Run: Run the selected task.
4. Set the event loop’s currently running task back to null.
5. Remove the task that was run in the Run step above from its task
queue.
6. Microtasks: Perform a microtask checkpoint.
7. Update the rendering: If this event loop is a browsing context event
loop (as opposed to a Worker event loop), then run the following
substeps.
1. Let now be the value that would be returned by the Performance
object’s now() method. [HR-TIME-2]
2. Let docs be the list of Document objects associated with the
event loop in question, sorted arbitrarily except that the
following conditions must be met:
* Any Document B that is nested through a Document A must be
listed after A in the list.
* If there are two documents A and B whose browsing contexts
are both nested browsing contexts and their browsing context
containers are both elements in the same Document C, then
the order of A and B in the list must match the relative
tree order of their respective browsing context containers
in C.
In the steps below that iterate over docs, each Document must be
processed in the order it is found in the list.
3. If there is a top-level browsing context B that the user agent
believes would not benefit from having its rendering updated at
this time, then remove from docs all Document objects whose
browsing context’s top-level browsing context is B.
There are many factors that affect the ideal update frequency for
the top-level browsing context including performance, power,
background operation, quality of user experience, refresh rate of
display(s), etc. When in foreground and not constrained by
resources (i.e. performance, battery versus mains power, other
resource limits), the user agent normally prioritizes for maximum
quality of user experience for that set of Documents by matching
update frequency and animation frame callback rate to the current
refresh rate of the current display (usually 60Hz, but refresh
rate may be higher or lower). When accommodating constraints on
resources, the update frequency might automatically run at a
lower rate. Also, if a top-level browsing context is in the
background, the user agent might decide to drop that page to a
much slower 4Hz, or even less.
Another example of why a browser might skip updating the
rendering is to ensure certain tasks are executed immediately
after each other, with only microtask checkpoints interleaved
(and without, e.g., animation frame callbacks interleaved). For
example, a user agent might wish to coalesce callbacks together,
with no intermediate rendering updates. However, when are no
constraints on resources, there must not be an arbitrary
permanent user agent limit on the update rate and animation frame
callback rate (i.e., high refresh rate displays and/or low
latency applications).
4. If there are a nested browsing contexts B that the user agent
believes would not benefit from having their rendering updated at
this time, then remove from docs all Document objects whose
browsing context is in B.
As with top-level browsing contexts, a variety of factors can
influence whether it is profitable for a browser to update the
rendering of nested browsing contexts. For example, a user agent
might wish to spend less resources rendering third-party content,
especially if it is not currently visible to the user or if
resources are constrained. In such cases, the browser could
decide to update the rendering for such content infrequently or
never.
5. For each fully active Document in docs, run the resize steps for
that Document, passing in now as the timestamp. [CSSOM-VIEW]
6. For each fully active Document in docs, run the scroll steps for
that Document, passing in now as the timestamp. [CSSOM-VIEW]
7. For each fully active Document in docs, evaluate media queries
and report changes for that Document, passing in now as the
timestamp. [CSSOM-VIEW]
8. For each fully active Document in docs, run CSS animations and
send events for that Document, passing in now as the timestamp.
[CSS3-ANIMATIONS]
9. For each fully active Document in docs, run the fullscreen
rendering steps for that Document, passing in now as the
timestamp. [FULLSCREEN]
10. For each fully active Document in docs, run the animation frame
callbacks for that Document, passing in now as the timestamp.
11. For each fully active Document in docs, update the rendering or
user interface of that Document and its browsing context to
reflect the current state.
8. If this is a Worker event loop (i.e., one running for a
WorkerGlobalScope), but there are no tasks in the event loop’s task
queues and the WorkerGlobalScope object’s closing flag is true, then
destroy the event loop, aborting these steps, resuming the run a
worker steps.
9. Return to the first step of the event loop.
----------------------------------------------------------------------
Each event loop has a microtask queue. A microtask is a task that is
originally to be queued on the microtask queue rather than a task queue.
There are two kinds of microtasks: solitary callback microtasks, and
compound microtasks.
This specification only has solitary callback microtasks. Specifications
that use compound microtasks have to take extra care to wrap callbacks to
handle spinning the event loop.
When an algorithm requires a microtask to be queued, it must be appended
to the relevant event loop’s microtask queue; the task source of such a
microtask is the microtask task source.
It is possible for a microtask to be moved to a regular task queue, if,
during its initial execution, it spins the event loop. In that case, the
microtask task source is the task source used. Normally, the task source
of a microtask is irrelevant.
When a user agent is to perform a microtask checkpoint, if the performing
a microtask checkpoint flag is false, then the user agent must run the
following steps:
1. Let the performing a microtask checkpoint flag be true.
2. Microtask queue handling: If the event loop’s microtask queue is
empty, jump to the Done step below.
3. Select the oldest microtask on the event loop’s microtask queue.
4. Set the event loop’s currently running task to the task selected in
the previous step.
5. Run: Run the selected task.
This might involve invoking scripted callbacks, which eventually calls
the clean up after running script steps, which call this perform a
microtask checkpoint algorithm again, which is why we use the
performing a microtask checkpoint flag to avoid reentrancy.
6. Set the event loop’s currently running task back to null.
7. Remove the microtask run in the step above from the microtask queue,
and return to the Microtask queue handling step.
8. Done: For each environment settings object whose responsible event
loop is this event loop, notify about rejected promises on that
environment settings object.
9. Cleanup Indexed Database transactions.
10. Let the performing a microtask checkpoint flag be false.
If, while a compound microtask is running, the user agent is required to
execute a compound microtask subtask to run a series of steps, the user
agent must run the following steps:
1. Let parent be the event loop’s currently running task (the currently
running compound microtask).
2. Let subtask be a new task that consists of running the given series of
steps. The task source of such a microtask is the microtask task
source. This is a compound microtask subtask.
3. Set the event loop’s currently running task to subtask.
4. Run subtask.
5. Set the event loop’s currently running task back to parent.
----------------------------------------------------------------------
When an algorithm running in parallel is to await a stable state, the user
agent must queue a microtask that runs the following steps, and must then
stop executing (execution of the algorithm resumes when the microtask is
run, as described in the following steps):
1. Run the algorithm’s synchronous section.
2. Resumes execution of the algorithm in parallel, if appropriate, as
described in the algorithm’s steps.
Steps in synchronous sections are marked with ⌛.
----------------------------------------------------------------------
When an algorithm says to spin the event loop until a condition goal is
met, the user agent must run the following steps:
1. Let task be the event loop’s currently running task.
This might be a microtask, in which case it is a solitary callback
microtask. It could also be a compound microtask subtask, or a regular
task that is not a microtask. It will not be a compound microtask.
2. Let task source be task’s task source.
3. Let old stack be a copy of the JavaScript execution context stack.
4. Empty the JavaScript execution context stack.
5. Run the global script clean-up jobs.
6. Perform a microtask checkpoint.
7. Stop task, allowing whatever algorithm that invoked it to resume, but
continue these steps in parallel.
This causes one of the following algorithms to continue: the event
loop’s main set of steps, the perform a microtask checkpoint
algorithm, or the execute a compound microtask subtask algorithm to
continue.
8. Wait until the condition goal is met.
9. Queue a task to continue running these steps, using the task source
task source. Wait until this new task runs before continuing these
steps.
10. Replace the JavaScript execution context stack with the old stack.
11. Return to the caller.
----------------------------------------------------------------------
Some of the algorithms in this specification, for historical reasons,
require the user agent to pause while running a task until a condition
goal is met. This means running the following steps:
1. If necessary, update the rendering or user interface of any Document
or browsing context to reflect the current state.
2. Wait until the condition goal is met. While a user agent has a paused
task, the corresponding event loop must not run further tasks, and any
script in the currently running task must block. User agents should
remain responsive to user input while paused, however, albeit in a
reduced capacity since the event loop will not be doing anything.
7.1.4.3. Generic task sources
The following task sources are used by a number of mostly unrelated
features in this and other specifications.
The DOM manipulation task source
This task source is used for features that react to DOM
manipulations, such as things that happen in a non-blocking
fashion when an element is inserted into the document.
The user interaction task source
This task source is used for features that react to user
interaction, for example keyboard or mouse input.
Events sent in response to user input (e.g., click events) must be
fired using tasks queued with the user interaction task source.
[UIEVENTS]
The networking task source
This task source is used for features that trigger in response to
network activity.
The history traversal task source
This task source is used to queue calls to history.back() and
similar APIs.
7.1.5. Events
7.1.5.1. Event handlers
Many objects can have event handlers specified. These act as non-capture
event listeners for the object on which they are specified. [DOM41]
An event handler has a name, which always starts with "on" and is followed
by the name of the event for which it is intended.
An event handler has a value, which is either null, or is a callback
object, or is an internal raw uncompiled handler. The EventHandler
callback function type describes how this is exposed to scripts.
Initially, an event handler’s value must be set to null.
Event handlers are exposed in one of two ways.
The first way, common to all event handlers, is as an event handler IDL
attribute.
The second way is as an event handler content attribute. Event handlers on
HTML elements and some of the event handlers on Window objects are exposed
in this way.
----------------------------------------------------------------------
An event handler IDL attribute is an IDL attribute for a specific event
handler. The name of the IDL attribute is the same as the name of the
event handler.
Event handler IDL attributes, on setting, must set the corresponding event
handler to their new value, and on getting, must return the result of
getting the current value of the event handler in question (this can throw
an exception, in which case the getting propagates it to the caller, it
does not catch it).
If an event handler IDL attribute exposes an event handler of an object
that doesn’t exist, it must always return null on getting and must do
nothing on setting.
This can happen in particular for event handler IDL attribute on body
elements that do not have corresponding Window objects.
Certain event handler IDL attributes have additional requirements, in
particular the onmessage attribute of MessagePort objects.
----------------------------------------------------------------------
An event handler content attribute is a content attribute for a specific
event handler. The name of the content attribute is the same as the name
of the event handler.
Event handler content attributes, when specified, must contain valid
JavaScript code which, when parsed, would match the FunctionBody
production after automatic semicolon insertion. [ECMA-262]
When an event handler content attribute is set, execute the following
steps:
1. If the Should element’s inline behavior be blocked by Content Security
Policy? algorithm returns "Blocked" when executed upon the attribute’s
element "script attribute", and the attribute’s value, then abort
these steps. [CSP3]
2. Set the corresponding event handler to an internal raw uncompiled
handler consisting of the attribute’s new value and the script
location where the attribute was set to this value.
When an event handler content attribute is removed, the user agent must
set the corresponding event handler to null.
----------------------------------------------------------------------
When an event handler H of an element or object T implementing the
EventTarget interface is first set to a non-null value, the user agent
must append an event listener to the list of event listeners associated
with T with type set to the event handler event type corresponding to H
and callback set to the event handler processing algorithm defined below.
[DOM41]
The callback is emphatically not the event handler itself. Every event
handler ends up registering the same callback the algorithm defined below,
which takes care of invoking the right callback, and processing the
callback’s return value.
This only happens the first time the event handler’s value is set. Since
listeners are called in the order they were registered, the order of event
listeners for a particular event type will always be first the event
listeners registered with addEventListener() before the first time the
event handler was set to a non-null value, then the callback to which it
is currently set, if any, and finally the event listeners registered with
addEventListener() after the first time the event handler was set to a
non-null value.
This example demonstrates the order in which event listeners are invoked.
If the button in this example is clicked by the user, the page will show
four alerts, with the text "ONE", "TWO", "THREE", and "FOUR" respectively.
Start Demo
The interfaces implemented by the event object do not influence whether an
event handler is triggered or not.
The event handler processing algorithm for an event handler H and an Event
object E is as follows:
1. Let callback be the result of getting the current value of the event
handler H.
2. If callback is null, then abort these steps.
3. Process the Event object E as follows:
If E is an ErrorEvent object and the event handler IDL
attribute’s type is OnErrorEventHandler
Invoke callback with five arguments, the first one having
the value of E’s message attribute, the second having the
value of E’s filename attribute, the third having the
value of E’s lineno attribute, the fourth having the
value of E’s colno attribute, the fifth having the value
of E’s error attribute, and with the callback this value
set to E’s currentTarget. Let return value be the
callback’s return value. [WEBIDL]
Otherwise
Invoke callback with one argument, the value of which is
the Event object E, with the callback this value set to
E’s currentTarget. Let return value be the callback’s
return value. [WEBIDL]
In this step, invoke means to invoke the Web IDL callback function.
If an exception gets thrown by the callback, end these steps and allow
the exception to propagate. (It will propagate to the DOM event
dispatch logic, which will then report the exception.)
4. Process return value as follows:
If the event type is mouseover
If the event type is error and E is an ErrorEvent object
If return value is a Web IDL boolean true value, then
cancel the event.
If the event type is beforeunload
The event handler IDL attribute’s type is
OnBeforeUnloadEventHandler, and the return value will
therefore have been coerced into either the value null or
a DOMString.
If the return value is null, then cancel the event.
Otherwise, if the Event object E is a BeforeUnloadEvent
object, and the Event object E’s returnValue attribute’s
value is the empty string, then set the returnValue
attribute’s value to return value.
Otherwise
If return value is a Web IDL boolean false value, then
cancel the event.
----------------------------------------------------------------------
The EventHandler callback function type represents a callback used for
event handlers. It is represented in Web IDL as follows:
[TreatNonObjectAsNull]
callback EventHandlerNonNull = any (Event event);
typedef EventHandlerNonNull? EventHandler;
In JavaScript, any Function object implements this interface.
For example, the following document fragment:
...leads to an alert saying "[object Window]" when the document is loaded,
and an alert saying "[object HTMLBodyElement]" whenever the user clicks
something in the page.
The return value of the function affects whether the event is canceled or
not: as described above, if the return value is false, the event is
canceled (except for mouseover events, where the return value has to be
true to cancel the event). With beforeunload events, the value is instead
used to determine whether or not to prompt about unloading the document.
For historical reasons, the onerror handler has different arguments:
[TreatNonObjectAsNull]
callback OnErrorEventHandlerNonNull = any ((Event or DOMString) event, optional DOMString source, optional unsigned long lineno, optional unsigned long column, optional any error);
typedef OnErrorEventHandlerNonNull? OnErrorEventHandler;
Similarly, the onbeforeunload handler has a different return value:
[TreatNonObjectAsNull]
callback OnBeforeUnloadEventHandlerNonNull = DOMString? (Event event);
typedef OnBeforeUnloadEventHandlerNonNull? OnBeforeUnloadEventHandler;
----------------------------------------------------------------------
An internal raw uncompiled handler is a tuple with the following
information:
* An uncompiled script body
* A location where the script body originated, in case an error needs to
be reported
When the user agent is to get the current value of the event handler H, it
must run these steps:
1. If H’s value is an internal raw uncompiled handler, run these
substeps:
1. If H is an element’s event handler, then let element be the
element, and document be the element’s node document.
Otherwise, H is a Window object’s event handler: let element be
null, and let document be the Document most recently associated
with that Window object.
2. If document does not have a browsing context, or if scripting is
enabled for document’s browsing context, then return null.
3. Let body be the uncompiled script body in the internal raw
uncompiled handler.
4. Let location be the location where the script body originated, as
given by the internal raw uncompiled handler.
5. If element is not null and element has a form owner, let form
owner be that form owner. Otherwise, let form owner be null.
6. Let script settings be the environment settings object created
for the Window object with which document is currently
associated.
7. If body is not parsable as FunctionBody or if parsing detects an
early error, then follow these substeps:
1. Set H’s value to null.
2. Report the error for the appropriate script and with the
appropriate position (line number and column number) given
by location, using the global object specified by script
settings as the target. If the error is still not handled
after this, then the error may be reported to a developer
console.
3. Return null.
8. If body begins with a Directive Prologue that contains a Use
Strict Directive then let strict be true, otherwise let strict be
false.
9. Let function be the result of calling FunctionCreate, with
arguments:
kind
Normal
ParameterList
If H is an onerror event handler of a Window
object
Let the function have five arguments,
named event, source, lineno, colno, and
error.
Otherwise
Let the function have a single argument
called event.
Body
The result of parsing body above.
Scope
1. If H is an element’s event handler, then let
Scope be the result of
NewObjectEnvironment(document, the global
environment).
Otherwise, H is a Window object’s event
handler: let Scope be the global environment.
2. If form owner is not null, let Scope be
NewObjectEnvironment(form owner, Scope).
3. If element is not null, let Scope be the
NewObjectEnvironment(element, Scope).
Strict
The value of strict.
10. Set H’s value to function.
2. Return H’s value.
7.1.5.2. Event handlers on elements, Document objects, and Window objects
The following are the event handlers (and their corresponding event
handler event types) that must be supported by all HTML elements, as both
event handler content attributes and event handler IDL attributes; and
that must be supported by all Document and Window objects, as event
handler IDL attributes:
Event handler Event handler event type
onabort abort
onauxclick auxclick
oncancel cancel
oncanplay canplay
oncanplaythrough canplaythrough
onchange change
onclick click
onclose close
oncuechange cuechange
ondblclick dblclick
ondrag drag
ondragend dragend
ondragenter dragenter
ondragexit dragexit
ondragleave dragleave
ondragover dragover
ondragstart dragstart
ondrop drop
ondurationchange durationchange
onemptied emptied
onended ended
oninput input
oninvalid invalid
onkeydown keydown
onkeypress keypress
onkeyup keyup
onloadeddata loadeddata
onloadedmetadata loadedmetadata
onloadend loadend
onloadstart loadstart
onmousedown mousedown
onmouseenter mouseenter
onmouseleave mouseleave
onmousemove mousemove
onmouseout mouseout
onmouseover mouseover
onmouseup mouseup
onwheel wheel
onpause pause
onplay play
onplaying playing
onprogress progress
onratechange ratechange
onreset reset
onseeked seeked
onseeking seeking
onselect select
onshow show
onstalled stalled
onsubmit submit
onsuspend suspend
ontimeupdate timeupdate
ontoggle toggle
onvolumechange volumechange
onwaiting waiting
----------------------------------------------------------------------
The following are the event handlers (and their corresponding event
handler event types) that must be supported by all HTML elements other
than body and frameset elements, as both event handler content attributes
and event handler IDL attributes; that must be supported by all Document
objects, as event handler IDL attributes; and that must be supported by
all Window objects, as event handler IDL attributes on the Window objects
themselves, and with corresponding event handler content attributes and
event handler IDL attributes exposed on all body and frameset elements
that are owned by that Window object’s Documents:
Event handler Event handler event type
onblur blur
onerror error
onfocus focus
onload load
onresize resize
onscroll scroll
----------------------------------------------------------------------
The following are the event handlers (and their corresponding event
handler event types) that must be supported by Window objects, as event
handler IDL attributes on the Window objects themselves, and with
corresponding event handler content attributes and event handler IDL
attributes exposed on all body and frameset elements that are owned by
that Window object’s Documents:
Event handler Event handler event type
onafterprint afterprint
onbeforeprint beforeprint
onbeforeunload beforeunload
onhashchange hashchange
onlanguagechange languagechange
onmessage message
onoffline offline
ononline online
onpagehide pagehide
onpageshow pageshow
onrejectionhandled rejectionhandled
onpopstate popstate
onstorage storage
onunhandledrejection unhandledrejection
onunload unload
----------------------------------------------------------------------
The following are the event handlers (and their corresponding event
handler event types) that must be supported by all HTML elements, as both
event handler content attributes and event handler IDL attributes and that
must be supported by all Document objects, as event handler IDL
attributes:
Event handler Event handler event type
oncut cut
oncopy copy
onpaste paste
----------------------------------------------------------------------
The following are the event handlers (and their corresponding event
handler event types) that must be supported on Document objects as event
handler IDL attributes:
Event handler Event handler event type
onreadystatechange readystatechange
7.1.5.2.1. IDL definitions
[NoInterfaceObject]
interface GlobalEventHandlers {
attribute EventHandler onabort;
attribute EventHandler onblur;
attribute EventHandler oncancel;
attribute EventHandler oncanplay;
attribute EventHandler oncanplaythrough;
attribute EventHandler onchange;
attribute EventHandler onclick;
attribute EventHandler onclose;
attribute EventHandler oncuechange;
attribute EventHandler ondblclick;
attribute EventHandler ondrag;
attribute EventHandler ondragend;
attribute EventHandler ondragenter;
attribute EventHandler ondragexit;
attribute EventHandler ondragleave;
attribute EventHandler ondragover;
attribute EventHandler ondragstart;
attribute EventHandler ondrop;
attribute EventHandler ondurationchange;
attribute EventHandler onemptied;
attribute EventHandler onended;
attribute OnErrorEventHandler onerror;
attribute EventHandler onfocus;
attribute EventHandler oninput;
attribute EventHandler oninvalid;
attribute EventHandler onkeydown;
attribute EventHandler onkeypress;
attribute EventHandler onkeyup;
attribute EventHandler onload;
attribute EventHandler onloadeddata;
attribute EventHandler onloadedmetadata;
attribute EventHandler onloadstart;
attribute EventHandler onmousedown;
[LenientThis] attribute EventHandler onmouseenter;
[LenientThis] attribute EventHandler onmouseleave;
attribute EventHandler onmousemove;
attribute EventHandler onmouseout;
attribute EventHandler onmouseover;
attribute EventHandler onmouseup;
attribute EventHandler onwheel;
attribute EventHandler onpause;
attribute EventHandler onplay;
attribute EventHandler onplaying;
attribute EventHandler onprogress;
attribute EventHandler onratechange;
attribute EventHandler onreset;
attribute EventHandler onresize;
attribute EventHandler onscroll;
attribute EventHandler onseeked;
attribute EventHandler onseeking;
attribute EventHandler onselect;
attribute EventHandler onshow;
attribute EventHandler onstalled;
attribute EventHandler onsubmit;
attribute EventHandler onsuspend;
attribute EventHandler ontimeupdate;
attribute EventHandler ontoggle;
attribute EventHandler onvolumechange;
attribute EventHandler onwaiting;
};
[NoInterfaceObject]
interface WindowEventHandlers {
attribute EventHandler onafterprint;
attribute EventHandler onbeforeprint;
attribute OnBeforeUnloadEventHandler onbeforeunload;
attribute EventHandler onhashchange;
attribute EventHandler onlanguagechange;
attribute EventHandler onmessage;
attribute EventHandler onoffline;
attribute EventHandler ononline;
attribute EventHandler onpagehide;
attribute EventHandler onpageshow;
attribute EventHandler onrejectionhandled;
attribute EventHandler onpopstate;
attribute EventHandler onstorage;
attribute EventHandler onunhandledrejection;
attribute EventHandler onunload;
};
[NoInterfaceObject]
interface DocumentAndElementEventHandlers {
attribute EventHandler oncopy;
attribute EventHandler oncut;
attribute EventHandler onpaste;
};
7.1.5.3. Event firing
Certain operations and methods are defined as firing events on elements.
For example, the click() method on the HTMLElement interface is defined as
firing a click event on the element. [UIEVENTS]
Firing a simple event named e means that a trusted event with the name e,
which does not bubble (except where otherwise stated) and is not
cancelable (except where otherwise stated), and which uses the Event
interface, must be created and dispatched at the given target.
Firing a synthetic mouse event named e means that an event with the name
e, which is trusted (except where otherwise stated), does not bubble
(except where otherwise stated), is not cancelable (except where otherwise
stated), and which uses the MouseEvent interface, must be created and
dispatched at the given target. The event object must have its screenX,
screenY, clientX, clientY, and button attributes initialized to 0, its
ctrlKey, shiftKey, altKey, and metaKey attributes initialized according to
the current state of the key input device, if any (false for any keys that
are not available), its detail attribute initialized to 1, its
relatedTarget attribute initialized to null (except where otherwise
stated), and its view attribute initialized to the Window object of the
Document object of the given target node, if any, or else null. The
getModifierState() method on the object must return values appropriately
describing the state of the key input device at the time the event is
created.
Firing a click event means firing a synthetic mouse event named click,
which bubbles and is cancelable.
The default action of these events is to do nothing except where otherwise
stated.
7.1.5.4. Events and the Window object
When an event is dispatched at a DOM node in a Document in a browsing
context, if the event is not a load event, the user agent must act as if,
for the purposes of event dispatching, the Window object is the parent of
the Document object. [DOM41]
7.2. The WindowOrWorkerGlobalScope mixin
The WindowOrWorkerGlobalScope mixin is for use of APIs that are to be
exposed on Window and WorkerGlobalScope objects.
Other specifications are encouraged to further extend it using partial
interface WindowOrWorkerGlobalScope { … }; along with an appropriate
reference.
typedef (DOMString or Function) TimerHandler;
[NoInterfaceObject, Exposed=(Window, Worker)]
interface WindowOrWorkerGlobalScope {
[Replaceable] readonly attribute USVString origin;
// Base64 utility methods (WindowBase64)
DOMString btoa(DOMString btoa);
DOMString atob(DOMString atob);
// Timers (WindowTimers)
long setTimeout((Function or DOMString) handler, optional long timeout = 0, any... arguments);
void clearTimeout(optional long handle = 0);
long setInterval((Function or DOMString) handler, optional long timeout = 0, any... arguments);
void clearInterval(optional long handle = 0);
// ImageBitmap, Images (ImageBitmapFactories)
Promise createImageBitmap(ImageBitmapSource image);
Promise createImageBitmap(ImageBitmapSource image, long sx, long sy, long sw, long sh);
};
Window implements WindowOrWorkerGlobalScope;
WorkerGlobalScope implements WindowOrWorkerGlobalScope;
origin = self . origin
Returns the global object’s origin, serialized as string.
Developers are strongly encouraged to use self.origin over
location.origin. self.origin returns the origin of the environment, while
location.origin returns URL of the environment.
Imagine the following script executing in a document on
https://example.com:
var frame = document.createElement("iframe")
frame.onload = function() {
var frameWin = frame.contentWindow
console.log(frameWin.location.origin) // "null"
console.log(frameWin.origin) // "https://example.com"
}
document.body.appendChild(frame)
self.origin is a more reliable security indicator.
The origin attribute’s getter must return this object’s relevant setting
object’s origin, serialized.
7.3. Base64 utility methods
The atob() and btoa() methods allow authors to transform content to and
from the base64 encoding.
In these APIs, for mnemonic purposes, the "b" can be considered to stand
for "binary", and the "a" for "ASCII". In practice, though, for primarily
historical reasons, both the input and output of these functions are
Unicode strings.
result = window . btoa( data )
Takes the input data, in the form of a Unicode string containing
only characters in the range U+0000 to U+00FF, each representing a
binary byte with values 0x00 to 0xFF respectively, and converts it
to its base64 representation, which it returns.
Throws an InvalidCharacterError exception if the input string
contains any out-of-range characters.
result = window . atob( data )
Takes the input data, in the form of a Unicode string containing
base64-encoded binary data, decodes it, and returns a string
consisting of characters in the range U+0000 to U+00FF, each
representing a binary byte with values 0x00 to 0xFF respectively,
corresponding to that binary data.
Throws an InvalidCharacterError exception if the input string is
not valid base64 data.
The btoa() method must throw an InvalidCharacterError exception if the
method’s first argument contains any character whose code point is greater
than U+00FF. Otherwise, the user agent must convert that argument to a
sequence of octets whose nth octet is the eight-bit representation of the
code point of the nth character of the argument, and then must apply the
base64 algorithm to that sequence of octets, and return the result.
[RFC4648]
The atob() method must run the following steps to parse the string passed
in the method’s first argument:
1. Let input be the string being parsed.
2. Let position be a pointer into input, initially pointing at the start
of the string.
3. Remove all space characters from input.
4. If the length of input divides by 4 leaving no remainder, then: if
input ends with one or two U+003D EQUALS SIGN (=) characters, remove
them from input.
5. If the length of input divides by 4 leaving a remainder of 1, throw an
InvalidCharacterError exception and abort these steps.
6. If input contains a character that is not in the following list of
characters and character ranges, throw an InvalidCharacterError
exception and abort these steps:
* U+002B PLUS SIGN (+)
* U+002F SOLIDUS (/)
* Alphanumeric ASCII characters
7. Let output be a string, initially empty.
8. Let buffer be a buffer that can have bits appended to it, initially
empty.
9. While position does not point past the end of input, run these
substeps:
1. Find the character pointed to by position in the first column of
the following table. Let n be the number given in the second cell
of the same row.
Character Number
A 0
B 1
C 2
D 3
E 4
F 5
G 6
H 7
I 8
J 9
K 10
L 11
M 12
N 13
O 14
P 15
Q 16
R 17
S 18
T 19
U 20
V 21
W 22
X 23
Y 24
Z 25
a 26
b 27
c 28
d 29
e 30
f 31
g 32
h 33
i 34
j 35
k 36
l 37
m 38
n 39
o 40
p 41
q 42
r 43
s 44
t 45
u 46
v 47
w 48
x 49
y 50
z 51
0 52
1 53
2 54
3 55
4 56
5 57
6 58
7 59
8 60
9 61
+ 62
/ 63
2. Append to buffer the six bits corresponding to number, most
significant bit first.
3. If buffer has accumulated 24 bits, interpret them as three 8-bit
big-endian numbers. Append the three characters with code points
equal to those numbers to output, in the same order, and then
empty buffer.
4. Advance position by one character.
10. If buffer is not empty, it contains either 12 or 18 bits. If it
contains 12 bits, discard the last four and interpret the remaining
eight as an 8-bit big-endian number. If it contains 18 bits, discard
the last two and interpret the remaining 16 as two 8-bit big-endian
numbers. Append the one or two characters with code points equal to
those one or two numbers to output, in the same order.
The discarded bits mean that, for instance, atob("YQ") and atob("YR")
both return "a".
11. Return output.
7.4. Dynamic markup insertion
APIs for dynamically inserting markup into the document interact with the
parser, and thus their behavior varies depending on whether they are used
with HTML documents (and the HTML parser) or XML documents (and the XML
parser).
Document objects have a throw-on-dynamic-markup-insertion counter, which
is used in conjunction with the create an element for the token algorithm
to prevent custom element constructors from being able to use
document.open(), document.close(), and document.write() when they are
invoked by the parser. Initially, the counter must be set to zero.
7.4.1. Opening the input stream
The open() method comes in several variants with different numbers of
arguments.
document = document . open( [ type [, replace ] ] )
Causes the Document to be replaced in-place, as if it was a new
Document object, but reusing the previous object, which is then
returned.
If the type argument is omitted or has the value "text/html", then
the resulting Document has an HTML parser associated with it,
which can be given data to parse using document.write().
Otherwise, all content passed to document.write() will be parsed
as plain text.
If the replace argument is present and has the value "replace",
the existing entries in the session history for the Document
object are removed.
The method has no effect if the Document is still being parsed.
Throws an "InvalidStateError" DOMException if the Document is an
XML document.
window = document . open( url, name, features [, replace ] )
Works like the window.open() method.
Document objects have an ignore-opens-during-unload counter, which is used
to prevent scripts from invoking the document.open() method (directly or
indirectly) while the document is being unloaded. Initially, the counter
must be set to zero.
When called with two arguments (or fewer), the document.open() method must
act as follows:
1. If the Document object is an XML document, then throw an
"InvalidStateError" DOMException and abort these steps.
2. If the Document object is not an active document, then abort these
steps.
3. If the origin of the Document is not equal to the origin of the
responsible document specified by the entry settings object, throw a
"SecurityError" DOMException and abort these steps.
4. Let type be the value of the first argument.
5. If the second argument is an ASCII case-insensitive match for the
value "replace", then let replace be true.
Otherwise, if the browsing context’s session history contains only one
Document, and that was the about:blank Document created when the
browsing context was created, and that Document has never had the
unload a document algorithm invoked on it (e.g., by a previous call to
document.open()), then let replace be true.
Otherwise, let replace be false.
6. If the Document has an active parser whose script nesting level is
greater than zero, then the method does nothing. Abort these steps and
return the Document object on which the method was invoked.
This basically causes document.open() to be ignored when it’s called
in an inline script found during parsing, while still letting it have
an effect when called from a non-parser task such as a timer callback
or event handler.
7. Similarly, if the Document's ignore-opens-during-unload counter is
greater than zero, then the method does nothing. Abort these steps and
return the Document object on which the method was invoked.
This basically causes document.open() to be ignored when it’s called
from a beforeunload pagehide, or unload event handler while the
Document is being unloaded.
8. Set the Document's salvageable state to false.
9. Prompt to unload the Document object. If the user refused to allow the
document to be unloaded, then abort these steps and return the
Document object on which the method was invoked.
10. Unload the Document object, with the recycle parameter set to true.
11. Abort the Document.
12. Unregister all event listeners registered on the Document node and its
descendants.
13. Remove any tasks associated with the Document in any task source.
14. Remove all child nodes of the document, without firing any mutation
events.
15. Call the JavaScript InitializeHostDefinedRealm() abstract operation
with the following customizations:
* For the global object, create a new Window object window.
* For the global this value, use the current browsing context’s
associated WindowProxy.
* Let realm execution context be the created JavaScript execution
context.
16. Set window’s associated Document to the Document.
17. Set up a browsing context environment settings object with realm
execution context.
18. Replace the Document's singleton objects with new instances of those
objects, created in window’s Realm. (This includes in particular the
History and Navigator objects, the various BarProp objects, the two
Storage objects, the various HTMLCollection objects, and objects
defined by other specifications, like Selection. It also includes all
the Web IDL prototypes in the JavaScript binding, including the
Document object’s prototype.)
19. Change the document’s character encoding to UTF-8.
20. If the Document is ready for post-load tasks, then set the Document
object’s reload override flag and set the Document's reload override
buffer to the empty string.
21. Set the Document's salvageable state back to true.
22. Change the document’s URL to the URL of the responsible document
specified by the entry settings object.
23. If the Document's iframe load in progress flag is set, set the
Document's mute iframe load flag.
24. Create a new HTML parser and associate it with the document. This is a
script-created parser (meaning that it can be closed by the
document.open() and document.close() methods, and that the tokenizer
will wait for an explicit call to document.close() before emitting an
end-of-file token). The encoding confidence is irrelevant.
25. Set the current document readiness of the document to "loading".
26. If type is an ASCII case-insensitive match for the string "replace",
then, for historical reasons, set it to the string "text/html".
Otherwise:
If the type string contains a U+003B SEMICOLON character (;), remove
the first such character and all characters from it up to the end of
the string.
Strip leading and trailing white space from type.
27. If type is not now an ASCII case-insensitive match for the string
"text/html", then act as if the tokenizer had emitted a start tag
token with the tag name "pre" followed by a single U+000A LINE FEED
(LF) character, then switch the HTML parser’s tokenizer to the
§8.2.4.5 PLAINTEXT state.
28. Remove all the entries in the browsing context’s session history after
the current entry. If the current entry is the last entry in the
session history, then no entries are removed.
This doesn’t necessarily have to affect the user agent’s user
interface.
29. Remove any tasks queued by the history traversal task source that are
associated with any Document objects in the top-level browsing
context’s document family.
30. Remove any earlier entries that share the same Document.
31. If replace is false, then add a new entry, just before the last entry,
and associate with the new entry the text that was parsed by the
previous parser associated with the Document object, as well as the
state of the document at the start of these steps. This allows the
user to step backwards in the session history to see the page before
it was blown away by the document.open() call. This new entry does not
have a Document object, so a new one will be created if the session
history is traversed to that entry.
32. Set the Document's fired unload flag to false. (It could have been set
to true during the unload step above.)
33. Finally, set the insertion point to point at just before the end of
the input stream (which at this point will be empty).
34. Return the Document on which the method was invoked.
The document.open() method does not affect whether a Document is ready for
post-load tasks or completely loaded.
When called with four arguments, the open() method on the Document object
must call the open() method on the Window object of the Document object,
with the same arguments as the original call to the open() method, and
return whatever that method returned. If the Document object has no Window
object, then the method must throw an "InvalidAccessError" DOMException.
7.4.2. Closing the input stream
document . close()
Closes the input stream that was opened by the document.open()
method.
Throws an InvalidStateError exception if the Document is an XML
document.
The close() method must run the following steps:
1. If the Document object is an XML document, then throw an
InvalidStateError exception and abort these steps.
2. If there is no script-created parser associated with the document,
then abort these steps.
3. Insert an explicit "EOF" character at the end of the parser’s input
stream.
4. If there is a pending parsing-blocking script, then abort these steps.
5. Run the tokenizer, processing resulting tokens as they are emitted,
and stopping when the tokenizer reaches the explicit "EOF" character
or spins the event loop.
7.4.3. document.write()
document . write(text...)
In general, adds the given string(s) to the Document’s input
stream.
This method has very idiosyncratic behavior. In some cases, this
method can affect the state of the HTML parser while the parser is
running, resulting in a DOM that does not correspond to the source
of the document (e.g., if the string written is the string
"<![CDATA[" or "<!--"). In other cases, the call can clear the
current page first, as if document.open() had been called. In yet
more cases, the method is simply ignored, or throws an exception.
To make matters worse, the exact behavior of this method can in
some cases be dependent on network latency, which can lead to
failures that are very hard to debug. For all these reasons, use
of this method is strongly discouraged.
This method throws an InvalidStateError exception when invoked on
XML documents.
Document objects have an ignore-destructive-writes counter, which is used
in conjunction with the processing of script elements to prevent external
scripts from being able to use document.write() to blow away the document
by implicitly calling document.open(). Initially, the counter must be set
to zero.
The document.write(...) method must act as follows:
1. If the method was invoked on an XML document, throw an
InvalidStateError exception and abort these steps.
2. If the Document object is not an active document, then abort these
steps.
3. If the insertion point is undefined and either the Document’s
ignore-opens-during-unload counter is greater than zero or the
Document’s ignore-destructive-writes counter is greater than zero,
abort these steps.
4. If the insertion point is undefined, call the open() method on the
document object (with no arguments). If the user refused to allow the
document to be unloaded, then abort these steps. Otherwise, the
insertion point will point at just before the end of the (empty) input
stream.
5. Insert the string consisting of the concatenation of all the arguments
to the method into the input stream just before the insertion point.
6. If the Document object’s reload override flag is set, then append the
string consisting of the concatenation of all the arguments to the
method to the Document’s reload override buffer.
7. If there is no pending parsing-blocking script, have the HTML parser
process the characters that were inserted, one at a time, processing
resulting tokens as they are emitted, and stopping when the tokenizer
reaches the insertion point or when the processing of the tokenizer is
aborted by the tree construction stage (this can happen if a script
end tag token is emitted by the tokenizer).
If the document.write() method was called from script executing inline
(i.e., executing because the parser parsed a set of script tags), then
this is a reentrant invocation of the parser.
8. Finally, return from the method.
7.4.4. document.writeln()
document . writeln(text...)
Adds the given string(s) to the Document’s input stream, followed
by a newline character. If necessary, calls the open() method
implicitly first.
This method throws an InvalidStateError exception when invoked on
XML documents.
The document.writeln(...) method, when invoked, must act as if the
document.write() method had been invoked with the same argument(s), plus
an extra argument consisting of a string containing a single line feed
character (U+000A).
7.5. Timers
The setTimeout() and setInterval() methods allow authors to schedule
timer-based callbacks.
handle = window . setTimeout( handler [, timeout [, arguments... ] ] )
Schedules a timeout to run handler after timeout milliseconds. Any
arguments are passed straight through to the handler.
handle = window . setTimeout( code [, timeout ] )
Schedules a timeout to compile and run code after timeout
milliseconds.
window . clearTimeout( handle )
Cancels the timeout set with setTimeout() or setInterval()
identified by handle.
handle = window . setInterval( handler [, timeout [, arguments... ] ] )
Schedules a timeout to run handler every timeout milliseconds. Any
arguments are passed straight through to the handler.
handle = window . setInterval( code [, timeout ] )
Schedules a timeout to compile and run code every timeout
milliseconds.
window . clearInterval( handle )
Cancels the timeout set with setInterval() or setTimeout()
identified by handle.
Timers can be nested; after five such nested timers, however, the interval
is forced to be at least four milliseconds.
This API does not guarantee that timers will run exactly on schedule.
Delays due to CPU load, other tasks, etc, are to be expected.
Objects that implement the WindowTimers interface have a list of active
timers. Each entry in this lists is identified by a number, which must be
unique within the list for the lifetime of the object that implements the
WindowTimers interface.
----------------------------------------------------------------------
The setTimeout() method must return the value returned by the timer
initialization steps, passing them the method’s arguments, the object on
which the method for which the algorithm is running is implemented (a
Window or WorkerGlobalScope object) as the method context, and the repeat
flag set to false.
The setInterval() method must return the value returned by the timer
initialization steps, passing them the method’s arguments, the object on
which the method for which the algorithm is running is implemented (a
Window or WorkerGlobalScope object) as the method context, and the repeat
flag set to true.
The clearTimeout() and clearInterval() methods must clear the entry
identified as handle from the list of active timers of the WindowTimers
object on which the method was invoked, if any, where handle is the
argument passed to the method. (If handle does not identify an entry in
the list of active timers of the WindowTimers object on which the method
was invoked, the method does nothing.)
Because clearTimeout() and clearInterval() clear entries from the same
list, either method can be used to clear timers created by setTimeout() or
setInterval().
----------------------------------------------------------------------
The timer initialization steps, which are invoked with some method
arguments, a method context, a repeat flag which can be true or false, and
optionally (and only if the repeat flag is true) a previous handle, are as
follows:
1. Let method context proxy be method context if that is a
WorkerGlobalScope object, or else the WindowProxy that corresponds to
method context.
2. If previous handle was provided, let handle be previous handle;
otherwise, let handle be a user-agent-defined integer that is greater
than zero that will identify the timeout to be set by this call in the
list of active timers.
3. If previous handle was not provided, add an entry to the list of
active timers for handle.
4. Let callerRealm be the current Realm Record, and calleeRealm be method
context’s JavaScript realm.
5. Let task be a task that runs the following substeps:
1. If the entry for handle in the list of active timers has been
cleared, then abort this task’s substeps.
2. Run the appropriate set of steps from the following list:
If the first method argument is a Function
Invoke the Function. Use the third and subsequent
method arguments (if any) as the arguments for
invoking the Function. Use method context proxy as
the Callback this value. [ECMA-262]
Otherwise
1. Perform
HostEnsureCanCompileStrings(callerRealm,
calleeRealm). If this throws an exception,
report the exception.
2. Let script source be the first method argument.
3. Let script language be JavaScript.
4. Let settings object be method context’s
environment settings object.
5. Create a script using script source as the
script source, the URL where script source can
be found, scripting language as the scripting
language, and settings object as the
environment settings object.
3. If the repeat flag is true, then call timer initialization steps
again, passing them the same method arguments, the same method
context, with the repeat flag still set to true, and with the
previous handle set to handler.
6. Let timeout be the second method argument.
7. If the currently running task is a task that was created by this
algorithm, then let nesting level be the task’s timer nesting level.
Otherwise, let nesting level be zero.
8. If nesting level is greater than 5, and timeout is less than 4, then
increase timeout to 4.
9. Increment nesting level by one.
10. Let task’s timer nesting level be nesting level.
11. Return handle, and then continue running this algorithm in parallel.
12. If method context is a Window object, wait until the Document
associated with method context has been fully active for a further
timeout milliseconds (not necessarily consecutively).
Otherwise, method context is a WorkerGlobalScope object; wait until
timeout milliseconds have passed with the worker not suspended (not
necessarily consecutively).
13. Wait until any invocations of this algorithm that had the same method
context, that started before this one, and whose timeout is equal to
or less than this one’s, have completed.
Argument conversion as defined by Web IDL (for example, invoking
toString() methods on objects passed as the first argument) happens in
the algorithms defined in Web IDL, before this algorithm is invoked.
So for example, the following rather silly code will result in the log
containing "ONE TWO ":
var log = '';function logger(s) { log += s + ' '; }
setTimeout({ toString: function () {
setTimeout("logger('ONE')", 100);
return "logger('TWO')";
} }, 100);
14. Optionally, wait a further user-agent defined length of time.
This is intended to allow user agents to pad timeouts as needed to
optimize the power usage of the device. For example, some processors
have a low-power mode where the granularity of timers is reduced; on
such platforms, user agents can slow timers down to fit this schedule
instead of requiring the processor to use the more accurate mode with
its associated higher power usage.
15. Queue the task task.
Once the task has been processed, if the repeat flag is false, it is
safe to remove the entry for handle from the list of active timers
(there is no way for the entry’s existence to be detected past this
point, so it does not technically matter one way or the other).
The task source for these tasks is the timer task source.
To run tasks of several milliseconds back to back without any delay, while
still yielding back to the browser to avoid starving the user interface
(and to avoid the browser killing the script for hogging the CPU), simply
queue the next timer before performing work:
function doExpensiveWork() {var done = false;
// ...
// this part of the function takes up to five milliseconds
// set done to true if we’re done
// ...
return done;
}
function rescheduleWork() {
var handle = setTimeout(rescheduleWork, 0); // preschedule next iteration
if (doExpensiveWork())
clearTimeout(handle); // clear the timeout if we don’t need it
}
function scheduleWork() {
setTimeout(rescheduleWork, 0);
}
scheduleWork(); // queues a task to do lots of work
7.6. User prompts
7.6.1. Simple dialogs
window . alert(message)
Displays a modal alert with the given message, and waits for the
user to dismiss it.
result = window . confirm(message)
Displays a modal OK/Cancel prompt with the given message, waits
for the user to dismiss it, and returns true if the user clicks OK
and false if the user clicks Cancel.
result = window . prompt(message [, default] )
Displays a modal text field prompt with the given message, waits
for the user to dismiss it, and returns the value that the user
entered. If the user cancels the prompt, then returns null
instead. If the second argument is present, then the given value
is used as a default.
Logic that depends on tasks or microtasks, such as media elements loading
their media data, are stalled when these methods are invoked.
To optionally truncate a simple dialog string s, return either s itself or
some string derived from s that is shorter. User agents should not provide
UI for displaying the elided portion of s, as this makes it too easy for
abusers to create dialogs of the form "Important security alert! Click
'Show More' for full details!".
For example, a user agent might want to only display the first 100
characters of a message. Or, a user agent might replace the middle of the
string with "…". These types of modifications can be useful in limiting
the abuse potential of unnaturally large, trustworthy-looking system
dialogs.
The alert(message) method, when invoked, must run the following steps:
1. If the event loop’s termination nesting level is non-zero, optionally
abort these steps.
2. If the active sandboxing flag set of the active document of the
responsible browsing context specified by the incumbent settings
object has the sandboxed modals flag set, then abort these steps.
3. Optionally, abort these steps. (For example, the user agent might give
the user the option to ignore all alerts, and would thus abort at this
step whenever the method was invoked.)
4. If the method was invoked with no arguments, then let message be the
empty string; otherwise, let message be the method’s first argument.
5. Show the given message to the user.
6. Optionally, pause while waiting for the user to acknowledge the
message.
The confirm(message) method, when invoked, must run the following steps:
1. If the event loop’s termination nesting level is non-zero, optionally
abort these steps, returning false.
2. If the active sandboxing flag set of the active document of the
responsible browsing context specified by the incumbent settings
object has the sandboxed modals flag set, then return false and abort
these steps.
3. Optionally, return false and abort these steps. (For example, the user
agent might give the user the option to ignore all prompts, and would
thus abort at this step whenever the method was invoked.)
4. Set message to the result of optionally truncating message.
5. Show message to the user, and ask the user to respond with a positive
or negative response.
6. Pause until the user responds either positively or negatively.
7. If the user responded positively, return true; otherwise, the user
responded negatively: return false.
The prompt(message, default) method, when invoked, must run the following
steps:
1. If the event loop’s termination nesting level is non-zero, optionally
abort these steps, returning null.
2. If the active sandboxing flag set of the active document of the
responsible browsing context specified by the incumbent settings
object has the sandboxed modals flag set, then return null and abort
these steps.
3. Optionally, return null and abort these steps. (For example, the user
agent might give the user the option to ignore all prompts, and would
thus abort at this step whenever the method was invoked.)
4. Set message to the result of optionally truncating message.
5. Set default to the result of optionally truncating default.
6. Show message to the user, and ask the user to either respond with a
string value or abort. The response must be defaulted to the value
given by default.
7. Pause while waiting for the user’s response.
8. If the user aborts, then return null; otherwise, return the string
that the user responded with.
7.6.2. Printing
window . print()
Prompts the user to print the page.
When the print() method is invoked, if the Document is ready for post-load
tasks, then the user agent must run the printing steps in parallel.
Otherwise, the user agent must only set the print when loaded flag on the
Document.
User agents should also run the printing steps whenever the user asks for
the opportunity to obtain a physical form (e.g., printed copy), or the
representation of a physical form (e.g., PDF copy), of a document.
The printing steps are as follows:
1. The user agent may display a message to the user or abort these steps
(or both).
For instance, a kiosk browser could silently ignore any invocations of
the print() method.
For instance, a browser on a mobile device could detect that there are
no printers in the vicinity and display a message saying so before
continuing to offer a "save to PDF" option.
2. If the active sandboxing flag set of the active document of the
responsible browsing context specified by the incumbent settings
object has the sandboxed modals flag set, then abort these steps.
If the printing dialog is blocked by a Document’s sandbox, then
neither the beforeprint nor afterprint events will be fired.
3. The user agent must fire a simple event named beforeprint at the
Window object of the Document that is being printed, as well as any
nested browsing contexts in it.
The beforeprint event can be used to annotate the printed copy, for
instance adding the time at which the document was printed.
4. The user agent should offer the user the opportunity to obtain a
physical form (or the representation of a physical form) of the
document. The user agent may wait for the user to either accept or
decline before returning; if so, the user agent must pause while the
method is waiting. Even if the user agent doesn’t wait at this point,
the user agent must use the state of the relevant documents as they
are at this point in the algorithm if and when it eventually creates
the alternate form.
5. The user agent must fire a simple event named afterprint at the Window
object of the Document that is being printed, as well as any nested
browsing contexts in it.
The afterprint event can be used to revert annotations added in the
earlier event, as well as showing post-printing UI. For instance, if a
page is walking the user through the steps of applying for a home
loan, the script could automatically advance to the next step after
having printed a form or other.
7.7. System state and capabilities
7.7.1. The Navigator object
The navigator attribute of the Window interface must return an instance of
the Navigator interface, which represents the identity and state of the
user agent (the client), and allows Web pages to register themselves as
potential protocol and content handlers:
interface Navigator {
// objects implementing this interface also implement the interfaces given below
};
Navigator implements NavigatorID;
Navigator implements NavigatorLanguage;
Navigator implements NavigatorOnLine;
Navigator implements NavigatorContentUtils;
Navigator implements NavigatorCookies;
These interfaces are defined separately so that other specifications can
re-use parts of the Navigator interface.
7.7.1.1. Client identification
[NoInterfaceObject, Exposed=(Window, Worker)]
interface NavigatorID {
[Exposed=Window] readonly attribute DOMString appCodeName; // constant "Mozilla"
readonly attribute DOMString appName; // constant "Netscape"
readonly attribute DOMString appVersion;
readonly attribute DOMString platform;
[Exposed=Window]readonly attribute DOMString product; // constant "Gecko"
readonly attribute DOMString userAgent;
};
In certain cases, despite the best efforts of the entire industry, Web
browsers have bugs and limitations that Web authors are forced to work
around.
This section defines a collection of attributes that can be used to
determine, from script, the kind of user agent in use, in order to work
around these issues.
Client detection should always be limited to detecting known current
versions; future versions and unknown versions should always be assumed to
be fully compliant.
window . navigator . appCodeName
Returns the string "Mozilla".
window . navigator . appName
Returns the string "Netscape".
window . navigator . appVersion
Returns the version of the browser.
window . navigator . platform
Returns the name of the platform.
window . navigator . product
Returns the string "Gecko".
window . navigator . productSub()
Returns either the string "20030107", or the string "20100101".
window . navigator . userAgent
Returns the complete User-Agent header.
appCodeName, of type DOMString, readonly
Must return the string "Mozilla".
appName, of type DOMString, readonly
Must return the string "Netscape".
appVersion, of type DOMString, readonly
Must return either the string "4.0" or a string representing the
version of the browser in detail, e.g., "1.0 (VMS; en-US)
Mellblomenator/9000".
platform, of type DOMString, readonly
Must return either the empty string or a string representing the
platform on which the browser is executing, e.g., "MacIntel",
"Win32", "FreeBSD i386", "WebTV OS".
product, of type DOMString, readonly
Must return the string "Gecko".
taintEnabled()
Must return false.
userAgent, of type DOMString, readonly
Must return the string used for the value of the "User-Agent"
header in HTTP requests, or the empty string if no such header is
ever sent.
Any information in this API that varies from user to user can be used to
profile the user. In fact, if enough such information is available, a user
can actually be uniquely identified. For this reason, user agent
implementors are strongly urged to include as little information in this
API as possible.
7.7.1.2. Language preferences
[NoInterfaceObject, Exposed=(Window, Worker)]
interface NavigatorLanguage {
readonly attribute DOMString? language;
readonly attribute DOMString[] languages;
};
window . navigator . language
Returns a language tag representing the user’s preferred language.
window . navigator . languages
Returns an array of language tags representing the user’s
preferred languages, with the most preferred language first. The
most preferred language is the one returned by navigator.language.
A languagechange event is fired at the Window or WorkerGlobalScope object
when the user agent’s understanding of what the user’s preferred languages
are changes.
language, of type DOMString, readonly, nullable
Must return a valid BCP 47 language tag representing either a
plausible language or the user’s most preferred language. [BCP47]
languages, of type DOMString[], readonly
Must return a read only array of valid BCP 47 language tags
representing either one or more plausible languages, or the user’s
preferred languages, ordered by preference with the most preferred
language first. The same object must be returned until the user
agent needs to return different values, or values in a different
order. [BCP47]
Whenever the user agent needs to make the navigator.languages
attribute of a Window or WorkerGlobalScope object return a new set
of language tags, the user agent must queue a task to fire a
simple event named languagechange at the Window or
WorkerGlobalScope object and wait until that task begins to be
executed before actually returning a new value.
The task source for this task is the DOM manipulation task source.
To determine a plausible language, the user agent should bear in mind the
following:
* Any information in this API that varies from user to user can be used
to profile or identify the user.
* If the user is not using a service that obfuscates the user’s point of
origin (e.g., the Tor anonymity network), then the value that is least
likely to distinguish the user from other users with similar origins
(e.g., from the same IP address block) is the language used by the
majority of such users. [TOR]
* If the user is using an anonymizing service, then the value "en-US" is
suggested; if all users of the service use that same value, that
reduces the possibility of distinguishing the users from each other.
To avoid introducing any more fingerprinting vectors, user agents should
use the same list for the APIs defined in this function as for the HTTP
Accept-Language header.
7.7.1.3. Custom scheme and content handlers: the registerProtocolHandler()
and registerContentHandler() methods
[NoInterfaceObject]
interface NavigatorContentUtils {
// content handler registration
void registerProtocolHandler(DOMString scheme, DOMString url, DOMString title);
void registerContentHandler(DOMString mimeType, DOMString url, DOMString title);
DOMString isProtocolHandlerRegistered(DOMString scheme, DOMString url);
DOMString isContentHandlerRegistered(DOMString mimeType, DOMString url);
void unregisterProtocolHandler(DOMString scheme, DOMString url);
void unregisterContentHandler(DOMString mimeType, DOMString url);
};
The registerProtocolHandler() method allows Web sites to register
themselves as possible handlers for particular schemes. For example, an
online telephone messaging service could register itself as a handler of
the sms: scheme, so that if the user clicks on such a link, he is given
the opportunity to use that Web site. Analogously, the
registerContentHandler() method allows Web sites to register themselves as
possible handlers for content in a particular MIME type. For example, the
same online telephone messaging service could register itself as a handler
for text/vcard files, so that if the user has no native application
capable of handling vCards, his Web browser can instead suggest he use
that site to view contact information stored on vCards that he opens.
[RFC5724] [RFC6350]
window . navigator . registerProtocolHandler(scheme, url, title)
window . navigator . registerContentHandler(mimeType, url, title)
Registers a handler for the given scheme or content type, at the
given URL, with the given title.
The string "%s" in the URL is used as a placeholder for where to
put the URL of the content to be handled.
Throws a "SecurityError" DOMException if the user agent blocks the
registration (this might happen if trying to register as a handler
for "http", for instance).
Throws a "SyntaxError" DOMException if the "%s" string is missing
in the URL.
User agents may, within the constraints described in this section, do
whatever they like when the methods are called. A user agent could, for
instance, prompt the user and offer the user the opportunity to add the
site to a shortlist of handlers, or make the handlers his default, or
cancel the request. user agents could provide such a UI through modal UI
or through a non-modal transient notification interface. user agents could
also simply silently collect the information, providing it only when
relevant to the user.
User agents should keep track of which sites have registered handlers
(even if the user has declined such registrations) so that the user is not
repeatedly prompted with the same request.
The arguments to the methods have the following meanings and corresponding
implementation requirements. The requirements that involve throwing
exceptions must be processed in the order given below, stopping at the
first exception thrown. (So the exceptions for the first argument take
precedence over the exceptions for the second argument.)
scheme (registerProtocolHandler() only)
A scheme, such as "mailto" or "web+auth". The scheme must be
compared in an ASCII case-insensitive manner by user agents for
the purposes of comparing with the scheme part of URLs that they
consider against the list of registered handlers.
The scheme value, if it contains a colon (as in "mailto:"), will
never match anything, since schemes don’t contain colons.
If the registerProtocolHandler() method is invoked with a scheme
that is neither a safelisted scheme nor a scheme whose value
starts with the substring "web+" and otherwise contains only
lowercase ASCII letters, and whose length is at least five
characters (including the "web+" prefix), the user agent must
throw a "SyntaxError" DOMException.
The following schemes are the safelisted schemes:
* bitcoin
* geo
* im
* irc
* ircs
* magnet
* mailto
* mms
* news
* nntp
* openpgp4fpr
* sip
* sms
* smsto
* ssh
* tel
* urn
* webcal
* wtai
* xmpp
This list can be changed. If there are schemes that should be
added, please send feedback.
This list excludes any schemes that could reasonably be expected
to be supported inline, e.g., in an iframe, such as http or (more
theoretically) gopher. If those were supported, they could
potentially be used in man-in-the-middle attacks, by replacing
pages that have frames with such content with content under the
control of the protocol handler. If the user agent has native
support for the schemes, this could further be used for
cookie-theft attacks.
mimeType (registerContentHandler() only)
A MIME type, such as model/vnd.flatland.3dml or
application/vnd.google-earth.kml+xml. The MIME type must be
compared in an ASCII case-insensitive manner by user agents for
the purposes of comparing with MIME types of documents that they
consider against the list of registered handlers.
User agents must compare the given values only to the MIME
type/subtype parts of content types, not to the complete type
including parameters. Thus, if mimeType values passed to this
method include characters such as commas or white space, or
include MIME parameters, then the handler being registered will
never be used.
The type is compared to the MIME type used by the user agent after
the sniffing algorithms have been applied.
If the registerContentHandler() method is invoked with a MIME type
that is in the type blocklist or that the user agent has deemed a
privileged type, the user agent must throw a "SecurityError"
DOMException.
The following MIME types are in the type blocklist:
* application/x-www-form-urlencoded
* application/xhtml+xml
* application/xml
* image/gif
* image/jpeg
* image/png
* image/svg+xml
* multipart/x-mixed-replace
* text/css
* text/html
* text/ping
* text/plain
* text/vtt
* text/xml
* All types that the user agent supports displaying natively in
a browsing context during navigation, except for
application/rss+xml and application/atom+xml
This list can be changed. If there are MIME types that should be
added, please send feedback.
url
A string used to build the URL of the page that will handle the
requests.
User agents must throw a "SyntaxError" DOMException if the url
argument passed to one of these methods does not contain the exact
literal string "%s".
User agents must throw a "SyntaxError" DOMException if parsing the
url argument relative to the API base URL specified by the entry
settings object is not successful.
The resulting URL string would by definition not be a valid URL as
it would include the string "%s" which is not a valid component in
a URL.
User agents must throw a "SecurityError" DOMException if the
resulting absolute URL has an origin that differs from the origin
specified by the entry settings object.
This is forcibly the case if the %s placeholder is in the scheme,
host, or port parts of the URL.
The resulting URL string is the proto-URL. It identifies the
handler for the purposes of the methods described below.
When the user agent uses this handler, it must replace the first
occurrence of the exact literal string "%s" in the url argument
with an escaped version of the absolute URL of the content in
question (as defined below), then parse the resulting URL,
relative to the API base URL specified by the entry settings
object at the time the registerContentHandler() or
registerProtocolHandler() methods were invoked, and then navigate
an appropriate browsing context to the resulting URL.
To get the escaped version of the absolute URL of the content in
question, the user agent must replace every character in that
absolute URL that is not a character in the URL default encode set
with the result of UTF-8 percent encoding that character.
If the user had visited a site at https://example.com/ that made
the following call:
navigator.registerContentHandler('application/x-soup', 'soup?url=%s', 'SoupWeb™')
...and then, much later, while visiting https://www.example.net/,
clicked on a link such as:
<a href="chickenkïwi.soup">Download our Chicken Kïwi soup!</a>
...then, assuming this chickenkïwi.soup file was served with the
MIME type application/x-soup, the user agent might navigate to the
following URL:
https://example.com/soup?url=https://www.example.net/chickenk%C3%AFwi.soup
This site could then fetch the chickenkïwi.soup file and do
whatever it is that it does with soup (synthesize it and ship it
to the user, or whatever).
title
A descriptive title of the handler, which the user agent might use
to remind the user what the site in question is.
This section does not define how the pages registered by these methods are
used, beyond the requirements on how to process the url value (see above).
To some extent, the processing model for navigating across documents
defines some cases where these methods are relevant, but in general user
agents may use this information wherever they would otherwise consider
handing content to native plugins or helper applications.
user agents must not use registered content handlers to handle content
that was returned as part of a non-GET transaction (or rather, as part of
any non-idempotent transaction), as the remote site would not be able to
fetch the same data.
----------------------------------------------------------------------
In addition to the registration methods, there are also methods for
determining if particular handlers have been registered, and for
unregistering handlers.
state = window . navigator . isProtocolHandlerRegistered(scheme, url)
state = window . navigator . isContentHandlerRegistered(mimeType, url)
Returns one of the following strings describing the state of the
handler given by the arguments:
new
Indicates that no attempt has been made to register
the given handler (or that the handler has been
unregistered). It would be appropriate to promote the
availability of the handler or to just automatically
register the handler.
registered
Indicates that the given handler has been registered
or that the site is blocked from registering the
handler. Trying to register the handler again would
have no effect.
declined
Indicates that the given handler has been offered but
was rejected. Trying to register the handler again
may prompt the user again.
window . navigator . unregisterProtocolHandler(scheme, url)
window . navigator . unregisterContentHandler(mimeType, url)
Unregisters the handler given by the arguments.
The isProtocolHandlerRegistered() method must return the handler state
string that most closely describes the current state of the handler
described by the two arguments to the method, where the first argument
gives the scheme and the second gives the string used to build the URL of
the page that will handle the requests.
The first argument must be compared to the schemes for which custom
protocol handlers are registered in an ASCII case-insensitive manner to
find the relevant handlers.
The second argument must be preprocessed as described below, and if that
is successful, must then be matched against the proto-URLs of the relevant
handlers to find the described handler.
----------------------------------------------------------------------
The isContentHandlerRegistered() method must return the handler state
string that most closely describes the current state of the handler
described by the two arguments to the method, where the first argument
gives the MIME type and the second gives the string used to build the URL
of the page that will handle the requests.
The first argument must be compared to the MIME types for which custom
content handlers are registered in an ASCII case-insensitive manner to
find the relevant handlers.
The second argument must be preprocessed as described below, and if that
is successful, must then be matched against the proto-URLs of the relevant
handlers to find the described handler.
----------------------------------------------------------------------
The handler state strings are the following strings. Each string describes
several situations, as given by the following list.
new
The described handler has never been registered for the given
scheme or type.
The described handler was once registered for the given scheme or
type, but the site has since unregistered it. If the handler were
to be reregistered, the user would be notified accordingly.
The described handler was once registered for the given scheme or
type, but the site has since unregistered it, but the user has
indicated that the site is to be blocked from registering the type
again, so the user agent would ignore further registration
attempts.
registered
An attempt was made to register the described handler for the
given scheme or type, but the user has not yet been notified, and
the user agent would ignore further registration attempts. (Maybe
the user agent batches registration requests to display them when
the user requests to be notified about them, and the user has not
yet requested that the user agent notify it of the previous
registration attempt.)
The described handler is registered for the given scheme or type
(maybe, or maybe not, as the default handler).
The described handler is permanently blocked from being
(re)registered. (Maybe the user marked the registration attempt as
spam, or blocked the site for other reasons.)
declined
An attempt was made to register the described handler for the
given scheme or type, but the user has not yet been notified;
however, the user might be notified if another registration
attempt were to be made. (Maybe the last registration attempt was
made while the page was in the background and the user closed the
page without looking at it, and the user agent requires
confirmation for this registration attempt.)
An attempt was made to register the described handler for the
given scheme or type, but the user has not yet responded.
An attempt was made to register the described handler for the
given scheme or type, but the user declined the offer. The user
has not indicated that the handler is to be permanently blocked,
however, so another attempt to register the described handler
might result in the user being prompted again.
The described handler was once registered for the given scheme or
type, but the user has since removed it. The user has not
indicated that the handler is to be permanently blocked, however,
so another attempt to register the described handler might result
in the user being prompted again.
----------------------------------------------------------------------
The unregisterProtocolHandler() method must unregister the handler
described by the two arguments to the method, where the first argument
gives the scheme and the second gives the string used to build the URL of
the page that will handle the requests.
The first argument must be compared to the schemes for which custom
protocol handlers are registered in an ASCII case-insensitive manner to
find the relevant handlers.
The second argument must be preprocessed as described below, and if that
is successful, must then be matched against the proto-URLs of the relevant
handlers to find the described handler.
----------------------------------------------------------------------
The unregisterContentHandler() method must unregister the handler
described by the two arguments to the method, where the first argument
gives the MIME type and the second gives the string used to build the URL
of the page that will handle the requests.
The first argument must be compared to the MIME types for which custom
content handlers are registered in an ASCII case-insensitive manner to
find the relevant handlers.
The second argument must be preprocessed as described below, and if that
is successful, must then be matched against the proto-URLs of the relevant
handlers to find the described handler.
----------------------------------------------------------------------
The second argument of the four methods described above must be
preprocessed as follows:
1. If the string does not contain the substring "%s", abort these steps.
There’s no matching handler.
2. Parse the string relative to the entry settings object. If this fails,
then throw a "SyntaxError" DOMException.
3. If the resulting URL record’s origin is not the same origin as the
origin specified by the entry settings object, throw a "SecurityError"
DOMException.
4. Return the resulting URL string as the result of preprocessing the
argument.
7.7.1.3.1. Security and privacy
These mechanisms can introduce a number of concerns, in particular
privacy concerns.
Hijacking all Web usage. User agents should not allow schemes that are
key to its normal operation, such as http or https, to be rerouted
through third-party sites. This would allow a user’s activities to be
trivially tracked, and would allow user information, even in secure
connections, to be collected.
Hijacking defaults. User agents are strongly urged to not
automatically change any defaults, as this could lead the user to send
data to remote hosts that the user is not expecting. New handlers
registering themselves should never automatically cause those sites to
be used.
Registration spamming. User agents should consider the possibility
that a site will attempt to register a large number of handlers,
possibly from multiple domains (e.g., by redirecting through a series
of pages each on a different domain, and each registering a handler
for video/mpeg — analogous practices abusing other Web browser
features have been used by pornography Web sites for many years). User
agents should gracefully handle such hostile attempts, protecting the
user.
Misleading titles. User agents should not rely wholly on the title
argument to the methods when presenting the registered handlers to the
user, since sites could easily lie. For example, a site
hostile.example.net could claim that it was registering the "Cuddly
Bear Happy Content Handler". User agents should therefore use the
handler’s domain in any UI along with any title.
Hostile handler metadata. User agents should protect against typical
attacks against strings embedded in their interface, for example
ensuring that markup or escape characters in such strings are not
executed, that null bytes are properly handled, that over-long strings
do not cause crashes or buffer overruns, and so forth.
Leaking Intranet URLs. The mechanism described in this section can
result in secret Intranet URLs being leaked, in the following manner:
1. The user registers a third-party content handler as the default
handler for a content type.
2. The user then browses his corporate Intranet site and accesses a
document that uses that content type.
3. The user agent contacts the third party and hands the third party
the URL to the Intranet content.
No actual confidential file data is leaked in this manner, but the
URLs themselves could contain confidential information. For example,
the URL could be
https://www.corp.example.com/upcoming-aquisitions/the-sample-company.egf,
which might tell the third party that Example Corporation is intending
to merge with The Sample Company. Implementors might wish to consider
allowing administrators to disable this feature for certain
subdomains, content types, or schemes.
Leaking secure URLs. User agents should not send HTTPS URLs to
third-party sites registered as content handlers without the user’s
informed consent, for the same reason that user agents sometimes avoid
sending Referer (sic) HTTP headers from secure sites to third-party
sites.
Leaking credentials. User agents must never send username or password
information in the URLs that are escaped and included sent to the
handler sites. User agents may even avoid attempting to pass to
Web-based handlers the URLs of resources that are known to require
authentication to access, as such sites would be unable to access the
resources in question without prompting the user for credentials
themselves (a practice that would require the user to know whether to
trust the third-party handler, a decision many users are unable to
make or even understand).
Interface interference. User agents should be prepared to handle
intentionally long arguments to the methods. For example, if the user
interface exposed consists of an "accept" button and a "deny" button,
with the "accept" binding containing the name of the handler, it’s
important that a long name not cause the "deny" button to be pushed
off the screen.
Fingerprinting users. Since a site can detect if it has attempted to
register a particular handler or not, whether or not the user
responds, the mechanism can be used to store data. User agents are
therefore strongly urged to treat registrations in the same manner as
cookies: clearing cookies for a site should also clear all
registrations for that site, and disabling cookies for a site should
also disable registrations.
7.7.1.3.2. Sample user interface
This section is non-normative.
A simple implementation of this feature for a desktop Web browser might
work as follows.
The registerContentHandler() method could display a modal dialog box:
The modal dialog box could have the title 'Content Handler Registration',
and could say 'This Web page: Kittens at work https://kittens.example.org/
...would like permission to handle files of type: application/x-meowmeow
using the following Web-based application: Kittens-at-work displayer
https://kittens.example.org/?show=%s Do you trust the administrators of
the "kittens.example.org" domain?' with two buttons, 'Trust
kittens.example.org' and 'Cancel'.
In this dialog box, "Kittens at work" is the title of the page that
invoked the method, "https://kittens.example.org/" is the URL of that
page, "application/x-meowmeow" is the string that was passed to the
registerContentHandler() method as its first argument (mimeType),
"https://kittens.example.org/?show=%s" was the second argument (url), and
"Kittens-at-work displayer" was the third argument (title).
If the user clicks the Cancel button, then nothing further happens. If the
user clicks the "Trust" button, then the handler is remembered.
When the user then attempts to fetch a URL that uses the
"application/x-meowmeow" MIME type, then it might display a dialog as
follows:
The dialog box could have the title 'Unknown File Type' and could say 'You
have attempted to access:' followed by a URL, followed by a prompt such as
'How would you like FerretBrowser to handle this resource?' with three
radio buttons, one saying 'Contact the FerretBrowser plugin registry to
see if there is an official way to handle this resource.', one saying
'Pass this URL to a local application' with an application selector, and
one saying 'Pass this URL to the "Kittens-at-work displayer" application
at "kittens.example.org"', with a checkbox labeled 'Always do this for
resources using the "application/x-meowmeow" type in future.', and with
two buttons, 'Ok' and 'Cancel'.
In this dialog, the third option is the one that was primed by the site
registering itself earlier.
If the user does select that option, then the browser, in accordance with
the requirements described in the previous two sections, will redirect the
user to
"https://kittens.example.org/?show=data%3Aapplication/x-meowmeow;base64,S2l0dGVucyBhcmUgdGhlIGN1dGVzdCE%253D".
The registerProtocolHandler() method would work equivalently, but for
schemes instead of unknown content types.
7.7.1.4. Cookies
[NoInterfaceObject]
interface NavigatorCookies {
readonly attribute boolean cookieEnabled;
};
window . navigator . cookieEnabled
Returns false if setting a cookie will be ignored, and true
otherwise.
The cookieEnabled attribute must return true if the user agent attempts to
handle cookies according to the cookie specification, and false if it
ignores cookie change requests. [COOKIES]
7.8. Images
[Exposed=(Window, Worker), Serializable, Transferable]
interface ImageBitmap {
readonly attribute unsigned long width;
readonly attribute unsigned long height;
};
typedef (HTMLImageElement or
HTMLVideoElement or
HTMLCanvasElement or
Blob or
ImageData or
CanvasRenderingContext2D or
ImageBitmap) ImageBitmapSource;
An ImageBitmap object represents a bitmap image that can be painted to a
canvas without undue latency.
The exact judgement of what is undue latency of this is left up to the
implementer, but in general if making use of the bitmap requires network
I/O, or even local disk I/O, then the latency is probably undue; whereas
if it only requires a blocking read from a GPU or system RAM, the latency
is probably acceptable.
promise = Window . createImageBitmap(image [, sx, sy, sw, sh ] )
Takes image, which can be an img element, video, or canvas
element, a Blob object, an ImageData object, a
CanvasRenderingContext2D object, or another ImageBitmap object,
and returns a promise that is resolved when a new ImageBitmap is
created.
If no ImageBitmap object can be constructed, for example because
the provided image data is not actually an image, then the promise
is rejected instead.
If sx, sy, sw, and sh arguments are provided, the source image is
cropped to the given pixels, with any pixels missing in the
original replaced by transparent black. These coordinates are in
the source image’s pixel coordinate space, not in CSS pixels.
Rejects the promise with an InvalidStateError exception if the
source image is not in a valid state (e.g., an img element that
hasn’t finished loading, or a CanvasRenderingContext2D object
whose bitmap data has zero length along one or both dimensions, or
an ImageData object whose data is data attribute has been
neutered). Rejects the promise with a "SyntaxError" DOMException
if the script is not allowed to access the image data of the
source image (e.g., a video that is CORS-cross-origin, or a canvas
being drawn on by a script in a worker from another origin).
imageBitmap . width
Returns the intrinsic width of the image, in CSS pixels.
imageBitmap . height
Returns the intrinsic height of the image, in CSS pixels.
An ImageBitmap object always has associated bitmap data, with a width and
a height. However, it is possible for this data to be corrupted. If an
ImageBitmap object’s media data can be decoded without errors, it is said
to be fully decodable.
An ImageBitmap object’s bitmap has an origin-clean flag, which indicates
whether the bitmap is tainted by content from a different origin. The flag
is initially set to true and may be changed to false by the steps of
createImageBitmap().
----------------------------------------------------------------------
ImageBitmap objects are serializable objects and transferable objects.
Their serialization steps, given value and serialized, are:
1. Set serialized.[[BitmapData]] to a copy of value’s bitmap data.
2. Set serialized.[[OriginClean]] to true if value’s origin-clean flag is
set, and false otherwise.
Their deserialization steps, given serialized and value, are:
1. Set value’s bitmap data to serialized.[[BitmapData]].
2. If serialized.[[OriginClean]] is true, set value’s origin-clean flag.
Their transfer steps, given value and dataHolder, are:
1. Set dataHolder.[[BitmapData]] to value’s bitmap data.
2. Set dataHolder.[[OriginClean]] to true if value’s origin-clean flag is
set, and false otherwise.
3. Unset value’s bitmap data.
Their transfer-receiving steps, given dataHolder and value, are:
1. Set value’s bitmap data to dataHolder.[[BitmapData]].
2. If dataHolder.[[OriginClean]] is true, set value’s origin-clean flag.
----------------------------------------------------------------------
An ImageBitmap object can be obtained from a variety of different objects,
using the createImageBitmap() method. When invoked, the method must act as
follows:
If image is an img element
1. If either the sw or sh arguments are specified but zero,
return a promise rejected with an IndexSizeError exception
and abort these steps.
2. If the img element is not completely available, then return a
promise rejected with an InvalidStateError exception and
abort these steps.
3. If the img element’s media data is not a bitmap (e.g., it’s a
vector graphic), then return a promise rejected with an
InvalidStateError exception and abort these steps.
4. Create a new ImageBitmap object.
5. Let the ImageBitmap object’s bitmap data be a copy of the img
element’s media data, cropped to the source rectangle. If
this is an animated image, the ImageBitmap object’s bitmap
data must only be taken from the default image of the
animation (the one that the format defines is to be used when
animation is not supported or is disabled), or, if there is
no such image, the first frame of the animation.
6. If the origin of the img element’s image is not the same
origin as the origin specified by the entry settings object,
then set the origin-clean flag of the ImageBitmap object’s
bitmap to false.
7. Return a new promise, but continue running these steps in
parallel.
8. Resolve the promise with the new ImageBitmap object as the
value.
If image is a video element
1. If either the sw or sh arguments are specified but zero,
return a promise rejected with an IndexSizeError exception
and abort these steps.
2. If the video element’s networkState attribute is
NETWORK_EMPTY, then return a promise rejected with an
InvalidStateError exception and abort these steps.
3. If the video element’s readyState attribute is either
HAVE_NOTHING or HAVE_METADATA, then return a promise rejected
with an InvalidStateError exception and abort these steps.
4. Create a new ImageBitmap object.
5. Let the ImageBitmap object’s bitmap data be a copy of the
frame at the current playback position, at the media
resource’s intrinsic width and intrinsic height (i.e., after
any aspect-ratio correction has been applied), cropped to the
source rectangle.
6. If the origin of the video element’s image is not the same
origin as the origin specified by the entry settings object,
then set the origin-clean flag of the ImageBitmap object’s
bitmap to false.
7. Return a new promise, but continue running these steps in
parallel.
8. Resolve the promise with the new ImageBitmap object as the
value.
If image is a canvas element
1. If either the sw or sh arguments are specified but zero,
return a promise rejected with an IndexSizeError exception
and abort these steps.
2. If the canvas element’s bitmap has either a horizontal
dimension or a vertical dimension equal to zero, then return
a promise rejected with an InvalidStateError exception and
abort these steps.
3. Create a new ImageBitmap object.
4. Let the ImageBitmap object’s bitmap data be a copy of the
canvas element’s bitmap data, cropped to the source
rectangle.
5. Set the origin of the ImageBitmap object’s bitmap to the same
value as the origin-clean flag of the canvas element’s
bitmap.
6. Return a new promise, but continue running these steps in
parallel.
7. Resolve the promise with the new ImageBitmap object as the
value.
If image is a Blob object
1. If either the sw or sh arguments are specified but zero,
return a promise rejected with an IndexSizeError exception
and abort these steps.
2. Return a new promise, but continue running these steps in
parallel.
3. Read the Blob object’s data. If an error occurs during
reading of the object, then reject the promise with an
InvalidStateError exception, and abort these steps.
4. Apply the image sniffing rules to determine the file format
of the image data, with MIME type of the Blob (as given by
the Blob object’s type attribute) giving the official type.
5. If the image data is not in a supported file format (e.g.,
it’s not actually an image at all), or if the image data is
corrupted in some fatal way such that the image dimensions
cannot be obtained, then reject the promise with null, and
abort these steps.
6. Create a new ImageBitmap object.
7. Let the ImageBitmap object’s bitmap data be the image data
read from the Blob object, cropped to the source rectangle.
If this is an animated image, the ImageBitmap object’s bitmap
data must only be taken from the default image of the
animation (the one that the format defines is to be used when
animation is not supported or is disabled), or, if there is
no such image, the first frame of the animation.
8. Resolve the promise with the new ImageBitmap object as the
value.
If image is an ImageData object
1. If either the sw or sh arguments are specified but zero,
return a promise rejected with an IndexSizeError exception
and abort these steps.
2. If the image object’s data attribute has been neutered,
return a promise rejected with an InvalidStateError exception
and abort these steps.
3. Create a new ImageBitmap object.
4. Let the ImageBitmap object’s bitmap data be the image data
given by the ImageData object, cropped to the source
rectangle.
5. Return a new promise, but continue running these steps in
parallel.
6. Resolve the promise with the new ImageBitmap object as the
value.
If image is a CanvasRenderingContext2D object
1. If either the sw or sh arguments are specified but zero,
return a promise rejected with an IndexSizeError exception
and abort these steps.
2. If the CanvasRenderingContext2D object’s scratch bitmap has
either a horizontal dimension or a vertical dimension equal
to zero, then return a promise rejected with an
InvalidStateError exception and abort these steps.
3. Create a new ImageBitmap object.
4. Let the ImageBitmap object’s bitmap data be a copy of the
CanvasRenderingContext2D object’s scratch bitmap, cropped to
the source rectangle.
5. Set the origin-clean flag of the ImageBitmap object’s bitmap
to the same value as the origin-clean flag of the
CanvasRenderingContext2D object’s scratch bitmap
6. Return a new promise, but continue running these steps in
parallel.
7. Resolve the promise with the new ImageBitmap object as the
value.
If image is an ImageBitmap object
1. If either the sw or sh arguments are specified but zero,
return a promise rejected with an IndexSizeError exception
and abort these steps.
2. Create a new ImageBitmap object.
3. Let the ImageBitmap object’s bitmap data be a copy of the
image argument’s bitmap data, cropped to the source
rectangle.
4. Set the origin-clean flag of the ImageBitmap object’s bitmap
to the same value as the origin-clean flag of the bitmap of
the image argument.
5. Return a new promise, but continue running these steps in
parallel.
6. Resolve the promise with the new ImageBitmap object as the
value.
When the steps above require that the user agent crop bitmap data to the
source rectangle, the user agent must run the following steps:
1. Let input be the image data being cropped.
2. If the sx, sy, sw, and sh arguments are omitted, return input.
3. Place input on an infinite transparent black grid plane, positioned so
that it’s top left corner is at the origin of the plane, with the
x-coordinate increasing to the right, and the y-coordinate increasing
down, and with each pixel in the input image data occupying a cell on
the plane’s grid.
4. Let output be the rectangle on the plane denoted by the rectangle
whose corners are the four points (sx, sy), (sx+sw, sy), (sx+sw,
sy+sh), (sx, sy+sh).
If either sw or sh are negative, then the top-left corner of this
rectangle will be to the left or above the (sx, sy) point. If any of
the pixels on this rectangle are outside the area where the input
bitmap was placed, then they will be transparent black in output.
5. Return output.
The width attribute must return the ImageBitmap object’s width, in CSS
pixels.
The height attribute must return the ImageBitmap object’s height, in CSS
pixels.
Using this API, a sprite sheet can be precut and prepared:
var sprites = {};
function loadMySprites() {
var image = new Image();
image.src = 'mysprites.png';
var resolver;
var promise = new Promise(function (arg) { resolver = arg });
image.onload = function () {
resolver(Promise.all(
createImageBitmap(image, 0, 0, 40, 40).then(function (image) { sprites.woman = image }),
createImageBitmap(image, 40, 0, 40, 40).then(function (image) { sprites.man = image }),
createImageBitmap(image, 80, 0, 40, 40).then(function (image) { sprites.tree = image }),
createImageBitmap(image, 0, 40, 40, 40).then(function (image) { sprites.hut = image }),
createImageBitmap(image, 40, 40, 40, 40).then(function (image) { sprites.apple = image }),
createImageBitmap(image, 80, 40, 40, 40).then(function (image) { sprites.snake = image }),
));
};
return promise;
}
function runDemo() {
var canvas = document.querySelector('canvas#demo');
var context = canvas.getContext('2d');
context.drawImage(sprites.tree, 30, 10);
context.drawImage(sprites.snake, 70, 10);
}
loadMySprites().then(runDemo);
7.9. Animation Frames
Each Document associated with a top-level browsing context has a list of
animation frame callbacks, which must be initially empty, and an animation
frame callback identifier, which is a number which must initially be zero.
When the requestAnimationFrame() method is called, the user agent must run
the following steps:
1. Let document be the Window object’s Document object
2. Increment document’s animation frame callback identifier by one.
3. Append the method’s argument to document’s list of animation frame
callbacks, associated with document’s animation frame callback
identifier’s current value
4. Return document’s animation frame callback identifier’s current value
When the cancelAnimationFrame() method is called, the user agent must run
the following steps:
1. Let document be the Window object’s Document object
2. Find the entry in document’s list of animation frame callbacks that is
associated with the value given by the method’s argument handle
3. If there is such an entry, remove it from document’s list of animation
frame callbacks
When the user agent is to run the animation frame callbacks for a Document
document with a timestamp now, it must run the following steps:
1. If the value returned by the document object’s hidden attribute is
true, abort these steps. [PAGE-VISIBILITY]
2. Let callbacks be a list of the entries in document’s list of animation
frame callbacks, in the order in which they were added to the list.
3. Set document’s list of animation frame callbacks to the empty list.
4. For each entry in callbacks, in order: invoke the Web IDL callback
function, passing now as the only argument, and if an exception is
thrown, report the exception. [WEBIDL]
8. The HTML syntax
This section only describes the rules for resources labeled with an HTML
MIME type. Rules for XML resources are discussed in the section below
entitled "The XML syntax".
8.1. Writing HTML documents
This section only applies to documents, authoring tools, and markup
generators. In particular, it does not apply to conformance checkers;
conformance checkers must use the requirements given in the next section
("parsing HTML documents").
Documents must consist of the following parts, in the given order:
1. Optionally, a single U+FEFF BYTE ORDER MARK (BOM) character.
2. Any number of comments and space characters.
3. A DOCTYPE.
4. Any number of comments and space characters.
5. The document element, in the form of an html element.
6. Any number of comments and space characters.
The various types of content mentioned above are described in the next few
sections.
In addition, there are some restrictions on how character encoding
declarations are to be serialized, as discussed in the section on that
topic.
Space characters before the html element, and space characters at the
start of the html element and before the head element, will be dropped
when the document is parsed; space characters after the html element will
be parsed as if they were at the end of the body element. Thus, space
characters around the document element do not round-trip.
It is suggested that newlines be inserted after the DOCTYPE, after any
comments that are before the document element, after the html element’s
start tag (if it is not omitted), and after any comments that are inside
the html element but before the head element.
Many strings in the HTML syntax (e.g., the names of elements and their
attributes) are case-insensitive, but only for uppercase ASCII letters and
lowercase ASCII letters. For convenience, in this section this is just
referred to as "case-insensitive".
8.1.1. The DOCTYPE
A DOCTYPE is a required preamble.
DOCTYPEs are required for legacy reasons. When omitted, browsers tend to
use a different rendering mode that is incompatible with some
specifications. Including the DOCTYPE in a document ensures that the
browser makes a best-effort attempt at following the relevant
specifications.
A DOCTYPE must consist of the following components, in this order:
1. A string that is an ASCII case-insensitive match for the string
"<!DOCTYPE".
2. One or more space characters.
3. A string that is an ASCII case-insensitive match for the string
"html".
4. Optionally, a DOCTYPE legacy string.
5. Zero or more space characters.
6. A U+003E GREATER-THAN SIGN character (>).
In other words, <!DOCTYPE html>, case-insensitively.
For the purposes of HTML generators that cannot output HTML markup with
the short DOCTYPE "<!DOCTYPE html>", a DOCTYPE legacy string may be
inserted into the DOCTYPE (in the position defined above). This string
must consist of:
1. One or more space characters.
2. A string that is an ASCII case-insensitive match for the string
"SYSTEM".
3. One or more space characters.
4. A U+0022 QUOTATION MARK or U+0027 APOSTROPHE character (the quote
mark).
5. The literal string "about:legacy-compat".
6. A matching U+0022 QUOTATION MARK or U+0027 APOSTROPHE character (i.e.,
the same character as in the earlier step labeled quote mark).
In other words, <!DOCTYPE html SYSTEM "about:legacy-compat"> or <!DOCTYPE
html SYSTEM 'about:legacy-compat'>, case-insensitively except for the part
in single or double quotes.
The DOCTYPE legacy string should not be used unless the document is
generated from a system that cannot output the shorter string.
8.1.2. Elements
There are six different kinds of elements: void elements, the template
elements, raw text elements, escapable raw text elements, foreign
elements, and normal elements.
Void elements
area, base, br, col, embed, hr, img, input, link, meta, param,
source, track, wbr
The template elements
template
Raw text elements
script, style
escapable raw text elements
textarea, title
Foreign elements
Elements from the MathML namespace and the SVG namespace.
Normal elements
All other allowed HTML elements are normal elements.
Tags are used to delimit the start and end of elements in the markup. Raw
text, escapable raw text, and normal elements have a start tag to indicate
where they begin, and an end tag to indicate where they end. The start and
end tags of certain normal elements can be omitted, as described below in
the section on [[#optional tags]]. Those that cannot be omitted must not
be omitted. Void elements only have a start tag; end tags must not be
specified for void elements. Foreign elements must either have a start tag
and an end tag, or a start tag that is marked as self-closing, in which
case they must not have an end tag.
The contents of the element must be placed between just after the start
tag (which might be implied, in certain cases) and just before the end tag
(which again, might be implied, in certain cases). The exact allowed
contents of each individual element depend on the content model of that
element, as described earlier in this specification. Elements must not
contain content that their content model disallows. In addition to the
restrictions placed on the contents by those content models, however, the
five types of elements have additional syntactic requirements.
Void elements can’t have any contents (since there’s no end tag, no
content can be put between the start tag and the end tag).
The template element can have template contents, but such template
contents are not children of the template element itself. Instead, they
are stored in a DocumentFragment associated with a different Document —
without a browsing context — so as to avoid the template contents
interfering with the main Document. The markup for the template contents
of a template element is placed just after the template element’s start
tag and just before template element’s end tag (as with other elements),
and may consist of any text, character references, elements, and comments,
but the text must not contain the character U+003C LESS-THAN SIGN (<) or
an ambiguous ampersand.
Raw text elements can have text, though it has restrictions described
below.
Escapable raw text elements can have text and character references, but
the text must not contain an ambiguous ampersand. There are also further
restrictions described below.
Foreign elements whose start tag is marked as self-closing can’t have any
contents (since, again, as there’s no end tag, no content can be put
between the start tag and the end tag). Foreign elements whose start tag
is not marked as self-closing can have text, character references, CDATA
sections, other elements, and comments, but the text must not contain the
character U+003C LESS-THAN SIGN (<) or an ambiguous ampersand.
The HTML syntax does not support namespace declarations, even in foreign
elements.
For instance, consider the following HTML fragment:
<p>
<svg>
<metadata>
<!-- this is invalid -->
<cdr:license xmlns:cdr="https://www.example.com/cdr/metadata" name="MIT"/>
</metadata>
</svg>
</p>
The innermost element, cdr:license, is actually in the SVG namespace, as
the "xmlns:cdr" attribute has no effect (unlike in XML). In fact, as the
comment in the fragment above says, the fragment is actually
non-conforming. This is because the SVG specification does not define any
elements called "cdr:license" in the SVG namespace.
Normal elements can have text, character references, other elements, and
comments, but the text must not contain the character U+003C LESS-THAN
SIGN (<) or an ambiguous ampersand. Some normal elements also have yet
more restrictions on what content they are allowed to hold, beyond the
restrictions imposed by the content model and those described in this
paragraph. Those restrictions are described below.
Tags contain a tag name, giving the element’s name. HTML elements all have
names that only use alphanumeric ASCII characters. In the HTML syntax, tag
names, even those for foreign elements, may be written with any mix of
lower- and uppercase letters that, when converted to all-lowercase,
matches the element’s tag name; tag names are case-insensitive.
8.1.2.1. Start tags
Start tags must have the following format:
1. The first character of a start tag must be a U+003C LESS-THAN SIGN
character (<).
2. The next few characters of a start tag must be the element’s tag name.
3. If there are to be any attributes in the next step, there must first
be one or more space characters.
4. Then, the start tag may have a number of attributes, the syntax for
which is described below. Attributes must be separated from each other
by one or more space characters.
5. After the attributes, or after the tag name if there are no
attributes, there may be one or more space characters. (Some
attributes are required to be followed by a space. See §8.1.2.3
Attributes below.)
6. Then, if the element is one of the void elements, or if the element is
a foreign element, then there may be a single U+002F SOLIDUS character
(/). This character has no effect on void elements, but on foreign
elements it marks the start tag as self-closing.
7. Finally, start tags must be closed by a U+003E GREATER-THAN SIGN
character (>).
8.1.2.2. End tags
End tags must have the following format:
1. The first character of an end tag must be a U+003C LESS-THAN SIGN
character (<).
2. The second character of an end tag must be a U+002F SOLIDUS character
(/).
3. The next few characters of an end tag must be the element’s tag name.
4. After the tag name, there may be one or more space characters.
5. Finally, end tags must be closed by a U+003E GREATER-THAN SIGN
character (>).
8.1.2.3. Attributes
Attributes for an element are expressed inside the element’s start tag.
Attributes have a name and a value. Attribute names must consist of one or
more characters other than the space characters, U+0000 NULL, U+0022
QUOTATION MARK ("), U+0027 APOSTROPHE ('), U+003E GREATER-THAN SIGN (>),
U+002F SOLIDUS (/), and U+003D EQUALS SIGN (=) characters, the control
characters, and any characters that are not defined by Unicode. In the
HTML syntax, attribute names, even those for foreign elements, may be
written with any mix of lower- and uppercase letters that are an ASCII
case-insensitive match for the attribute’s name.
Attribute values are a mixture of text and character references, except
with the additional restriction that the text cannot contain an ambiguous
ampersand.
Attributes can be specified in four different ways:
Empty attribute syntax
Just the attribute name. The value is implicitly the empty string.
In the following example, the disabled attribute is given with the
empty attribute syntax:
<input disabled>
If an attribute using the empty attribute syntax is to be followed
by another attribute, then there must be a space character
separating the two.
Unquoted attribute value syntax
The attribute name, followed by zero or more space characters,
followed by a single U+003D EQUALS SIGN character, followed by
zero or more space characters, followed by the attribute value,
which, in addition to the requirements given above for attribute
values, must not contain any literal space characters, any U+0022
QUOTATION MARK characters ("), U+0027 APOSTROPHE characters ('),
U+003D EQUALS SIGN characters (=), U+003C LESS-THAN SIGN
characters (<), U+003E GREATER-THAN SIGN characters (>), or U+0060
GRAVE ACCENT characters (`), and must not be the empty string.
In the following example, the value attribute is given with the
unquoted attribute value syntax:
<input value=yes>
If an attribute using the unquoted attribute syntax is to be
followed by another attribute or by the optional U+002F SOLIDUS
character (/) allowed in step 6 of the start tag syntax above,
then there must be a space character separating the two.
Single-quoted attribute value syntax
The attribute name, followed by zero or more space characters,
followed by a single U+003D EQUALS SIGN character, followed by
zero or more space characters, followed by a single U+0027
APOSTROPHE character ('), followed by the attribute value, which,
in addition to the requirements given above for attribute values,
must not contain any literal U+0027 APOSTROPHE characters ('), and
finally followed by a second single U+0027 APOSTROPHE character
(').
In the following example, the type attribute is given with the
single-quoted attribute value syntax:
<input type='checkbox'>
If an attribute using the single-quoted attribute syntax is to be
followed by another attribute, then there must be a space
character separating the two.
Double-quoted attribute value syntax
The attribute name, followed by zero or more space characters,
followed by a single U+003D EQUALS SIGN character, followed by
zero or more space characters, followed by a single U+0022
QUOTATION MARK character ("), followed by the attribute value,
which, in addition to the requirements given above for attribute
values, must not contain any literal U+0022 QUOTATION MARK
characters ("), and finally followed by a second single U+0022
QUOTATION MARK character (").
In the following example, the name attribute is given with the
double-quoted attribute value syntax:
<input name="be evil">
If an attribute using the double-quoted attribute syntax is to be
followed by another attribute, then there must be a space
character separating the two.
There must never be two or more attributes on the same start tag whose
names are an ASCII case-insensitive match for each other.
----------------------------------------------------------------------
When a foreign element has one of the namespaced attributes given by the
local name and namespace of the first and second cells of a row from the
following table, it must be written using the name given by the third cell
from the same row.
Local name Namespace Attribute name
actuate XLink namespace xlink:actuate
arcrole XLink namespace xlink:arcrole
href XLink namespace xlink:href
role XLink namespace xlink:role
show XLink namespace xlink:show
title XLink namespace xlink:title
type XLink namespace xlink:type
lang XML namespace xml:lang
space XML namespace xml:space
xmlns XMLNS namespace xmlns
xlink XMLNS namespace xmlns:xlink
No other namespaced attribute can be expressed in the HTML syntax.
Whether the attributes in the table above are conforming or not is defined
by other specifications (e.g., the SVG and MathML specifications); this
section only describes the syntax rules if the attributes are serialized
using the HTML syntax.
8.1.2.4. Optional tags
Certain tags can be omitted.
Omitting an element’s start tag in the situations described below does not
mean the element is not present; it is implied, but it is still there. For
example, an HTML document always has a root html element, even if the
string <html> doesn’t appear anywhere in the markup.
An html element’s start tag may be omitted if the first thing inside the
html element is not a comment.
For example, in the following case it’s ok to remove the "<html>" tag:
<!DOCTYPE HTML>
<html>
<head>
<title>Hello</title>
</head>
<body>
<p>Welcome to this example.</p>
</body>
</html>
Doing so would make the document look like this:
<!DOCTYPE HTML>
<head>
<title>Hello</title>
</head>
<body>
<p>Welcome to this example.</p>
</body>
</html>
This has the exact same DOM. In particular, note that white space around
the document element is ignored by the parser. The following example would
also have the exact same DOM:
<!DOCTYPE HTML><head>
<title>Hello</title>
</head>
<body>
<p>Welcome to this example.</p>
</body>
</html>
However, in the following example, removing the start tag moves the
comment to before the html element:
<!DOCTYPE HTML>
<html>
<!-- where is this comment in the DOM? -->
<head>
<title>Hello</title>
</head>
<body>
<p>Welcome to this example.</p>
</body>
</html>
With the tag removed, the document actually turns into the same as this:
<!DOCTYPE HTML>
<!-- where is this comment in the DOM? -->
<html>
<head>
<title>Hello</title>
</head>
<body>
<p>Welcome to this example.</p>
</body>
</html>
This is why the tag can only be removed if it is not followed by a
comment: removing the tag when there is a comment there changes the
document’s resulting parse tree. Of course, if the position of the comment
does not matter, then the tag can be omitted, as if the comment had been
moved to before the start tag in the first place.
An html element’s end tag may be omitted if the html element is not
immediately followed by a comment.
A head element’s start tag may be omitted if the element is empty, or if
the first thing inside the head element is an element.
A head element’s end tag may be omitted if the head element is not
immediately followed by a space character or a comment.
A body element’s start tag may be omitted if the element is empty, or if
the first thing inside the body element is not a space character or a
comment, except if the first thing inside the body element is a meta,
link, script, style, or template element.
A body element’s end tag may be omitted if the body element is not
immediately followed by a comment.
Note that in the example above, the head element start and end tags, and
the body element start tag, can’t be omitted, because they are surrounded
by white space:
<!DOCTYPE HTML>
<html>
<head>
<title>Hello</title>
</head>
<body>
<p>Welcome to this example.</p>
</body>
</html>
(The body and html element end tags could be omitted without trouble; any
spaces after those get parsed into the body element anyway.)
Usually, however, white space isn’t an issue. If we first remove the white
space we don’t care about:
<!DOCTYPE HTML><html><head><title>Hello</title></head><body><p>Welcome to this example.</p></body></html>
Then we can omit a number of tags without affecting the DOM:
<!DOCTYPE HTML><title>Hello</title><p>Welcome to this example.</p>
At that point, we can also add some white space back:
<!DOCTYPE HTML>
<title>Hello</title>
<p>Welcome to this example.</p>
This would be equivalent to this document, with the omitted tags shown in
their parser-implied positions; the only white space text node that
results from this is the newline at the end of the head element:
<!DOCTYPE HTML>
<html><head><title>Hello</title>
</head><body><p>Welcome to this example.</p></body></html>
An li element’s end tag may be omitted if the li element is immediately
followed by another li element or if there is no more content in the
parent element.
A dt element’s end tag may be omitted if the dt element is immediately
followed by another dt element or a dd element.
A dd element’s end tag may be omitted if the dd element is immediately
followed by another dd element or a dt element, or if there is no more
content in the parent element.
A p element’s end tag may be omitted if the p element is immediately
followed by an address, article, aside, blockquote, details, div, dl,
fieldset, figcaption, figure, footer, form, h1, h2, h3, h4, h5, h6,
header, hr, main, nav, ol, p, pre, section, table, or ul element, or if
there is no more content in the parent element and the parent element is
an HTML element that is not an a, audio, del, ins, map, noscript, or video
element, or an autonomous custom element.
We can thus simplify the earlier example further:
<!DOCTYPE HTML><title>Hello</title><p>Welcome to this example.</p>
An rt element’s end tag may be omitted if the rt element is immediately
followed by an rt or rp element, or if there is no more content in the
parent element.
An rp element’s end tag may be omitted if the rp element is immediately
followed by an rt or rp element, or if there is no more content in the
parent element.
An optgroup element’s end tag may be omitted if the optgroup element is
immediately followed by another optgroup element, or if there is no more
content in the parent element.
An option element’s end tag may be omitted if the option element is
immediately followed by another option element, or if it is immediately
followed by an optgroup element, or if there is no more content in the
parent element.
A colgroup element’s start tag may be omitted if the first thing inside
the colgroup element is a col element, and if the element is not
immediately preceded by another colgroup element whose end tag has been
omitted. (It can’t be omitted if the element is empty.)
A colgroup element’s end tag may be omitted if the colgroup element is not
immediately followed by a space character or a comment.
A caption element’s end tag may be omitted if the caption element is not
immediately followed by a space character or a comment.
A thead element’s end tag may be omitted if the thead element is
immediately followed by a tbody or tfoot element.
A tbody element’s start tag may be omitted if the first thing inside the
tbody element is a tr element, and if the element is not immediately
preceded by a tbody, thead, or tfoot element whose end tag has been
omitted. (It can’t be omitted if the element is empty.)
A tbody element’s end tag may be omitted if the tbody element is
immediately followed by a tbody or tfoot element, or if there is no more
content in the parent element.
A tfoot element’s end tag may be omitted if there is no more content in
the parent element.
A tr element’s end tag may be omitted if the tr element is immediately
followed by another tr element, or if there is no more content in the
parent element.
A td element’s end tag may be omitted if the td element is immediately
followed by a td or th element, or if there is no more content in the
parent element.
A th element’s end tag may be omitted if the th element is immediately
followed by a td or th element, or if there is no more content in the
parent element.
The ability to omit all these table-related tags makes table markup much
terser.
Take this example:
<table>
<caption>37547 TEE Electric Powered Rail Car Train Functions (Abbreviated)</caption>
<colgroup><col><col><col></colgroup>
<thead>
<tr>
<th>Function</th>
<th>Control Unit</th>
<th>Central Station</th>
</tr>
</thead>
<tbody>
<tr>
<td>Headlights</td>
<td>✔</td>
<td>✔</td>
</tr>
<tr>
<td>Interior Lights</td>
<td>✔</td>
<td>✔</td>
</tr>
<tr>
<td>Electric locomotive operating sounds</td>
<td>✔</td>
<td>✔</td>
</tr>
<tr>
<td>Engineer’s cab lighting</td>
<td></td>
<td>✔</td>
</tr>
<tr>
<td>Station Announcements - Swiss</td>
<td></td>
<td>✔</td>
</tr>
</tbody>
</table>
The exact same table, modulo some white space differences, could be marked
up as follows:
<table>
<caption>37547 TEE Electric Powered Rail Car Train Functions (Abbreviated)
<colgroup><col><col><col>
<thead>
<tr>
<th>Function
<th>Control Unit
<th>Central Station
<tbody>
<tr>
<td>Headlights
<td>✔
<td>✔
<tr>
<td>Interior Lights
<td>✔
<td>✔
<tr>
<td>Electric locomotive operating sounds
<td>✔
<td>✔
<tr>
<td>Engineer’s cab lighting
<td>
<td>✔
<tr>
<td>Station Announcements - Swiss
<td>
<td>✔
</table>
Since the cells take up much less room this way, this can be made even
terser by having each row on one line:
<table>
<caption>37547 TEE Electric Powered Rail Car Train Functions (Abbreviated)
<colgroup><col><col><col>
<thead>
<tr> <th>Function <th>Control Unit <th>Central Station
<tbody>
<tr> <td>Headlights <td>✔ <td>✔
<tr> <td>Interior Lights <td>✔ <td>✔
<tr> <td>Electric locomotive operating sounds <td>✔ <td>✔
<tr> <td>Engineer’s cab lighting <td> <td>✔
<tr> <td>Station Announcements - Swiss <td> <td>✔
</table>
The only differences between these tables, at the DOM level, is with the
precise position of the (in any case semantically-neutral) white space.
However, a start tag must never be omitted if it has any attributes.
Returning to the earlier example with all the white space removed and then
all the optional tags removed:
<!DOCTYPE HTML><title>Hello</title><p>Welcome to this example.
If the body element in this example had to have a class attribute and the
html element had to have a lang attribute, the markup would have to
become:
<!DOCTYPE HTML><html lang="en"><title>Hello</title><body class="demo"><p>Welcome to this example.
This section assumes that the document is conforming, in particular, that
there are no content model violations. Omitting tags in the fashion
described in this section in a document that does not conform to the
content models described in this specification is likely to result in
unexpected DOM differences (this is, in part, what the content models are
designed to avoid).
8.1.2.5. Restrictions on content models
For historical reasons, certain elements have extra restrictions beyond
even the restrictions given by their content model.
A table element must not contain tr elements, even though these elements
are technically allowed inside table elements according to the content
models described in this specification. (If a tr element is put inside a
table in the markup, it will in fact imply a tbody start tag before it.)
A single newline may be placed immediately after the start tag of pre and
textarea elements. This does not affect the processing of the element. The
otherwise optional newline must be included if the element’s contents
themselves start with a newline (because otherwise the leading newline in
the contents would be treated like the optional newline, and ignored).
The following two pre blocks are equivalent:
<pre>Hello</pre>
<pre>
Hello</pre>
8.1.2.6. Restrictions on the contents of raw text and escapable raw text
elements
The text in raw text and escapable raw text elements must not contain any
occurrences of the string "</" (U+003C LESS-THAN SIGN, U+002F SOLIDUS)
followed by characters that case-insensitively match the tag name of the
element followed by one of U+0009 CHARACTER TABULATION (tab), U+000A LINE
FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR), U+0020
SPACE, U+003E GREATER-THAN SIGN (>), or U+002F SOLIDUS (/).
8.1.3. Text
Text is allowed inside elements, attribute values, and comments. Extra
constraints are placed on what is and what is not allowed in text based on
where the text is to be put, as described in the other sections.
8.1.3.1. Newlines
Newlines in HTML may be represented either as U+000D CARRIAGE RETURN (CR)
characters, U+000A LINE FEED (LF) characters, or pairs of U+000D CARRIAGE
RETURN (CR), U+000A LINE FEED (LF) characters in that order.
Where character references are allowed, a character reference of a U+000A
LINE FEED (LF) character (but not a U+000D CARRIAGE RETURN (CR) character)
also represents a newline.
8.1.4. Character references
In certain cases described in other sections, text may be mixed with
character references. These can be used to escape characters that couldn’t
otherwise legally be included in text.
Character references must start with a U+0026 AMPERSAND character (&).
Following this, there are three possible kinds of character references:
Named character references
The ampersand must be followed by one of the names given in §8.5
Named character references section, using the same case. The name
must be one that is terminated by a U+003B SEMICOLON character
(;).
Decimal numeric character reference
The ampersand must be followed by a U+0023 NUMBER SIGN character
(#), followed by one or more ASCII digits, representing a base-ten
integer that corresponds to a Unicode code point that is allowed
according to the definition below. The digits must then be
followed by a U+003B SEMICOLON character (;).
Hexadecimal numeric character reference
The ampersand must be followed by a U+0023 NUMBER SIGN character
(#), which must be followed by either a U+0078 LATIN SMALL LETTER
X character (x) or a U+0058 LATIN CAPITAL LETTER X character (X),
which must then be followed by one or more ASCII hex digits,
representing a hexadecimal integer that corresponds to a Unicode
code point that is allowed according to the definition below. The
digits must then be followed by a U+003B SEMICOLON character (;).
The numeric character reference forms described above are allowed to
reference any Unicode code point other than U+0000, U+000D, permanently
undefined Unicode characters (noncharacters), surrogates (U+D800–U+DFFF),
and control characters other than space characters.
An ambiguous ampersand is a U+0026 AMPERSAND character (&) that is
followed by one or more alphanumeric ASCII characters, followed by a
U+003B SEMICOLON character (;), where these characters do not match any of
the names given in the §8.5 Named character references section.
8.1.5. CDATA sections
CDATA sections must consist of the following components, in this order:
1. The string "<![CDATA[".
2. Optionally, text, with the additional restriction that the text must
not contain the string "]]]]><![CDATA[>".
3. The string "]]]]><![CDATA[>".
CDATA sections can only be used in foreign content (MathML or SVG). In
this example, a CDATA section is used to escape the contents of a MathML
ms element:
<p>You can add a string to a number, but this stringifies the number:</p>
<math>
<ms><![CDATA[x<y]]]]><![CDATA[></ms>
<mo>+</mo>
<mn>3</mn>
<mo>=</mo>
<ms><![CDATA[x<y3]]]]><![CDATA[></ms>
</math>
8.1.6. Comments
Comments must have the following format:
1. The string "<!--"
2. Optionally, text, with the additional restriction that the text must
not start with the string ">", nor start with the string "->", nor
contain the strings "<!--", "-->", or "--!>", nor end with the string
"<!-".
3. The string "-->"
The text is allowed to end with the string "<!", as in <!--My favorite
operators are > and <!-->.
8.2. Parsing HTML documents
This section only applies to user agents, data mining tools, and
conformance checkers.
The rules for parsing XML documents into DOM trees are covered by the next
section, entitled "§9 The XML syntax".
User agents must use the parsing rules described in this section to
generate the DOM trees from text/html resources. Together, these rules
define what is referred to as the HTML parser.
While the HTML syntax described in this specification bears a close
resemblance to SGML and XML, it is a separate language with its own
parsing rules.
Some earlier versions of HTML (in particular from HTML 2.0 to HTML 4.01)
were based on SGML and used SGML parsing rules. However, few (if any) web
browsers ever implemented true SGML parsing for HTML documents; the only
user agents to strictly handle HTML as an SGML application have
historically been validators. The resulting confusion — with validators
claiming documents to have one representation while widely deployed Web
browsers interoperably implemented a different representation — has wasted
decades of productivity. This version of HTML thus returns to a non-SGML
basis.
Authors interested in using SGML tools in their authoring pipeline are
encouraged to use XML tools and the XML serialization of HTML.
This specification defines the parsing rules for HTML documents, whether
they are syntactically correct or not. Certain points in the parsing
algorithm are said to be parse errors. The error handling for parse errors
is well-defined (that’s the processing rules described throughout this
specification), but user agents, while parsing an HTML document, may abort
the parser at the first parse error that they encounter for which they do
not wish to apply the rules described in this specification.
Conformance checkers must report at least one parse error condition to the
user if one or more parse error conditions exist in the document and must
not report parse error conditions if none exist in the document.
Conformance checkers may report more than one parse error condition if
more than one parse error condition exists in the document.
Parse errors are only errors with the syntax of HTML. In addition to
checking for parse errors, conformance checkers will also verify that the
document obeys all the other conformance requirements described in this
specification.
For the purposes of conformance checkers, if a resource is determined to
be in the HTML syntax, then it is an HTML document.
As stated in the terminology section, references to element types that do
not explicitly specify a namespace always refer to elements in the HTML
namespace. Where possible, references to such elements are hyperlinked to
their definition.
8.2.1. Overview of the parsing model
The input to the HTML parsing process consists of a stream of Unicode code
points, which is passed through a tokenization stage followed by a tree
construction stage. The output is a Document object.
Implementations that do not support scripting do not have to actually
create a DOM Document object, but the DOM tree in such cases is still used
as the model for the rest of the specification.
In the common case, the data handled by the tokenization stage comes from
the network, but it can also come from script running in the user agent,
e.g., using the document.write() API.
There is only one set of states for the tokenizer stage and the tree
construction stage, but the tree construction stage is reentrant, meaning
that while the tree construction stage is handling one token, the
tokenizer might be resumed, causing further tokens to be emitted and
processed before the first token’s processing is complete.
In the following example, the tree construction stage will be called upon
to handle a "p" start tag token while handling the "script" end tag token:
...
<script>
document.write('<p>');
</script>
...
To handle these cases, parsers have a script nesting level, which must be
initially set to zero, and a parser pause flag, which must be initially
set to false.
8.2.2. The input byte stream
The stream of Unicode code points that comprises the input to the
tokenization stage will be initially seen by the user agent as a stream of
bytes (typically coming over the network or from the local file system).
The bytes encode the actual characters according to a particular character
encoding, which the user agent uses to decode the bytes into characters.
For XML documents, the algorithm user agents are required to use to
determine the character encoding is given by the XML specification. This
section does not apply to XML documents. [XML]
Usually, the encoding sniffing algorithm defined below is used to
determine the character encoding.
Given a character encoding, the bytes in the input byte stream must be
converted to characters for the tokenizer’s input stream, by passing the
input byte stream and character encoding to decode.
A leading Byte Order Mark (BOM) causes the character encoding argument to
be ignored and will itself be skipped.
Bytes or sequences of bytes in the original byte stream that did not
conform to the Encoding specification (e.g., invalid UTF-8 byte sequences
in a UTF-8 input byte stream) are errors that conformance checkers are
expected to report. [ENCODING]
The decoder algorithms describe how to handle invalid input; for security
reasons, it is imperative that those rules be followed precisely.
Differences in how invalid byte sequences are handled can result in,
amongst other problems, script injection vulnerabilities ("XSS").
When the HTML parser is decoding an input byte stream, it uses a character
encoding and a confidence. The confidence is either tentative, certain, or
irrelevant. The encoding used, and whether the confidence in that encoding
is tentative or certain, is used during the parsing to determine whether
to change the encoding. If no encoding is necessary, e.g., because the
parser is operating on a Unicode stream and doesn’t have to use a
character encoding at all, then the confidence is irrelevant.
Some algorithms feed the parser by directly adding characters to the input
stream rather than adding bytes to the input byte stream.
8.2.2.1. Parsing with a known character encoding
When the HTML parser is to operate on an input byte stream that has a
known definite encoding, then the character encoding is that encoding and
the confidence is certain.
8.2.2.2. Determining the character encoding
In some cases, it might be impractical to unambiguously determine the
encoding before parsing the document. Because of this, this specification
provides for a two-pass mechanism with an optional pre-scan.
Implementations are allowed, as described below, to apply a simplified
parsing algorithm to whatever bytes they have available before beginning
to parse the document. Then, the real parser is started, using a tentative
encoding derived from this pre-parse and other out-of-band metadata. If,
while the document is being loaded, the user agent discovers a character
encoding declaration that conflicts with this information, then the parser
can get reinvoked to perform a parse of the document with the real
encoding.
User agents must use the following algorithm, called the encoding sniffing
algorithm, to determine the character encoding to use when decoding a
document in the first pass. This algorithm takes as input any out-of-band
metadata available to the user agent (e.g., the Content-Type metadata of
the document) and all the bytes available so far, and returns a character
encoding and a confidence that is either tentative or certain.
1. If the user has explicitly instructed the user agent to override the
document’s character encoding with a specific encoding, optionally
return that encoding with the confidence certain and abort these
steps.
Typically, user agents remember such user requests across sessions,
and in some cases apply them to documents in iframes as well.
2. The user agent may wait for more bytes of the resource to be
available, either in this step or at any later step in this algorithm.
For instance, a user agent might wait 500ms or 1024 bytes, whichever
came first. In general preparsing the source to find the encoding
improves performance, as it reduces the need to throw away the data
structures used when parsing upon finding the encoding information.
However, if the user agent delays too long to obtain data to determine
the encoding, then the cost of the delay could outweigh any
performance improvements from the preparse.
The authoring conformance requirements for character encoding
declarations limit them to only appearing in the first 1024 bytes.
User agents are therefore encouraged to use the prescan algorithm
below (as invoked by these steps) on the first 1024 bytes, but not to
stall beyond that.
3. If the transport layer specifies a character encoding, and it is
supported, return that encoding with the confidence certain, and abort
these steps.
4. Optionally prescan the byte stream to determine its encoding. The end
condition is that the user agent decides that scanning further bytes
would not be efficient. User agents are encouraged to only prescan the
first 1024 bytes. User agents may decide that scanning any bytes is
not efficient, in which case these substeps are entirely skipped.
The aforementioned algorithm either aborts unsuccessfully or returns a
character encoding. If it returns a character encoding, then this
algorithm must be aborted, returning the same encoding, with
confidence tentative.
5. If the HTML parser for which this algorithm is being run is associated
with a Document that is itself in a nested browsing context, run these
substeps:
1. Let new document be the Document with which the HTML parser is
associated.
2. Let parent document be the Document through which new document is
nested (the active document of the parent browsing context of new
document).
3. If parent document’s origin is not the same origin as new
document’s origin, then abort these substeps.
4. If parent document’s character encoding is not an
ASCII-compatible encoding, then abort these substeps.
5. Return parent document’s character encoding, with the confidence
tentative, and abort the encoding sniffing algorithm's steps.
6. Otherwise, if the user agent has information on the likely encoding
for this page, e.g., based on the encoding of the page when it was
last visited, then return that encoding, with the confidence
tentative, and abort these steps.
7. The user agent may attempt to autodetect the character encoding from
applying frequency analysis or other algorithms to the data stream.
Such algorithms may use information about the resource other than the
resource’s contents, including the address of the resource. If
autodetection succeeds in determining a character encoding, and that
encoding is a supported encoding, then return that encoding, with the
confidence tentative, and abort these steps. [UNIVCHARDET]
User agents are generally discouraged from attempting to autodetect
encodings for resources obtained over the network, since doing so
involves inherently non-interoperable heuristics. Attempting to detect
encodings based on an HTML document’s preamble is especially tricky
since HTML markup typically uses only ASCII characters, and HTML
documents tend to begin with a lot of markup rather than with text
content.
The UTF-8 encoding has a highly detectable bit pattern. Files from the
local file system that contain bytes with values greater than 0x7F
which match the UTF-8 pattern are very likely to be UTF-8, while
documents with byte sequences that do not match it are very likely
not. When a user agent can examine the whole file, rather than just
the preamble, detecting for UTF-8 specifically can be especially
effective. [PPUTF8] [UTF8DET]
8. Otherwise, return an implementation-defined or user-specified default
character encoding, with the confidence tentative.
In controlled environments or in environments where the encoding of
documents can be prescribed (for example, for user agents intended for
dedicated use in new networks), the comprehensive UTF-8 encoding is
suggested.
In other environments, the default encoding is typically dependent on
the user’s locale (an approximation of the languages, and thus often
encodings, of the pages that the user is likely to frequent). The
following table gives suggested defaults based on the user’s locale,
for compatibility with legacy content. Locales are identified by BCP
47 language tags. [BCP47] [ENCODING]
Locale language Suggested default encoding
ar Arabic windows-1256
ba Bashkir windows-1251
be Belarusian windows-1251
bg Bulgarian windows-1251
cs Czech windows-1250
el Greek ISO-8859-7
et Estonian windows-1257
fa Persian windows-1256
he Hebrew windows-1255
hr Croatian windows-1250
hu Hungarian ISO-8859-2
ja Japanese Shift_JIS
kk Kazakh windows-1251
ko Korean EUC-KR
ku Kurdish windows-1254
ky Kyrgyz windows-1251
lt Lithuanian windows-1257
lv Latvian windows-1257
mk Macedonian windows-1251
pl Polish ISO-8859-2
ru Russian windows-1251
sah Yakut windows-1251
sk Slovak windows-1250
sl Slovenian ISO-8859-2
sr Serbian windows-1251
tg Tajik windows-1251
th Thai windows-874
tr Turkish windows-1254
tt Tatar windows-1251
uk Ukrainian windows-1251
vi Vietnamese windows-1258
zh-CN Chinese (People’s Republic of China) gb18030
zh-TW Chinese (Taiwan) Big5
All other locales windows-1252
The contents of this table are derived from the intersection of
Windows, Chrome, and Firefox defaults.
The document’s character encoding must immediately be set to the value
returned from this algorithm, at the same time as the user agent uses the
returned value to select the decoder to use for the input byte stream.
----------------------------------------------------------------------
When an algorithm requires a user agent to prescan a byte stream to
determine its encoding, given some defined end condition, then it must run
the following steps. These steps either abort unsuccessfully or return a
character encoding. If at any point during these steps (including during
instances of the get an attribute algorithm invoked by this one) the user
agent either runs out of bytes (meaning the position pointer created in
the first step below goes beyond the end of the byte stream obtained so
far) or reaches its end condition, then abort the prescan a byte stream to
determine its encoding algorithm unsuccessfully.
1. Let position be a pointer to a byte in the input byte stream,
initially pointing at the first byte.
2. Loop: If position points to:
A sequence of bytes starting with: 0x3C 0x21 0x2D 0x2D (ASCII
'<!--')
Advance the position pointer so that it points at the
first 0x3E byte which is preceded by two 0x2D bytes
(i.e., at the end of an ASCII '-->' sequence) and comes
after the 0x3C byte that was found. (The two 0x2D bytes
can be the same as those in the '<!--' sequence.)
A sequence of bytes starting with: 0x3C, 0x4D or 0x6D, 0x45 or
0x65, 0x54 or 0x74, 0x41 or 0x61, and one of 0x09, 0x0A, 0x0C,
0x0D, 0x20, 0x2F (case-insensitive ASCII '<meta' followed by a
space or slash)
1. Advance the position pointer so that it points at
the next 0x09, 0x0A, 0x0C, 0x0D, 0x20, or 0x2F byte
(the one in sequence of characters matched above).
2. Let attribute list be an empty list of strings.
3. Let got pragma be false.
4. Let need pragma be null.
5. Let charset be the null value (which, for the
purposes of this algorithm, is distinct from an
unrecognized encoding or the empty string).
6. Attributes: Get an attribute and its value. If no
attribute was sniffed, then jump to the Processing
step below.
7. If the attribute’s name is already in attribute
list, then return to the step labeled Attributes.
8. Add the attribute’s name to attribute list.
9. Run the appropriate step from the following list, if
one applies:
If the attribute’s name is "http-equiv"
If the attribute’s value is
"content-type", then set got pragma to
true.
If the attribute’s name is "content"
Apply the algorithm for extracting a
character encoding from a meta element,
giving the attribute’s value as the
string to parse. If a character
encoding is returned, and if charset is
still set to null, let charset be the
encoding returned, and set need pragma
to true.
If the attribute’s name is "charset"
Let charset be the result of getting an
encoding from the attribute’s value,
and set need pragma to false.
10. Return to the step labeled Attributes.
11. Processing: If need pragma is null, then jump to the
step below labeled Next byte.
12. If need pragma is true but got pragma is false, then
jump to the step below labeled Next byte.
13. If charset is failure, then jump to the step below
labeled Next byte.
14. If charset is a UTF-16 encoding, then set charset to
UTF-8.
15. If charset is x-user-defined, then set charset to
windows-1252.
16. Abort the prescan a byte stream to determine its
encoding algorithm, returning the encoding given by
charset.
A sequence of bytes starting with a 0x3C byte (ASCII <),
optionally a 0x2F byte (ASCII /), and finally a byte in the range
0x41-0x5A or 0x61-0x7A (an ASCII letter)
1. Advance the position pointer so that it points at
the next 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0C
(ASCII FF), 0x0D (ASCII CR), 0x20 (ASCII space), or
0x3E (ASCII >) byte.
2. Repeatedly get an attribute until no further
attributes can be found, then jump to the step below
labeled Next byte.
A sequence of bytes starting with: 0x3C 0x21 (ASCII '<!')
A sequence of bytes starting with: 0x3C 0x2F (ASCII '</')
A sequence of bytes starting with: 0x3C 0x3F (ASCII '<?')
Advance the position pointer so that it points at the
first 0x3E byte (ASCII >) that comes after the 0x3C byte
that was found.
Any other byte
Do nothing with that byte.
3. Next byte: Move position so it points at the next byte in the input
byte stream, and return to the step above labeled Loop.
When the prescan a byte stream to determine its encoding algorithm says to
get an attribute, it means doing this:
1. If the byte at position is one of 0x09 (ASCII TAB), 0x0A (ASCII LF),
0x0C (ASCII FF), 0x0D (ASCII CR), 0x20 (ASCII space), or 0x2F (ASCII
/) then advance position to the next byte and redo this step.
2. If the byte at position is 0x3E (ASCII >), then abort the get an
attribute algorithm. There isn’t one.
3. Otherwise, the byte at position is the start of the attribute name.
Let attribute name and attribute value be the empty string.
4. Process the byte at position as follows:
If it is 0x3D (ASCII =), and the attribute name is longer than
the empty string
Advance position to the next byte and jump to the step
below labeled Value.
If it is 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0C (ASCII FF), 0x0D
(ASCII CR), or 0x20 (ASCII space)
Jump to the step below labeled Spaces.
If it is 0x2F (ASCII /) or 0x3E (ASCII >)
Abort the get an attribute algorithm. The attribute’s
name is the value of attribute name, its value is the
empty string.
If it is in the range 0x41 (ASCII A) to 0x5A (ASCII Z)
Append the Unicode character with code point b+0x20 to
attribute name (where b is the value of the byte at
position). (This converts the input to lowercase.)
Anything else
Append the Unicode character with the same code point as
the value of the byte at position to attribute name. (It
doesn’t actually matter how bytes outside the ASCII range
are handled here, since only ASCII characters can
contribute to the detection of a character encoding.)
5. Advance position to the next byte and return to the previous step.
6. Spaces: If the byte at position is one of 0x09 (ASCII TAB), 0x0A
(ASCII LF), 0x0C (ASCII FF), 0x0D (ASCII CR), or 0x20 (ASCII space)
then advance position to the next byte, then, repeat this step.
7. If the byte at position is not 0x3D (ASCII =), abort the get an
attribute algorithm. The attribute’s name is the value of attribute
name, its value is the empty string.
8. Advance position past the 0x3D (ASCII =) byte.
9. Value: If the byte at position is one of 0x09 (ASCII TAB), 0x0A (ASCII
LF), 0x0C (ASCII FF), 0x0D (ASCII CR), or 0x20 (ASCII space) then
advance position to the next byte, then, repeat this step.
10. Process the byte at position as follows:
If it is 0x22 (ASCII ") or 0x27 (ASCII ')
1. Let b be the value of the byte at position.
2. Quote loop: Advance position to the next byte.
3. If the value of the byte at position is the value of
b, then advance position to the next byte and abort
the get an attribute algorithm. The attribute’s name
is the value of attribute name, and its value is the
value of attribute value.
4. Otherwise, if the value of the byte at position is
in the range 0x41 (ASCII A) to 0x5A (ASCII Z), then
append a Unicode character to attribute value whose
code point is 0x20 more than the value of the byte
at position.
5. Otherwise, append a Unicode character to attribute
value whose code point is the same as the value of
the byte at position.
6. Return to the step above labeled Quote loop.
If it is 0x3E (ASCII >)
Abort the get an attribute algorithm. The attribute’s
name is the value of attribute name, its value is the
empty string.
If it is in the range 0x41 (ASCII A) to 0x5A (ASCII Z)
Append the Unicode character with code point b+0x20 to
attribute value (where b is the value of the byte at
position). Advance position to the next byte.
Anything else
Append the Unicode character with the same code point as
the value of the byte at position to attribute value.
Advance position to the next byte.
11. Process the byte at position as follows:
If it is 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0C (ASCII FF), 0x0D
(ASCII CR), 0x20 (ASCII space), or 0x3E (ASCII >)
Abort the get an attribute algorithm. The attribute’s
name is the value of attribute name and its value is the
value of attribute value.
If it is in the range 0x41 (ASCII A) to 0x5A (ASCII Z)
Append the Unicode character with code point b+0x20 to
attribute value (where b is the value of the byte at
position).
Anything else
Append the Unicode character with the same code point as
the value of the byte at position to attribute value.
12. Advance position to the next byte and return to the previous step.
For the sake of interoperability, user agents should not use a pre-scan
algorithm that returns different results than the one described above.
(But, if you do, please at least let us know, so that we can improve this
algorithm and benefit everyone...)
8.2.2.3. Character encodings
User agents must support the encodings defined in the WHATWG Encoding
specification, including, but not limited to, UTF-8, ISO-8859-2,
ISO-8859-8, windows-1250, windows-1251, windows-1252, windows-1254,
windows-1256, windows-1257, gb18030, Big5, ISO-2022-JP, Shift_JIS, EUC-KR,
UTF-16BE, UTF-16LE, and x-user-defined. User agents must not support other
encodings.
The above prohibits supporting, for example, CESU-8, UTF-7, BOCU-1, SCSU,
EBCDIC, and UTF-32. This specification does not make any attempt to
support prohibited encodings in its algorithms; support and use of
prohibited encodings would thus lead to unexpected behavior. [CESU8]
[RFC2152] [BOCU1] [SCSU]
8.2.2.4. Changing the encoding while parsing
When the parser requires the user agent to change the encoding, it must
run the following steps. This might happen if the encoding sniffing
algorithm described above failed to find a character encoding, or if it
found a character encoding that was not the actual encoding of the file.
1. If the encoding that is already being used to interpret the input
stream is a UTF-16 encoding, then set the confidence to certain and
abort these steps. The new encoding is ignored; if it was anything but
the same encoding, then it would be clearly incorrect.
2. If the new encoding is a UTF-16 encoding, then change it to UTF-8.
3. If the new encoding is the x-user-defined encoding, then change it to
windows-1252. [ENCODING]
4. If the new encoding is identical or equivalent to the encoding that is
already being used to interpret the input stream, then set the
confidence to certain and abort these steps. This happens when the
encoding information found in the file matches what the encoding
sniffing algorithm determined to be the encoding, and in the second
pass through the parser if the first pass found that the encoding
sniffing algorithm described in the earlier section failed to find the
right encoding.
5. If all the bytes up to the last byte converted by the current decoder
have the same Unicode interpretations in both the current encoding and
the new encoding, and if the user agent supports changing the
converter on the fly, then the user agent may change to the new
converter for the encoding on the fly. Set the document’s character
encoding and the encoding used to convert the input stream to the new
encoding, set the confidence to certain, and abort these steps.
6. Otherwise, navigate to the document again, with replacement enabled,
and using the same source browsing context, but this time skip the
encoding sniffing algorithm and instead just set the encoding to the
new encoding and the confidence to certain. Whenever possible, this
should be done without actually contacting the network layer (the
bytes should be re-parsed from memory), even if, e.g., the document is
marked as not being cacheable. If this is not possible and contacting
the network layer would involve repeating a request that uses a method
other than GET), then instead set the confidence to certain and ignore
the new encoding. The resource will be misinterpreted. User agents may
notify the user of the situation, to aid in application development.
This algorithm is only invoked when a new encoding is found declared on a
meta element.
8.2.2.5. Preprocessing the input stream
The input stream consists of the characters pushed into it as the input
byte stream is decoded or from the various APIs that directly manipulate
the input stream.
Any occurrences of any characters in the ranges U+0001 to U+0008, U+000E
to U+001F, U+007F to U+009F, U+FDD0 to U+FDEF, and characters U+000B,
U+FFFE, U+FFFF, U+1FFFE, U+1FFFF, U+2FFFE, U+2FFFF, U+3FFFE, U+3FFFF,
U+4FFFE, U+4FFFF, U+5FFFE, U+5FFFF, U+6FFFE, U+6FFFF, U+7FFFE, U+7FFFF,
U+8FFFE, U+8FFFF, U+9FFFE, U+9FFFF, U+AFFFE, U+AFFFF, U+BFFFE, U+BFFFF,
U+CFFFE, U+CFFFF, U+DFFFE, U+DFFFF, U+EFFFE, U+EFFFF, U+FFFFE, U+FFFFF,
U+10FFFE, and U+10FFFF are parse errors. These are all control characters
or permanently undefined Unicode characters (noncharacters).
Any character that is a not a Unicode character, i.e., any isolated
surrogate, is a parse error. (These can only find their way into the input
stream via script APIs such as document.write().)
U+000D CARRIAGE RETURN (CR) characters and U+000A LINE FEED (LF)
characters are treated specially. Any LF character that immediately
follows a CR character must be ignored, and all CR characters must then be
converted to LF characters. Thus, newlines in HTML DOMs are represented by
LF characters, and there are never any CR characters in the input to the
tokenization stage.
The next input character is the first character in the input stream that
has not yet been consumed or explicitly ignored by the requirements in
this section. Initially, the next input character is the first character
in the input. The current input character is the last character to have
been consumed.
The insertion point is the position (just before a character or just
before the end of the input stream) where content inserted using
document.write() is actually inserted. The insertion point is relative to
the position of the character immediately after it, it is not an absolute
offset into the input stream. Initially, the insertion point is undefined.
The "EOF" character in the tables below is a conceptual character
representing the end of the input stream. If the parser is a
script-created parser, then the end of the input stream is reached when an
explicit "EOF" character (inserted by the document.close() method) is
consumed. Otherwise, the "EOF" character is not a real character in the
stream, but rather the lack of any further characters.
The handling of U+0000 NULL characters varies based on where the
characters are found. In general, they are ignored except where doing so
could plausibly introduce an attack vector. This handling is, by
necessity, spread across both the tokenization stage and the tree
construction stage.
8.2.3. Parse state
8.2.3.1. The insertion mode
The insertion mode is a state variable that controls the primary operation
of the tree construction stage.
Initially, the insertion mode is "initial". It can change to "before
html", "before head", "in head", "in head noscript", "after head", "in
body", "text", "in table", "in table text", "in caption", "in column
group", "in table body", "in row", "in cell", "in select", "in select in
table", "in template", "after body", "in frameset", "after frameset",
"after after body", and "after after frameset" during the course of the
parsing, as described in the tree construction stage. The insertion mode
affects how tokens are processed and whether CDATA sections are supported.
Several of these modes, namely "in head", "in body", "in table", and "in
select", are special, in that the other modes defer to them at various
times. When the algorithm below says that the user agent is to do
something "using the rules for the m insertion mode", where m is one of
these modes, the user agent must use the rules described under the m
insertion mode's section, but must leave the insertion mode unchanged
unless the rules in m themselves switch the insertion mode to a new value.
When the insertion mode is switched to "text" or "in table text", the
original insertion mode is also set. This is the insertion mode to which
the tree construction stage will return.
Similarly, to parse nested template elements, a stack of template
insertion modes is used. It is initially empty. The current template
insertion mode is the insertion mode that was most recently added to the
stack of template insertion modes. The algorithms in the sections below
will push insertion modes onto this stack, meaning that the specified
insertion mode is to be added to the stack, and pop insertion modes from
the stack, which means that the most recently added insertion mode must be
removed from the stack.
----------------------------------------------------------------------
When the steps below require the UA to reset the insertion mode
appropriately, it means the UA must follow these steps:
1. Let last be false.
2. Let node be the last node in the stack of open elements.
3. Loop: If node is the first node in the stack of open elements, then
set last to true, and, if the parser was originally created as part of
the HTML fragment parsing algorithm (fragment case), set node to the
context element passed to that algorithm.
4. If node is a select element, run these substeps:
1. If last is true, jump to the step below labeled Done.
2. Let ancestor be node.
3. Loop: If ancestor is the first node in the stack of open
elements, jump to the step below labeled Done.
4. Let ancestor be the node before ancestor in the stack of open
elements.
5. If ancestor is a template node, jump to the step below labeled
Done.
6. If ancestor is a table node, switch the insertion mode to "in
select in table" and abort these steps.
7. Jump back to the step labeled Loop.
8. Done: Switch the insertion mode to "in select" and abort these
steps.
5. If node is a td or th element and last is false, then switch the
insertion mode to "in cell" and abort these steps.
6. If node is a tr element, then switch the insertion mode to "in row"
and abort these steps.
7. If node is a tbody, thead, or tfoot element, then switch the insertion
mode to "in table body" and abort these steps.
8. If node is a caption element, then switch the insertion mode to "in
caption" and abort these steps.
9. If node is a colgroup element, then switch the insertion mode to "in
column group" and abort these steps.
10. If node is a table element, then switch the insertion mode to "in
table" and abort these steps.
11. If node is a template element, then switch the insertion mode to the
current template insertion mode and abort these steps.
12. If node is a head element and last is false, then switch the insertion
mode to "in head" and abort these steps.
13. If node is a body element, then switch the insertion mode to "in body"
and abort these steps.
14. If node is a frameset element, then switch the insertion mode to "in
frameset" and abort these steps. (fragment case)
15. If node is an html element, run these substeps:
1. If the head element pointer is null, switch the insertion mode to
"before head" and abort these steps. (fragment case)
2. Otherwise, the head element pointer is not null, switch the
insertion mode to "after head" and abort these steps.
16. If last is true, then switch the insertion mode to "in body" and abort
these steps. (fragment case)
17. Let node now be the node before node in the stack of open elements.
18. Return to the step labeled Loop.
8.2.3.2. The stack of open elements
Initially, the stack of open elements is empty. The stack grows downwards;
the topmost node on the stack is the first one added to the stack, and the
bottommost node of the stack is the most recently added node in the stack
(notwithstanding when the stack is manipulated in a random access fashion
as part of the handling for misnested tags).
The "before html" insertion mode creates the html document element, which
is then added to the stack.
In the fragment case, the stack of open elements is initialized to contain
an html element that is created as part of that algorithm. (The fragment
case skips the "before html" insertion mode.)
The html node, however it is created, is the topmost node of the stack. It
only gets popped off the stack when the parser finishes.
The current node is the bottommost node in this stack of open elements.
The adjusted current node is the context element if the parser was created
by the HTML fragment parsing algorithm and the stack of open elements has
only one element in it (fragment case); otherwise, the adjusted current
node is the current node.
Elements in the stack of open elements fall into the following categories:
Special
The following elements have varying levels of special parsing
rules: HTML’s address, applet, area, article, aside, base,
basefont, bgsound, blockquote, body, br, button, caption, center,
col, colgroup, dd, details, dir, div, dl, dt, embed, fieldset,
figcaption, figure, footer, form, frame, frameset, h1, h2, h3, h4,
h5, h6, head, header, hr, html, iframe, img, input, li, link,
listing, main, marquee, meta, nav, noembed, noframes, noscript,
object, ol, p, param, plaintext, pre, script, section, select,
source, style, summary, table, tbody, td, template, textarea,
tfoot, th, thead, title, tr, track, ul, wbr, xmp; MathML mi,
MathML mo, MathML mn, MathML ms, MathML mtext, and MathML
annotation-xml; and SVG foreignObject, SVG desc, and SVG title.
An image start tag token is handled by the tree builder, but it is
not in this list because it is not an element; it gets turned into
an img element.
Formatting
The following HTML elements are those that end up in the list of
active formatting elements: a, b, big, code, em, font, i, nobr, s,
small, strike, strong, tt, and u.
Ordinary
All other elements found while parsing an HTML document.
Typically, the special elements have the start and end tag tokens handled
specifically, while ordinary elements' tokens fall into "any other start
tag" and "any other end tag" clauses, and some parts of the tree builder
check if a particular element in the stack of open elements is in the
special category. However, some elements (e.g., the option element) have
their start or end tag tokens handled specifically, but are still not in
the special category, so that they get the ordinary handling elsewhere.
The stack of open elements is said to have an element target node in a
specific scope consisting of a list of element types list when the
following algorithm terminates in a match state:
1. Initialize node to be the current node (the bottommost node of the
stack).
2. If node is the target node, terminate in a match state.
3. Otherwise, if node is one of the element types in list, terminate in a
failure state.
4. Otherwise, set node to the previous entry in the stack of open
elements and return to step 2. (This will never fail, since the loop
will always terminate in the previous step if the top of the stack —
an html element — is reached.)
The stack of open elements is said to have a particular element in scope
when it has that element in the specific scope consisting of the following
element types:
* applet
* caption
* html
* table
* td
* th
* marquee
* object
* template
* MathML mi
* MathML mo
* MathML mn
* MathML ms
* MathML mtext
* MathML annotation-xml
* SVG foreignObject
* SVG desc
* SVG title
The stack of open elements is said to have a particular element in list
item scope when it has that element in the specific scope consisting of
the following element types:
* All the element types listed above for the has an element in scope
algorithm.
* ol in the HTML namespace
* ul in the HTML namespace
The stack of open elements is said to have a particular element in button
scope when it has that element in the specific scope consisting of the
following element types:
* All the element types listed above for the has an element in scope
algorithm.
* button in the HTML namespace
The stack of open elements is said to have a particular element in table
scope when it has that element in the specific scope consisting of the
following element types:
* html in the HTML namespace
* table in the HTML namespace
* template in the HTML namespace
The stack of open elements is said to have a particular element in select
scope when it has that element in the specific scope consisting of all
element types except the following:
* optgroup in the HTML namespace
* option in the HTML namespace
Nothing happens if at any time any of the elements in the stack of open
elements are moved to a new location in, or removed from, the Document
tree. In particular, the stack is not changed in this situation. This can
cause, amongst other strange effects, content to be appended to nodes that
are no longer in the DOM.
In some cases (namely, when closing misnested formatting elements), the
stack is manipulated in a random-access fashion.
8.2.3.3. The list of active formatting elements
Initially, the list of active formatting elements is empty. It is used to
handle mis-nested formatting element tags.
The list contains elements in the formatting category, and markers. The
markers are inserted when entering applet, object, marquee, template, td,
th, and caption elements, and are used to prevent formatting from
"leaking" into applet, object, marquee, template, td, th, and caption
elements.
In addition, each element in the list of active formatting elements is
associated with the token for which it was created, so that further
elements can be created for that token if necessary.
When the steps below require the UA to push onto the list of active
formatting elements an element element, the UA must perform the following
steps:
1. If there are already three elements in the list of active formatting
elements after the last marker, if any, or anywhere in the list if
there are no markers, that have the same tag name, namespace, and
attributes as element, then remove the earliest such element from the
list of active formatting elements. For these purposes, the attributes
must be compared as they were when the elements were created by the
parser; two elements have the same attributes if all their parsed
attributes can be paired such that the two attributes in each pair
have identical names, namespaces, and values (the order of the
attributes does not matter).
This is the Noah’s Ark clause. But with three per family instead of
two.
2. Add element to the list of active formatting elements.
When the steps below require the UA to reconstruct the active formatting
elements, the UA must perform the following steps:
1. If there are no entries in the list of active formatting elements,
then there is nothing to reconstruct; stop this algorithm.
2. If the last (most recently added) entry in the list of active
formatting elements is a marker, or if it is an element that is in the
stack of open elements, then there is nothing to reconstruct; stop
this algorithm.
3. Let entry be the last (most recently added) element in the list of
active formatting elements.
4. Rewind: If there are no entries before entry in the list of active
formatting elements, then jump to the step labeled Create.
5. Let entry be the entry one earlier than entry in the list of active
formatting elements.
6. If entry is neither a marker nor an element that is also in the stack
of open elements, go to the step labeled Rewind.
7. Advance: Let entry be the element one later than entry in the list of
active formatting elements.
8. Create: Insert an HTML element for the token for which the element
entry was created, to obtain new element.
9. Replace the entry for entry in the list with an entry for new element.
10. If the entry for new element in the list of active formatting elements
is not the last entry in the list, return to the step labeled Advance.
This has the effect of reopening all the formatting elements that were
opened in the current body, cell, or caption (whichever is youngest) that
haven’t been explicitly closed.
The way this specification is written, the list of active formatting
elements always consists of elements in chronological order with the least
recently added element first and the most recently added element last
(except for while steps 7 to 10 of the above algorithm are being executed,
of course).
When the steps below require the UA to clear the list of active formatting
elements up to the last marker, the UA must perform the following steps:
1. Let entry be the last (most recently added) entry in the list of
active formatting elements.
2. Remove entry from the list of active formatting elements.
3. If entry was a marker, then stop the algorithm at this point. The list
has been cleared up to the last marker.
4. Go to step 1.
8.2.3.4. The element pointers
Initially, the head element pointer and the form element pointer are both
null.
Once a head element has been parsed (whether implicitly or explicitly) the
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 make form controls
associate with forms in the face of dramatically bad markup, for
historical reasons. It is ignored inside template elements.
8.2.3.5. Other parsing state flags
The scripting flag is set to "enabled" if scripting was enabled for the
Document with which the parser is associated when the parser was created,
and "disabled" otherwise.
The scripting flag can be enabled even when the parser was originally
created for the HTML fragment parsing algorithm, even though script
elements don’t execute in that case.
The frameset-ok flag is set to "ok" when the parser is created. It is set
to "not ok" after certain tokens are seen.
8.2.4. Tokenization
Implementations must act as if they used the following state machine to
tokenize HTML. The state machine must start in the data state. Most states
consume a single character, which may have various side-effects, and
either switches the state machine to a new state to reconsume the current
input character, or switches it to a new state to consume the next
character, or stays in the same state to consume the next character. Some
states have more complicated behavior and can consume several characters
before switching to another state. In some cases, the tokenizer state is
also changed by the tree construction stage.
When a state says to reconsume a matched character in a specified state,
that means to switch to that state, but when it attempts to consume the
next input character, provide it with the current input character instead.
The exact behavior of certain states depends on the insertion mode and the
stack of open elements. Certain states also use a temporary buffer to
track progress, and the character reference state uses a return state to
return to the state it was invoked from.
The output of the tokenization step is a series of zero or more of the
following tokens: DOCTYPE, start tag, end tag, comment, character,
end-of-file. DOCTYPE tokens have a name, a public identifier, a system
identifier, and a force-quirks flag. When a DOCTYPE token is created, its
name, public identifier, and system identifier must be marked as missing
(which is a distinct state from the empty string), and the force-quirks
flag must be set to off (its other state is on). Start and end tag tokens
have a tag name, a self-closing flag, and a list of attributes, each of
which has a name and a value. When a start or end tag token is created,
its self-closing flag must be unset (its other state is that it be set),
and its attributes list must be empty. Comment and character tokens have
data.
When a token is emitted, it must immediately be handled by the tree
construction stage. The tree construction stage can affect the state of
the tokenization stage, and can insert additional characters into the
stream. (For example, the script element can result in scripts executing
and using the dynamic markup insertion APIs to insert characters into the
stream being tokenized.)
Creating a token and emitting it are distinct actions. It is possible for
a token to be created but implicitly abandoned (never emitted), e.g., if
the file ends unexpectedly while processing the characters that are being
parsed into a start tag token.
When a start tag token is emitted with its self-closing flag set, if the
flag is not acknowledged when it is processed by the tree construction
stage, that is a parse error.
When an end tag token is emitted with attributes, that is a parse error.
When an end tag token is emitted with its self-closing flag set, that is a
parse error.
An appropriate end tag token is an end tag token whose tag name matches
the tag name of the last start tag to have been emitted from this
tokenizer, if any. If no start tag has been emitted from this tokenizer,
then no end tag token is appropriate.
Before each step of the tokenizer, the user agent must first check the
parser pause flag. If it is true, then the tokenizer must abort the
processing of any nested invocations of the tokenizer, yielding control
back to the caller.
The tokenizer state machine consists of the states defined in the
following subsections.
8.2.4.1. Data state
Consume the next input character:
U+0026 AMPERSAND (&)
Set the return state to the data state. Switch to the character
reference state.
U+003C LESS-THAN SIGN (<)
Switch to the tag open state.
U+0000 NULL
Parse error. Emit the current input character as a character
token.
EOF
Emit an end-of-file token.
Anything else
Emit the current input character as a character token.
8.2.4.2. RCDATA state
Consume the next input character:
U+0026 AMPERSAND (&)
Set the return state to the RCDATA state. Switch to the character
reference state.
U+003C LESS-THAN SIGN (<)
Switch to the RCDATA less-than sign state.
U+0000 NULL
Parse error. Emit a U+FFFD REPLACEMENT CHARACTER character token.
EOF
Emit an end-of-file token.
Anything else
Emit the current input character as a character token.
8.2.4.3. RAWTEXT state
Consume the next input character:
U+003C LESS-THAN SIGN (<)
Switch to the RAWTEXT less-than sign state.
U+0000 NULL
Parse error. Emit a U+FFFD REPLACEMENT CHARACTER character token.
EOF
Emit an end-of-file token.
Anything else
Emit the current input character as a character token.
8.2.4.4. Script data state
Consume the next input character:
U+003C LESS-THAN SIGN (<)
Switch to the script data less-than sign state.
U+0000 NULL
Parse error. Emit a U+FFFD REPLACEMENT CHARACTER character token.
EOF
Emit an end-of-file token.
Anything else
Emit the current input character as a character token.
8.2.4.5. PLAINTEXT state
Consume the next input character:
U+0000 NULL
Parse error. Emit a U+FFFD REPLACEMENT CHARACTER character token.
EOF
Emit an end-of-file token.
Anything else
Emit the current input character as a character token.
8.2.4.6. Tag open state
Consume the next input character:
U+0021 EXCLAMATION MARK (!)
Switch to the markup declaration open state.
U+002F SOLIDUS (/)
Switch to the end tag open state.
ASCII letter
Create a new start tag token, set its tag name to the empty
string. Reconsume in the tag name state.
U+003F QUESTION MARK (?)
Parse error. Create a comment token whose data is the empty
string. Reconsume in the bogus comment state.
Anything else
Parse error. Emit a U+003C LESS-THAN SIGN character token.
Reconsume in the data state.
8.2.4.7. End tag open state
Consume the next input character:
ASCII letter
Create a new end tag token, set its tag name to the empty string.
Reconsume in the tag name state.
U+003E GREATER-THAN SIGN (>)
Parse error. Switch to the data state.
EOF
Parse error. Emit a U+003C LESS-THAN SIGN character token, a
U+002F SOLIDUS character token and an end-of-file token.
Anything else
Parse error. Create a comment token whose data is the empty
string. Reconsume in the bogus comment state.
8.2.4.8. Tag name state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Switch to the before attribute name state.
U+002F SOLIDUS (/)
Switch to the self-closing start tag state.
U+003E GREATER-THAN SIGN (>)
Switch to the data state. Emit the current tag token.
Uppercase ASCII letter
Append the lowercase version of the current input character (add
0x0020 to the character’s code point) to the current tag token’s
tag name.
U+0000 NULL
Parse error. Append a U+FFFD REPLACEMENT CHARACTER character to
the current tag token’s tag name.
EOF
Parse error. Emit an end-of-file token.
Anything else
Append the current input character to the current tag token’s tag
name.
8.2.4.9. RCDATA less-than sign state
Consume the next input character:
U+002F SOLIDUS (/)
Set the temporary buffer to the empty string. Switch to the RCDATA
end tag open state.
Anything else
Emit a U+003C LESS-THAN SIGN character token. Reconsume in the
RCDATA state.
8.2.4.10. RCDATA end tag open state
Consume the next input character:
ASCII letter
Create a new end tag token, set its tag name to the empty string.
Reconsume in RCDATA end tag name state.
Anything else
Emit a U+003C LESS-THAN SIGN character token and a U+002F SOLIDUS
character token. Reconsume in the RCDATA state.
8.2.4.11. RCDATA end tag name state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
If the current end tag token is an appropriate end tag token, then
switch to the before attribute name state. Otherwise, treat it as
per the "anything else" entry below.
U+002F SOLIDUS (/)
If the current end tag token is an appropriate end tag token, then
switch to the self-closing start tag state. Otherwise, treat it as
per the "anything else" entry below.
U+003E GREATER-THAN SIGN (>)
If the current end tag token is an appropriate end tag token, then
switch to the data state and emit the current tag token.
Otherwise, treat it as per the "anything else" entry below.
Uppercase ASCII letter
Append the lowercase version of the current input character (add
0x0020 to the character’s code point) to the current tag token’s
tag name. Append the current input character to the temporary
buffer.
Lowercase ASCII letter
Append the current input character to the current tag token’s tag
name. Append the current input character to the temporary buffer.
Anything else
Emit a U+003C LESS-THAN SIGN character token, a U+002F SOLIDUS
character token, and a character token for each of the characters
in the temporary buffer (in the order they were added to the
buffer). Reconsume in the RCDATA state.
8.2.4.12. RAWTEXT less-than sign state
Consume the next input character:
U+002F SOLIDUS (/)
Set the temporary buffer to the empty string. Switch to the
RAWTEXT end tag open state.
Anything else
Emit a U+003C LESS-THAN SIGN character token. Reconsume in the
RAWTEXT state.
8.2.4.13. RAWTEXT end tag open state
Consume the next input character:
ASCII letter
Create a new end tag token, set its tag name to the empty string.
Reconsume in the RAWTEXT end tag name state.
Anything else
Emit a U+003C LESS-THAN SIGN character token and a U+002F SOLIDUS
character token. Reconsume in the RAWTEXT state.
8.2.4.14. RAWTEXT end tag name state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
If the current end tag token is an appropriate end tag token, then
switch to the before attribute name state. Otherwise, treat it as
per the "anything else" entry below.
U+002F SOLIDUS (/)
If the current end tag token is an appropriate end tag token, then
switch to the self-closing start tag state. Otherwise, treat it as
per the "anything else" entry below.
U+003E GREATER-THAN SIGN (>)
If the current end tag token is an appropriate end tag token, then
switch to the data state and emit the current tag token.
Otherwise, treat it as per the "anything else" entry below.
Uppercase ASCII letter
Append the lowercase version of the current input character (add
0x0020 to the character’s code point) to the current tag token’s
tag name. Append the current input character to the temporary
buffer.
Lowercase ASCII letter
Append the current input character to the current tag token’s tag
name. Append the current input character to the temporary buffer.
Anything else
Emit a U+003C LESS-THAN SIGN character token, a U+002F SOLIDUS
character token, and a character token for each of the characters
in the temporary buffer (in the order they were added to the
buffer). Reconsume in the RAWTEXT state.
8.2.4.15. Script data less-than sign state
Consume the next input character:
U+002F SOLIDUS (/)
Set the temporary buffer to the empty string. Switch to the script
data end tag open state.
U+0021 EXCLAMATION MARK (!)
Switch to the script data escape start state. Emit a U+003C
LESS-THAN SIGN character token and a U+0021 EXCLAMATION MARK
character token.
Anything else
Emit a U+003C LESS-THAN SIGN character token. Reconsume in the
script data state.
8.2.4.16. Script data end tag open state
Consume the next input character:
ASCII letter
Create a new end tag token, set its tag name to the empty string.
Reconsume in the script data end tag name state.
Anything else
Emit a U+003C LESS-THAN SIGN character token and a U+002F SOLIDUS
character token. Reconsume in the script data state.
8.2.4.17. Script data end tag name state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
If the current end tag token is an appropriate end tag token, then
switch to the before attribute name state. Otherwise, treat it as
per the "anything else" entry below.
U+002F SOLIDUS (/)
If the current end tag token is an appropriate end tag token, then
switch to the self-closing start tag state. Otherwise, treat it as
per the "anything else" entry below.
U+003E GREATER-THAN SIGN (>)
If the current end tag token is an appropriate end tag token, then
switch to the data state and emit the current tag token.
Otherwise, treat it as per the "anything else" entry below.
Uppercase ASCII letter
Append the lowercase version of the current input character (add
0x0020 to the character’s code point) to the current tag token’s
tag name. Append the current input character to the temporary
buffer.
Lowercase ASCII letter
Append the current input character to the current tag token’s tag
name. Append the current input character to the temporary buffer.
Anything else
Emit a U+003C LESS-THAN SIGN character token, a U+002F SOLIDUS
character token, and a character token for each of the characters
in the temporary buffer (in the order they were added to the
buffer). Reconsume in the script data state.
8.2.4.18. Script data escape start state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Switch to the script data escape start dash state. Emit a U+002D
HYPHEN-MINUS character token.
Anything else
Reconsume in the script data state.
8.2.4.19. Script data escape start dash state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Switch to the script data escaped dash dash state. Emit a U+002D
HYPHEN-MINUS character token.
Anything else
Reconsume in the script data state.
8.2.4.20. Script data escaped state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Switch to the script data escaped dash state. Emit a U+002D
HYPHEN-MINUS character token.
U+003C LESS-THAN SIGN (<)
Switch to the script data escaped less-than sign state.
U+0000 NULL
Parse error. Emit a U+FFFD REPLACEMENT CHARACTER character token.
EOF
Parse error. Emit an end-of-file token.
Anything else
Emit the current input character as a character token.
8.2.4.21. Script data escaped dash state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Switch to the script data escaped dash dash state. Emit a U+002D
HYPHEN-MINUS character token.
U+003C LESS-THAN SIGN (<)
Switch to the script data escaped less-than sign state.
U+0000 NULL
Parse error. Switch to the script data escaped state. Emit a
U+FFFD REPLACEMENT CHARACTER character token.
EOF
Parse error. Emit an end-of-file token.
Anything else
Switch to the script data escaped state. Emit the current input
character as a character token.
8.2.4.22. Script data escaped dash dash state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Emit a U+002D HYPHEN-MINUS character token.
U+003C LESS-THAN SIGN (<)
Switch to the script data escaped less-than sign state.
U+003E GREATER-THAN SIGN (>)
Switch to the script data state. Emit a U+003E GREATER-THAN SIGN
character token.
U+0000 NULL
Parse error. Switch to the script data escaped state. Emit a
U+FFFD REPLACEMENT CHARACTER character token.
EOF
Parse error. Emit an end-of-file token.
Anything else
Switch to the script data escaped state. Emit the current input
character as a character token.
8.2.4.23. Script data escaped less-than sign state
Consume the next input character:
U+002F SOLIDUS (/)
Set the temporary buffer to the empty string. Switch to the script
data escaped end tag open state.
ASCII letter
Set the temporary buffer to the empty string. Emit a U+003C
LESS-THAN SIGN character token. Reconsume in the script data
double escape start state.
Anything else
Emit a U+003C LESS-THAN SIGN character token. Reconsume in the
script data escaped state.
8.2.4.24. Script data escaped end tag open state
Consume the next input character:
ASCII letter
Create a new end tag token. Reconsume in the script data escaped
end tag name state. (Don’t emit the token yet; further details
will be filled in before it is emitted.)
Anything else
Emit a U+003C LESS-THAN SIGN character token and a U+002F SOLIDUS
character token. Reconsume in the script data escaped state.
8.2.4.25. Script data escaped end tag name state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
If the current end tag token is an appropriate end tag token, then
switch to the before attribute name state. Otherwise, treat it as
per the "anything else" entry below.
U+002F SOLIDUS (/)
If the current end tag token is an appropriate end tag token, then
switch to the self-closing start tag state. Otherwise, treat it as
per the "anything else" entry below.
U+003E GREATER-THAN SIGN (>)
If the current end tag token is an appropriate end tag token, then
switch to the data state and emit the current tag token.
Otherwise, treat it as per the "anything else" entry below.
Uppercase ASCII letter
Append the lowercase version of the current input character (add
0x0020 to the character’s code point) to the current tag token’s
tag name. Append the current input character to the temporary
buffer.
Lowercase ASCII letter
Append the current input character to the current tag token’s tag
name. Append the current input character to the temporary buffer.
Anything else
Emit a U+003C LESS-THAN SIGN character token, a U+002F SOLIDUS
character token, and a character token for each of the characters
in the temporary buffer (in the order they were added to the
buffer). Reconsume in the script data escaped state.
8.2.4.26. Script data double escape start state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
U+002F SOLIDUS (/)
U+003E GREATER-THAN SIGN (>)
If the temporary buffer is the string "script", then switch to the
script data double escaped state. Otherwise, switch to the script
data escaped state. Emit the current input character as a
character token.
Uppercase ASCII letter
Append the lowercase version of the current input character (add
0x0020 to the character’s code point) to the temporary buffer.
Emit the current input character as a character token.
Lowercase ASCII letter
Append the current input character to the temporary buffer. Emit
the current input character as a character token.
Anything else
Reconsume in the script data escaped state.
8.2.4.27. Script data double escaped state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Switch to the script data double escaped dash state. Emit a U+002D
HYPHEN-MINUS character token.
U+003C LESS-THAN SIGN (<)
Switch to the script data double escaped less-than sign state.
Emit a U+003C LESS-THAN SIGN character token.
U+0000 NULL
Parse error. Emit a U+FFFD REPLACEMENT CHARACTER character token.
EOF
Parse error. Emit an end-of-file token.
Anything else
Emit the current input character as a character token.
8.2.4.28. Script data double escaped dash state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Switch to the script data double escaped dash dash state. Emit a
U+002D HYPHEN-MINUS character token.
U+003C LESS-THAN SIGN (<)
Switch to the script data double escaped less-than sign state.
Emit a U+003C LESS-THAN SIGN character token.
U+0000 NULL
Parse error. Switch to the script data double escaped state. Emit
a U+FFFD REPLACEMENT CHARACTER character token.
EOF
Parse error. Emit an end-of-file token.
Anything else
Switch to the script data double escaped state. Emit the current
input character as a character token.
8.2.4.29. Script data double escaped dash dash state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Emit a U+002D HYPHEN-MINUS character token.
U+003C LESS-THAN SIGN (<)
Switch to the script data double escaped less-than sign state.
Emit a U+003C LESS-THAN SIGN character token.
U+003E GREATER-THAN SIGN (>)
Switch to the script data state. Emit a U+003E GREATER-THAN SIGN
character token.
U+0000 NULL
Parse error. Switch to the script data double escaped state. Emit
a U+FFFD REPLACEMENT CHARACTER character token.
EOF
Parse error. Emit an end-of-file token.
Anything else
Switch to the script data double escaped state. Emit the current
input character as a character token.
8.2.4.30. Script data double escaped less-than sign state
Consume the next input character:
U+002F SOLIDUS (/)
Set the temporary buffer to the empty string. Switch to the script
data double escape end state. Emit a U+002F SOLIDUS character
token.
Anything else
Reconsume in the script data double escaped state.
8.2.4.31. Script data double escape end state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
U+002F SOLIDUS (/)
U+003E GREATER-THAN SIGN (>)
If the temporary buffer is the string "script", then switch to the
script data escaped state. Otherwise, switch to the script data
double escaped state. Emit the current input character as a
character token.
Uppercase ASCII letter
Append the lowercase version of the current input character (add
0x0020 to the character’s code point) to the temporary buffer.
Emit the current input character as a character token.
Lowercase ASCII letter
Append the current input character to the temporary buffer. Emit
the current input character as a character token.
Anything else
Reconsume in the script data double escaped state.
8.2.4.32. Before attribute name state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Ignore the character.
U+002F SOLIDUS (/)
U+003E GREATER-THAN SIGN (>)
EOF
Reconsume in the after attribute name state.
U+003D EQUALS SIGN (=)
Parse error. Start a new attribute in the current tag token. Set
that attribute’s name to the current input character, and its
value to the empty string. Switch to the attribute name state.
Anything else
Start a new attribute in the current tag token. Set that
attribute’s name and value to the empty string. Reconsume in the
attribute name state.
8.2.4.33. Attribute name state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
U+002F SOLIDUS (/)
U+003E GREATER-THAN SIGN (>)
EOF
Reconsume in the after attribute name state.
U+003D EQUALS SIGN (=)
Switch to the before attribute value state.
Uppercase ASCII letter
Append the lowercase version of the current input character (add
0x0020 to the character’s code point) to the current attribute’s
name.
U+0000 NULL
Parse error. Append a U+FFFD REPLACEMENT CHARACTER character to
the current attribute’s name.
U+0022 QUOTATION MARK (")
U+0027 APOSTROPHE (')
U+003C LESS-THAN SIGN (<)
Parse error. Treat it as per the "anything else" entry below.
Anything else
Append the current input character to the current attribute’s
name.
When the user agent leaves the attribute name state (and before emitting
the tag token, if appropriate), the complete attribute’s name must be
compared to the other attributes on the same token; if there is already an
attribute on the token with the exact same name, then this is a parse
error and the new attribute must be removed from the token.
If an attribute is so removed from a token, it, and the value that gets
associated with it, if any, are never subsequently used by the parser, and
are therefore effectively discarded. Removing the attribute in this way
does not change its status as the "current attribute" for the purposes of
the tokenizer, however.
8.2.4.34. After attribute name state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Ignore the character.
U+002F SOLIDUS (/)
Switch to the self-closing start tag state.
U+003D EQUALS SIGN (=)
Switch to the before attribute value state.
U+003E GREATER-THAN SIGN (>)
Switch to the data state. Emit the current tag token.
EOF
Parse error. Emit an end-of-file token.
Anything else
Start a new attribute in the current tag token. Set that
attribute’s name and value to the empty string. Reconsume in the
attribute name state.
8.2.4.35. Before attribute value state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Ignore the character.
U+0022 QUOTATION MARK (")
Switch to the attribute value (double-quoted) state.
U+0027 APOSTROPHE (')
Switch to the attribute value (single-quoted) state.
U+003E GREATER-THAN SIGN (>)
Parse error. Treat it as per the "anything else" entry below.
Anything else
Reconsume in the attribute value (unquoted) state.
8.2.4.36. Attribute value (double-quoted) state
Consume the next input character:
U+0022 QUOTATION MARK (")
Switch to the after attribute value (quoted) state.
U+0026 AMPERSAND (&)
Set the return state to the attribute value (double-quoted) state.
Switch to the character reference state.
U+0000 NULL
Parse error. Append a U+FFFD REPLACEMENT CHARACTER character to
the current attribute’s value.
EOF
Parse error. Emit an end-of-file token.
Anything else
Append the current input character to the current attribute’s
value.
8.2.4.37. Attribute value (single-quoted) state
Consume the next input character:
U+0027 APOSTROPHE (')
Switch to the after attribute value (quoted) state.
U+0026 AMPERSAND (&)
Set the return state to the attribute value (single-quoted) state.
Switch to the character reference state.
U+0000 NULL
Parse error. Append a U+FFFD REPLACEMENT CHARACTER character to
the current attribute’s value.
EOF
Parse error. Emit an end-of-file token.
Anything else
Append the current input character to the current attribute’s
value.
8.2.4.38. Attribute value (unquoted) state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Switch to the before attribute name state.
U+0026 AMPERSAND (&)
Set the return state to the attribute value (unquoted) state.
Switch to the character reference state.
U+003E GREATER-THAN SIGN (>)
Switch to the data state. Emit the current tag token.
U+0000 NULL
Parse error. Append a U+FFFD REPLACEMENT CHARACTER character to
the current attribute’s value.
U+0022 QUOTATION MARK (")
U+0027 APOSTROPHE (')
U+003C LESS-THAN SIGN (<)
U+003D EQUALS SIGN (=)
U+0060 GRAVE ACCENT (`)
Parse error. Treat it as per the "anything else" entry below.
EOF
Parse error. Emit an end-of-file token.
Anything else
Append the current input character to the current attribute’s
value.
8.2.4.39. After attribute value (quoted) state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Switch to the before attribute name state.
U+002F SOLIDUS (/)
Switch to the self-closing start tag state.
U+003E GREATER-THAN SIGN (>)
Switch to the data state. Emit the current tag token.
EOF
Parse error. Emit an end-of-file token.
Anything else
Parse error. Reconsume in the before attribute name state.
8.2.4.40. Self-closing start tag state
Consume the next input character:
U+003E GREATER-THAN SIGN (>)
Set the self-closing flag of the current tag token. Switch to the
data state. Emit the current tag token.
EOF
Parse error. Emit an end-of-file token.
Anything else
Parse error. Reconsume in the before attribute name state.
8.2.4.41. Bogus comment state
Consume the next input character:
U+003E GREATER-THAN SIGN (>)
Switch to the data state. Emit the comment token.
EOF
Emit the comment. Emit an end-of-file token.
U+0000 NULL
Append a U+FFFD REPLACEMENT CHARACTER character to the comment
token’s data.
Anything else
Append the current input character to the comment token’s data.
8.2.4.42. Markup declaration open state
If the next two characters are both U+002D HYPHEN-MINUS characters (-),
consume those two characters, create a comment token whose data is the
empty string, and switch to the comment start state.
Otherwise, if the next seven characters are an ASCII case-insensitive
match for the word "DOCTYPE", then consume those characters and switch to
the DOCTYPE state.
Otherwise, if there is an adjusted current node and it is not an element
in the HTML namespace and the next seven characters are a case-sensitive
match for the string "[CDATA[" (the five uppercase letters "CDATA" with a
U+005B LEFT SQUARE BRACKET character before and after), then consume those
characters and switch to the CDATA section state.
Otherwise, this is a parse error. Create a comment token whose data is the
empty string. Switch to the bogus comment state (don’t consume anything in
the current state).
8.2.4.43. Comment start state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Switch to the comment start dash state.
U+003E GREATER-THAN SIGN (>)
Parse error. Switch to the data state. Emit the comment token.
Anything else
Reconsume in the comment state.
8.2.4.44. Comment start dash state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Switch to the comment end state
U+003E GREATER-THAN SIGN (>)
Parse error. Switch to the data state. Emit the comment token.
EOF
Parse error. Emit the comment token. Emit an end-of-file token.
Anything else
Append a U+002D HYPHEN-MINUS character (-) to the comment token’s
data. Reconsume in the comment state.
8.2.4.45. Comment state
Consume the next input character:
U+003C LESS-THAN SIGN (<)
Append the current input character to the comment token’s data.
Switch to the comment less-than sign state.
U+002D HYPHEN-MINUS (-)
Switch to the comment end dash state
U+0000 NULL
Parse error. Append a U+FFFD REPLACEMENT CHARACTER character to
the comment token’s data.
EOF
Parse error. Emit the comment token. Emit an end-of-file token.
Anything else
Append the current input character to the comment token’s data.
8.2.4.46. Comment less-than sign state
Consume the next input character:
U+0021 EXCLAMATION MARK (!)
Append the current input character to the comment token’s data.
Switch to the comment less-than sign bang state.
U+003C LESS-THAN SIGN (<)
Append the current input character to the comment token’s data.
Anything else
Reconsume in the comment state.
8.2.4.47. Comment less-than sign bang state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Switch to the comment less-than sign bang dash state.
Anything else
Reconsume in the comment state.
8.2.4.48. Comment less-than sign bang dash state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Switch to the comment less-than sign bang dash dash state.
Anything else
Reconsume in the comment end dash state.
8.2.4.49. Comment less-than sign bang dash dash state
Consume the next input character:
U+003E GREATER-THAN SIGN (>)
EOF
Reconsume in the comment end state.
Anything else
Parse error. Reconsume in the comment end state.
8.2.4.50. Comment end dash state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Switch to the comment end state
EOF
Parse error. Emit the comment token. Emit an end-of-file token.
Anything else
Append a U+002D HYPHEN-MINUS character (-) to the comment token’s
data. Reconsume in the comment state.
8.2.4.51. Comment end state
Consume the next input character:
U+003E GREATER-THAN SIGN (>)
Switch to the data state. Emit the comment token.
U+0021 EXCLAMATION MARK (!)
Switch to the comment end bang state.
U+002D HYPHEN-MINUS (-)
Append a U+002D HYPHEN-MINUS character (-) to the comment token’s
data.
EOF
Parse error. Emit the comment token. Emit an end-of-file token.
Anything else
Append two U+002D HYPHEN-MINUS characters (-) to the comment
token’s data. Reconsume in the comment state.
8.2.4.52. Comment end bang state
Consume the next input character:
U+002D HYPHEN-MINUS (-)
Append two U+002D HYPHEN-MINUS characters (-) and a U+0021
EXCLAMATION MARK character (!) to the comment token’s data. Switch
to the comment end dash state.
U+003E GREATER-THAN SIGN (>)
Parse error. Switch to the data state. Emit the comment token.
EOF
Parse error. Emit the comment token. Emit an end-of-file token.
Anything else
Append two U+002D HYPHEN-MINUS characters (-) and a U+0021
EXCLAMATION MARK character (!) to the comment token’s data.
Reconsume in the comment state.
8.2.4.53. DOCTYPE state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Switch to the before DOCTYPE name state.
EOF
Parse error. Create a new DOCTYPE token. Set its force-quirks flag
to on. Emit the token. Emit an end-of-file token.
Anything else
Parse error. Reconsume in the before DOCTYPE name state.
8.2.4.54. Before DOCTYPE name state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Ignore the character.
Uppercase ASCII letter
Create a new DOCTYPE token. Set the token’s name to the lowercase
version of the current input character (add 0x0020 to the
character’s code point). Switch to the DOCTYPE name state.
U+0000 NULL
Parse error. Create a new DOCTYPE token. Set the token’s name to a
U+FFFD REPLACEMENT CHARACTER character. Switch to the DOCTYPE name
state.
U+003E GREATER-THAN SIGN (>)
Parse error. Create a new DOCTYPE token. Set its force-quirks flag
to on. Switch to the data state. Emit the token.
EOF
Parse error. Create a new DOCTYPE token. Set its force-quirks flag
to on. Emit the token. Emit an end-of-file token.
Anything else
Create a new DOCTYPE token. Set the token’s name to the current
input character. Switch to the DOCTYPE name state.
8.2.4.55. DOCTYPE name state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Switch to the after DOCTYPE name state.
U+003E GREATER-THAN SIGN (>)
Switch to the data state. Emit the current DOCTYPE token.
Uppercase ASCII letter
Append the lowercase version of the current input character (add
0x0020 to the character’s code point) to the current DOCTYPE
token’s name.
U+0000 NULL
Parse error. Append a U+FFFD REPLACEMENT CHARACTER character to
the current DOCTYPE token’s name.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
Append the current input character to the current DOCTYPE token’s
name.
8.2.4.56. After DOCTYPE name state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Ignore the character.
U+003E GREATER-THAN SIGN (>)
Switch to the data state. Emit the current DOCTYPE token.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
If the six characters starting from the current input character
are an ASCII case-insensitive match for the word "PUBLIC", then
consume those characters and switch to the after DOCTYPE public
keyword state.
Otherwise, if the six characters starting from the current input
character are an ASCII case-insensitive match for the word
"SYSTEM", then consume those characters and switch to the after
DOCTYPE system keyword state.
Otherwise, this is a parse error. Set the DOCTYPE token’s
force-quirks flag to on. Switch to the bogus DOCTYPE state.
8.2.4.57. After DOCTYPE public keyword state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Switch to the before DOCTYPE public identifier state.
U+0022 QUOTATION MARK (")
Parse error. Set the DOCTYPE token’s public identifier to the
empty string (not missing), then switch to the DOCTYPE public
identifier (double-quoted) state.
U+0027 APOSTROPHE (')
Parse error. Set the DOCTYPE token’s public identifier to the
empty string (not missing), then switch to the DOCTYPE public
identifier (single-quoted) state.
U+003E GREATER-THAN SIGN (>)
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the data state. Emit that DOCTYPE token.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the bogus DOCTYPE state.
8.2.4.58. Before DOCTYPE public identifier state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Ignore the character.
U+0022 QUOTATION MARK (")
Set the DOCTYPE token’s public identifier to the empty string (not
missing), then switch to the DOCTYPE public identifier
(double-quoted) state.
U+0027 APOSTROPHE (')
Set the DOCTYPE token’s public identifier to the empty string (not
missing), then switch to the DOCTYPE public identifier
(single-quoted) state.
U+003E GREATER-THAN SIGN (>)
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the data state. Emit that DOCTYPE token.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the bogus DOCTYPE state.
8.2.4.59. DOCTYPE public identifier (double-quoted) state
Consume the next input character:
U+0022 QUOTATION MARK (")
Switch to the after DOCTYPE public identifier state.
U+0000 NULL
Parse error. Append a U+FFFD REPLACEMENT CHARACTER character to
the current DOCTYPE token’s public identifier.
U+003E GREATER-THAN SIGN (>)
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the data state. Emit that DOCTYPE token.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
Append the current input character to the current DOCTYPE token’s
public identifier.
8.2.4.60. DOCTYPE public identifier (single-quoted) state
Consume the next input character:
U+0027 APOSTROPHE (')
Switch to the after DOCTYPE public identifier state.
U+0000 NULL
Parse error. Append a U+FFFD REPLACEMENT CHARACTER character to
the current DOCTYPE token’s public identifier.
U+003E GREATER-THAN SIGN (>)
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the data state. Emit that DOCTYPE token.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
Append the current input character to the current DOCTYPE token’s
public identifier.
8.2.4.61. After DOCTYPE public identifier state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Switch to the between DOCTYPE public and system identifiers state.
U+003E GREATER-THAN SIGN (>)
Switch to the data state. Emit the current DOCTYPE token.
U+0022 QUOTATION MARK (")
Parse error. Set the DOCTYPE token’s system identifier to the
empty string (not missing), then switch to the DOCTYPE system
identifier (double-quoted) state.
U+0027 APOSTROPHE (')
Parse error. Set the DOCTYPE token’s system identifier to the
empty string (not missing), then switch to the DOCTYPE system
identifier (single-quoted) state.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the bogus DOCTYPE state.
8.2.4.62. Between DOCTYPE public and system identifiers state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Ignore the character.
U+003E GREATER-THAN SIGN (>)
Switch to the data state. Emit the current DOCTYPE token.
U+0022 QUOTATION MARK (")
Set the DOCTYPE token’s system identifier to the empty string (not
missing), then switch to the DOCTYPE system identifier
(double-quoted) state.
U+0027 APOSTROPHE (')
Set the DOCTYPE token’s system identifier to the empty string (not
missing), then switch to the DOCTYPE system identifier
(single-quoted) state.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the bogus DOCTYPE state.
8.2.4.63. After DOCTYPE system keyword state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Switch to the before DOCTYPE system identifier state.
U+0022 QUOTATION MARK (")
Parse error. Set the DOCTYPE token’s system identifier to the
empty string (not missing), then switch to the DOCTYPE system
identifier (double-quoted) state.
U+0027 APOSTROPHE (')
Parse error. Set the DOCTYPE token’s system identifier to the
empty string (not missing), then switch to the DOCTYPE system
identifier (single-quoted) state.
U+003E GREATER-THAN SIGN (>)
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the data state. Emit that DOCTYPE token.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the bogus DOCTYPE state.
8.2.4.64. Before DOCTYPE system identifier state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Ignore the character.
U+0022 QUOTATION MARK (")
Set the DOCTYPE token’s system identifier to the empty string (not
missing), then switch to the DOCTYPE system identifier
(double-quoted) state.
U+0027 APOSTROPHE (')
Set the DOCTYPE token’s system identifier to the empty string (not
missing), then switch to the DOCTYPE system identifier
(single-quoted) state.
U+003E GREATER-THAN SIGN (>)
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the data state. Emit that DOCTYPE token.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the bogus DOCTYPE state.
8.2.4.65. DOCTYPE system identifier (double-quoted) state
Consume the next input character:
U+0022 QUOTATION MARK (")
Switch to the after DOCTYPE system identifier state.
U+0000 NULL
Parse error. Append a U+FFFD REPLACEMENT CHARACTER character to
the current DOCTYPE token’s system identifier.
U+003E GREATER-THAN SIGN (>)
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the data state. Emit that DOCTYPE token.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
Append the current input character to the current DOCTYPE token’s
system identifier.
8.2.4.66. DOCTYPE system identifier (single-quoted) state
Consume the next input character:
U+0027 APOSTROPHE (')
Switch to the after DOCTYPE system identifier state.
U+0000 NULL
Parse error. Append a U+FFFD REPLACEMENT CHARACTER character to
the current DOCTYPE token’s system identifier.
U+003E GREATER-THAN SIGN (>)
Parse error. Set the DOCTYPE token’s force-quirks flag to on.
Switch to the data state. Emit that DOCTYPE token.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
Append the current input character to the current DOCTYPE token’s
system identifier.
8.2.4.67. After DOCTYPE system identifier state
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
Ignore the character.
U+003E GREATER-THAN SIGN (>)
Switch to the data state. Emit the current DOCTYPE token.
EOF
Parse error. Set the DOCTYPE token’s force-quirks flag to on. Emit
that DOCTYPE token. Emit an end-of-file token.
Anything else
Parse error. Switch to the bogus DOCTYPE state. (This does not set
the DOCTYPE token’s force-quirks flag to on.)
8.2.4.68. Bogus DOCTYPE state
Consume the next input character:
U+003E GREATER-THAN SIGN (>)
Switch to the data state. Emit the DOCTYPE token.
EOF
Emit the DOCTYPE token. Emit an end-of-file token.
Anything else
Ignore the character.
8.2.4.69. CDATA section state
Consume the next input character:
U+005D RIGHT SQUARE BRACKET (])
Switch to the CDATA section bracket state.
EOF
Parse error. Emit an end-of-file token.
Anything else
Emit the current input character as a character token.
U+0000 NULL characters are handled in the tree construction stage, as part
of the in foreign content insertion mode, which is the only place where
CDATA sections can appear.
8.2.4.70. CDATA section bracket state
Consume the next input character:
U+005D RIGHT SQUARE BRACKET (])
Switch to the CDATA section end state.
Anything else
Emit a U+005D RIGHT SQUARE BRACKET character token. Reconsume in
the CDATA section state
8.2.4.71. CDATA section end state
Consume the next input character:
U+005D RIGHT SQUARE BRACKET (])
Emit a U+005D RIGHT SQUARE BRACKET character token.
U+003E GREATER-THAN SIGN (>)
Switch to the data state.
Anything else
Emit two U+005D RIGHT SQUARE BRACKET character tokens. Reconsume
in the CDATA section state
8.2.4.72. Character reference state
Set the temporary buffer to the empty string. Append a U+0026 AMPERSAND
(&) character to the temporary buffer.
Consume the next input character:
U+0009 CHARACTER TABULATION (tab)
U+000A LINE FEED (LF)
U+000C FORM FEED (FF)
U+0020 SPACE
U+003C LESS-THAN SIGN
U+0026 AMPERSAND
EOF
Reconsume in the character reference end state.
U+0023 NUMBER SIGN (#)
Append the current input character to the temporary buffer. Switch
to the numeric character reference state.
Anything else
Consume the maximum number of characters possible, with the
consumed characters matching one of the identifiers in the first
column of the §8.5 Named character references table (in a
case-sensitive manner). Append each character to the temporary
buffer when it’s consumed.
If no match can be made and the temporary buffer consists of a
U+0026 AMPERSAND character (&) followed by a sequence of one or
more alphanumeric ASCII characters and a U+003B SEMICOLON
character (;), then this is a parse error.
If no match can be made, switch to the character reference end
state.
If the character reference was consumed as part of an attribute
(return state is either attribute value (double-quoted) state,
attribute value (single-quoted) state or attribute value
(unquoted) state), and the last character matched is not a U+003B
SEMICOLON character (;), and the next input character is either a
U+003D EQUALS SIGN character (=) or an alphanumeric ASCII
character, then, for historical reasons, switch to the character
reference end state.
If the last character matched is not a U+003B SEMICOLON character
(;), this is a parse error.
Set the temporary buffer to the empty string. Append one or two
characters corresponding to the character reference name (as given
by the second column of the §8.5 Named character references table)
to the temporary buffer.
Switch to the character reference end state.
If the markup contains (not in an attribute) the string I'm
¬it; I tell you, the character reference is parsed as "not", as
in, I'm ¬it; I tell you (and this is a parse error). But if the
markup was I'm &notin; I tell you, the character reference
would be parsed as "notin;", resulting in I'm ∉ I tell you (and no
parse error).
However, if the markup contains the string I'm &notit; I tell
you in an attribute, no character reference is parsed and string
remains intact (and there is no parse error).
8.2.4.73. Numeric character reference state
Set the character reference code to zero (0).
Consume the next input character:
U+0078 LATIN SMALL LETTER X
U+0058 LATIN CAPITAL LETTER X
Append the current input character to the temporary buffer. Switch
to the hexadecimal character reference start state.
Anything else
Reconsume in the decimal character reference start state.
8.2.4.74. Hexadecimal character reference start state
Consume the next input character:
ASCII hex digit
Reconsume in the hexadecimal character reference state.
Anything else
Parse error. Reconsume in the character reference end state.
8.2.4.75. Decimal character reference start state
Consume the next input character:
ASCII digit
Reconsume in the decimal character reference state.
Anything else
Parse error. Reconsume in the character reference end state.
8.2.4.76. Hexadecimal character reference state
Consume the next input character:
ASCII digit
Multiply the character reference code by 16. Add a numeric version
of the current input character (subtract 0x0030 from the
character’s code point) to the character reference code.
Uppercase ASCII hex digit
Multiply the character reference code by 16. Add a numeric version
of the current input character as a hexademical digit (subtract
0x0037 from the character’s code point) to the character reference
code.
Lowercase ASCII hex digit
Multiply the character reference code by 16. Add a numeric version
of the current input character as a hexademical digit (subtract
0x0057 from the character’s code point) to the character reference
code.
U+003B SEMICOLON character (;)
Switch to the numeric character reference end state.
Anything else
Parse error. Reconsume in the numeric character reference end
state.
8.2.4.77. Decimal character reference state
Consume the next input character:
ASCII digit
Multiply the character reference code by 16. Add a numeric version
of the current input character (subtract 0x0030 from the
character’s code point) to the character reference code.
U+003B SEMICOLON character (;)
Switch to the numeric character reference end state.
Anything else
Parse error. Reconsume in the numeric character reference end
state.
8.2.4.78. Numeric character reference end state
Check the character reference code.
If that number is one of the numbers in the first column of the following
table, then this is a parse error. Find the row with that number in the
first column, and set the character reference code to the number in the
second column of that row.
Number Unicode character
0x00 U+FFFD REPLACEMENT CHARACTER
0x80 U+20AC EURO SIGN (€)
0x82 U+201A SINGLE LOW-9 QUOTATION MARK (‚)
0x83 U+0192 LATIN SMALL LETTER F WITH HOOK (ƒ)
0x84 U+201E DOUBLE LOW-9 QUOTATION MARK („)
0x85 U+2026 HORIZONTAL ELLIPSIS (…)
0x86 U+2020 DAGGER (†)
0x87 U+2021 DOUBLE DAGGER (‡)
0x88 U+02C6 MODIFIER LETTER CIRCUMFLEX ACCENT (ˆ)
0x89 U+2030 PER MILLE SIGN (‰)
0x8A U+0160 LATIN CAPITAL LETTER S WITH CARON (Š)
0x8B U+2039 SINGLE LEFT-POINTING ANGLE QUOTATION MARK (‹)
0x8C U+0152 LATIN CAPITAL LIGATURE OE (Œ)
0x8E U+017D LATIN CAPITAL LETTER Z WITH CARON (Ž)
0x91 U+2018 LEFT SINGLE QUOTATION MARK (‘)
0x92 U+2019 RIGHT SINGLE QUOTATION MARK (’)
0x93 U+201C LEFT DOUBLE QUOTATION MARK (“)
0x94 U+201D RIGHT DOUBLE QUOTATION MARK (”)
0x95 U+2022 BULLET (•)
0x96 U+2013 EN DASH (–)
0x97 U+2014 EM DASH (—)
0x98 U+02DC SMALL TILDE (˜)
0x99 U+2122 TRADE MARK SIGN (™)
0x9A U+0161 LATIN SMALL LETTER S WITH CARON (š)
0x9B U+203A SINGLE RIGHT-POINTING ANGLE QUOTATION MARK (›)
0x9C U+0153 LATIN SMALL LIGATURE OE (œ)
0x9E U+017E LATIN SMALL LETTER Z WITH CARON (ž)
0x9F U+0178 LATIN CAPITAL LETTER Y WITH DIAERESIS (Ÿ)
If the number is in the range 0xD800 to 0xDFFF or is greater than
0x10FFFF, then this is a parse error. Set the character reference code to
0xFFFD.
If the number is in the range 0x0001 to 0x0008, 0x000D to 0x001F, 0x007F
to 0x009F, 0xFDD0 to 0xFDEF, or is one of 0x000B, 0xFFFE, 0xFFFF, 0x1FFFE,
0x1FFFF, 0x2FFFE, 0x2FFFF, 0x3FFFE, 0x3FFFF, 0x4FFFE, 0x4FFFF, 0x5FFFE,
0x5FFFF, 0x6FFFE, 0x6FFFF, 0x7FFFE, 0x7FFFF, 0x8FFFE, 0x8FFFF, 0x9FFFE,
0x9FFFF, 0xAFFFE, 0xAFFFF, 0xBFFFE, 0xBFFFF, 0xCFFFE, 0xCFFFF, 0xDFFFE,
0xDFFFF, 0xEFFFE, 0xEFFFF, 0xFFFFE, 0xFFFFF, 0x10FFFE, or 0x10FFFF, then
this is a parse error.
Set the temporary buffer to the empty string. Append the Unicode character
with code point equal to the character reference code to the temporary
buffer. Switch to the character reference end state.
8.2.4.79. Character reference end state
Consume the next input character.
Check the return state:
attribute value (double-quoted) state
attribute value (single-quoted) state
attribute value (unquoted) state
Append each character in the temporary buffer (in the order they
were added to the buffer) to the current attribute’s value.
Anything else
For each of the characters in the temporary buffer (in the order
they were added to the buffer), emit the character as a character
token.
Reconsume in the return state.
8.2.5. Tree construction
The input to the tree construction stage is a sequence of tokens from the
tokenization stage. The tree construction stage is associated with a DOM
Document object when a parser is created. The "output" of this stage
consists of dynamically modifying or extending that document’s DOM tree.
This specification does not define when an interactive user agent has to
render the Document so that it is available to the user, or when it has to
begin accepting user input.
----------------------------------------------------------------------
As each token is emitted from the tokenizer, the user agent must follow
the appropriate steps from the following list, known as the tree
construction dispatcher:
If the stack of open elements is empty
If the adjusted current node is an element in the HTML namespace
If the adjusted current node is a MathML text integration point and the
token is a start tag whose tag name is neither "mglyph" nor "malignmark"
If the adjusted current node is a MathML text integration point and the
token is a character token
If the adjusted current node is a MathML annotation-xml element and the
token is a start tag whose tag name is "svg"
If the adjusted current node is an HTML integration point and the token is
a start tag
If the adjusted current node is an HTML integration point and the token is
a character token
If the token is an end-of-file token
Process the token according to the rules given in the section
corresponding to the current insertion mode in HTML content.
Otherwise
Process the token according to the rules given in the section for
parsing tokens in foreign content.
The next token is the token that is about to be processed by the tree
construction dispatcher (even if the token is subsequently just ignored).
A node is a MathML text integration point if it is one of the following
elements:
* A MathML mi element
* A MathML mo element
* A MathML mn element
* A MathML ms element
* A MathML mtext element
A node is an HTML integration point if it is one of the following
elements:
* A MathML annotation-xml element whose start tag token had an attribute
with the name "encoding" whose value was an ASCII case-insensitive
match for the string "text/html"
* A MathML annotation-xml element whose start tag token had an attribute
with the name "encoding" whose value was an ASCII case-insensitive
match for the string "application/xhtml+xml"
* An SVG foreignObject element
* An SVG desc element
* An SVG title element
If the node in question is the context element passed to the HTML fragment
parsing algorithm, then the start tag token for that element is the "fake"
token created during by that HTML fragment parsing algorithm.
----------------------------------------------------------------------
Not all of the tag names mentioned below are conformant tag names in this
specification; many are included to handle legacy content. They still form
part of the algorithm that implementations are required to implement to
claim conformance.
The algorithm described below places no limit on the depth of the DOM tree
generated, or on the length of tag names, attribute names, attribute
values, Text nodes, etc. While implementors are encouraged to avoid
arbitrary limits, it is recognized that practical concerns will likely
force user agents to impose nesting depth constraints.
8.2.5.1. Creating and inserting nodes
While the parser is processing a token, it can enable or disable foster
parenting. This affects the following algorithm.
The appropriate place for inserting a node, optionally using a particular
override target, is the position in an element returned by running the
following steps:
1. If there was an override target specified, then let target be the
override target.
Otherwise, let target be the current node.
2. Determine the adjusted insertion location using the first matching
steps from the following list:
If foster parenting is enabled and target is a table, tbody,
tfoot, thead, or tr element
Foster parenting happens when content is misnested in
tables.
Run these substeps:
1. Let last template be the last template element in
the stack of open elements, if any.
2. Let last table be the last table element in the
stack of open elements, if any.
3. If there is a last template and either there is no
last table, or there is one, but last template is
lower (more recently added) than last table in the
stack of open elements, then: let adjusted insertion
location be inside last template’s template
contents, after its last child (if any), and abort
these substeps.
4. If there is no last table, then let adjusted
insertion location be inside the first element in
the stack of open elements (the html element), after
its last child (if any), and abort these substeps.
(fragment case)
5. If last table has a parent node, then let adjusted
insertion location be inside last table’s parent
node, immediately before last table, and abort these
substeps.
6. Let previous element be the element immediately
above last table in the stack of open elements.
7. Let adjusted insertion location be inside previous
element, after its last child (if any).
These steps are involved in part because it’s possible
for elements, the table element in this case in
particular, to have been moved by a script around in the
DOM, or indeed removed from the DOM entirely, after the
element was inserted by the parser.
Otherwise
Let adjusted insertion location be inside target, after
its last child (if any).
3. If the adjusted insertion location is inside a template element, let
it instead be inside the template element’s template contents, after
its last child (if any).
4. Return the adjusted insertion location.
----------------------------------------------------------------------
When the steps below require the UA to create an element for a token in a
particular given namespace and with a particular intended parent, the UA
must run the following steps:
1. Let document be intended parent’s node document.
2. Let local name be the tag name of the token.
3. Let is be the value of the "is" attribute in the given token, if such
an attribute exists, or null otherwise.
4. Let definition be the result of looking up a custom element definition
given document, given namespace, local name, and is.
5. If definition is non-null and the parser was not originally created
for the HTML fragment parsing algorithm, then let will execute script
be true. Otherwise, let it be false.
6. If will execute script is true, then:
1. Increment document’s throw-on-dynamic-markup-insertion counter.
2. If the JavaScript execution context stack is empty, then perform
a microtask checkpoint.
3. Push a new element queue onto the custom element reactions stack.
7. Let element be the result of creating an element given document, local
name, given namespace, null, and is. If will execute script is true,
set the synchronous custom elements flag; otherwise, leave it unset.
This will cause custom element constructors to run, if will execute
script is true. However, since we incremented the
throw-on-dynamic-markup-insertion counter, this cannot cause new
characters to be inserted into the tokenizer, or the document to be
blown away.
8. Append each attribute in the given token to element.
This can enqueue a custom element callback reaction for the
attributeChangedCallback, which might run immediately (in the next
step).
Even though the is attribute governs the creation of a customized
built-in element, it is not present during the execution of the
relevant custom element constructor; it is appended in this step,
along with all other attributes.
9. If will execute script is true, then:
1. Let queue be the result of popping the current element queue from
the custom element reactions stack. (This will be the same
element queue as was pushed above.)
2. Invoke custom element reactions in queue.
3. Decrement document’s throw-on-dynamic-markup-insertion counter.
10. If element has an xmlns attribute *in the XMLNS namespace* whose value
is not exactly the same as the element’s namespace, that is a parse
error. Similarly, if element has an xmlns:xlink attribute in the XMLNS
namespace whose value is not the XLink namespace, that is a parse
error.
11. If element is a resettable element, invoke its reset algorithm. (This
initializes the element’s value and checkedness based on the element’s
attributes.)
12. If element is a form-associated element, and the form element pointer
is not null, and there is no template element on the stack of open
elements, and element is either not listed or doesn’t have a form
attribute, and the intended parent is in the same tree as the element
pointed to by the form element pointer, associate element with the
form element pointed to by the form element pointer, and suppress the
running of the reset the form owner algorithm when the parser
subsequently attempts to insert the element.
13. Return element.
----------------------------------------------------------------------
When the steps below require the user agent to insert a foreign element
for a token in a given namespace, the user agent must run these steps:
1. Let the adjusted insertion location be the appropriate place for
inserting a node.
2. Let element be the result of creating an element for the token in the
given namespace, with the intended parent being the element in which
the adjusted insertion location finds itself.
3. If it is possible to insert element at the adjusted insertion
location, then:
1. Push a new element queue onto the custom element reactions stack.
2. Insert element at the adjusted insertion location.
3. Pop the element queue from the custom element reactions stack,
and invoke custom element reactions in that queue.
If the adjusted insertion location cannot accept more elements, e.g.,
because it’s a Document that already has an element child, then
element is dropped on the floor.
4. Push element onto the stack of open elements so that it is the new
current node.
5. Return element.
When the steps below require the user agent to insert an HTML element for
a token, the user agent must insert a foreign element for the token, in
the HTML namespace.
----------------------------------------------------------------------
When the steps below require the user agent to adjust MathML attributes
for a token, then, if the token has an attribute named definitionurl,
change its name to definitionURL (note the case difference).
When the steps below require the user agent to adjust SVG attributes for a
token, then, for each attribute on the token whose attribute name is one
of the ones in the first column of the following table, change the
attribute’s name to the name given in the corresponding cell in the second
column. (This fixes the case of SVG attributes that are not all
lowercase.)
Attribute name on token Attribute name on element
attributename attributeName
attributetype attributeType
basefrequency baseFrequency
baseprofile baseProfile
calcmode calcMode
clippathunits clipPathUnits
diffuseconstant diffuseConstant
edgemode edgeMode
filterunits filterUnits
glyphref glyphRef
gradienttransform gradientTransform
gradientunits gradientUnits
kernelmatrix kernelMatrix
kernelunitlength kernelUnitLength
keypoints keyPoints
keysplines keySplines
keytimes keyTimes
lengthadjust lengthAdjust
limitingconeangle limitingConeAngle
markerheight markerHeight
markerunits markerUnits
markerwidth markerWidth
maskcontentunits maskContentUnits
maskunits maskUnits
numoctaves numOctaves
pathlength pathLength
patterncontentunits patternContentUnits
patterntransform patternTransform
patternunits patternUnits
pointsatx pointsAtX
pointsaty pointsAtY
pointsatz pointsAtZ
preservealpha preserveAlpha
preserveaspectratio preserveAspectRatio
primitiveunits primitiveUnits
refx refX
refy refY
repeatcount repeatCount
repeatdur repeatDur
requiredextensions requiredExtensions
requiredfeatures requiredFeatures
specularconstant specularConstant
specularexponent specularExponent
spreadmethod spreadMethod
startoffset startOffset
stddeviation stdDeviation
stitchtiles stitchTiles
surfacescale surfaceScale
systemlanguage systemLanguage
tablevalues tableValues
targetx targetX
targety targetY
textlength textLength
viewbox viewBox
viewtarget viewTarget
xchannelselector xChannelSelector
ychannelselector yChannelSelector
zoomandpan zoomAndPan
When the steps below require the user agent to adjust foreign attributes
for a token, then, if any of the attributes on the token match the strings
given in the first column of the following table, let the attribute be a
namespaced attribute, with the prefix being the string given in the
corresponding cell in the second column, the local name being the string
given in the corresponding cell in the third column, and the namespace
being the namespace given in the corresponding cell in the fourth column.
(This fixes the use of namespaced attributes, in particular lang
attributes in the XML namespace.)
Attribute name Prefix Local name Namespace
xlink:actuate xlink actuate XLink namespace
xlink:arcrole xlink arcrole XLink namespace
xlink:href xlink href XLink namespace
xlink:role xlink role XLink namespace
xlink:show xlink show XLink namespace
xlink:title xlink title XLink namespace
xlink:type xlink type XLink namespace
xml:lang xml lang XML namespace
xml:space xml space XML namespace
xmlns (none) xmlns XMLNS namespace
xmlns:xlink xmlns xlink XMLNS namespace
----------------------------------------------------------------------
When the steps below require the user agent to insert a character while
processing a token, the user agent must run the following steps:
1. Let data be the characters passed to the algorithm, or, if no
characters were explicitly specified, the character of the character
token being processed.
2. Let the adjusted insertion location be the appropriate place for
inserting a node.
3. If the adjusted insertion location is in a Document node, then abort
these steps.
The DOM will not let Document nodes have Text node children, so they
are dropped on the floor.
4. If there is a Text node immediately before the adjusted insertion
location, then append data to that Text node’s data.
Otherwise, create a new Text node whose data is data and whose node
document is the same as that of the element in which the adjusted
insertion location finds itself, and insert the newly created node at
the adjusted insertion location.
Here are some sample inputs to the parser and the corresponding number of
Text nodes that they result in, assuming a user agent that executes
scripts.
Input Number of Text nodes
A<script> One Text node in the
var script = document.getElementsByTagName('script')[0]; document, containing
document.body.removeChild(script); "AB".
</script>B
Three Text nodes;
"A" before the
A<script> script, the script’s
var text = document.createTextNode('B'); contents, and "BC"
document.body.appendChild(text); after the script
</script>C (the parser appends
to the Text node
created by the
script).
A<script> Two adjacent Text
var text = document.getElementsByTagName('script')[0].firstChild; nodes in the
text.data = 'B'; document, containing
document.body.appendChild(text); "A" and "BC".
</script>C
One Text node before
the table,
A<table>B<tr>C</tr>D</table> containing "ABCD".
(This is caused by
foster parenting.)
One Text node before
the table,
A<table><tr> B</tr> C</table> containing "A B C"
(A-space-B-space-C).
(This is caused by
foster parenting.)
One Text node before
the table,
containing "A BC"
(A-space-B-C), and
one Text node inside
the table (as a
child of a tbody)
with a single space
A<table><tr> B</tr> </em>C</table> character. (Space
characters separated
from non-space
characters by
non-character tokens
are not affected by
foster parenting,
even if those other
tokens then get
ignored.)
----------------------------------------------------------------------
When the steps below require the user agent to insert a comment while
processing a comment token, optionally with an explicitly insertion
position position, the user agent must run the following steps:
1. Let data be the data given in the comment token being processed.
2. If position was specified, then let the adjusted insertion location be
position. Otherwise, let adjusted insertion location be the
appropriate place for inserting a node.
3. Create a Comment node whose data attribute is set to data and whose
node document is the same as that of the node in which the adjusted
insertion location finds itself.
4. Insert the newly created node at the adjusted insertion location.
----------------------------------------------------------------------
DOM mutation events must not fire for changes caused by the UA parsing the
document. This includes the parsing of any content inserted using
document.write() and document.writeln() calls. [UIEVENTS]
However, mutation observers do fire, as required by the DOM specification.
8.2.5.2. Parsing elements that contain only text
The generic raw text element parsing algorithm and the generic RCDATA
element parsing algorithm consist of the following steps. These algorithms
are always invoked in response to a start tag token.
1. Insert an HTML element for the token.
2. If the algorithm that was invoked is the generic raw text element
parsing algorithm, switch the tokenizer to the RAWTEXT state;
otherwise the algorithm invoked was the generic RCDATA element parsing
algorithm, switch the tokenizer to the RCDATA state.
3. Let the original insertion mode be the current insertion mode.
4. Then, switch the insertion mode to "text".
8.2.5.3. Closing elements that have implied end tags
When the steps below require the UA to generate implied end tags, then,
while the current node is a dd element, a dt element, an li element, an
optgroup element, an option element, a p element, an rb element, an rp
element, an rt element, or an rtc element, the UA must pop the current
node off the stack of open elements.
If a step requires the UA to generate implied end tags but lists an
element to exclude from the process, then the UA must perform the above
steps as if that element was not in the above list.
When the steps below require the UA to generate all implied end tags
thoroughly, then, while the current node is a caption element, a colgroup
element, a dd element, a dt element, an li element, an optgroup element,
an option element, a p element, an rb element, an rp element, an rt
element, an rtc element, a tbody element, a td element, a tfoot element, a
th element, a thead element, or a tr element, the UA must pop the current
node off the stack of open elements.
8.2.5.4. The rules for parsing tokens in HTML content
8.2.5.4.1. The "initial" insertion mode
When the user agent is to apply the rules for the "initial" insertion
mode, the user agent must handle the token as follows:
A character token that is one of U+0009 CHARACTER TABULATION, U+000A LINE
FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR), or U+0020
SPACE
Ignore the token.
A comment token
Insert a comment as the last child of the Document object.
A DOCTYPE token
If the DOCTYPE token’s name is not a case-sensitive match for the
string "html", or the token’s public identifier is not missing, or
the token’s system identifier is neither missing nor a
case-sensitive match for the string "about:legacy-compat", then
there is a parse error.
Append a DocumentType node to the Document node, with the name
attribute set to the name given in the DOCTYPE token, or the empty
string if the name was missing; the publicId attribute set to the
public identifier given in the DOCTYPE token, or the empty string
if the public identifier was missing; the systemId attribute set
to the system identifier given in the DOCTYPE token, or the empty
string if the system identifier was missing; and the other
attributes specific to DocumentType objects set to null and empty
lists as appropriate. Associate the DocumentType node with the
Document object so that it is returned as the value of the doctype
attribute of the Document object.
Then, if the document is not an iframe srcdoc document, and the
DOCTYPE token matches one of the conditions in the following list,
then set the Document to quirks mode:
* The force-quirks flag is set to on.
* The name is set to anything other than "html" (compared
case-sensitively).
* The public identifier is set to: "-//W3O//DTD W3 HTML Strict
3.0//EN//"
* The public identifier is set to: "-/W3C/DTD HTML 4.0
Transitional/EN"
* The public identifier is set to: "HTML"
* The system identifier is set to:
"http://www.ibm.com/data/dtd/v11/ibmxhtml1-transitional.dtd"
* The public identifier starts with: "+//Silmaril//dtd html Pro
v0r11 19970101//"
* The public identifier starts with: "-//AS//DTD HTML 3.0
asWedit + extensions//"
* The public identifier starts with: "-//AdvaSoft Ltd//DTD HTML
3.0 asWedit + extensions//"
* The public identifier starts with: "-//IETF//DTD HTML 2.0
Level 1//"
* The public identifier starts with: "-//IETF//DTD HTML 2.0
Level 2//"
* The public identifier starts with: "-//IETF//DTD HTML 2.0
Strict Level 1//"
* The public identifier starts with: "-//IETF//DTD HTML 2.0
Strict Level 2//"
* The public identifier starts with: "-//IETF//DTD HTML 2.0
Strict//"
* The public identifier starts with: "-//IETF//DTD HTML 2.0//"
* The public identifier starts with: "-//IETF//DTD HTML 2.1E//"
* The public identifier starts with: "-//IETF//DTD HTML 3.0//"
* The public identifier starts with: "-//IETF//DTD HTML 3.2
Final//"
* The public identifier starts with: "-//IETF//DTD HTML 3.2//"
* The public identifier starts with: "-//IETF//DTD HTML 3//"
* The public identifier starts with: "-//IETF//DTD HTML Level
0//"
* The public identifier starts with: "-//IETF//DTD HTML Level
1//"
* The public identifier starts with: "-//IETF//DTD HTML Level
2//"
* The public identifier starts with: "-//IETF//DTD HTML Level
3//"
* The public identifier starts with: "-//IETF//DTD HTML Strict
Level 0//"
* The public identifier starts with: "-//IETF//DTD HTML Strict
Level 1//"
* The public identifier starts with: "-//IETF//DTD HTML Strict
Level 2//"
* The public identifier starts with: "-//IETF//DTD HTML Strict
Level 3//"
* The public identifier starts with: "-//IETF//DTD HTML
Strict//"
* The public identifier starts with: "-//IETF//DTD HTML//"
* The public identifier starts with: "-//Metrius//DTD Metrius
Presentational//"
* The public identifier starts with: "-//Microsoft//DTD
Internet Explorer 2.0 HTML Strict//"
* The public identifier starts with: "-//Microsoft//DTD
Internet Explorer 2.0 HTML//"
* The public identifier starts with: "-//Microsoft//DTD
Internet Explorer 2.0 Tables//"
* The public identifier starts with: "-//Microsoft//DTD
Internet Explorer 3.0 HTML Strict//"
* The public identifier starts with: "-//Microsoft//DTD
Internet Explorer 3.0 HTML//"
* The public identifier starts with: "-//Microsoft//DTD
Internet Explorer 3.0 Tables//"
* The public identifier starts with: "-//Netscape Comm.
Corp.//DTD HTML//"
* The public identifier starts with: "-//Netscape Comm.
Corp.//DTD Strict HTML//"
* The public identifier starts with: "-//O'Reilly and
Associates//DTD HTML 2.0//"
* The public identifier starts with: "-//O'Reilly and
Associates//DTD HTML Extended 1.0//"
* The public identifier starts with: "-//O'Reilly and
Associates//DTD HTML Extended Relaxed 1.0//"
* The public identifier starts with: "-//SQ//DTD HTML 2.0
HoTMetaL + extensions//"
* The public identifier starts with: "-//SoftQuad Software//DTD
HoTMetaL PRO 6.0::19990601::extensions to HTML 4.0//"
* The public identifier starts with: "-//SoftQuad//DTD HoTMetaL
PRO 4.0::19971010::extensions to HTML 4.0//"
* The public identifier starts with: "-//Spyglass//DTD HTML 2.0
Extended//"
* The public identifier starts with: "-//Sun Microsystems
Corp.//DTD HotJava HTML//"
* The public identifier starts with: "-//Sun Microsystems
Corp.//DTD HotJava Strict HTML//"
* The public identifier starts with: "-//W3C//DTD HTML 3
1995-03-24//"
* The public identifier starts with: "-//W3C//DTD HTML 3.2
Draft//"
* The public identifier starts with: "-//W3C//DTD HTML 3.2
Final//"
* The public identifier starts with: "-//W3C//DTD HTML 3.2//"
* The public identifier starts with: "-//W3C//DTD HTML 3.2S
Draft//"
* The public identifier starts with: "-//W3C//DTD HTML 4.0
Frameset//"
* The public identifier starts with: "-//W3C//DTD HTML 4.0
Transitional//"
* The public identifier starts with: "-//W3C//DTD HTML
Experimental 19960712//"
* The public identifier starts with: "-//W3C//DTD HTML
Experimental 970421//"
* The public identifier starts with: "-//W3C//DTD W3 HTML//"
* The public identifier starts with: "-//W3O//DTD W3 HTML
3.0//"
* The public identifier starts with: "-//WebTechs//DTD Mozilla
HTML 2.0//"
* The public identifier starts with: "-//WebTechs//DTD Mozilla
HTML//"
* The system identifier is missing and the public identifier
starts with: "-//W3C//DTD HTML 4.01 Frameset//"
* The system identifier is missing and the public identifier
starts with: "-//W3C//DTD HTML 4.01 Transitional//"
Otherwise, if the document is not an iframe srcdoc document, and
the DOCTYPE token matches one of the conditions in the following
list, then set the Document to limited-quirks mode:
* The public identifier starts with: "-//W3C//DTD XHTML 1.0
Frameset//"
* The public identifier starts with: "-//W3C//DTD XHTML 1.0
Transitional//"
* The system identifier is not missing and the public
identifier starts with: "-//W3C//DTD HTML 4.01 Frameset//"
* The system identifier is not missing and the public
identifier starts with: "-//W3C//DTD HTML 4.01
Transitional//"
The system identifier and public identifier strings must be
compared to the values given in the lists above in an ASCII
case-insensitive manner. A system identifier whose value is the
empty string is not considered missing for the purposes of the
conditions above.
Then, switch the insertion mode to "before html".
Anything else
If the document is not an iframe srcdoc document, then this is a
parse error; set the Document to quirks mode.
In any case, switch the insertion mode to "before html", then
reprocess the token.
8.2.5.4.2. The "before html" insertion mode
When the user agent is to apply the rules for the "before html" insertion
mode, the user agent must handle the token as follows:
A DOCTYPE token
Parse error.
A comment token
Insert a comment as the last child of the Document object.
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
Ignore the token.
A start tag whose tag name is "html"
Create an element for the token in the HTML namespace, with
the Document as the intended parent. Append it to the
Document object. Put this element in the stack of open
elements.
Switch the insertion mode to "before head".
An end tag whose tag name is one of: "head", "body", "html", "br"
Act as described in the "anything else" entry below.
Any other end tag
Parse error.
Anything else
Create an html element whose node document is the Document
object. Append it to the Document object. Put this element in
the stack of open elements.
Switch the insertion mode to "before head", then reprocess
the token.
The document element can end up being removed from the Document object,
e.g., by scripts; nothing in particular happens in such cases, content
continues being appended to the nodes as described in the next section.
8.2.5.4.3. The "before head" insertion mode
When the user agent is to apply the rules for the "before head" insertion
mode, the user agent must handle the token as follows:
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
Ignore the token.
A comment token
Insert a comment.
A DOCTYPE token
Parse error.
A start tag whose tag name is "html"
Process the token using the rules for the "in body" insertion
mode.
A start tag whose tag name is "head"
Insert an HTML element for the token.
Set the head element pointer to the newly created head
element.
Switch the insertion mode to "in head".
An end tag whose tag name is one of: "head", "body", "html", "br"
Act as described in the "anything else" entry below.
Any other end tag
Parse error.
Anything else
Insert an HTML element for a "head" start tag token with no
attributes.
Set the head element pointer to the newly created head
element.
Switch the insertion mode to "in head".
Reprocess the current token.
8.2.5.4.4. The "in head" insertion mode
When the user agent is to apply the rules for the "in head" insertion
mode, the user agent must handle the token as follows:
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
Insert the character.
A comment token
Insert a comment.
A DOCTYPE token
Parse error.
A start tag whose tag name is "html"
Process the token using the rules for the "in body" insertion
mode.
A start tag whose tag name is one of: "base", "basefont", "bgsound",
"link"
Insert an HTML element for the token. Immediately pop the
current node off the stack of open elements.
Acknowledge the token’s *self-closing flag*, if it is set.
A start tag whose tag name is "meta"
Insert an HTML element for the token. Immediately pop the
current node off the stack of open elements.
Acknowledge the token’s *self-closing flag*, if it is set.
If the element has a charset attribute, and getting an
encoding from its value results in an encoding, and the
confidence is currently tentative, then change the encoding
to the resulting encoding.
Otherwise, if the element has an http-equiv attribute whose
value is an ASCII case-insensitive match for the string
"Content-Type", and the element has a content attribute, and
applying the algorithm for extracting a character encoding
from a meta element to that attribute’s value returns an
encoding, and the confidence is currently tentative, then
change the encoding to the extracted encoding.
A start tag whose tag name is "title"
Follow the generic RCDATA element parsing algorithm.
A start tag whose tag name is "noscript", if the scripting flag is
enabled
A start tag whose tag name is one of: "noframes", "style"
Follow the generic raw text element parsing algorithm.
A start tag whose tag name is "noscript", if the scripting flag is
disabled
Insert an HTML element for the token.
Switch the insertion mode to "in head noscript".
A start tag whose tag name is "script"
Run these steps:
1. Let the adjusted insertion location be the appropriate
place for inserting a node.
2. Create an element for the token in the HTML namespace,
with the intended parent being the element in which the
adjusted insertion location finds itself.
3. Mark the element as being "parser-inserted" and unset
the element’s "non-blocking" flag.
This ensures that, if the script is external, any
document.write() calls in the script will execute
in-line, instead of blowing the document away, as would
happen in most other cases. It also prevents the script
from executing until the end tag is seen.
4. If the parser was originally created for the HTML
fragment parsing algorithm, then mark the script element
as "already started". (fragment case)
5. Insert the newly created element at the adjusted
insertion location.
6. Push the element onto the stack of open elements so that
it is the new current node.
7. Switch the tokenizer to the script data state.
8. Let the original insertion mode be the current insertion
mode.
9. Switch the insertion mode to "text".
An end tag whose tag name is "head"
Pop the current node (which will be the head element) off the
stack of open elements.
Switch the insertion mode to "after head".
An end tag whose tag name is one of: "body", "html", "br"
Act as described in the "anything else" entry below.
A start tag whose tag name is "template"
Insert an HTML element for the token.
Insert a marker at the end of the list of active formatting
elements.
Set the frameset-ok flag to "not ok".
Switch the insertion mode to "in template".
Push "in template" onto the stack of template insertion modes
so that it is the new current template insertion mode.
An end tag whose tag name is "template"
If there is no template element on the stack of open
elements, then this is a parse error; ignore the token.
Otherwise, run these steps:
1. Generate all implied end tags thoroughly.
2. If the current node is not a template element, then this
is a parse error.
3. Pop elements from the stack of open elements until a
template element has been popped from the stack.
4. Clear the list of active formatting elements up to the
last marker.
5. Pop the current template insertion mode off the stack of
template insertion modes.
6. Reset the insertion mode appropriately.
A start tag whose tag name is "head"
Any other end tag
Parse error.
Anything else
Pop the current node (which will be the head element) off the
stack of open elements.
Switch the insertion mode to "after head".
Reprocess the token.
8.2.5.4.5. The "in head noscript" insertion mode
When the user agent is to apply the rules for the "in head noscript"
insertion mode, the user agent must handle the token as follows:
A DOCTYPE token
Parse error.
A start tag whose tag name is "html"
Process the token using the rules for the "in body" insertion
mode.
An end tag whose tag name is "noscript"
Pop the current node (which will be a noscript element) from
the stack of open elements; the new current node will be a
head element.
Switch the insertion mode to "in head".
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
A comment token
A start tag whose tag name is one of: "basefont", "bgsound", "link",
"meta", "noframes", "style"
Process the token using the rules for the "in head" insertion
mode.
An end tag whose tag name is "br"
Act as described in the "anything else" entry below.
A start tag whose tag name is one of: "head", "noscript"
Any other end tag
Parse error.
Anything else
Parse error.
Pop the current node (which will be a noscript element) from
the stack of open elements; the new current node will be a
head element.
Switch the insertion mode to "in head".
Reprocess the token.
8.2.5.4.6. The "after head" insertion mode
When the user agent is to apply the rules for the "after head" insertion
mode, the user agent must handle the token as follows:
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
Insert the character.
A comment token
Insert a comment.
A DOCTYPE token
Parse error.
A start tag whose tag name is "html"
Process the token using the rules for the "in body" insertion
mode.
A start tag whose tag name is "body"
Insert an HTML element for the token.
Set the frameset-ok flag to "not ok".
Switch the insertion mode to "in body".
A start tag whose tag name is "frameset"
Insert an HTML element for the token.
Switch the insertion mode to "in frameset".
A start tag whose tag name is one of: "base", "basefont", "bgsound",
"link", "meta", "noframes", "script", "style", "template", "title"
Parse error.
Push the node pointed to by the head element pointer onto the
stack of open elements.
Process the token using the rules for the "in head" insertion
mode.
Remove the node pointed to by the head element pointer from
the stack of open elements. (It might not be the current node
at this point.)
The head element pointer cannot be null at this point.
An end tag whose tag name is "template"
Process the token using the rules for the "in head" insertion
mode.
An end tag whose tag name is one of: "body", "html", "br"
Act as described in the "anything else" entry below.
A start tag whose tag name is "head"
Any other end tag
Parse error.
Anything else
Insert an HTML element for a "body" start tag token with no
attributes.
Switch the insertion mode to "in body".
Reprocess the current token.
8.2.5.4.7. The "in body" insertion mode
When the user agent is to apply the rules for the "in body" insertion
mode, the user agent must handle the token as follows:
A character token that is U+0000 NULL
Parse error.
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
Reconstruct the active formatting elements, if any.
Insert the token’s character.
Any other character token
Reconstruct the active formatting elements, if any.
Insert the token’s character.
Set the frameset-ok flag to "not ok".
A comment token
Insert a comment.
A DOCTYPE token
Parse error.
A start tag whose tag name is "html"
Parse error.
If there is a template element on the stack of open elements,
then ignore the token.
Otherwise, for each attribute on the token, check to see if
the attribute is already present on the top element of the
stack of open elements. If it is not, add the attribute and
its corresponding value to that element.
A start tag whose tag name is one of: "base", "basefont", "bgsound",
"link", "meta", "noframes", "script", "style", "template", "title"
An end tag whose tag name is "template"
Process the token using the rules for the "in head" insertion
mode.
A start tag whose tag name is "body"
Parse error.
If the second element on the stack of open elements is not a
body element, if the stack of open elements has only one node
on it, or if there is a template element on the stack of open
elements, then ignore the token. (fragment case)
Otherwise, set the frameset-ok flag to "not ok"; then, for
each attribute on the token, check to see if the attribute is
already present on the body element (the second element) on
the stack of open elements, and if it is not, add the
attribute and its corresponding value to that element.
A start tag whose tag name is "frameset"
Parse error.
If the stack of open elements has only one node on it, or if
the second element on the stack of open elements is not a
body element, then ignore the token. (fragment case)
If the frameset-ok flag is set to "not ok", ignore the token.
Otherwise, run the following steps:
1. Remove the second element on the stack of open elements
from its parent node, if it has one.
2. Pop all the nodes from the bottom of the stack of open
elements, from the current node up to, but not
including, the root html element.
3. Insert an HTML element for the token.
4. Switch the insertion mode to "in frameset".
An end-of-file token
If the stack of template insertion modes is not empty, then
process the token using the rules for the "in template"
insertion mode.
Otherwise, follow these steps:
1. If there is a node in the stack of open elements that is
not either a dd element, a dt element, an li element, an
optgroup element, an option element, a p element, an rb
element, an rp element, an rt element, an rtc element, a
tbody element, a td element, a tfoot element, a th
element, a thead element, a tr element, the body
element, or the html element, then this is a parse
error.
2. Stop parsing.
An end tag whose tag name is "body"
If the stack of open elements does not have a body element in
scope, this is a parse error; ignore the token.
Otherwise, if there is a node in the stack of open elements
that is not either a dd element, a dt element, an li element,
an optgroup element, an option element, a p element, an rb
element, an rp element, an rt element, an rtc element, a
tbody element, a td element, a tfoot element, a th element, a
thead element, a tr element, the body element, or the html
element, then this is a parse error.
Switch the insertion mode to "after body".
An end tag whose tag name is "html"
If the stack of open elements does not have a body element in
scope, this is a parse error; ignore the token.
Otherwise, if there is a node in the stack of open elements
that is not either a dd element, a dt element, an li element,
an optgroup element, an option element, a p element, an rb
element, an rp element, an rt element, an rtc element, a
tbody element, a td element, a tfoot element, a th element, a
thead element, a tr element, the body element, or the html
element, then this is a parse error.
Switch the insertion mode to "after body".
Reprocess the token.
A start tag whose tag name is one of: "address", "article", "aside",
"blockquote", "center", "details", "dialog", "dir", "div", "dl",
"fieldset", "figcaption", "figure", "footer", "header", "main",
"nav", "ol", "p", "section", "summary", "ul"
If the stack of open elements has a p element in button
scope, then close a p element.
Insert an HTML element for the token.
A start tag whose tag name is one of: "h1", "h2", "h3", "h4", "h5",
"h6"
If the stack of open elements has a p element in button
scope, then close a p element.
If the current node is an HTML element whose tag name is one
of "h1", "h2", "h3", "h4", "h5", or "h6", then this is a
parse error; pop the current node off the stack of open
elements.
Insert an HTML element for the token.
A start tag whose tag name is one of: "pre", "listing"
If the stack of open elements has a p element in button
scope, then close a p element.
Insert an HTML element for the token.
If the next token is a U+000A LINE FEED (LF) character token,
then ignore that token and move on to the next one. (Newlines
at the start of pre blocks are ignored as an authoring
convenience.)
Set the frameset-ok flag to "not ok".
A start tag whose tag name is "form"
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.
Otherwise:
If the stack of open elements has a p element in button
scope, then close a p element.
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.
A start tag whose tag name is "li"
Run these steps:
1. Set the frameset-ok flag to "not ok".
2. Initialize node to be the current node (the bottommost
node of the stack).
3. Loop: If node is an li element, then run these substeps:
1. Generate implied end tags, except for li elements.
2. If the current node is not an li element, then this
is a parse error.
3. Pop elements from the stack of open elements until
an li element has been popped from the stack.
4. Jump to the step labeled Done below.
4. If node is in the special category, but is not an
address, div, or p element, then jump to the step
labeled Done below.
5. Otherwise, set node to the previous entry in the stack
of open elements and return to the step labeled Loop.
6. Done: If the stack of open elements has a p element in
button scope, then close a p element.
7. Finally, insert an HTML element for the token.
A start tag whose tag name is one of: "dd", "dt"
Run these steps:
1. Set the frameset-ok flag to "not ok".
2. Initialize node to be the current node (the bottommost
node of the stack).
3. Loop: If node is a dd element, then run these substeps:
1. Generate implied end tags, except for dd elements.
2. If the current node is not a dd element, then this
is a parse error.
3. Pop elements from the stack of open elements until
a dd element has been popped from the stack.
4. Jump to the step labeled Done below.
4. If node is a dt element, then run these substeps:
1. Generate implied end tags, except for dt elements.
2. If the current node is not a dt element, then this
is a parse error.
3. Pop elements from the stack of open elements until
a dt element has been popped from the stack.
4. Jump to the step labeled Done below.
5. If node is in the special category, but is not an
address, div, or p element, then jump to the step
labeled Done below.
6. Otherwise, set node to the previous entry in the stack
of open elements and return to the step labeled Loop.
7. Done: If the stack of open elements has a p element in
button scope, then close a p element.
8. Finally, insert an HTML element for the token.
A start tag whose tag name is "plaintext"
If the stack of open elements has a p element in button
scope, then close a p element.
Insert an HTML element for the token.
Switch the tokenizer to the §8.2.4.5 PLAINTEXT state.
Once a start tag with the tag name "plaintext" has been seen,
that will be the last token ever seen other than character
tokens (and the end-of-file token), because there is no way
to switch out of the §8.2.4.5 PLAINTEXT state.
A start tag whose tag name is "button"
1. If the stack of open elements has a button element in
scope, then run these substeps:
1. Parse error.
2. Generate implied end tags.
3. Pop elements from the stack of open elements until
a button element has been popped from the stack.
2. Reconstruct the active formatting elements, if any.
3. Insert an HTML element for the token.
4. Set the frameset-ok flag to "not ok".
An end tag whose tag name is one of: "address", "article", "aside",
"blockquote", "button", "center", "details", "dialog", "dir", "div",
"dl", "fieldset", "figcaption", "figure", "footer", "header",
"listing", "main", "nav", "ol", "pre", "section", "summary", "ul"
If the stack of open elements does not have an element in
scope that is an HTML element with the same tag name as that
of the token, then this is a parse error; ignore the token.
Otherwise, run these steps:
1. Generate implied end tags.
2. If the current node is not an HTML element with the same
tag name as that of the token, then this is a parse
error.
3. Pop elements from the stack of open elements until an
HTML element with the same tag name as the token has
been popped from the stack.
An end tag whose tag name is "form"
If there is no template element on the stack of open
elements, then run these substeps:
1. Let node be the element that the form element pointer is
set to, or null if it is not set to an element.
2. Set the form element pointer to null.
3. If node is null or if the stack of open elements does
not have node in scope, then this is a parse error;
abort these steps and ignore the token.
4. Generate implied end tags.
5. If the current node is not node, then this is a parse
error.
6. Remove node from the stack of open elements.
If there is a template element on the stack of open elements,
then run these substeps instead:
1. If the stack of open elements does not have a form
element in scope, then this is a parse error; abort
these steps and ignore the token.
2. Generate implied end tags.
3. If the current node is not a form element, then this is
a parse error.
4. Pop elements from the stack of open elements until a
form element has been popped from the stack.
An end tag whose tag name is "p"
If the stack of open elements does not have a p element in
button scope, then this is a parse error; insert an HTML
element for a "p" start tag token with no attributes.
Close a p element.
An end tag whose tag name is "li"
If the stack of open elements does not have an li element in
list item scope, then this is a parse error; ignore the
token.
Otherwise, run these steps:
1. Generate implied end tags, except for li elements.
2. If the current node is not an li element, then this is a
parse error.
3. Pop elements from the stack of open elements until an li
element has been popped from the stack.
An end tag whose tag name is one of: "dd", "dt"
If the stack of open elements does not have an element in
scope that is an HTML element with the same tag name as that
of the token, then this is a parse error; ignore the token.
Otherwise, run these steps:
1. Generate implied end tags, except for HTML elements with
the same tag name as the token.
2. If the current node is not an HTML element with the same
tag name as that of the token, then this is a parse
error.
3. Pop elements from the stack of open elements until an
HTML element with the same tag name as the token has
been popped from the stack.
An end tag whose tag name is one of: "h1", "h2", "h3", "h4", "h5",
"h6"
If the stack of open elements does not have an element in
scope that is an HTML element and whose tag name is one of
"h1", "h2", "h3", "h4", "h5", or "h6", then this is a parse
error; ignore the token.
Otherwise, run these steps:
1. Generate implied end tags.
2. If the current node is not an HTML element with the same
tag name as that of the token, then this is a parse
error.
3. Pop elements from the stack of open elements until an
HTML element whose tag name is one of "h1", "h2", "h3",
"h4", "h5", or "h6" has been popped from the stack.
An end tag whose tag name is "sarcasm"
Take a deep breath, then act as described in the "any other
end tag" entry below.
A start tag whose tag name is "a"
If the list of active formatting elements contains an a
element between the end of the list and the last marker on
the list (or the start of the list if there is no marker on
the list), then this is a parse error; run the adoption
agency algorithm for the token, then remove that element from
the list of active formatting elements and the stack of open
elements if the adoption agency algorithm didn’t already
remove it (it might not have if the element is not in table
scope).
In the non-conforming stream
<a href="a">a<table><a href="b">b</table>x,
the first a element would be closed upon seeing the second
one, and the "x" character would be inside a link to "b", not
to "a". This is despite the fact that the outer a element is
not in table scope (meaning that a regular </a> end tag at
the start of the table wouldn’t close the outer a element).
The result is that the two a elements are indirectly nested
inside each other — non-conforming markup will often result
in non-conforming DOMs when parsed.
Reconstruct the active formatting elements, if any.
Insert an HTML element for the token. Push onto the list of
active formatting elements that element.
A start tag whose tag name is one of: "b", "big", "code", "em",
"font", "i", "s", "small", "strike", "strong", "tt", "u"
Reconstruct the active formatting elements, if any.
Insert an HTML element for the token. Push onto the list of
active formatting elements that element.
A start tag whose tag name is "nobr"
Reconstruct the active formatting elements, if any.
If the stack of open elements has a nobr element in scope,
then this is a parse error; run the adoption agency algorithm
for the token, then once again Reconstruct the active
formatting elements, if any.
Insert an HTML element for the token. Push onto the list of
active formatting elements that element.
An end tag whose tag name is one of: "a", "b", "big", "code", "em",
"font", "i", "nobr", "s", "small", "strike", "strong", "tt", "u"
Run the adoption agency algorithm for the token.
A start tag whose tag name is one of: "applet", "marquee", "object"
Reconstruct the active formatting elements, if any.
Insert an HTML element for the token.
Insert a marker at the end of the list of active formatting
elements.
Set the frameset-ok flag to "not ok".
An end tag token whose tag name is one of: "applet", "marquee",
"object"
If the stack of open elements does not have an element in
scope that is an HTML element with the same tag name as that
of the token, then this is a parse error; ignore the token.
Otherwise, run these steps:
1. Generate implied end tags.
2. If the current node is not an HTML element with the same
tag name as that of the token, then this is a parse
error.
3. Pop elements from the stack of open elements until an
HTML element with the same tag name as the token has
been popped from the stack.
4. Clear the list of active formatting elements up to the
last marker.
A start tag whose tag name is "table"
If the Document is not set to quirks mode, and the stack of
open elements has a p element in button scope, then close a p
element.
Insert an HTML element for the token.
Set the frameset-ok flag to "not ok".
Switch the insertion mode to "in table".
An end tag whose tag name is "br"
Parse error. Drop the attributes from the token, and act as
described in the next entry; i.e., act as if this was a "br"
start tag token with no attributes, rather than the end tag
token that it actually is.
A start tag whose tag name is one of: "area", "br", "embed", "img",
"wbr"
Reconstruct the active formatting elements, if any.
Insert an HTML element for the token. Immediately pop the
current node off the stack of open elements.
Acknowledge the token’s *self-closing flag*, if it is set.
Set the frameset-ok flag to "not ok".
A start tag whose tag name is "input"
Reconstruct the active formatting elements, if any.
Insert an HTML element for the token. Immediately pop the
current node off the stack of open elements.
Acknowledge the token’s *self-closing flag*, if it is set.
If the token does not have an attribute with the name "type",
or if it does, but that attribute’s value is not an ASCII
case-insensitive match for the string "hidden", then: set the
frameset-ok flag to "not ok".
A start tag whose tag name is one of: "param", "source", "track"
Insert an HTML element for the token. Immediately pop the
current node off the stack of open elements.
Acknowledge the token’s *self-closing flag*, if it is set.
A start tag whose tag name is "hr"
If the stack of open elements has a p element in button
scope, then close a p element.
Insert an HTML element for the token. Immediately pop the
current node off the stack of open elements.
Acknowledge the token’s *self-closing flag*, if it is set.
Set the frameset-ok flag to "not ok".
A start tag whose tag name is "image"
Parse error. Change the token’s tag name to "img" and
reprocess it. (Don’t ask.)
A start tag whose tag name is "textarea"
Run these steps:
1. Insert an HTML element for the token.
2. If the next token is a U+000A LINE FEED (LF) character
token, then ignore that token and move on to the next
one. (Newlines at the start of textarea elements are
ignored as an authoring convenience.)
3. Switch the tokenizer to the RCDATA state.
4. Let the original insertion mode be the current insertion
mode.
5. Set the frameset-ok flag to "not ok".
6. Switch the insertion mode to "text".
A start tag whose tag name is "xmp"
If the stack of open elements has a p element in button
scope, then close a p element.
Reconstruct the active formatting elements, if any.
Set the frameset-ok flag to "not ok".
Follow the generic raw text element parsing algorithm.
A start tag whose tag name is "iframe"
Set the frameset-ok flag to "not ok".
Follow the generic raw text element parsing algorithm.
A start tag whose tag name is "noembed"
A start tag whose tag name is "noscript", if the scripting flag is
enabled
Follow the generic raw text element parsing algorithm.
A start tag whose tag name is "select"
Reconstruct the active formatting elements, if any.
Insert an HTML element for the token.
Set the frameset-ok flag to "not ok".
If the insertion mode is one of "in table", "in caption", "in
table body", "in row", or "in cell", then switch the
insertion mode to "in select in table". Otherwise, switch the
insertion mode to "in select".
A start tag whose tag name is one of: "optgroup", "option"
If the current node is an option element, then pop the
current node off the stack of open elements.
Reconstruct the active formatting elements, if any.
Insert an HTML element for the token.
A start tag whose tag name is one of: "rb", "rtc"
If the stack of open elements has a ruby element in scope,
then generate implied end tags. If the current node is not
now a ruby element, this is a parse error.
Insert an HTML element for the token.
A start tag whose tag name is one of: "rp", "rt"
If the stack of open elements has a ruby element in scope,
then generate implied end tags, except for rtc elements. If
the current node is not now a rtc element or a ruby element,
this is a parse error.
Insert an HTML element for the token.
A start tag whose tag name is "math"
Reconstruct the active formatting elements, if any.
Adjust MathML attributes for the token. (This fixes the case
of MathML attributes that are not all lowercase.)
Adjust foreign attributes for the token. (This fixes the use
of namespaced attributes, in particular XLink.)
Insert a foreign element for the token, in the MathML
namespace.
If the token has its self-closing flag set, pop the current
node off the stack of open elements and acknowledge the
token’s *self-closing flag*.
A start tag whose tag name is "svg"
Reconstruct the active formatting elements, if any.
Adjust SVG attributes for the token. (This fixes the case of
SVG attributes that are not all lowercase.)
Adjust foreign attributes for the token. (This fixes the use
of namespaced attributes, in particular XLink in SVG.)
Insert a foreign element for the token, in the SVG namespace.
If the token has its self-closing flag set, pop the current
node off the stack of open elements and acknowledge the
token’s *self-closing flag*.
A start tag whose tag name is one of: "caption", "col", "colgroup",
"frame", "head", "tbody", "td", "tfoot", "th", "thead", "tr"
Parse error.
Any other start tag
Reconstruct the active formatting elements, if any.
Insert an HTML element for the token.
This element will be an ordinaryelement.
Any other end tag
Run these steps:
1. Initialize node to be the current node (the bottommost
node of the stack).
2. Loop: If node is an HTML element with the same tag name
as the token, then:
1. Generate implied end tags, except for HTML elements
with the same tag name as the token.
2. If node is not the current node, then this is a
parse error.
3. Pop all the nodes from the current node up to node,
including node, then stop these steps.
3. Otherwise, if node is in the special category, then this
is a parse error; ignore the token, and abort these
steps.
4. Set node to the previous entry in the stack of open
elements.
5. Return to the step labeled Loop.
When the steps above say the UA is to close a p element, it means that the
UA must run the following steps:
1. Generate implied end tags, except for p elements.
2. If the current node is not a p element, then this is a parse error.
3. Pop elements from the stack of open elements until a p element has
been popped from the stack.
The adoption agency algorithm, which takes as its only argument a token
token for which the algorithm is being run, consists of the following
steps:
1. Let subject be token’s tag name.
2. If the current node is an HTML element whose tag name is subject, and
the current node is not in the list of active formatting elements,
then pop the current node off the stack of open elements, and abort
these steps.
3. Let outer loop counter be zero.
4. Outer loop: If outer loop counter is greater than or equal to eight,
then abort these steps.
5. Increment outer loop counter by one.
6. Let formatting element be the last element in the list of active
formatting elements that:
* is between the end of the list and the last marker in the list,
if any, or the start of the list otherwise, and
* has the tag name subject.
If there is no such element, then abort these steps and instead act
as described in the "any other end tag" entry above.
7. If formatting element is not in the stack of open elements, then this
is a parse error; remove the element from the list, and abort these
steps.
8. If formatting element is in the stack of open elements, but the
element is not in scope, then this is a parse error; abort these
steps.
9. If formatting element is not the current node, this is a parse error.
(But do not abort these steps.)
10. Let furthest block be the topmost node in the stack of open elements
that is lower in the stack than formatting element, and is an element
in the special category. There might not be one.
11. If there is no furthest block, then the UA must first pop all the
nodes from the bottom of the stack of open elements, from the current
node up to and including formatting element, then remove formatting
element from the list of active formatting elements, and finally
abort these steps.
12. Let common ancestor be the element immediately above formatting
element in the stack of open elements.
13. Let a bookmark note the position of formatting element in the list of
active formatting elements relative to the elements on either side of
it in the list.
14. Let node and last node be furthest block. Follow these steps:
1. Let inner loop counter be zero.
2. Inner loop: Increment inner loop counter by one.
3. Let node be the element immediately above node in the stack of
open elements, or if node is no longer in the stack of open
elements (e.g., because it got removed by this algorithm), the
element that was immediately above node in the stack of open
elements before node was removed.
4. If node is formatting element, then go to the next step in the
overall algorithm.
5. If inner loop counter is greater than three and node is in the
list of active formatting elements, then remove node from the
list of active formatting elements.
6. If node is not in the list of active formatting elements, then
remove node from the stack of open elements and then go back to
the step labeled Inner loop.
7. Create an element for the token for which the element node was
created, in the HTML namespace, with common ancestor as the
intended parent; replace the entry for node in the list of
active formatting elements with an entry for the new element,
replace the entry for node in the stack of open elements with an
entry for the new element, and let node be the new element.
8. If last node is furthest block, then move the aforementioned
bookmark to be immediately after the new node in the list of
active formatting elements.
9. Insert last node into node, first removing it from its previous
parent node if any.
10. Let last node be node.
11. Return to the step labeled Inner loop.
15. Insert whatever last node ended up being in the previous step at the
appropriate place for inserting a node, but using common ancestor as
the override target.
16. Create an element for the token for which formatting element was
created, in the HTML namespace, with furthest block as the intended
parent.
17. Take all of the child nodes of furthest block and append them to the
element created in the last step.
18. Append that new element to furthest block.
19. Remove formatting element from the list of active formatting
elements, and insert the new element into the list of active
formatting elements at the position of the aforementioned bookmark.
20. Remove formatting element from the stack of open elements, and insert
the new element into the stack of open elements immediately below the
position of furthest block in that stack.
21. Jump back to the step labeled Outer loop.
This algorithm’s name, the "adoption agency algorithm", comes from the way
it causes elements to change parents, and is in contrast with other
possible algorithms for dealing with misnested content, which included the
"incest algorithm", the "secret affair algorithm", and the "Heisenberg
algorithm".
8.2.5.4.8. The "text" insertion mode
When the user agent is to apply the rules for the "text" insertion mode,
the user agent must handle the token as follows:
A character token
Insert the token’s character.
This can never be a U+0000 NULL character; the tokenizer
converts those to U+FFFD REPLACEMENT CHARACTER characters.
An end-of-file token
Parse error.
If the current node is a script element, mark the script
element as "already started".
Pop the current node off the stack of open elements.
Switch the insertion mode to the original insertion mode and
reprocess the token.
An end tag whose tag name is "script"
If the JavaScript execution context stack is empty, perform a
microtask checkpoint.
Let script be the current node (which will be a script
element).
Pop the current node off the stack of open elements.
Switch the insertion mode to the original insertion mode.
Let the old insertion point have the same value as the
current insertion point. Let the insertion point be just
before the next input character.
Increment the parser’s script nesting level by one.
Prepare the script. This might cause some script to execute,
which might cause new characters to be inserted into the
tokenizer, and might cause the tokenizer to output more
tokens, resulting in a reentrant invocation of the parser.
Decrement the parser’s script nesting level by one. If the
parser’s script nesting level is zero, then set the parser
pause flag to false.
Let the insertion point have the value of the old insertion
point. (In other words, restore the insertion point to its
previous value. This value might be the "undefined" value.)
At this stage, if there is a pending parsing-blocking script,
then:
If the script nesting level is not zero:
Set the parser pause flag to true, and abort the
processing of any nested invocations of the
tokenizer, yielding control back to the caller.
(Tokenization will resume when the caller
returns to the "outer" tree construction stage.)
The tree construction stage of this particular
parser is being called reentrantly, say from a
call to document.write().
Otherwise:
Run these steps:
1. Let the script be the pending
parsing-blocking script. There is no longer
a pending parsing-blocking script.
2. Block the tokenizer for this instance of
the HTML parser, such that the event loop
will not run tasks that invoke the
tokenizer.
3. If the parser’s Document has a style sheet
that is blocking scripts or the script’s
"ready to be parser-executed" flag is not
set: spin the event loop until the parser’s
Document has no style sheet that is
blocking scripts and the script’s "ready to
be parser-executed" flag is set.
4. If this parser has been aborted in the
meantime, abort these steps.
This could happen if, e.g., while the spin
the event loop algorithm is running, the
browsing context gets closed, or the
document.open() method gets invoked on the
Document.
5. Unblock the tokenizer for this instance of
the HTML parser, such that tasks that
invoke the tokenizer can again be run.
6. Let the insertion point be just before the
next input character.
7. Increment the parser’s script nesting level
by one (it should be zero before this step,
so this sets it to one).
8. Execute the script.
9. Decrement the parser’s script nesting level
by one. If the parser’s script nesting
level is zero (which it always should be at
this point), then set the parser pause flag
to false.
10. Let the insertion point be undefined again.
11. If there is once again a pending
parsing-blocking script, then repeat these
steps from step 1.
Any other end tag
Pop the current node off the stack of open elements.
Switch the insertion mode to the original insertion mode.
8.2.5.4.9. The "in table" insertion mode
When the user agent is to apply the rules for the "in table" insertion
mode, the user agent must handle the token as follows:
A character token, if the current node is table, tbody, tfoot, thead,
or tr element
Let the pending table character tokens be an empty list of
tokens.
Let the original insertion mode be the current insertion
mode.
Switch the insertion mode to "in table text" and reprocess
the token.
A comment token
Insert a comment.
A DOCTYPE token
Parse error.
A start tag whose tag name is "caption"
Clear the stack back to a table context. (See below.)
Insert a marker at the end of the list of active formatting
elements.
Insert an HTML element for the token, then switch the
insertion mode to "in caption".
A start tag whose tag name is "colgroup"
Clear the stack back to a table context. (See below.)
Insert an HTML element for the token, then switch the
insertion mode to "in column group".
A start tag whose tag name is "col"
Clear the stack back to a table context. (See below.)
Insert an HTML element for a "colgroup" start tag token with
no attributes, then switch the insertion mode to "in column
group".
Reprocess the current token.
A start tag whose tag name is one of: "tbody", "tfoot", "thead"
Clear the stack back to a table context. (See below.)
Insert an HTML element for the token, then switch the
insertion mode to "in table body".
A start tag whose tag name is one of: "td", "th", "tr"
Clear the stack back to a table context. (See below.)
Insert an HTML element for a "tbody" start tag token with no
attributes, then switch the insertion mode to "in table
body".
Reprocess the current token.
A start tag whose tag name is "table"
Parse error.
If the stack of open elements does not have a table element
in table scope, ignore the token.
Otherwise:
Pop elements from this stack until a table element has been
popped from the stack.
Reset the insertion mode appropriately.
Reprocess the token.
An end tag whose tag name is "table"
If the stack of open elements does not have a table element
in table scope, this is a parse error; ignore the token.
Otherwise:
Pop elements from this stack until a table element has been
popped from the stack.
Reset the insertion mode appropriately.
An end tag whose tag name is one of: "body", "caption", "col",
"colgroup", "html", "tbody", "td", "tfoot", "th", "thead", "tr"
Parse error.
A start tag whose tag name is one of: "style", "script", "template"
An end tag whose tag name is "template"
Process the token using the rules for the "in head" insertion
mode.
A start tag whose tag name is "input"
If the token does not have an attribute with the name "type",
or if it does, but that attribute’s value is not an ASCII
case-insensitive match for the string "hidden", then: act as
described in the "anything else" entry below.
Otherwise:
Parse error.
Insert an HTML element for the token.
Pop that input element off the stack of open elements.
Acknowledge the token’s *self-closing flag*, if it is set.
A start tag whose tag name is "form"
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 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.
An end-of-file token
Process the token using the rules for the "in body" insertion
mode.
Anything else
Parse error. Enable foster parenting, process the token using
the rules for the "in body" insertion mode, and then disable
foster parenting.
When the steps above require the UA to clear the stack back to a table
context, it means that the UA must, while the current node is not a table,
template, or html element, pop elements from the stack of open elements.
This is the same list of elements as used in the has an element in table
scope steps.
The current node being an html element after this process is a fragment
case.
8.2.5.4.10. The "in table text" insertion mode
When the user agent is to apply the rules for the "in table text"
insertion mode, the user agent must handle the token as follows:
A character token that is U+0000 NULL
Parse error.
Any other character token
Append the character token to the pending table character
tokens list.
Anything else
If any of the tokens in the pending table character tokens
list are character tokens that are not space characters, then
this is a parse error: reprocess the character tokens in the
pending table character tokens list using the rules given in
the "anything else" entry in the "in table" insertion mode.
Otherwise, insert the characters given by the pending table
character tokens list.
Switch the insertion mode to the original insertion mode and
reprocess the token.
8.2.5.4.11. The "in caption" insertion mode
When the user agent is to apply the rules for the "in caption" insertion
mode, the user agent must handle the token as follows:
An end tag whose tag name is "caption"
If the stack of open elements does not have a caption element
in table scope, this is a parse error; ignore the token.
(fragment case)
Otherwise:
Generate implied end tags.
Now, if the current node is not a caption element, then this
is a parse error.
Pop elements from this stack until a caption element has been
popped from the stack.
Clear the list of active formatting elements up to the last
marker.
Switch the insertion mode to "in table".
A start tag whose tag name is one of: "caption", "col", "colgroup",
"tbody", "td", "tfoot", "th", "thead", "tr"
An end tag whose tag name is "table"
If the stack of open elements does not have a caption element
in table scope, this is a parse error; ignore the token.
(fragment case)
Otherwise:
Generate implied end tags.
Now, if the current node is not a caption element, then this
is a parse error.
Pop elements from this stack until a caption element has been
popped from the stack.
Clear the list of active formatting elements up to the last
marker.
Switch the insertion mode to "in table".
Reprocess the token.
An end tag whose tag name is one of: "body", "col", "colgroup",
"html", "tbody", "td", "tfoot", "th", "thead", "tr"
Parse error.
Anything else
Process the token using the rules for the "in body" insertion
mode.
8.2.5.4.12. The "in column group" insertion mode
When the user agent is to apply the rules for the "in column group"
insertion mode, the user agent must handle the token as follows:
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
Insert the character.
A comment token
Insert a comment.
A DOCTYPE token
Parse error.
A start tag whose tag name is "html"
Process the token using the rules for the "in body" insertion
mode.
A start tag whose tag name is "col"
Insert an HTML element for the token. Immediately pop the
current node off the stack of open elements.
Acknowledge the token’s *self-closing flag*, if it is set.
An end tag whose tag name is "colgroup"
If the current node is not a colgroup element, then this is a
parse error; ignore the token.
Otherwise, pop the current node from the stack of open
elements. Switch the insertion mode to "in table".
An end tag whose tag name is "col"
Parse error.
A start tag whose tag name is "template"
An end tag whose tag name is "template"
Process the token using the rules for the "in head" insertion
mode.
An end-of-file token
Process the token using the rules for the "in body" insertion
mode.
Anything else
If the current node is not a colgroup element, then this is a
parse error; ignore the token.
Otherwise, pop the current node from the stack of open
elements.
Switch the insertion mode to "in table".
Reprocess the token.
8.2.5.4.13. The "in table body" insertion mode
When the user agent is to apply the rules for the "in table body"
insertion mode, the user agent must handle the token as follows:
A start tag whose tag name is "tr"
Clear the stack back to a table body context. (See below.)
Insert an HTML element for the token, then switch the
insertion mode to "in row".
A start tag whose tag name is one of: "th", "td"
Parse error.
Clear the stack back to a table body context. (See below.)
Insert an HTML element for a "tr" start tag token with no
attributes, then switch the insertion mode to "in row".
Reprocess the current token.
An end tag whose tag name is one of: "tbody", "tfoot", "thead"
If the stack of open elements does not have an element in
table scope that is an HTML element with the same tag name as
the token, this is a parse error; ignore the token.
Otherwise:
Clear the stack back to a table body context. (See below.)
Pop the current node from the stack of open elements. Switch
the insertion mode to "in table".
A start tag whose tag name is one of: "caption", "col", "colgroup",
"tbody", "tfoot", "thead"
An end tag whose tag name is "table"
If the stack of open elements does not have a tbody, thead,
or tfoot element in table scope, this is a parse error;
ignore the token.
Otherwise:
Clear the stack back to a table body context. (See below.)
Pop the current node from the stack of open elements. Switch
the insertion mode to "in table".
Reprocess the token.
An end tag whose tag name is one of: "body", "caption", "col",
"colgroup", "html", "td", "th", "tr"
Parse error.
Anything else
Process the token using the rules for the "in table"
insertion mode.
When the steps above require the UA to clear the stack back to a table
body context, it means that the UA must, while the current node is not a
tbody, tfoot, thead, template, or html element, pop elements from the
stack of open elements.
The current node being an html element after this process is a fragment
case.
8.2.5.4.14. The "in row" insertion mode
When the user agent is to apply the rules for the "in row" insertion mode,
the user agent must handle the token as follows:
A start tag whose tag name is one of: "th", "td"
Clear the stack back to a table row context. (See below.)
Insert an HTML element for the token, then switch the
insertion mode to "in cell".
Insert a marker at the end of the list of active formatting
elements.
An end tag whose tag name is "tr"
If the stack of open elements does not have a tr element in
table scope, this is a parse error; ignore the token.
Otherwise:
Clear the stack back to a table row context. (See below.)
Pop the current node (which will be a tr element) from the
stack of open elements. Switch the insertion mode to "in
table body".
A start tag whose tag name is one of: "caption", "col", "colgroup",
"tbody", "tfoot", "thead", "tr"
An end tag whose tag name is "table"
If the stack of open elements does not have a tr element in
table scope, this is a parse error; ignore the token.
Otherwise:
Clear the stack back to a table row context. (See below.)
Pop the current node (which will be a tr element) from the
stack of open elements. Switch the insertion mode to "in
table body".
Reprocess the token.
An end tag whose tag name is one of: "tbody", "tfoot", "thead"
If the stack of open elements does not have an element in
table scope that is an HTML element with the same tag name as
the token, this is a parse error; ignore the token.
If the stack of open elements does not have a tr element in
table scope, ignore the token.
Otherwise:
Clear the stack back to a table row context. (See below.)
Pop the current node (which will be a tr element) from the
stack of open elements. Switch the insertion mode to "in
table body".
Reprocess the token.
An end tag whose tag name is one of: "body", "caption", "col",
"colgroup", "html", "td", "th"
Parse error.
Anything else
Process the token using the rules for the "in table"
insertion mode.
When the steps above require the UA to clear the stack back to a table row
context, it means that the UA must, while the current node is not a tr,
template, or html element, pop elements from the stack of open elements.
The current node being an html element after this process is a fragment
case.
8.2.5.4.15. The "in cell" insertion mode
When the user agent is to apply the rules for the "in cell" insertion
mode, the user agent must handle the token as follows:
An end tag whose tag name is one of: "td", "th"
If the stack of open elements does not have an element in
table scope that is an HTML element with the same tag name as
that of the token, then this is a parse error; ignore the
token.
Otherwise:
Generate implied end tags.
Now, if the current node is not an HTML element with the same
tag name as the token, then this is a parse error.
Pop elements from the stack of open elements stack until an
HTML element with the same tag name as the token has been
popped from the stack.
Clear the list of active formatting elements up to the last
marker.
Switch the insertion mode to "in row".
A start tag whose tag name is one of: "caption", "col", "colgroup",
"tbody", "td", "tfoot", "th", "thead", "tr"
If the stack of open elements does not have a td or th
element in table scope, then this is a parse error; ignore
the token. (fragment case)
Otherwise, close the cell (see below) and reprocess the
token.
An end tag whose tag name is one of: "body", "caption", "col",
"colgroup", "html"
Parse error.
An end tag whose tag name is one of: "table", "tbody", "tfoot",
"thead", "tr"
If the stack of open elements does not have an element in
table scope that is an HTML element with the same tag name as
that of the token, then this is a parse error; ignore the
token.
Otherwise, close the cell (see below) and reprocess the
token.
Anything else
Process the token using the rules for the "in body" insertion
mode.
Where the steps above say to close the cell, they mean to run the
following algorithm:
1. Generate implied end tags.
2. If the current node is not now a td element or a th element, then
this is a parse error.
3. Pop elements from the stack of open elements stack until a td element
or a th element has been popped from the stack.
4. Clear the list of active formatting elements up to the last marker.
5. Switch the insertion mode to "in row".
The stack of open elements cannot have both a td and a th element in table
scope at the same time, nor can it have neither when the close the cell
algorithm is invoked.
8.2.5.4.16. The "in select" insertion mode
When the user agent is to apply the rules for the "in select" insertion
mode, the user agent must handle the token as follows:
A character token that is U+0000 NULL
Parse error.
Any other character token
Insert the token’s character.
A comment token
Insert a comment.
A DOCTYPE token
Parse error.
A start tag whose tag name is "html"
Process the token using the rules for the "in body" insertion
mode.
A start tag whose tag name is "option"
If the current node is an option element, pop that node from
the stack of open elements.
Insert an HTML element for the token.
A start tag whose tag name is "optgroup"
If the current node is an option element, pop that node from
the stack of open elements.
If the current node is an optgroup element, pop that node
from the stack of open elements.
Insert an HTML element for the token.
An end tag whose tag name is "optgroup"
First, if the current node is an option element, and the node
immediately before it in the stack of open elements is an
optgroup element, then pop the current node from the stack of
open elements.
If the current node is an optgroup element, then pop that
node from the stack of open elements. Otherwise, this is a
parse error; ignore the token.
An end tag whose tag name is "option"
If the current node is an option element, then pop that node
from the stack of open elements. Otherwise, this is a parse
error; ignore the token.
An end tag whose tag name is "select"
If the stack of open elements does not have a select element
in select scope, this is a parse error; ignore the token.
(fragment case)
Otherwise:
Pop elements from the stack of open elements until a select
element has been popped from the stack.
Reset the insertion mode appropriately.
A start tag whose tag name is "select"
Parse error.
If the stack of open elements does not have a select element
in select scope, ignore the token. (fragment case)
Otherwise:
Pop elements from the stack of open elements until a select
element has been popped from the stack.
Reset the insertion mode appropriately.
Note: It just gets treated like an end tag.
A start tag whose tag name is one of: "input", "textarea"
Parse error.
If the stack of open elements does not have a select element
in select scope, ignore the token. (fragment case)
Otherwise:
Pop elements from the stack of open elements until a select
element has been popped from the stack.
Reset the insertion mode appropriately.
Reprocess the token.
A start tag whose tag name is one of: "script", "template"
An end tag whose tag name is "template"
Process the token using the rules for the "in head" insertion
mode.
An end-of-file token
Process the token using the rules for the "in body" insertion
mode.
Anything else
Parse error.
8.2.5.4.17. The "in select in table" insertion mode
When the user agent is to apply the rules for the "in select in table"
insertion mode, the user agent must handle the token as follows:
A start tag whose tag name is one of: "caption", "table", "tbody",
"tfoot", "thead", "tr", "td", "th"
Parse error.
Pop elements from the stack of open elements until a select
element has been popped from the stack.
Reset the insertion mode appropriately.
Reprocess the token.
An end tag whose tag name is one of: "caption", "table", "tbody",
"tfoot", "thead", "tr", "td", "th"
Parse error.
If the stack of open elements does not have an element in
table scope that is an HTML element with the same tag name as
that of the token, then ignore the token.
Otherwise:
Pop elements from the stack of open elements until a select
element has been popped from the stack.
Reset the insertion mode appropriately.
Reprocess the token.
Anything else
Process the token using the rules for the "in select"
insertion mode.
8.2.5.4.18. The "in template" insertion mode
When the user agent is to apply the rules for the "in template" insertion
mode, the user agent must handle the token as follows:
A character token
A comment token
A DOCTYPE token
Process the token using the rules for the "in body" insertion
mode.
A start tag whose tag name is one of: "base", "basefont", "bgsound",
"link", "meta", "noframes", "script", "style", "template", "title"
An end tag whose tag name is "template"
Process the token using the rules for the "in head" insertion
mode.
A start tag whose tag name is one of: "caption", "colgroup", "tbody",
"tfoot", "thead"
Pop the current template insertion mode off the stack of
template insertion modes.
Push "in table" onto the stack of template insertion modes so
that it is the new current template insertion mode.
Switch the insertion mode to "in table", and reprocess the
token.
A start tag whose tag name is "col"
Pop the current template insertion mode off the stack of
template insertion modes.
Push "in column group" onto the stack of template insertion
modes so that it is the new current template insertion mode.
Switch the insertion mode to "in column group", and reprocess
the token.
A start tag whose tag name is "tr"
Pop the current template insertion mode off the stack of
template insertion modes.
Push "in table body" onto the stack of template insertion
modes so that it is the new current template insertion mode.
Switch the insertion mode to "in table body", and reprocess
the token.
A start tag whose tag name is one of: "td", "th"
Pop the current template insertion mode off the stack of
template insertion modes.
Push "in row" onto the stack of template insertion modes so
that it is the new current template insertion mode.
Switch the insertion mode to "in row", and reprocess the
token.
Any other start tag
Pop the current template insertion mode off the stack of
template insertion modes.
Push "in body" onto the stack of template insertion modes so
that it is the new current template insertion mode.
Switch the insertion mode to "in body", and reprocess the
token.
Any other end tag
Parse error.
An end-of-file token
If there is no template element on the stack of open
elements, then stop parsing. (fragment case)
Otherwise, this is a parse error.
Pop elements from the stack of open elements until a template
element has been popped from the stack.
Clear the list of active formatting elements up to the last
marker.
Pop the current template insertion mode off the stack of
template insertion modes.
Reset the insertion mode appropriately.
Reprocess the token.
8.2.5.4.19. The "after body" insertion mode
When the user agent is to apply the rules for the "after body" insertion
mode, the user agent must handle the token as follows:
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
Process the token using the rules for the "in body" insertion
mode.
A comment token
Insert a comment as the last child of the first element in
the stack of open elements (the html element).
A DOCTYPE token
Parse error.
A start tag whose tag name is "html"
Process the token using the rules for the "in body" insertion
mode.
An end tag whose tag name is "html"
If the parser was originally created as part of the HTML
fragment parsing algorithm, this is a parse error; ignore the
token. (fragment case)
Otherwise, switch the insertion mode to "after after body".
An end-of-file token
Stop parsing.
Anything else
Parse error. Switch the insertion mode to "in body" and
reprocess the token.
8.2.5.4.20. The "in frameset" insertion mode
When the user agent is to apply the rules for the "in frameset" insertion
mode, the user agent must handle the token as follows:
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
Insert the character.
A comment token
Insert a comment.
A DOCTYPE token
Parse error.
A start tag whose tag name is "html"
Process the token using the rules for the "in body" insertion
mode.
A start tag whose tag name is "frameset"
Insert an HTML element for the token.
An end tag whose tag name is "frameset"
If the current node is the root html element, then this is a
parse error; ignore the token. (fragment case)
Otherwise, pop the current node from the stack of open
elements.
If the parser was not originally created as part of the HTML
fragment parsing algorithm (fragment case), and the current
node is no longer a frameset element, then switch the
insertion mode to "after frameset".
A start tag whose tag name is "frame"
Insert an HTML element for the token. Immediately pop the
current node off the stack of open elements.
Acknowledge the token’s *self-closing flag*, if it is set.
A start tag whose tag name is "noframes"
Process the token using the rules for the "in head" insertion
mode.
An end-of-file token
If the current node is not the root html element, then this
is a parse error.
The current node can only be the root html element in the
fragment case.
Stop parsing.
Anything else
Parse error.
8.2.5.4.21. The "after frameset" insertion mode
When the user agent is to apply the rules for the "after frameset"
insertion mode, the user agent must handle the token as follows:
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
Insert the character.
A comment token
Insert a comment.
A DOCTYPE token
Parse error.
A start tag whose tag name is "html"
Process the token using the rules for the "in body" insertion
mode.
An end tag whose tag name is "html"
Switch the insertion mode to "after after frameset".
A start tag whose tag name is "noframes"
Process the token using the rules for the "in head" insertion
mode.
An end-of-file token
Stop parsing.
Anything else
Parse error.
8.2.5.4.22. The "after after body" insertion mode
When the user agent is to apply the rules for the "after after body"
insertion mode, the user agent must handle the token as follows:
A comment token
Insert a comment as the last child of the Document object.
A DOCTYPE token
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
A start tag whose tag name is "html"
Process the token using the rules for the "in body" insertion
mode.
An end-of-file token
Stop parsing.
Anything else
Parse error. Switch the insertion mode to "in body" and
reprocess the token.
8.2.5.4.23. The "after after frameset" insertion mode
When the user agent is to apply the rules for the "after after frameset"
insertion mode, the user agent must handle the token as follows:
A comment token
Insert a comment as the last child of the Document object.
A DOCTYPE token
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
A start tag whose tag name is "html"
Process the token using the rules for the "in body" insertion
mode.
An end-of-file token
Stop parsing.
A start tag whose tag name is "noframes"
Process the token using the rules for the "in head" insertion
mode.
Anything else
Parse error.
8.2.5.5. The rules for parsing tokens in foreign content
When the user agent is to apply the rules for parsing tokens in foreign
content, the user agent must handle the token as follows:
A character token that is U+0000 NULL
Parse error. Insert a U+FFFD REPLACEMENT CHARACTER character.
A character token that is one of U+0009 CHARACTER TABULATION, U+000A
LINE FEED (LF), U+000C FORM FEED (FF), U+000D CARRIAGE RETURN (CR),
or U+0020 SPACE
Insert the token’s character.
Any other character token
Insert the token’s character.
Set the frameset-ok flag to "not ok".
A comment token
Insert a comment.
A DOCTYPE token
Parse error.
A start tag whose tag name is one of: "b", "big", "blockquote",
"body", "br", "center", "code", "dd", "div", "dl", "dt", "em",
"embed", "h1", "h2", "h3", "h4", "h5", "h6", "head", "hr", "i",
"img", "li", "listing", "meta", "nobr", "ol", "p", "pre", "ruby",
"s", "small", "span", "strong", "strike", "sub", "sup", "table",
"tt", "u", "ul", "var"
A start tag whose tag name is "font", if the token has any attributes
named "color", "face", or "size"
Parse error.
If the parser was originally created for the HTML fragment
parsing algorithm, then act as described in the "any other
start tag" entry below. (fragment case)
Otherwise:
Pop an element from the stack of open elements, and then keep
popping more elements from the stack of open elements until
the current node is a MathML text integration point, an HTML
integration point, or an element in the HTML namespace.
Then, reprocess the token.
Any other start tag
If the adjusted current node is an element in the MathML
namespace, adjust MathML attributes for the token. (This
fixes the case of MathML attributes that are not all
lowercase.)
If the adjusted current node is an element in the SVG
namespace, and the token’s tag name is one of the ones in the
first column of the following table, change the tag name to
the name given in the corresponding cell in the second
column. (This fixes the case of SVG elements that are not all
lowercase.)
Tag name Element name
altglyph altGlyph
altglyphdef altGlyphDef
altglyphitem altGlyphItem
animatecolor animateColor
animatemotion animateMotion
animatetransform animateTransform
clippath clipPath
feblend feBlend
fecolormatrix feColorMatrix
fecomponenttransfer feComponentTransfer
fecomposite feComposite
feconvolvematrix feConvolveMatrix
fediffuselighting feDiffuseLighting
fedisplacementmap feDisplacementMap
fedistantlight feDistantLight
fedropshadow feDropShadow
feflood feFlood
fefunca feFuncA
fefuncb feFuncB
fefuncg feFuncG
fefuncr feFuncR
fegaussianblur feGaussianBlur
feimage feImage
femerge feMerge
femergenode feMergeNode
femorphology feMorphology
feoffset feOffset
fepointlight fePointLight
fespecularlighting feSpecularLighting
fespotlight feSpotLight
fetile feTile
feturbulence feTurbulence
foreignobject foreignObject
glyphref glyphRef
lineargradient linearGradient
radialgradient radialGradient
textpath textPath
If the adjusted current node is an element in the SVG
namespace, adjust SVG attributes for the token. (This fixes
the case of SVG attributes that are not all lowercase.)
Adjust foreign attributes for the token. (This fixes the use
of namespaced attributes, in particular XLink in SVG.)
Insert a foreign element for the token, in the same namespace
as the adjusted current node.
If the token has its self-closing flag set, then run the
appropriate steps from the following list:
If the token’s tag name is "script", and the new current
node is in the SVG namespace
Acknowledge the token’s *self-closing flag*, and
then act as described in the steps for a
"script" end tag below.
Otherwise
Pop the current node off the stack of open
elements and acknowledge the token’s
*self-closing flag*.
An end tag whose tag name is "script", if the current node is an SVG
script element
Pop the current node off the stack of open elements.
Let the old insertion point have the same value as the
current insertion point. Let the insertion point be just
before the next input character.
Increment the parser’s script nesting level by one. Set the
parser pause flag to true.
Process the SVG script element according to the SVG rules, if
the user agent supports SVG. [SVG11]
Even if this causes new characters to be inserted into the
tokenizer, the parser will not be executed reentrantly, since
the parser pause flag is true.
Decrement the parser’s script nesting level by one. If the
parser’s script nesting level is zero, then set the parser
pause flag to false.
Let the insertion point have the value of the old insertion
point. (In other words, restore the insertion point to its
previous value. This value might be the "undefined" value.)
Any other end tag
Run these steps:
1. Initialize node to be the current node (the bottommost
node of the stack).
2. If node’s tag name, converted to ASCII lowercase, is not
the same as the tag name of the token, then this is a
parse error.
3. Loop: If node is the topmost element in the stack of
open elements, abort these steps. (fragment case)
4. If node’s tag name, converted to ASCII lowercase, is the
same as the tag name of the token, pop elements from the
stack of open elements until node has been popped from
the stack, and then abort these steps.
5. Set node to the previous entry in the stack of open
elements.
6. If node is not an element in the HTML namespace, return
to the step labeled Loop.
7. Otherwise, process the token according to the rules
given in the section corresponding to the current
insertion mode in HTML content.
8.2.6. The end
Once the user agent stops parsing the document, the user agent must run
the following steps:
1. Set the current document readiness to "interactive" and the insertion
point to undefined.
2. Pop all the nodes off the stack of open elements.
3. If the list of scripts that will execute when the document has
finished parsing is not empty, run these substeps:
1. Spin the event loop until the first script in the list of
scripts that will execute when the document has finished parsing
has its "ready to be parser-executed" flag set and the parser’s
Document has no style sheet that is blocking scripts.
2. Execute the first script in the list of scripts that will
execute when the document has finished parsing.
3. Remove the first script element from the list of scripts that
will execute when the document has finished parsing (i.e., shift
out the first entry in the list).
4. If the list of scripts that will execute when the document has
finished parsing is still not empty, repeat these substeps again
from substep 1.
4. Queue a task to run the following substeps:
1. fire an event named DOMContentLoaded at the Document object,
with its bubbles attribute initialized to true.
2. Enable the client message queue of the ServiceWorkerContainer
object whose associated service worker client is the Document
object’s relevant settings object.
5. Spin the event loop until the set of scripts that will execute as
soon as possible and the list of scripts that will execute in order
as soon as possible are empty.
6. Spin the event loop until there is nothing that delays the load event
in the Document.
7. Queue a task to run the following substeps:
1. Set the current document readiness to "complete".
2. Load event: If the Document has a browsing context, then fire an
event named load at the Document object’s Window object, with
legacy target override flag set.
8. If the Document has a browsing context, then queue a task to run the
following substeps:
1. If the Document's page showing flag is true, then abort this
task (i.e., don’t fire the event below).
2. Set the Document's page showing flag to true.
3. Fire an event named pageshow at the Document object’s Window
object using PageTransitionEvent, with the persisted attribute
initialized to false, and legacy target override flag set.
9. If the Document's print when loaded flag is set, then run the
printing steps.
10. The Document is now ready for post-load tasks.
11. Queue a task to mark the Document as completely loaded.
When the user agent is to abort a parser, it must run the following steps:
1. Throw away any pending content in the input stream, and discard any
future content that would have been added to it.
2. Set the current document readiness to "interactive".
3. Pop all the nodes off the stack of open elements.
4. Set the current document readiness to "complete".
Except where otherwise specified, the task source for the tasks mentioned
in this section is the DOM manipulation task source.
8.2.7. Coercing an HTML DOM into an infoset
When an application uses an HTML parser in conjunction with an XML
pipeline, it is possible that the constructed DOM is not compatible with
the XML tool chain in certain subtle ways. For example, an XML toolchain
might not be able to represent attributes with the name xmlns, since they
conflict with the Namespaces in XML syntax. There is also some data that
the HTML parser generates that isn’t included in the DOM itself. This
section specifies some rules for handling these issues.
If the XML API being used doesn’t support DOCTYPEs, the tool may drop
DOCTYPEs altogether.
If the XML API doesn’t support attributes in no namespace that are named
"xmlns", attributes whose names start with "xmlns:", or attributes in the
XMLNS namespace, then the tool may drop such attributes.
The tool may annotate the output with any namespace declarations required
for proper operation.
If the XML API being used restricts the allowable characters in the local
names of elements and attributes, then the tool may map all element and
attribute local names that the API wouldn’t support to a set of names that
are allowed, by replacing any character that isn’t supported with the
uppercase letter U and the six digits of the character’s Unicode code
point when expressed in hexadecimal, using digits 0-9 and capital letters
A-F as the symbols, in increasing numeric order.
For example, the element name foo<bar, which can be output by the HTML
parser, though it is neither a legal HTML element name nor a well-formed
XML element name, would be converted into fooU00003Cbar, which is a
well-formed XML element name (though it’s still not legal in HTML by any
means).
As another example, consider the attribute xlink:href. Used on a MathML
element, it becomes, after being adjusted, an attribute with a prefix
"xlink" and a local name "href". However, used on an HTML element, it
becomes an attribute with no prefix and the local name "xlink:href", which
is not a valid NCName, and thus might not be accepted by an XML API. It
could thus get converted, becoming "xlinkU00003Ahref".
The resulting names from this conversion conveniently can’t clash with any
attribute generated by the HTML parser, since those are all either
lowercase or those listed in the adjust foreign attributes algorithm’s
table.
If the XML API restricts comments from having two consecutive U+002D
HYPHEN-MINUS characters (--), the tool may insert a single U+0020 SPACE
character between any such offending characters.
If the XML API restricts comments from ending in a U+002D HYPHEN-MINUS
character (-), the tool may insert a single U+0020 SPACE character at the
end of such comments.
If the XML API restricts allowed characters in character data, attribute
values, or comments, the tool may replace any U+000C FORM FEED (FF)
character with a U+0020 SPACE character, and any other literal non-XML
character with a U+FFFD REPLACEMENT CHARACTER.
If the tool has no way to convey out-of-band information, then the tool
may drop the following information:
* Whether the document is set to no-quirks mode, limited-quirks mode,
or quirks mode
* The association between form controls and forms that aren’t their
nearest form element ancestor (use of the form element pointer in the
parser)
* The template contents of any template elements.
The mutations allowed by this section apply after the HTML parser's rules
have been applied. For example, a <a::> start tag will be closed by a
</a::> end tag, and never by a </aU00003AU00003A> end tag, even if
the user agent is using the rules above to then generate an actual element
in the DOM with the name aU00003AU00003A for that start tag.
8.2.8. An introduction to error handling and strange cases in the parser
This section is non-normative.
This section examines some erroneous markup and discusses how the HTML
parser handles these cases.
8.2.8.1. Misnested tags: <b><i></b></i>
This section is non-normative.
The most-often discussed example of erroneous markup is as follows:
<p>1<b>2<i>3</b>4</i>5</p>
The parsing of this markup is straightforward up to the "3". At this
point, the DOM looks like this:
* html
* head
* body
* p
* #text: 1
* b
* #text: 2
* i
* #text: 3
Here, the stack of open elements has five elements on it: html, body, p,
b, and i. The list of active formatting elements just has two: b and i.
The insertion mode is "in body".
Upon receiving the end tag token with the tag name "b", the "adoption
agency algorithm" is invoked. This is a simple case, in that the
formatting element is the b element, and there is no furthest block. Thus,
the stack of open elements ends up with just three elements: html, body,
and p, while the list of active formatting elements has just one: i. The
DOM tree is unmodified at this point.
The next token is a character ("4"), triggers the reconstruction of the
active formatting elements, in this case just the i element. A new i
element is thus created for the "4" Text node. After the end tag token for
the "i" is also received, and the "5" Text node is inserted, the DOM looks
as follows:
* html
* head
* body
* p
* #text: 1
* b
* #text: 2
* i
* #text: 3
* i
* #text: 4
* #text: 5
8.2.8.2. Misnested tags: <b><p></b></p>
This section is non-normative.
A case similar to the previous one is the following:
<b>1<p>2</b>3</p>
Up to the "2" the parsing here is straightforward:
* html
* head
* body
* b
* #text: 1
* p
* #text: 2
The interesting part is when the end tag token with the tag name "b" is
parsed.
Before that token is seen, the stack of open elements has four elements on
it: html, body, b, and p. The list of active formatting elements just has
the one: b. The insertion mode is "in body".
Upon receiving the end tag token with the tag name "b", the "adoption
agency algorithm" is invoked, as in the previous example. However, in this
case, there is a furthest block, namely the p element. Thus, this time the
adoption agency algorithm isn’t skipped over.
The common ancestor is the body element. A conceptual "bookmark" marks the
position of the b in the list of active formatting elements, but since
that list has only one element in it, the bookmark won’t have much effect.
As the algorithm progresses, node ends up set to the formatting element
(b), and last node ends up set to the furthest block (p).
The last node gets appended (moved) to the common ancestor, so that the
DOM looks like:
* html
* head
* body
* b
* #text: 1
* p
* #text: 2
A new b element is created, and the children of the p element are moved to
it:
* html
* head
* body
* b
* #text: 1
* p
* b
* #text: 2
Finally, the new b element is appended to the p element, so that the DOM
looks like:
* html
* head
* body
* b
* #text: 1
* p
* b
* #text: 2
The b element is removed from the list of active formatting elements and
the stack of open elements, so that when the "3" is parsed, it is appended
to the p element:
* html
* head
* body
* b
* #text: 1
* p
* b
* #text: 2
* #text: 3
8.2.8.3. Unexpected markup in tables
This section is non-normative.
Error handling in tables is, for historical reasons, especially strange.
For example, consider the following markup:
<table><b><tr><td>aaa</td></tr>bbb</table>ccc
The highlighted b element start tag is not allowed directly inside a table
like that, and the parser handles this case by placing the element before
the table. (This is called foster parenting.) This can be seen by
examining the DOM tree as it stands just after the table element’s start
tag has been seen:
* html
* head
* body
* table
...and then immediately after the b element start tag has been seen:
* html
* head
* body
* b
* table
At this point, the stack of open elements has on it the elements html,
body, table, and b (in that order, despite the resulting DOM tree); the
list of active formatting elements just has the b element in it; and the
insertion mode is "in table".
The tr start tag causes the b element to be popped off the stack and a
tbody start tag to be implied; the tbody and tr elements are then handled
in a rather straight-forward manner, taking the parser through the "in
table body" and "in row" insertion modes, after which the DOM looks as
follows:
* html
* head
* body
* b
* table
* tbody
* tr
Here, the stack of open elements has on it the elements html, body, table,
tbody, and tr; the list of active formatting elements still has the b
element in it; and the insertion mode is "in row".
The td element start tag token, after putting a td element on the tree,
puts a marker on the list of active formatting elements (it also switches
to the "in cell" insertion mode).
* html
* head
* body
* b
* table
* tbody
* tr
* td
The marker means that when the "aaa" character tokens are seen, no b
element is created to hold the resulting Text node:
* html
* head
* body
* b
* table
* tbody
* tr
* td
* #text: aaa
The end tags are handled in a straight-forward manner; after handling
them, the stack of open elements has on it the elements html, body, table,
and tbody; the list of active formatting elements still has the b element
in it (the marker having been removed by the "td" end tag token); and the
insertion mode is "in table body".
Thus it is that the "bbb" character tokens are found. These trigger the
"in table text" insertion mode to be used (with the original insertion
mode set to "in table body"). The character tokens are collected, and when
the next token (the table element end tag) is seen, they are processed as
a group. Since they are not all spaces, they are handled as per the
"anything else" rules in the "in table" insertion mode, which defer to the
"in body" insertion mode but with foster parenting.
When the active formatting elements are reconstructed, a b element is
created and foster parented, and then the "bbb" Text node is appended to
it:
* html
* head
* body
* b
* b
* #text: bbb
* table
* tbody
* tr
* td
* #text: aaa
The stack of open elements has on it the elements html, body, table,
tbody, and the new b (again, note that this doesn’t match the resulting
tree!); the list of active formatting elements has the new b element in
it; and the insertion mode is still "in table body".
Had the character tokens been only space characters instead of "bbb", then
those space characters would just be appended to the tbody element.
Finally, the table is closed by a "table" end tag. This pops all the nodes
from the stack of open elements up to and including the table element, but
it doesn’t affect the list of active formatting elements, so the "ccc"
character tokens after the table result in yet another b element being
created, this time after the table:
* html
* head
* body
* b
* b
* #text: bbb
* table
* tbody
* tr
* td
* #text: aaa
* b
* #text: ccc
8.2.8.4. Scripts that modify the page as it is being parsed
This section is non-normative.
Consider the following markup, which for this example we will assume is
the document with URL https://example.com/inner, being rendered as the
content of an iframe in another document with the URL
https://example.com/outer:
<div id=a>
<script>
var div = document.getElementById("a");
parent.document.body.appendChild(div);
</script>
<script>
alert(document.URL);
</script>
</div>
<script>
alert(document.URL);
</script>
Up to the first "script" end tag, before the script is parsed, the result
is relatively straightforward:
* html
* head
* body
* div id="a"
* #text:
* script
* #text: var div = document.getElementById("a"); ⏎
parent.document.body.appendChild(div);
After the script is parsed, though, the div element and its child script
element are gone:
* html
* head
* body
They are, at this point, in the Document of the aforementioned outer
browsing context. However, the stack of open elements *still contains the
div element*.
Thus, when the second script element is parsed, it is inserted *into the
outer Document object*.
Those parsed into different Documents than the one the parser was created
for do not execute, so the first alert does not show.
Once the div element’s end tag is parsed, the div element is popped off
the stack, and so the next script element is in the inner Document:
* html
* head
* body
* script
* #text: alert(document.URL);
This script does execute, resulting in an alert that says
"https://example.com/inner".
8.2.8.5. The execution of scripts that are moving across multiple
documents
This section is non-normative.
Elaborating on the example in the previous section, consider the case
where the second script element is an external script (i.e., one with a
src attribute). Since the element was not in the parser’s Document when it
was created, that external script is not even downloaded.
In a case where a script element with a src attribute is parsed normally
into its parser’s Document, but while the external script is being
downloaded, the element is moved to another document, the script continues
to download, but does not execute.
In general, moving script elements between Documents is considered a bad
practice.
8.2.8.6. Unclosed formatting elements
This section is non-normative.
The following markup shows how nested formatting elements (such as b) get
collected and continue to be applied even as the elements they are
contained in are closed, but that excessive duplicates are thrown away.
<!DOCTYPE html>
<p><b class=x><b class=x><b><b class=x><b class=x><b>X
<p>X
<p><b><b class=x><b>X
<p></b></b></b></b></b></b>X
The resulting DOM tree is as follows:
* DOCTYPE: html
* html
* head
* body
* p
* b class="x"
* b class="x"
* b
* b class="x"
* b class="x"
* b
* #text: X⏎
* p
* b class="x"
* b
* b class="x"
* b class="x"
* b
* #text: X⏎
* p
* b class="x"
* b
* b class="x"
* b class="x"
* b
* b
* b class="x"
* b
* #text: X⏎
* p
* #text: X⏎
Note how the second p element in the markup has no explicit b elements,
but in the resulting DOM, up to three of each kind of formatting element
(in this case three b elements with the class attribute, and two unadorned
b elements) get reconstructed before the element’s "X".
Also note how this means that in the final paragraph only six b end tags
are needed to completely clear the list of active formatting elements,
even though nine b start tags have been seen up to this point.
8.3. Serializing HTML fragments
The following steps form the HTML fragment serialization algorithm. The
algorithm takes as input a DOM Element, Document, or DocumentFragment
referred to as the node, and returns a string.
This algorithm serializes the children of the node being serialized, not
the node itself.
1. Let s be a string, and initialize it to the empty string.
2. If the node is a template element, then let the node instead be the
template element’s template contents (a DocumentFragment node).
3. For each child node of the node, in tree order, run the following
steps:
1. Let current node be the child node being processed.
2. Append the appropriate string from the following list to s:
If current node is an Element
If current node is an element in the HTML
namespace, the MathML namespace, or the SVG
namespace, then let tagname be current node’s local
name. Otherwise, let tagname be current node’s
qualified name.
Append a U+003C LESS-THAN SIGN character (<),
followed by tagname.
For HTML elements created by the HTML parser or
createElement(), tagname will be lowercase.
For each attribute that the element has, append a
U+0020 SPACE character, the attribute’s serialized
name as described below, a U+003D EQUALS SIGN
character (=), a U+0022 QUOTATION MARK character
("), the attribute’s value, escaped as described
below in attribute mode, and a second U+0022
QUOTATION MARK character (").
An attribute’s serialized name for the purposes of
the previous paragraph must be determined as
follows:
If the attribute has no namespace
The attribute’s serialized name is the
attribute’s local name.
For attributes on HTML elements set by
the HTML parser or by
Element.setAttribute(), the local name
will be lowercase.
If the attribute is in the XML namespace
The attribute’s serialized name is the
string "xml:" followed by the
attribute’s local name.
If the attribute is in the XMLNS namespace and
the attribute’s local name is xmlns
The attribute’s serialized name is the
string "xmlns".
If the attribute is in the XMLNS namespace and
the attribute’s local name is not xmlns
The attribute’s serialized name is the
string "xmlns:" followed by the
attribute’s local name.
If the attribute is in the XLink namespace
The attribute’s serialized name is the
string "xlink:" followed by the
attribute’s local name.
If the attribute is in some other namespace
The attribute’s serialized name is the
attribute’s qualified name.
While the exact order of attributes is UA-defined,
and may depend on factors such as the order that
the attributes were given in the original markup,
the sort order must be stable, such that
consecutive invocations of this algorithm serialize
an element’s attributes in the same order.
Append a U+003E GREATER-THAN SIGN character (>).
If current node is an area, base, basefont,
bgsound, br, col, embed, frame, hr, img, input,
link, meta, param, source, track or wbr element,
then continue on to the next child node at this
point.
Append the value of running the HTML fragment
serialization algorithm on the current node element
(thus recursing into this algorithm for that
element), followed by a U+003C LESS-THAN SIGN
character (<), a U+002F SOLIDUS character (/),
tagname again, and finally a U+003E GREATER-THAN
SIGN character (>).
If current node is a Text node
If the parent of current node is a style, script,
xmp, iframe, noembed, noframes, or plaintext
element, or if the parent of current node is a
noscript element and scripting is enabled for the
node, then append the value of current node’s data
IDL attribute literally.
Otherwise, append the value of current node’s data
IDL attribute, escaped as described below.
If current node is a Comment
Append the literal string "<!--" (U+003C
LESS-THAN SIGN, U+0021 EXCLAMATION MARK, U+002D
HYPHEN-MINUS, U+002D HYPHEN-MINUS), followed by the
value of current node’s data IDL attribute,
followed by the literal string "-->" (U+002D
HYPHEN-MINUS, U+002D HYPHEN-MINUS, U+003E
GREATER-THAN SIGN).
If current node is a ProcessingInstruction
Append the literal string "<?" (U+003C LESS-THAN
SIGN, U+003F QUESTION MARK), followed by the value
of current node’s target IDL attribute, followed by
a single U+0020 SPACE character, followed by the
value of current node’s data IDL attribute,
followed by a single U+003E GREATER-THAN SIGN
character (>).
If current node is a DocumentType
Append the literal string "<!DOCTYPE" (U+003C
LESS-THAN SIGN, U+0021 EXCLAMATION MARK, U+0044
LATIN CAPITAL LETTER D, U+004F LATIN CAPITAL LETTER
O, U+0043 LATIN CAPITAL LETTER C, U+0054 LATIN
CAPITAL LETTER T, U+0059 LATIN CAPITAL LETTER Y,
U+0050 LATIN CAPITAL LETTER P, U+0045 LATIN CAPITAL
LETTER E), followed by a space (U+0020 SPACE),
followed by the value of current node’s name IDL
attribute, followed by the literal string ">"
(U+003E GREATER-THAN SIGN).
4. The result of the algorithm is the string s.
It is possible that the output of this algorithm, if parsed with an HTML
parser, will not return the original tree structure. Tree structures that
do not roundtrip a serialize and reparse step can also be produced by the
HTML parser itself, although such cases are typically non-conforming.
For instance, if a textarea element to which a Comment node has been
appended is serialized and the output is then reparsed, the comment will
end up being displayed in the text field. Similarly, if, as a result of
DOM manipulation, an element contains a comment that contains the literal
string "-->", then when the result of serializing the element is
parsed, the comment will be truncated at that point and the rest of the
comment will be interpreted as markup. More examples would be making a
script element contain a Text node with the text string "</script>", or
having a p element that contains a ul element (as the ul element’s start
tag would imply the end tag for the p).
This can enable cross-site scripting attacks. An example of this would be
a page that lets the user enter some font family names that are then
inserted into a CSS style block via the DOM and which then uses the
innerHTML IDL attribute to get the HTML serialization of that style
element: if the user enters "</style><script>attack</script>" as
a font family name, innerHTML will return markup that, if parsed in a
different context, would contain a script node, even though no script node
existed in the original DOM.
For example, consider the following markup:
<form id="outer"><div></form><form id="inner"><input>
This will be parsed into:
* html
* head
* body
* form id="outer"
* div
* form id="inner"
* input
The input element will be associated with the inner form element. 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>
* html
* head
* body
* form id="outer"
* div
* input
As another example, consider the following markup:
<a><table><a>
This will be parsed into:
* html
* head
* body
* a
* a
* table
That is, the a elements are nested, because the second a element is foster
parented. After a serialize-reparse roundtrip, the a elements and the
table element would all be siblings, because the second <a> start tag
implicitly closes the first a element.
<html><head></head><body><a><a></a><table></table></a></body></html>
* html
* head
* body
* a
* a
* table
For historical reasons, this algorithm does not round-trip an initial
U+000A LINE FEED (LF) character in pre, textarea, or listing elements,
even though (in the first two cases) the markup being round-tripped can be
conforming. The HTML parser will drop such a character during parsing, but
this algorithm does not serialize an extra U+000A LINE FEED (LF)
character.
For example, consider the following markup:
<pre>
Hello.</pre>
When this document is first parsed, the pre element’s child text content
starts with a single newline character. After a serialize-reparse
roundtrip, the pre element’s child text content is simply "Hello.".
Escaping a string (for the purposes of the algorithm above) consists of
running the following steps:
1. Replace any occurrence of the "&" character by the string
"&amp;".
2. Replace any occurrences of the U+00A0 NO-BREAK SPACE character by the
string "&nbsp;".
3. If the algorithm was invoked in the attribute mode, replace any
occurrences of the """ character by the string "&quot;".
4. If the algorithm was not invoked in the attribute mode, replace any
occurrences of the "<" character by the string "&lt;", and any
occurrences of the ">" character by the string "&gt;".
8.4. Parsing HTML fragments
The following steps form the HTML fragment parsing algorithm. The
algorithm takes as input an Element node, referred to as the context
element, which gives the context for the parser, as well as input, a
string to parse, and returns a list of zero or more nodes.
Parts marked fragment case in algorithms in the parser section are parts
that only occur if the parser was created for the purposes of this
algorithm. The algorithms have been annotated with such markings for
informational purposes only; such markings have no normative weight. If it
is possible for a condition described as a fragment case to occur even
when the parser wasn’t created for the purposes of handling this
algorithm, then that is an error in the specification.
1. Create a new Document node, and mark it as being an HTML document.
2. If the node document of the context element is in quirks mode, then
let the Document be in quirks mode. Otherwise, the node document of
the context element is in limited-quirks mode, then let the Document
be in limited-quirks mode. Otherwise, leave the Document in no-quirks
mode.
3. Create a new HTML parser, and associate it with the just created
Document node.
4. Set the state of the HTML parser's tokenization stage as follows,
switching on the context element:
title
textarea
Switch the tokenizer to the RCDATA state.
style
xmp
iframe
noembed
noframes
Switch the tokenizer to the RAWTEXT state.
script
Switch the tokenizer to the script data state.
noscript
If the scripting flag is enabled, switch the tokenizer
to the RAWTEXT state. Otherwise, leave the tokenizer in
the data state.
plaintext
Switch the tokenizer to the §8.2.4.5 PLAINTEXT state.
Any other element
Leave the tokenizer in the data state.
For performance reasons, an implementation that does not report
errors and that uses the actual state machine described in this
specification directly could use the PLAINTEXT state instead of the
RAWTEXT and script data states where those are mentioned in the list
above. Except for rules regarding parse errors, they are equivalent,
since there is no appropriate end tag token in the fragment case, yet
they involve far fewer state transitions.
5. Let root be a new html element with no attributes.
6. Append the element root to the Document node created above.
7. Set up the parser’s stack of open elements so that it contains just
the single element root.
8. If the context element is a template element, push "in template" onto
the stack of template insertion modes so that it is the new current
template insertion mode.
9. Create a start tag token whose name is the local name of context and
whose attributes are the attributes of context.
Let this start tag token be the start tag token of the context node,
e.g., for the purposes of determining if it is an HTML integration
point.
10. Reset the parser’s insertion mode appropriately.
The parser will reference the context element as part of that
algorithm.
11. 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.)
12. Place the input into the input stream for the HTML parser just
created. The encoding confidence is irrelevant.
13. Start the parser and let it run until it has consumed all the
characters just inserted into the input stream.
14. Return the child nodes of root, in tree order.
8.5. Named character references
This table lists the character reference names that are supported by HTML,
and the code points to which they refer. It is referenced by the previous
sections.
Name Character(s) Glyph
Aacute; U+000C1 Á
Aacute U+000C1 Á
aacute; U+000E1 á
aacute U+000E1 á
Abreve; U+00102 Ă
abreve; U+00103 ă
ac; U+0223E ∾
acd; U+0223F ∿
acE; U+0223E U+00333 ∾̳
Acirc; U+000C2 Â
Acirc U+000C2 Â
acirc; U+000E2 â
acirc U+000E2 â
acute; U+000B4 ´
acute U+000B4 ´
Acy; U+00410 А
acy; U+00430 а
AElig; U+000C6 Æ
AElig U+000C6 Æ
aelig; U+000E6 æ
aelig U+000E6 æ
af; U+02061
Afr; U+1D504 𝔄
afr; U+1D51E 𝔞
Agrave; U+000C0 À
Agrave U+000C0 À
agrave; U+000E0 à
agrave U+000E0 à
alefsym; U+02135 ℵ
aleph; U+02135 ℵ
Alpha; U+00391 Α
alpha; U+003B1 α
Amacr; U+00100 Ā
amacr; U+00101 ā
amalg; U+02A3F ⨿
AMP; U+00026 &
AMP U+00026 &
amp; U+00026 &
amp U+00026 &
And; U+02A53 ⩓
and; U+02227 ∧
andand; U+02A55 ⩕
andd; U+02A5C ⩜
andslope; U+02A58 ⩘
andv; U+02A5A ⩚
ang; U+02220 ∠
ange; U+029A4 ⦤
angle; U+02220 ∠
angmsd; U+02221 ∡
angmsdaa; U+029A8 ⦨
angmsdab; U+029A9 ⦩
angmsdac; U+029AA ⦪
angmsdad; U+029AB ⦫
angmsdae; U+029AC ⦬
angmsdaf; U+029AD ⦭
angmsdag; U+029AE ⦮
angmsdah; U+029AF ⦯
angrt; U+0221F ∟
angrtvb; U+022BE ⊾
angrtvbd; U+0299D ⦝
angsph; U+02222 ∢
angst; U+000C5 Å
angzarr; U+0237C ⍼
Aogon; U+00104 Ą
aogon; U+00105 ą
Aopf; U+1D538 𝔸
aopf; U+1D552 𝕒
ap; U+02248 ≈
apacir; U+02A6F ⩯
apE; U+02A70 ⩰
ape; U+0224A ≊
apid; U+0224B ≋
apos; U+00027 '
ApplyFunction; U+02061
approx; U+02248 ≈
approxeq; U+0224A ≊
Aring; U+000C5 Å
Aring U+000C5 Å
aring; U+000E5 å
aring U+000E5 å
Ascr; U+1D49C 𝒜
ascr; U+1D4B6 𝒶
Assign; U+02254 ≔
ast; U+0002A *
asymp; U+02248 ≈
asympeq; U+0224D ≍
Atilde; U+000C3 Ã
Atilde U+000C3 Ã
atilde; U+000E3 ã
atilde U+000E3 ã
Auml; U+000C4 Ä
Auml U+000C4 Ä
auml; U+000E4 ä
auml U+000E4 ä
awconint; U+02233 ∳
awint; U+02A11 ⨑
backcong; U+0224C ≌
backepsilon; U+003F6 ϶
backprime; U+02035 ‵
backsim; U+0223D ∽
backsimeq; U+022CD ⋍
Backslash; U+02216 ∖
Barv; U+02AE7 ⫧
barvee; U+022BD ⊽
Barwed; U+02306 ⌆
barwed; U+02305 ⌅
barwedge; U+02305 ⌅
bbrk; U+023B5 ⎵
bbrktbrk; U+023B6 ⎶
bcong; U+0224C ≌
Bcy; U+00411 Б
bcy; U+00431 б
bdquo; U+0201E „
becaus; U+02235 ∵
Because; U+02235 ∵
because; U+02235 ∵
bemptyv; U+029B0 ⦰
bepsi; U+003F6 ϶
bernou; U+0212C ℬ
Bernoullis; U+0212C ℬ
Beta; U+00392 Β
beta; U+003B2 β
beth; U+02136 ℶ
between; U+0226C ≬
Bfr; U+1D505 𝔅
bfr; U+1D51F 𝔟
bigcap; U+022C2 ⋂
bigcirc; U+025EF ◯
bigcup; U+022C3 ⋃
bigodot; U+02A00 ⨀
bigoplus; U+02A01 ⨁
bigotimes; U+02A02 ⨂
bigsqcup; U+02A06 ⨆
bigstar; U+02605 ★
bigtriangledown; U+025BD ▽
bigtriangleup; U+025B3 △
biguplus; U+02A04 ⨄
bigvee; U+022C1 ⋁
bigwedge; U+022C0 ⋀
bkarow; U+0290D ⤍
blacklozenge; U+029EB ⧫
blacksquare; U+025AA ▪
blacktriangle; U+025B4 ▴
blacktriangledown; U+025BE ▾
blacktriangleleft; U+025C2 ◂
blacktriangleright; U+025B8 ▸
blank; U+02423 ␣
blk12; U+02592 ▒
blk14; U+02591 ░
blk34; U+02593 ▓
block; U+02588 █
bne; U+0003D U+020E5 =⃥
bnequiv; U+02261 U+020E5 ≡⃥
bNot; U+02AED ⫭
bnot; U+02310 ⌐
Bopf; U+1D539 𝔹
bopf; U+1D553 𝕓
bot; U+022A5 ⊥
bottom; U+022A5 ⊥
bowtie; U+022C8 ⋈
boxbox; U+029C9 ⧉
boxDL; U+02557 ╗
boxDl; U+02556 ╖
boxdL; U+02555 ╕
boxdl; U+02510 ┐
boxDR; U+02554 ╔
boxDr; U+02553 ╓
boxdR; U+02552 ╒
boxdr; U+0250C ┌
boxH; U+02550 ═
boxh; U+02500 ─
boxHD; U+02566 ╦
boxHd; U+02564 ╤
boxhD; U+02565 ╥
boxhd; U+0252C ┬
boxHU; U+02569 ╩
boxHu; U+02567 ╧
boxhU; U+02568 ╨
boxhu; U+02534 ┴
boxminus; U+0229F ⊟
boxplus; U+0229E ⊞
boxtimes; U+022A0 ⊠
boxUL; U+0255D ╝
boxUl; U+0255C ╜
boxuL; U+0255B ╛
boxul; U+02518 ┘
boxUR; U+0255A ╚
boxUr; U+02559 ╙
boxuR; U+02558 ╘
boxur; U+02514 └
boxV; U+02551 ║
boxv; U+02502 │
boxVH; U+0256C ╬
boxVh; U+0256B ╫
boxvH; U+0256A ╪
boxvh; U+0253C ┼
boxVL; U+02563 ╣
boxVl; U+02562 ╢
boxvL; U+02561 ╡
boxvl; U+02524 ┤
boxVR; U+02560 ╠
boxVr; U+0255F ╟
boxvR; U+0255E ╞
boxvr; U+0251C ├
bprime; U+02035 ‵
Breve; U+002D8 ˘
breve; U+002D8 ˘
brvbar; U+000A6 ¦
brvbar U+000A6 ¦
Bscr; U+0212C ℬ
bscr; U+1D4B7 𝒷
bsemi; U+0204F ⁏
bsim; U+0223D ∽
bsime; U+022CD ⋍
bsol; U+0005C \
bsolb; U+029C5 ⧅
bsolhsub; U+027C8 ⟈
bull; U+02022 •
bullet; U+02022 •
bump; U+0224E ≎
bumpE; U+02AAE ⪮
bumpe; U+0224F ≏
Bumpeq; U+0224E ≎
bumpeq; U+0224F ≏
Cacute; U+00106 Ć
cacute; U+00107 ć
Cap; U+022D2 ⋒
cap; U+02229 ∩
capand; U+02A44 ⩄
capbrcup; U+02A49 ⩉
capcap; U+02A4B ⩋
capcup; U+02A47 ⩇
capdot; U+02A40 ⩀
CapitalDifferentialD; U+02145 ⅅ
caps; U+02229 U+0FE00 ∩︀
caret; U+02041 ⁁
caron; U+002C7 ˇ
Cayleys; U+0212D ℭ
ccaps; U+02A4D ⩍
Ccaron; U+0010C Č
ccaron; U+0010D č
Ccedil; U+000C7 Ç
Ccedil U+000C7 Ç
ccedil; U+000E7 ç
ccedil U+000E7 ç
Ccirc; U+00108 Ĉ
ccirc; U+00109 ĉ
Cconint; U+02230 ∰
ccups; U+02A4C ⩌
ccupssm; U+02A50 ⩐
Cdot; U+0010A Ċ
cdot; U+0010B ċ
cedil; U+000B8 ¸
cedil U+000B8 ¸
Cedilla; U+000B8 ¸
cemptyv; U+029B2 ⦲
cent; U+000A2 ¢
cent U+000A2 ¢
CenterDot; U+000B7 ·
centerdot; U+000B7 ·
Cfr; U+0212D ℭ
cfr; U+1D520 𝔠
CHcy; U+00427 Ч
chcy; U+00447 ч
check; U+02713 ✓
checkmark; U+02713 ✓
Chi; U+003A7 Χ
chi; U+003C7 χ
cir; U+025CB ○
circ; U+002C6 ˆ
circeq; U+02257 ≗
circlearrowleft; U+021BA ↺
circlearrowright; U+021BB ↻
circledast; U+0229B ⊛
circledcirc; U+0229A ⊚
circleddash; U+0229D ⊝
CircleDot; U+02299 ⊙
circledR; U+000AE ®
circledS; U+024C8 Ⓢ
CircleMinus; U+02296 ⊖
CirclePlus; U+02295 ⊕
CircleTimes; U+02297 ⊗
cirE; U+029C3 ⧃
cire; U+02257 ≗
cirfnint; U+02A10 ⨐
cirmid; U+02AEF ⫯
cirscir; U+029C2 ⧂
ClockwiseContourIntegral; U+02232 ∲
CloseCurlyDoubleQuote; U+0201D ”
CloseCurlyQuote; U+02019 ’
clubs; U+02663 ♣
clubsuit; U+02663 ♣
Colon; U+02237 ∷
colon; U+0003A :
Colone; U+02A74 ⩴
colone; U+02254 ≔
coloneq; U+02254 ≔
comma; U+0002C ,
commat; U+00040 @
comp; U+02201 ∁
compfn; U+02218 ∘
complement; U+02201 ∁
complexes; U+02102 ℂ
cong; U+02245 ≅
congdot; U+02A6D ⩭
Congruent; U+02261 ≡
Conint; U+0222F ∯
conint; U+0222E ∮
ContourIntegral; U+0222E ∮
Copf; U+02102 ℂ
copf; U+1D554 𝕔
coprod; U+02210 ∐
Coproduct; U+02210 ∐
COPY; U+000A9 ©
COPY U+000A9 ©
copy; U+000A9 ©
copy U+000A9 ©
copysr; U+02117 ℗
CounterClockwiseContourIntegral; U+02233 ∳
crarr; U+021B5 ↵
Cross; U+02A2F ⨯
cross; U+02717 ✗
Cscr; U+1D49E 𝒞
cscr; U+1D4B8 𝒸
csub; U+02ACF ⫏
csube; U+02AD1 ⫑
csup; U+02AD0 ⫐
csupe; U+02AD2 ⫒
ctdot; U+022EF ⋯
cudarrl; U+02938 ⤸
cudarrr; U+02935 ⤵
cuepr; U+022DE ⋞
cuesc; U+022DF ⋟
cularr; U+021B6 ↶
cularrp; U+0293D ⤽
Cup; U+022D3 ⋓
cup; U+0222A ∪
cupbrcap; U+02A48 ⩈
CupCap; U+0224D ≍
cupcap; U+02A46 ⩆
cupcup; U+02A4A ⩊
cupdot; U+0228D ⊍
cupor; U+02A45 ⩅
cups; U+0222A U+0FE00 ∪︀
curarr; U+021B7 ↷
curarrm; U+0293C ⤼
curlyeqprec; U+022DE ⋞
curlyeqsucc; U+022DF ⋟
curlyvee; U+022CE ⋎
curlywedge; U+022CF ⋏
curren; U+000A4 ¤
curren U+000A4 ¤
curvearrowleft; U+021B6 ↶
curvearrowright; U+021B7 ↷
cuvee; U+022CE ⋎
cuwed; U+022CF ⋏
cwconint; U+02232 ∲
cwint; U+02231 ∱
cylcty; U+0232D ⌭
Dagger; U+02021 ‡
dagger; U+02020 †
daleth; U+02138 ℸ
Darr; U+021A1 ↡
dArr; U+021D3 ⇓
darr; U+02193 ↓
dash; U+02010 ‐
Dashv; U+02AE4 ⫤
dashv; U+022A3 ⊣
dbkarow; U+0290F ⤏
dblac; U+002DD ˝
Dcaron; U+0010E Ď
dcaron; U+0010F ď
Dcy; U+00414 Д
dcy; U+00434 д
DD; U+02145 ⅅ
dd; U+02146 ⅆ
ddagger; U+02021 ‡
ddarr; U+021CA ⇊
DDotrahd; U+02911 ⤑
ddotseq; U+02A77 ⩷
deg; U+000B0 °
deg U+000B0 °
Del; U+02207 ∇
Delta; U+00394 Δ
delta; U+003B4 δ
demptyv; U+029B1 ⦱
dfisht; U+0297F ⥿
Dfr; U+1D507 𝔇
dfr; U+1D521 𝔡
dHar; U+02965 ⥥
dharl; U+021C3 ⇃
dharr; U+021C2 ⇂
DiacriticalAcute; U+000B4 ´
DiacriticalDot; U+002D9 ˙
DiacriticalDoubleAcute; U+002DD ˝
DiacriticalGrave; U+00060 `
DiacriticalTilde; U+002DC ˜
diam; U+022C4 ⋄
Diamond; U+022C4 ⋄
diamond; U+022C4 ⋄
diamondsuit; U+02666 ♦
diams; U+02666 ♦
die; U+000A8 ¨
DifferentialD; U+02146 ⅆ
digamma; U+003DD ϝ
disin; U+022F2 ⋲
div; U+000F7 ÷
divide; U+000F7 ÷
divide U+000F7 ÷
divideontimes; U+022C7 ⋇
divonx; U+022C7 ⋇
DJcy; U+00402 Ђ
djcy; U+00452 ђ
dlcorn; U+0231E ⌞
dlcrop; U+0230D ⌍
dollar; U+00024 $
Dopf; U+1D53B 𝔻
dopf; U+1D555 𝕕
Dot; U+000A8 ¨
dot; U+002D9 ˙
DotDot; U+020DC ◌⃜
doteq; U+02250 ≐
doteqdot; U+02251 ≑
DotEqual; U+02250 ≐
dotminus; U+02238 ∸
dotplus; U+02214 ∔
dotsquare; U+022A1 ⊡
doublebarwedge; U+02306 ⌆
DoubleContourIntegral; U+0222F ∯
DoubleDot; U+000A8 ¨
DoubleDownArrow; U+021D3 ⇓
DoubleLeftArrow; U+021D0 ⇐
DoubleLeftRightArrow; U+021D4 ⇔
DoubleLeftTee; U+02AE4 ⫤
DoubleLongLeftArrow; U+027F8 ⟸
DoubleLongLeftRightArrow; U+027FA ⟺
DoubleLongRightArrow; U+027F9 ⟹
DoubleRightArrow; U+021D2 ⇒
DoubleRightTee; U+022A8 ⊨
DoubleUpArrow; U+021D1 ⇑
DoubleUpDownArrow; U+021D5 ⇕
DoubleVerticalBar; U+02225 ∥
DownArrow; U+02193 ↓
Downarrow; U+021D3 ⇓
downarrow; U+02193 ↓
DownArrowBar; U+02913 ⤓
DownArrowUpArrow; U+021F5 ⇵
DownBreve; U+00311 ◌̑
downdownarrows; U+021CA ⇊
downharpoonleft; U+021C3 ⇃
downharpoonright; U+021C2 ⇂
DownLeftRightVector; U+02950 ⥐
DownLeftTeeVector; U+0295E ⥞
DownLeftVector; U+021BD ↽
DownLeftVectorBar; U+02956 ⥖
DownRightTeeVector; U+0295F ⥟
DownRightVector; U+021C1 ⇁
DownRightVectorBar; U+02957 ⥗
DownTee; U+022A4 ⊤
DownTeeArrow; U+021A7 ↧
drbkarow; U+02910 ⤐
drcorn; U+0231F ⌟
drcrop; U+0230C ⌌
Dscr; U+1D49F 𝒟
dscr; U+1D4B9 𝒹
DScy; U+00405 Ѕ
dscy; U+00455 ѕ
dsol; U+029F6 ⧶
Dstrok; U+00110 Đ
dstrok; U+00111 đ
dtdot; U+022F1 ⋱
dtri; U+025BF ▿
dtrif; U+025BE ▾
duarr; U+021F5 ⇵
duhar; U+0296F ⥯
dwangle; U+029A6 ⦦
DZcy; U+0040F Џ
dzcy; U+0045F џ
dzigrarr; U+027FF ⟿
Eacute; U+000C9 É
Eacute U+000C9 É
eacute; U+000E9 é
eacute U+000E9 é
easter; U+02A6E ⩮
Ecaron; U+0011A Ě
ecaron; U+0011B ě
ecir; U+02256 ≖
Ecirc; U+000CA Ê
Ecirc U+000CA Ê
ecirc; U+000EA ê
ecirc U+000EA ê
ecolon; U+02255 ≕
Ecy; U+0042D Э
ecy; U+0044D э
eDDot; U+02A77 ⩷
Edot; U+00116 Ė
eDot; U+02251 ≑
edot; U+00117 ė
ee; U+02147 ⅇ
efDot; U+02252 ≒
Efr; U+1D508 𝔈
efr; U+1D522 𝔢
eg; U+02A9A ⪚
Egrave; U+000C8 È
Egrave U+000C8 È
egrave; U+000E8 è
egrave U+000E8 è
egs; U+02A96 ⪖
egsdot; U+02A98 ⪘
el; U+02A99 ⪙
Element; U+02208 ∈
elinters; U+023E7 ⏧
ell; U+02113 ℓ
els; U+02A95 ⪕
elsdot; U+02A97 ⪗
Emacr; U+00112 Ē
emacr; U+00113 ē
empty; U+02205 ∅
emptyset; U+02205 ∅
EmptySmallSquare; U+025FB ◻
emptyv; U+02205 ∅
EmptyVerySmallSquare; U+025AB ▫
emsp; U+02003
emsp13; U+02004
emsp14; U+02005
ENG; U+0014A Ŋ
eng; U+0014B ŋ
ensp; U+02002
Eogon; U+00118 Ę
eogon; U+00119 ę
Eopf; U+1D53C 𝔼
eopf; U+1D556 𝕖
epar; U+022D5 ⋕
eparsl; U+029E3 ⧣
eplus; U+02A71 ⩱
epsi; U+003B5 ε
Epsilon; U+00395 Ε
epsilon; U+003B5 ε
epsiv; U+003F5 ϵ
eqcirc; U+02256 ≖
eqcolon; U+02255 ≕
eqsim; U+02242 ≂
eqslantgtr; U+02A96 ⪖
eqslantless; U+02A95 ⪕
Equal; U+02A75 ⩵
equals; U+0003D =
EqualTilde; U+02242 ≂
equest; U+0225F ≟
Equilibrium; U+021CC ⇌
equiv; U+02261 ≡
equivDD; U+02A78 ⩸
eqvparsl; U+029E5 ⧥
erarr; U+02971 ⥱
erDot; U+02253 ≓
Escr; U+02130 ℰ
escr; U+0212F ℯ
esdot; U+02250 ≐
Esim; U+02A73 ⩳
esim; U+02242 ≂
Eta; U+00397 Η
eta; U+003B7 η
ETH; U+000D0 Ð
ETH U+000D0 Ð
eth; U+000F0 ð
eth U+000F0 ð
Euml; U+000CB Ë
Euml U+000CB Ë
euml; U+000EB ë
euml U+000EB ë
euro; U+020AC €
excl; U+00021 !
exist; U+02203 ∃
Exists; U+02203 ∃
expectation; U+02130 ℰ
ExponentialE; U+02147 ⅇ
exponentiale; U+02147 ⅇ
fallingdotseq; U+02252 ≒
Fcy; U+00424 Ф
fcy; U+00444 ф
female; U+02640 ♀
ffilig; U+0FB03 ffi
fflig; U+0FB00 ff
ffllig; U+0FB04 ffl
Ffr; U+1D509 𝔉
ffr; U+1D523 𝔣
filig; U+0FB01 fi
FilledSmallSquare; U+025FC ◼
FilledVerySmallSquare; U+025AA ▪
fjlig; U+00066 U+0006A fj
flat; U+0266D ♭
fllig; U+0FB02 fl
fltns; U+025B1 ▱
fnof; U+00192 ƒ
Fopf; U+1D53D 𝔽
fopf; U+1D557 𝕗
ForAll; U+02200 ∀
forall; U+02200 ∀
fork; U+022D4 ⋔
forkv; U+02AD9 ⫙
Fouriertrf; U+02131 ℱ
fpartint; U+02A0D ⨍
frac12; U+000BD ½
frac12 U+000BD ½
frac13; U+02153 ⅓
frac14; U+000BC ¼
frac14 U+000BC ¼
frac15; U+02155 ⅕
frac16; U+02159 ⅙
frac18; U+0215B ⅛
frac23; U+02154 ⅔
frac25; U+02156 ⅖
frac34; U+000BE ¾
frac34 U+000BE ¾
frac35; U+02157 ⅗
frac38; U+0215C ⅜
frac45; U+02158 ⅘
frac56; U+0215A ⅚
frac58; U+0215D ⅝
frac78; U+0215E ⅞
frasl; U+02044 ⁄
frown; U+02322 ⌢
Fscr; U+02131 ℱ
fscr; U+1D4BB 𝒻
gacute; U+001F5 ǵ
Gamma; U+00393 Γ
gamma; U+003B3 γ
Gammad; U+003DC Ϝ
gammad; U+003DD ϝ
gap; U+02A86 ⪆
Gbreve; U+0011E Ğ
gbreve; U+0011F ğ
Gcedil; U+00122 Ģ
Gcirc; U+0011C Ĝ
gcirc; U+0011D ĝ
Gcy; U+00413 Г
gcy; U+00433 г
Gdot; U+00120 Ġ
gdot; U+00121 ġ
gE; U+02267 ≧
ge; U+02265 ≥
gEl; U+02A8C ⪌
gel; U+022DB ⋛
geq; U+02265 ≥
geqq; U+02267 ≧
geqslant; U+02A7E ⩾
ges; U+02A7E ⩾
gescc; U+02AA9 ⪩
gesdot; U+02A80 ⪀
gesdoto; U+02A82 ⪂
gesdotol; U+02A84 ⪄
gesl; U+022DB U+0FE00 ⋛︀
gesles; U+02A94 ⪔
Gfr; U+1D50A 𝔊
gfr; U+1D524 𝔤
Gg; U+022D9 ⋙
gg; U+0226B ≫
ggg; U+022D9 ⋙
gimel; U+02137 ℷ
GJcy; U+00403 Ѓ
gjcy; U+00453 ѓ
gl; U+02277 ≷
gla; U+02AA5 ⪥
glE; U+02A92 ⪒
glj; U+02AA4 ⪤
gnap; U+02A8A ⪊
gnapprox; U+02A8A ⪊
gnE; U+02269 ≩
gne; U+02A88 ⪈
gneq; U+02A88 ⪈
gneqq; U+02269 ≩
gnsim; U+022E7 ⋧
Gopf; U+1D53E 𝔾
gopf; U+1D558 𝕘
grave; U+00060 `
GreaterEqual; U+02265 ≥
GreaterEqualLess; U+022DB ⋛
GreaterFullEqual; U+02267 ≧
GreaterGreater; U+02AA2 ⪢
GreaterLess; U+02277 ≷
GreaterSlantEqual; U+02A7E ⩾
GreaterTilde; U+02273 ≳
Gscr; U+1D4A2 𝒢
gscr; U+0210A ℊ
gsim; U+02273 ≳
gsime; U+02A8E ⪎
gsiml; U+02A90 ⪐
GT; U+0003E >
GT U+0003E >
Gt; U+0226B ≫
gt; U+0003E >
gt U+0003E >
gtcc; U+02AA7 ⪧
gtcir; U+02A7A ⩺
gtdot; U+022D7 ⋗
gtlPar; U+02995 ⦕
gtquest; U+02A7C ⩼
gtrapprox; U+02A86 ⪆
gtrarr; U+02978 ⥸
gtrdot; U+022D7 ⋗
gtreqless; U+022DB ⋛
gtreqqless; U+02A8C ⪌
gtrless; U+02277 ≷
gtrsim; U+02273 ≳
gvertneqq; U+02269 U+0FE00 ≩︀
gvnE; U+02269 U+0FE00 ≩︀
Hacek; U+002C7 ˇ
hairsp; U+0200A
half; U+000BD ½
hamilt; U+0210B ℋ
HARDcy; U+0042A Ъ
hardcy; U+0044A ъ
hArr; U+021D4 ⇔
harr; U+02194 ↔
harrcir; U+02948 ⥈
harrw; U+021AD ↭
Hat; U+0005E ^
hbar; U+0210F ℏ
Hcirc; U+00124 Ĥ
hcirc; U+00125 ĥ
hearts; U+02665 ♥
heartsuit; U+02665 ♥
hellip; U+02026 …
hercon; U+022B9 ⊹
Hfr; U+0210C ℌ
hfr; U+1D525 𝔥
HilbertSpace; U+0210B ℋ
hksearow; U+02925 ⤥
hkswarow; U+02926 ⤦
hoarr; U+021FF ⇿
homtht; U+0223B ∻
hookleftarrow; U+021A9 ↩
hookrightarrow; U+021AA ↪
Hopf; U+0210D ℍ
hopf; U+1D559 𝕙
horbar; U+02015 ―
HorizontalLine; U+02500 ─
Hscr; U+0210B ℋ
hscr; U+1D4BD 𝒽
hslash; U+0210F ℏ
Hstrok; U+00126 Ħ
hstrok; U+00127 ħ
HumpDownHump; U+0224E ≎
HumpEqual; U+0224F ≏
hybull; U+02043 ⁃
hyphen; U+02010 ‐
Iacute; U+000CD Í
Iacute U+000CD Í
iacute; U+000ED í
iacute U+000ED í
ic; U+02063
Icirc; U+000CE Î
Icirc U+000CE Î
icirc; U+000EE î
icirc U+000EE î
Icy; U+00418 И
icy; U+00438 и
Idot; U+00130 İ
IEcy; U+00415 Е
iecy; U+00435 е
iexcl; U+000A1 ¡
iexcl U+000A1 ¡
iff; U+021D4 ⇔
Ifr; U+02111 ℑ
ifr; U+1D526 𝔦
Igrave; U+000CC Ì
Igrave U+000CC Ì
igrave; U+000EC ì
igrave U+000EC ì
ii; U+02148 ⅈ
iiiint; U+02A0C ⨌
iiint; U+0222D ∭
iinfin; U+029DC ⧜
iiota; U+02129 ℩
IJlig; U+00132 IJ
ijlig; U+00133 ij
Im; U+02111 ℑ
Imacr; U+0012A Ī
imacr; U+0012B ī
image; U+02111 ℑ
ImaginaryI; U+02148 ⅈ
imagline; U+02110 ℐ
imagpart; U+02111 ℑ
imath; U+00131 ı
imof; U+022B7 ⊷
imped; U+001B5 Ƶ
Implies; U+021D2 ⇒
in; U+02208 ∈
incare; U+02105 ℅
infin; U+0221E ∞
infintie; U+029DD ⧝
inodot; U+00131 ı
Int; U+0222C ∬
int; U+0222B ∫
intcal; U+022BA ⊺
integers; U+02124 ℤ
Integral; U+0222B ∫
intercal; U+022BA ⊺
Intersection; U+022C2 ⋂
intlarhk; U+02A17 ⨗
intprod; U+02A3C ⨼
InvisibleComma; U+02063
InvisibleTimes; U+02062
IOcy; U+00401 Ё
iocy; U+00451 ё
Iogon; U+0012E Į
iogon; U+0012F į
Iopf; U+1D540 𝕀
iopf; U+1D55A 𝕚
Iota; U+00399 Ι
iota; U+003B9 ι
iprod; U+02A3C ⨼
iquest; U+000BF ¿
iquest U+000BF ¿
Iscr; U+02110 ℐ
iscr; U+1D4BE 𝒾
isin; U+02208 ∈
isindot; U+022F5 ⋵
isinE; U+022F9 ⋹
isins; U+022F4 ⋴
isinsv; U+022F3 ⋳
isinv; U+02208 ∈
it; U+02062
Itilde; U+00128 Ĩ
itilde; U+00129 ĩ
Iukcy; U+00406 І
iukcy; U+00456 і
Iuml; U+000CF Ï
Iuml U+000CF Ï
iuml; U+000EF ï
iuml U+000EF ï
Jcirc; U+00134 Ĵ
jcirc; U+00135 ĵ
Jcy; U+00419 Й
jcy; U+00439 й
Jfr; U+1D50D 𝔍
jfr; U+1D527 𝔧
jmath; U+00237 ȷ
Jopf; U+1D541 𝕁
jopf; U+1D55B 𝕛
Jscr; U+1D4A5 𝒥
jscr; U+1D4BF 𝒿
Jsercy; U+00408 Ј
jsercy; U+00458 ј
Jukcy; U+00404 Є
jukcy; U+00454 є
Kappa; U+0039A Κ
kappa; U+003BA κ
kappav; U+003F0 ϰ
Kcedil; U+00136 Ķ
kcedil; U+00137 ķ
Kcy; U+0041A К
kcy; U+0043A к
Kfr; U+1D50E 𝔎
kfr; U+1D528 𝔨
kgreen; U+00138 ĸ
KHcy; U+00425 Х
khcy; U+00445 х
KJcy; U+0040C Ќ
kjcy; U+0045C ќ
Kopf; U+1D542 𝕂
kopf; U+1D55C 𝕜
Kscr; U+1D4A6 𝒦
kscr; U+1D4C0 𝓀
lAarr; U+021DA ⇚
Lacute; U+00139 Ĺ
lacute; U+0013A ĺ
laemptyv; U+029B4 ⦴
lagran; U+02112 ℒ
Lambda; U+0039B Λ
lambda; U+003BB λ
Lang; U+027EA ⟪
lang; U+027E8 ⟨
langd; U+02991 ⦑
langle; U+027E8 〈
lap; U+02A85 ⪅
Laplacetrf; U+02112 ℒ
laquo; U+000AB «
laquo U+000AB «
Larr; U+0219E ↞
lArr; U+021D0 ⇐
larr; U+02190 ←
larrb; U+021E4 ⇤
larrbfs; U+0291F ⤟
larrfs; U+0291D ⤝
larrhk; U+021A9 ↩
larrlp; U+021AB ↫
larrpl; U+02939 ⤹
larrsim; U+02973 ⥳
larrtl; U+021A2 ↢
lat; U+02AAB ⪫
lAtail; U+0291B ⤛
latail; U+02919 ⤙
late; U+02AAD ⪭
lates; U+02AAD U+0FE00 ⪭︀
lBarr; U+0290E ⤎
lbarr; U+0290C ⤌
lbbrk; U+02772 ❲
lbrace; U+0007B {
lbrack; U+0005B [
lbrke; U+0298B ⦋
lbrksld; U+0298F ⦏
lbrkslu; U+0298D ⦍
Lcaron; U+0013D Ľ
lcaron; U+0013E ľ
Lcedil; U+0013B Ļ
lcedil; U+0013C ļ
lceil; U+02308 ⌈
lcub; U+0007B {
Lcy; U+0041B Л
lcy; U+0043B л
ldca; U+02936 ⤶
ldquo; U+0201C “
ldquor; U+0201E „
ldrdhar; U+02967 ⥧
ldrushar; U+0294B ⥋
ldsh; U+021B2 ↲
lE; U+02266 ≦
le; U+02264 ≤
LeftAngleBracket; U+027E8 〈
LeftArrow; U+02190 ←
Leftarrow; U+021D0 ⇐
leftarrow; U+02190 ←
LeftArrowBar; U+021E4 ⇤
LeftArrowRightArrow; U+021C6 ⇆
leftarrowtail; U+021A2 ↢
LeftCeiling; U+02308 ⌈
LeftDoubleBracket; U+027E6 ⟦
LeftDownTeeVector; U+02961 ⥡
LeftDownVector; U+021C3 ⇃
LeftDownVectorBar; U+02959 ⥙
LeftFloor; U+0230A ⌊
leftharpoondown; U+021BD ↽
leftharpoonup; U+021BC ↼
leftleftarrows; U+021C7 ⇇
LeftRightArrow; U+02194 ↔
Leftrightarrow; U+021D4 ⇔
leftrightarrow; U+02194 ↔
leftrightarrows; U+021C6 ⇆
leftrightharpoons; U+021CB ⇋
leftrightsquigarrow; U+021AD ↭
LeftRightVector; U+0294E ⥎
LeftTee; U+022A3 ⊣
LeftTeeArrow; U+021A4 ↤
LeftTeeVector; U+0295A ⥚
leftthreetimes; U+022CB ⋋
LeftTriangle; U+022B2 ⊲
LeftTriangleBar; U+029CF ⧏
LeftTriangleEqual; U+022B4 ⊴
LeftUpDownVector; U+02951 ⥑
LeftUpTeeVector; U+02960 ⥠
LeftUpVector; U+021BF ↿
LeftUpVectorBar; U+02958 ⥘
LeftVector; U+021BC ↼
LeftVectorBar; U+02952 ⥒
lEg; U+02A8B ⪋
leg; U+022DA ⋚
leq; U+02264 ≤
leqq; U+02266 ≦
leqslant; U+02A7D ⩽
les; U+02A7D ⩽
lescc; U+02AA8 ⪨
lesdot; U+02A7F ⩿
lesdoto; U+02A81 ⪁
lesdotor; U+02A83 ⪃
lesg; U+022DA U+0FE00 ⋚︀
lesges; U+02A93 ⪓
lessapprox; U+02A85 ⪅
lessdot; U+022D6 ⋖
lesseqgtr; U+022DA ⋚
lesseqqgtr; U+02A8B ⪋
LessEqualGreater; U+022DA ⋚
LessFullEqual; U+02266 ≦
LessGreater; U+02276 ≶
lessgtr; U+02276 ≶
LessLess; U+02AA1 ⪡
lesssim; U+02272 ≲
LessSlantEqual; U+02A7D ⩽
LessTilde; U+02272 ≲
lfisht; U+0297C ⥼
lfloor; U+0230A ⌊
Lfr; U+1D50F 𝔏
lfr; U+1D529 𝔩
lg; U+02276 ≶
lgE; U+02A91 ⪑
lHar; U+02962 ⥢
lhard; U+021BD ↽
lharu; U+021BC ↼
lharul; U+0296A ⥪
lhblk; U+02584 ▄
LJcy; U+00409 Љ
ljcy; U+00459 љ
Ll; U+022D8 ⋘
ll; U+0226A ≪
llarr; U+021C7 ⇇
llcorner; U+0231E ⌞
Lleftarrow; U+021DA ⇚
llhard; U+0296B ⥫
lltri; U+025FA ◺
Lmidot; U+0013F Ŀ
lmidot; U+00140 ŀ
lmoust; U+023B0 ⎰
lmoustache; U+023B0 ⎰
lnap; U+02A89 ⪉
lnapprox; U+02A89 ⪉
lnE; U+02268 ≨
lne; U+02A87 ⪇
lneq; U+02A87 ⪇
lneqq; U+02268 ≨
lnsim; U+022E6 ⋦
loang; U+027EC ⟬
loarr; U+021FD ⇽
lobrk; U+027E6 ⟦
LongLeftArrow; U+027F5 ⟵
Longleftarrow; U+027F8 ⟸
longleftarrow; U+027F5 ⟵
LongLeftRightArrow; U+027F7 ⟷
Longleftrightarrow; U+027FA ⟺
longleftrightarrow; U+027F7 ⟷
longmapsto; U+027FC ⟼
LongRightArrow; U+027F6 ⟶
Longrightarrow; U+027F9 ⟹
longrightarrow; U+027F6 ⟶
looparrowleft; U+021AB ↫
looparrowright; U+021AC ↬
lopar; U+02985 ⦅
Lopf; U+1D543 𝕃
lopf; U+1D55D 𝕝
loplus; U+02A2D ⨭
lotimes; U+02A34 ⨴
lowast; U+02217 ∗
lowbar; U+0005F _
LowerLeftArrow; U+02199 ↙
LowerRightArrow; U+02198 ↘
loz; U+025CA ◊
lozenge; U+025CA ◊
lozf; U+029EB ⧫
lpar; U+00028 (
lparlt; U+02993 ⦓
lrarr; U+021C6 ⇆
lrcorner; U+0231F ⌟
lrhar; U+021CB ⇋
lrhard; U+0296D ⥭
lrm; U+0200E
lrtri; U+022BF ⊿
lsaquo; U+02039 ‹
Lscr; U+02112 ℒ
lscr; U+1D4C1 𝓁
Lsh; U+021B0 ↰
lsh; U+021B0 ↰
lsim; U+02272 ≲
lsime; U+02A8D ⪍
lsimg; U+02A8F ⪏
lsqb; U+0005B [
lsquo; U+02018 ‘
lsquor; U+0201A ‚
Lstrok; U+00141 Ł
lstrok; U+00142 ł
LT; U+0003C <
LT U+0003C <
Lt; U+0226A ≪
lt; U+0003C <
lt U+0003C <
ltcc; U+02AA6 ⪦
ltcir; U+02A79 ⩹
ltdot; U+022D6 ⋖
lthree; U+022CB ⋋
ltimes; U+022C9 ⋉
ltlarr; U+02976 ⥶
ltquest; U+02A7B ⩻
ltri; U+025C3 ◃
ltrie; U+022B4 ⊴
ltrif; U+025C2 ◂
ltrPar; U+02996 ⦖
lurdshar; U+0294A ⥊
luruhar; U+02966 ⥦
lvertneqq; U+02268 U+0FE00 ≨︀
lvnE; U+02268 U+0FE00 ≨︀
macr; U+000AF ¯
macr U+000AF ¯
male; U+02642 ♂
malt; U+02720 ✠
maltese; U+02720 ✠
Map; U+02905 ⤅
map; U+021A6 ↦
mapsto; U+021A6 ↦
mapstodown; U+021A7 ↧
mapstoleft; U+021A4 ↤
mapstoup; U+021A5 ↥
marker; U+025AE ▮
mcomma; U+02A29 ⨩
Mcy; U+0041C М
mcy; U+0043C м
mdash; U+02014 —
mDDot; U+0223A ∺
measuredangle; U+02221 ∡
MediumSpace; U+0205F
Mellintrf; U+02133 ℳ
Mfr; U+1D510 𝔐
mfr; U+1D52A 𝔪
mho; U+02127 ℧
micro; U+000B5 µ
micro U+000B5 µ
mid; U+02223 ∣
midast; U+0002A *
midcir; U+02AF0 ⫰
middot; U+000B7 ·
middot U+000B7 ·
minus; U+02212 −
minusb; U+0229F ⊟
minusd; U+02238 ∸
minusdu; U+02A2A ⨪
MinusPlus; U+02213 ∓
mlcp; U+02ADB ⫛
mldr; U+02026 …
mnplus; U+02213 ∓
models; U+022A7 ⊧
Mopf; U+1D544 𝕄
mopf; U+1D55E 𝕞
mp; U+02213 ∓
Mscr; U+02133 ℳ
mscr; U+1D4C2 𝓂
mstpos; U+0223E ∾
Mu; U+0039C Μ
mu; U+003BC μ
multimap; U+022B8 ⊸
mumap; U+022B8 ⊸
nabla; U+02207 ∇
Nacute; U+00143 Ń
nacute; U+00144 ń
nang; U+02220 U+020D2 ∠⃒
nap; U+02249 ≉
napE; U+02A70 U+00338 ⩰̸
napid; U+0224B U+00338 ≋̸
napos; U+00149 ʼn
napprox; U+02249 ≉
natur; U+0266E ♮
natural; U+0266E ♮
naturals; U+02115 ℕ
nbsp; U+000A0
nbsp U+000A0
nbump; U+0224E U+00338 ≎̸
nbumpe; U+0224F U+00338 ≏̸
ncap; U+02A43 ⩃
Ncaron; U+00147 Ň
ncaron; U+00148 ň
Ncedil; U+00145 Ņ
ncedil; U+00146 ņ
ncong; U+02247 ≇
ncongdot; U+02A6D U+00338 ⩭̸
ncup; U+02A42 ⩂
Ncy; U+0041D Н
ncy; U+0043D н
ndash; U+02013 –
ne; U+02260 ≠
nearhk; U+02924 ⤤
neArr; U+021D7 ⇗
nearr; U+02197 ↗
nearrow; U+02197 ↗
nedot; U+02250 U+00338 ≐̸
NegativeMediumSpace; U+0200B
NegativeThickSpace; U+0200B
NegativeThinSpace; U+0200B
NegativeVeryThinSpace; U+0200B
nequiv; U+02262 ≢
nesear; U+02928 ⤨
nesim; U+02242 U+00338 ≂̸
NestedGreaterGreater; U+0226B ≫
NestedLessLess; U+0226A ≪
NewLine; U+0000A ␊
nexist; U+02204 ∄
nexists; U+02204 ∄
Nfr; U+1D511 𝔑
nfr; U+1D52B 𝔫
ngE; U+02267 U+00338 ≧̸
nge; U+02271 ≱
ngeq; U+02271 ≱
ngeqq; U+02267 U+00338 ≧̸
ngeqslant; U+02A7E U+00338 ⩾̸
nges; U+02A7E U+00338 ⩾̸
nGg; U+022D9 U+00338 ⋙̸
ngsim; U+02275 ≵
nGt; U+0226B U+020D2 ≫⃒
ngt; U+0226F ≯
ngtr; U+0226F ≯
nGtv; U+0226B U+00338 ≫̸
nhArr; U+021CE ⇎
nharr; U+021AE ↮
nhpar; U+02AF2 ⫲
ni; U+0220B ∋
nis; U+022FC ⋼
nisd; U+022FA ⋺
niv; U+0220B ∋
NJcy; U+0040A Њ
njcy; U+0045A њ
nlArr; U+021CD ⇍
nlarr; U+0219A ↚
nldr; U+02025 ‥
nlE; U+02266 U+00338 ≦̸
nle; U+02270 ≰
nLeftarrow; U+021CD ⇍
nleftarrow; U+0219A ↚
nLeftrightarrow; U+021CE ⇎
nleftrightarrow; U+021AE ↮
nleq; U+02270 ≰
nleqq; U+02266 U+00338 ≦̸
nleqslant; U+02A7D U+00338 ⩽̸
nles; U+02A7D U+00338 ⩽̸
nless; U+0226E ≮
nLl; U+022D8 U+00338 ⋘̸
nlsim; U+02274 ≴
nLt; U+0226A U+020D2 ≪⃒
nlt; U+0226E ≮
nltri; U+022EA ⋪
nltrie; U+022EC ⋬
nLtv; U+0226A U+00338 ≪̸
nmid; U+02224 ∤
NoBreak; U+02060
NonBreakingSpace; U+000A0
Nopf; U+02115 ℕ
nopf; U+1D55F 𝕟
Not; U+02AEC ⫬
not; U+000AC ¬
not U+000AC ¬
NotCongruent; U+02262 ≢
NotCupCap; U+0226D ≭
NotDoubleVerticalBar; U+02226 ∦
NotElement; U+02209 ∉
NotEqual; U+02260 ≠
NotEqualTilde; U+02242 U+00338 ≂̸
NotExists; U+02204 ∄
NotGreater; U+0226F ≯
NotGreaterEqual; U+02271 ≱
NotGreaterFullEqual; U+02267 U+00338 ≧̸
NotGreaterGreater; U+0226B U+00338 ≫̸
NotGreaterLess; U+02279 ≹
NotGreaterSlantEqual; U+02A7E U+00338 ⩾̸
NotGreaterTilde; U+02275 ≵
NotHumpDownHump; U+0224E U+00338 ≎̸
NotHumpEqual; U+0224F U+00338 ≏̸
notin; U+02209 ∉
notindot; U+022F5 U+00338 ⋵̸
notinE; U+022F9 U+00338 ⋹̸
notinva; U+02209 ∉
notinvb; U+022F7 ⋷
notinvc; U+022F6 ⋶
NotLeftTriangle; U+022EA ⋪
NotLeftTriangleBar; U+029CF U+00338 ⧏̸
NotLeftTriangleEqual; U+022EC ⋬
NotLess; U+0226E ≮
NotLessEqual; U+02270 ≰
NotLessGreater; U+02278 ≸
NotLessLess; U+0226A U+00338 ≪̸
NotLessSlantEqual; U+02A7D U+00338 ⩽̸
NotLessTilde; U+02274 ≴
NotNestedGreaterGreater; U+02AA2 U+00338 ⪢̸
NotNestedLessLess; U+02AA1 U+00338 ⪡̸
notni; U+0220C ∌
notniva; U+0220C ∌
notnivb; U+022FE ⋾
notnivc; U+022FD ⋽
NotPrecedes; U+02280 ⊀
NotPrecedesEqual; U+02AAF U+00338 ⪯̸
NotPrecedesSlantEqual; U+022E0 ⋠
NotReverseElement; U+0220C ∌
NotRightTriangle; U+022EB ⋫
NotRightTriangleBar; U+029D0 U+00338 ⧐̸
NotRightTriangleEqual; U+022ED ⋭
NotSquareSubset; U+0228F U+00338 ⊏̸
NotSquareSubsetEqual; U+022E2 ⋢
NotSquareSuperset; U+02290 U+00338 ⊐̸
NotSquareSupersetEqual; U+022E3 ⋣
NotSubset; U+02282 U+020D2 ⊂⃒
NotSubsetEqual; U+02288 ⊈
NotSucceeds; U+02281 ⊁
NotSucceedsEqual; U+02AB0 U+00338 ⪰̸
NotSucceedsSlantEqual; U+022E1 ⋡
NotSucceedsTilde; U+0227F U+00338 ≿̸
NotSuperset; U+02283 U+020D2 ⊃⃒
NotSupersetEqual; U+02289 ⊉
NotTilde; U+02241 ≁
NotTildeEqual; U+02244 ≄
NotTildeFullEqual; U+02247 ≇
NotTildeTilde; U+02249 ≉
NotVerticalBar; U+02224 ∤
npar; U+02226 ∦
nparallel; U+02226 ∦
nparsl; U+02AFD U+020E5 ⫽⃥
npart; U+02202 U+00338 ∂̸
npolint; U+02A14 ⨔
npr; U+02280 ⊀
nprcue; U+022E0 ⋠
npre; U+02AAF U+00338 ⪯̸
nprec; U+02280 ⊀
npreceq; U+02AAF U+00338 ⪯̸
nrArr; U+021CF ⇏
nrarr; U+0219B ↛
nrarrc; U+02933 U+00338 ⤳̸
nrarrw; U+0219D U+00338 ↝̸
nRightarrow; U+021CF ⇏
nrightarrow; U+0219B ↛
nrtri; U+022EB ⋫
nrtrie; U+022ED ⋭
nsc; U+02281 ⊁
nsccue; U+022E1 ⋡
nsce; U+02AB0 U+00338 ⪰̸
Nscr; U+1D4A9 𝒩
nscr; U+1D4C3 𝓃
nshortmid; U+02224 ∤
nshortparallel; U+02226 ∦
nsim; U+02241 ≁
nsime; U+02244 ≄
nsimeq; U+02244 ≄
nsmid; U+02224 ∤
nspar; U+02226 ∦
nsqsube; U+022E2 ⋢
nsqsupe; U+022E3 ⋣
nsub; U+02284 ⊄
nsubE; U+02AC5 U+00338 ⫅̸
nsube; U+02288 ⊈
nsubset; U+02282 U+020D2 ⊂⃒
nsubseteq; U+02288 ⊈
nsubseteqq; U+02AC5 U+00338 ⫅̸
nsucc; U+02281 ⊁
nsucceq; U+02AB0 U+00338 ⪰̸
nsup; U+02285 ⊅
nsupE; U+02AC6 U+00338 ⫆̸
nsupe; U+02289 ⊉
nsupset; U+02283 U+020D2 ⊃⃒
nsupseteq; U+02289 ⊉
nsupseteqq; U+02AC6 U+00338 ⫆̸
ntgl; U+02279 ≹
Ntilde; U+000D1 Ñ
Ntilde U+000D1 Ñ
ntilde; U+000F1 ñ
ntilde U+000F1 ñ
ntlg; U+02278 ≸
ntriangleleft; U+022EA ⋪
ntrianglelefteq; U+022EC ⋬
ntriangleright; U+022EB ⋫
ntrianglerighteq; U+022ED ⋭
Nu; U+0039D Ν
nu; U+003BD ν
num; U+00023 #
numero; U+02116 №
numsp; U+02007
nvap; U+0224D U+020D2 ≍⃒
nVDash; U+022AF ⊯
nVdash; U+022AE ⊮
nvDash; U+022AD ⊭
nvdash; U+022AC ⊬
nvge; U+02265 U+020D2 ≥⃒
nvgt; U+0003E U+020D2 >⃒
nvHarr; U+02904 ⤄
nvinfin; U+029DE ⧞
nvlArr; U+02902 ⤂
nvle; U+02264 U+020D2 ≤⃒
nvlt; U+0003C U+020D2 <⃒
nvltrie; U+022B4 U+020D2 ⊴⃒
nvrArr; U+02903 ⤃
nvrtrie; U+022B5 U+020D2 ⊵⃒
nvsim; U+0223C U+020D2 ∼⃒
nwarhk; U+02923 ⤣
nwArr; U+021D6 ⇖
nwarr; U+02196 ↖
nwarrow; U+02196 ↖
nwnear; U+02927 ⤧
Oacute; U+000D3 Ó
Oacute U+000D3 Ó
oacute; U+000F3 ó
oacute U+000F3 ó
oast; U+0229B ⊛
ocir; U+0229A ⊚
Ocirc; U+000D4 Ô
Ocirc U+000D4 Ô
ocirc; U+000F4 ô
ocirc U+000F4 ô
Ocy; U+0041E О
ocy; U+0043E о
odash; U+0229D ⊝
Odblac; U+00150 Ő
odblac; U+00151 ő
odiv; U+02A38 ⨸
odot; U+02299 ⊙
odsold; U+029BC ⦼
OElig; U+00152 Œ
oelig; U+00153 œ
ofcir; U+029BF ⦿
Ofr; U+1D512 𝔒
ofr; U+1D52C 𝔬
ogon; U+002DB ˛
Ograve; U+000D2 Ò
Ograve U+000D2 Ò
ograve; U+000F2 ò
ograve U+000F2 ò
ogt; U+029C1 ⧁
ohbar; U+029B5 ⦵
ohm; U+003A9 Ω
oint; U+0222E ∮
olarr; U+021BA ↺
olcir; U+029BE ⦾
olcross; U+029BB ⦻
oline; U+0203E ‾
olt; U+029C0 ⧀
Omacr; U+0014C Ō
omacr; U+0014D ō
Omega; U+003A9 Ω
omega; U+003C9 ω
Omicron; U+0039F Ο
omicron; U+003BF ο
omid; U+029B6 ⦶
ominus; U+02296 ⊖
Oopf; U+1D546 𝕆
oopf; U+1D560 𝕠
opar; U+029B7 ⦷
OpenCurlyDoubleQuote; U+0201C “
OpenCurlyQuote; U+02018 ‘
operp; U+029B9 ⦹
oplus; U+02295 ⊕
Or; U+02A54 ⩔
or; U+02228 ∨
orarr; U+021BB ↻
ord; U+02A5D ⩝
order; U+02134 ℴ
orderof; U+02134 ℴ
ordf; U+000AA ª
ordf U+000AA ª
ordm; U+000BA º
ordm U+000BA º
origof; U+022B6 ⊶
oror; U+02A56 ⩖
orslope; U+02A57 ⩗
orv; U+02A5B ⩛
oS; U+024C8 Ⓢ
Oscr; U+1D4AA 𝒪
oscr; U+02134 ℴ
Oslash; U+000D8 Ø
Oslash U+000D8 Ø
oslash; U+000F8 ø
oslash U+000F8 ø
osol; U+02298 ⊘
Otilde; U+000D5 Õ
Otilde U+000D5 Õ
otilde; U+000F5 õ
otilde U+000F5 õ
Otimes; U+02A37 ⨷
otimes; U+02297 ⊗
otimesas; U+02A36 ⨶
Ouml; U+000D6 Ö
Ouml U+000D6 Ö
ouml; U+000F6 ö
ouml U+000F6 ö
ovbar; U+0233D ⌽
OverBar; U+0203E ‾
OverBrace; U+023DE ⏞
OverBracket; U+023B4 ⎴
OverParenthesis; U+023DC ⏜
par; U+02225 ∥
para; U+000B6 ¶
para U+000B6 ¶
parallel; U+02225 ∥
parsim; U+02AF3 ⫳
parsl; U+02AFD ⫽
part; U+02202 ∂
PartialD; U+02202 ∂
Pcy; U+0041F П
pcy; U+0043F п
percnt; U+00025 %
period; U+0002E .
permil; U+02030 ‰
perp; U+022A5 ⊥
pertenk; U+02031 ‱
Pfr; U+1D513 𝔓
pfr; U+1D52D 𝔭
Phi; U+003A6 Φ
phi; U+003C6 φ
phiv; U+003D5 ϕ
phmmat; U+02133 ℳ
phone; U+0260E ☎
Pi; U+003A0 Π
pi; U+003C0 π
pitchfork; U+022D4 ⋔
piv; U+003D6 ϖ
planck; U+0210F ℏ
planckh; U+0210E ℎ
plankv; U+0210F ℏ
plus; U+0002B +
plusacir; U+02A23 ⨣
plusb; U+0229E ⊞
pluscir; U+02A22 ⨢
plusdo; U+02214 ∔
plusdu; U+02A25 ⨥
pluse; U+02A72 ⩲
PlusMinus; U+000B1 ±
plusmn; U+000B1 ±
plusmn U+000B1 ±
plussim; U+02A26 ⨦
plustwo; U+02A27 ⨧
pm; U+000B1 ±
Poincareplane; U+0210C ℌ
pointint; U+02A15 ⨕
Popf; U+02119 ℙ
popf; U+1D561 𝕡
pound; U+000A3 £
pound U+000A3 £
Pr; U+02ABB ⪻
pr; U+0227A ≺
prap; U+02AB7 ⪷
prcue; U+0227C ≼
prE; U+02AB3 ⪳
pre; U+02AAF ⪯
prec; U+0227A ≺
precapprox; U+02AB7 ⪷
preccurlyeq; U+0227C ≼
Precedes; U+0227A ≺
PrecedesEqual; U+02AAF ⪯
PrecedesSlantEqual; U+0227C ≼
PrecedesTilde; U+0227E ≾
preceq; U+02AAF ⪯
precnapprox; U+02AB9 ⪹
precneqq; U+02AB5 ⪵
precnsim; U+022E8 ⋨
precsim; U+0227E ≾
Prime; U+02033 ″
prime; U+02032 ′
primes; U+02119 ℙ
prnap; U+02AB9 ⪹
prnE; U+02AB5 ⪵
prnsim; U+022E8 ⋨
prod; U+0220F ∏
Product; U+0220F ∏
profalar; U+0232E ⌮
profline; U+02312 ⌒
profsurf; U+02313 ⌓
prop; U+0221D ∝
Proportion; U+02237 ∷
Proportional; U+0221D ∝
propto; U+0221D ∝
prsim; U+0227E ≾
prurel; U+022B0 ⊰
Pscr; U+1D4AB 𝒫
pscr; U+1D4C5 𝓅
Psi; U+003A8 Ψ
psi; U+003C8 ψ
puncsp; U+02008
Qfr; U+1D514 𝔔
qfr; U+1D52E 𝔮
qint; U+02A0C ⨌
Qopf; U+0211A ℚ
qopf; U+1D562 𝕢
qprime; U+02057 ⁗
Qscr; U+1D4AC 𝒬
qscr; U+1D4C6 𝓆
quaternions; U+0210D ℍ
quatint; U+02A16 ⨖
quest; U+0003F ?
questeq; U+0225F ≟
QUOT; U+00022 "
QUOT U+00022 "
quot; U+00022 "
quot U+00022 "
rAarr; U+021DB ⇛
race; U+0223D U+00331 ∽̱
Racute; U+00154 Ŕ
racute; U+00155 ŕ
radic; U+0221A √
raemptyv; U+029B3 ⦳
Rang; U+027EB ⟫
rang; U+027E9 ⟩
rangd; U+02992 ⦒
range; U+029A5 ⦥
rangle; U+027E9 〉
raquo; U+000BB »
raquo U+000BB »
Rarr; U+021A0 ↠
rArr; U+021D2 ⇒
rarr; U+02192 →
rarrap; U+02975 ⥵
rarrb; U+021E5 ⇥
rarrbfs; U+02920 ⤠
rarrc; U+02933 ⤳
rarrfs; U+0291E ⤞
rarrhk; U+021AA ↪
rarrlp; U+021AC ↬
rarrpl; U+02945 ⥅
rarrsim; U+02974 ⥴
Rarrtl; U+02916 ⤖
rarrtl; U+021A3 ↣
rarrw; U+0219D ↝
rAtail; U+0291C ⤜
ratail; U+0291A ⤚
ratio; U+02236 ∶
rationals; U+0211A ℚ
RBarr; U+02910 ⤐
rBarr; U+0290F ⤏
rbarr; U+0290D ⤍
rbbrk; U+02773 ❳
rbrace; U+0007D }
rbrack; U+0005D ]
rbrke; U+0298C ⦌
rbrksld; U+0298E ⦎
rbrkslu; U+02990 ⦐
Rcaron; U+00158 Ř
rcaron; U+00159 ř
Rcedil; U+00156 Ŗ
rcedil; U+00157 ŗ
rceil; U+02309 ⌉
rcub; U+0007D }
Rcy; U+00420 Р
rcy; U+00440 р
rdca; U+02937 ⤷
rdldhar; U+02969 ⥩
rdquo; U+0201D ”
rdquor; U+0201D ”
rdsh; U+021B3 ↳
Re; U+0211C ℜ
real; U+0211C ℜ
realine; U+0211B ℛ
realpart; U+0211C ℜ
reals; U+0211D ℝ
rect; U+025AD ▭
REG; U+000AE ®
REG U+000AE ®
reg; U+000AE ®
reg U+000AE ®
ReverseElement; U+0220B ∋
ReverseEquilibrium; U+021CB ⇋
ReverseUpEquilibrium; U+0296F ⥯
rfisht; U+0297D ⥽
rfloor; U+0230B ⌋
Rfr; U+0211C ℜ
rfr; U+1D52F 𝔯
rHar; U+02964 ⥤
rhard; U+021C1 ⇁
rharu; U+021C0 ⇀
rharul; U+0296C ⥬
Rho; U+003A1 Ρ
rho; U+003C1 ρ
rhov; U+003F1 ϱ
RightAngleBracket; U+027E9 〉
RightArrow; U+02192 →
Rightarrow; U+021D2 ⇒
rightarrow; U+02192 →
RightArrowBar; U+021E5 ⇥
RightArrowLeftArrow; U+021C4 ⇄
rightarrowtail; U+021A3 ↣
RightCeiling; U+02309 ⌉
RightDoubleBracket; U+027E7 ⟧
RightDownTeeVector; U+0295D ⥝
RightDownVector; U+021C2 ⇂
RightDownVectorBar; U+02955 ⥕
RightFloor; U+0230B ⌋
rightharpoondown; U+021C1 ⇁
rightharpoonup; U+021C0 ⇀
rightleftarrows; U+021C4 ⇄
rightleftharpoons; U+021CC ⇌
rightrightarrows; U+021C9 ⇉
rightsquigarrow; U+0219D ↝
RightTee; U+022A2 ⊢
RightTeeArrow; U+021A6 ↦
RightTeeVector; U+0295B ⥛
rightthreetimes; U+022CC ⋌
RightTriangle; U+022B3 ⊳
RightTriangleBar; U+029D0 ⧐
RightTriangleEqual; U+022B5 ⊵
RightUpDownVector; U+0294F ⥏
RightUpTeeVector; U+0295C ⥜
RightUpVector; U+021BE ↾
RightUpVectorBar; U+02954 ⥔
RightVector; U+021C0 ⇀
RightVectorBar; U+02953 ⥓
ring; U+002DA ˚
risingdotseq; U+02253 ≓
rlarr; U+021C4 ⇄
rlhar; U+021CC ⇌
rlm; U+0200F
rmoust; U+023B1 ⎱
rmoustache; U+023B1 ⎱
rnmid; U+02AEE ⫮
roang; U+027ED ⟭
roarr; U+021FE ⇾
robrk; U+027E7 ⟧
ropar; U+02986 ⦆
Ropf; U+0211D ℝ
ropf; U+1D563 𝕣
roplus; U+02A2E ⨮
rotimes; U+02A35 ⨵
RoundImplies; U+02970 ⥰
rpar; U+00029 )
rpargt; U+02994 ⦔
rppolint; U+02A12 ⨒
rrarr; U+021C9 ⇉
Rrightarrow; U+021DB ⇛
rsaquo; U+0203A ›
Rscr; U+0211B ℛ
rscr; U+1D4C7 𝓇
Rsh; U+021B1 ↱
rsh; U+021B1 ↱
rsqb; U+0005D ]
rsquo; U+02019 ’
rsquor; U+02019 ’
rthree; U+022CC ⋌
rtimes; U+022CA ⋊
rtri; U+025B9 ▹
rtrie; U+022B5 ⊵
rtrif; U+025B8 ▸
rtriltri; U+029CE ⧎
RuleDelayed; U+029F4 ⧴
ruluhar; U+02968 ⥨
rx; U+0211E ℞
Sacute; U+0015A Ś
sacute; U+0015B ś
sbquo; U+0201A ‚
Sc; U+02ABC ⪼
sc; U+0227B ≻
scap; U+02AB8 ⪸
Scaron; U+00160 Š
scaron; U+00161 š
sccue; U+0227D ≽
scE; U+02AB4 ⪴
sce; U+02AB0 ⪰
Scedil; U+0015E Ş
scedil; U+0015F ş
Scirc; U+0015C Ŝ
scirc; U+0015D ŝ
scnap; U+02ABA ⪺
scnE; U+02AB6 ⪶
scnsim; U+022E9 ⋩
scpolint; U+02A13 ⨓
scsim; U+0227F ≿
Scy; U+00421 С
scy; U+00441 с
sdot; U+022C5 ⋅
sdotb; U+022A1 ⊡
sdote; U+02A66 ⩦
searhk; U+02925 ⤥
seArr; U+021D8 ⇘
searr; U+02198 ↘
searrow; U+02198 ↘
sect; U+000A7 §
sect U+000A7 §
semi; U+0003B ;
seswar; U+02929 ⤩
setminus; U+02216 ∖
setmn; U+02216 ∖
sext; U+02736 ✶
Sfr; U+1D516 𝔖
sfr; U+1D530 𝔰
sfrown; U+02322 ⌢
sharp; U+0266F ♯
SHCHcy; U+00429 Щ
shchcy; U+00449 щ
SHcy; U+00428 Ш
shcy; U+00448 ш
ShortDownArrow; U+02193 ↓
ShortLeftArrow; U+02190 ←
shortmid; U+02223 ∣
shortparallel; U+02225 ∥
ShortRightArrow; U+02192 →
ShortUpArrow; U+02191 ↑
shy; U+000AD
shy U+000AD
Sigma; U+003A3 Σ
sigma; U+003C3 σ
sigmaf; U+003C2 ς
sigmav; U+003C2 ς
sim; U+0223C ∼
simdot; U+02A6A ⩪
sime; U+02243 ≃
simeq; U+02243 ≃
simg; U+02A9E ⪞
simgE; U+02AA0 ⪠
siml; U+02A9D ⪝
simlE; U+02A9F ⪟
simne; U+02246 ≆
simplus; U+02A24 ⨤
simrarr; U+02972 ⥲
slarr; U+02190 ←
SmallCircle; U+02218 ∘
smallsetminus; U+02216 ∖
smashp; U+02A33 ⨳
smeparsl; U+029E4 ⧤
smid; U+02223 ∣
smile; U+02323 ⌣
smt; U+02AAA ⪪
smte; U+02AAC ⪬
smtes; U+02AAC U+0FE00 ⪬︀
SOFTcy; U+0042C Ь
softcy; U+0044C ь
sol; U+0002F /
solb; U+029C4 ⧄
solbar; U+0233F ⌿
Sopf; U+1D54A 𝕊
sopf; U+1D564 𝕤
spades; U+02660 ♠
spadesuit; U+02660 ♠
spar; U+02225 ∥
sqcap; U+02293 ⊓
sqcaps; U+02293 U+0FE00 ⊓︀
sqcup; U+02294 ⊔
sqcups; U+02294 U+0FE00 ⊔︀
Sqrt; U+0221A √
sqsub; U+0228F ⊏
sqsube; U+02291 ⊑
sqsubset; U+0228F ⊏
sqsubseteq; U+02291 ⊑
sqsup; U+02290 ⊐
sqsupe; U+02292 ⊒
sqsupset; U+02290 ⊐
sqsupseteq; U+02292 ⊒
squ; U+025A1 □
Square; U+025A1 □
square; U+025A1 □
SquareIntersection; U+02293 ⊓
SquareSubset; U+0228F ⊏
SquareSubsetEqual; U+02291 ⊑
SquareSuperset; U+02290 ⊐
SquareSupersetEqual; U+02292 ⊒
SquareUnion; U+02294 ⊔
squarf; U+025AA ▪
squf; U+025AA ▪
srarr; U+02192 →
Sscr; U+1D4AE 𝒮
sscr; U+1D4C8 𝓈
ssetmn; U+02216 ∖
ssmile; U+02323 ⌣
sstarf; U+022C6 ⋆
Star; U+022C6 ⋆
star; U+02606 ☆
starf; U+02605 ★
straightepsilon; U+003F5 ϵ
straightphi; U+003D5 ϕ
strns; U+000AF ¯
Sub; U+022D0 ⋐
sub; U+02282 ⊂
subdot; U+02ABD ⪽
subE; U+02AC5 ⫅
sube; U+02286 ⊆
subedot; U+02AC3 ⫃
submult; U+02AC1 ⫁
subnE; U+02ACB ⫋
subne; U+0228A ⊊
subplus; U+02ABF ⪿
subrarr; U+02979 ⥹
Subset; U+022D0 ⋐
subset; U+02282 ⊂
subseteq; U+02286 ⊆
subseteqq; U+02AC5 ⫅
SubsetEqual; U+02286 ⊆
subsetneq; U+0228A ⊊
subsetneqq; U+02ACB ⫋
subsim; U+02AC7 ⫇
subsub; U+02AD5 ⫕
subsup; U+02AD3 ⫓
succ; U+0227B ≻
succapprox; U+02AB8 ⪸
succcurlyeq; U+0227D ≽
Succeeds; U+0227B ≻
SucceedsEqual; U+02AB0 ⪰
SucceedsSlantEqual; U+0227D ≽
SucceedsTilde; U+0227F ≿
succeq; U+02AB0 ⪰
succnapprox; U+02ABA ⪺
succneqq; U+02AB6 ⪶
succnsim; U+022E9 ⋩
succsim; U+0227F ≿
SuchThat; U+0220B ∋
Sum; U+02211 ∑
sum; U+02211 ∑
sung; U+0266A ♪
Sup; U+022D1 ⋑
sup; U+02283 ⊃
sup1; U+000B9 ¹
sup1 U+000B9 ¹
sup2; U+000B2 ²
sup2 U+000B2 ²
sup3; U+000B3 ³
sup3 U+000B3 ³
supdot; U+02ABE ⪾
supdsub; U+02AD8 ⫘
supE; U+02AC6 ⫆
supe; U+02287 ⊇
supedot; U+02AC4 ⫄
Superset; U+02283 ⊃
SupersetEqual; U+02287 ⊇
suphsol; U+027C9 ⟉
suphsub; U+02AD7 ⫗
suplarr; U+0297B ⥻
supmult; U+02AC2 ⫂
supnE; U+02ACC ⫌
supne; U+0228B ⊋
supplus; U+02AC0 ⫀
Supset; U+022D1 ⋑
supset; U+02283 ⊃
supseteq; U+02287 ⊇
supseteqq; U+02AC6 ⫆
supsetneq; U+0228B ⊋
supsetneqq; U+02ACC ⫌
supsim; U+02AC8 ⫈
supsub; U+02AD4 ⫔
supsup; U+02AD6 ⫖
swarhk; U+02926 ⤦
swArr; U+021D9 ⇙
swarr; U+02199 ↙
swarrow; U+02199 ↙
swnwar; U+0292A ⤪
szlig; U+000DF ß
szlig U+000DF ß
Tab; U+00009 ␉
target; U+02316 ⌖
Tau; U+003A4 Τ
tau; U+003C4 τ
tbrk; U+023B4 ⎴
Tcaron; U+00164 Ť
tcaron; U+00165 ť
Tcedil; U+00162 Ţ
tcedil; U+00163 ţ
Tcy; U+00422 Т
tcy; U+00442 т
tdot; U+020DB ◌⃛
telrec; U+02315 ⌕
Tfr; U+1D517 𝔗
tfr; U+1D531 𝔱
there4; U+02234 ∴
Therefore; U+02234 ∴
therefore; U+02234 ∴
Theta; U+00398 Θ
theta; U+003B8 θ
thetasym; U+003D1 ϑ
thetav; U+003D1 ϑ
thickapprox; U+02248 ≈
thicksim; U+0223C ∼
ThickSpace; U+0205F U+0200A
thinsp; U+02009
ThinSpace; U+02009
thkap; U+02248 ≈
thksim; U+0223C ∼
THORN; U+000DE Þ
THORN U+000DE Þ
thorn; U+000FE þ
thorn U+000FE þ
Tilde; U+0223C ∼
tilde; U+002DC ˜
TildeEqual; U+02243 ≃
TildeFullEqual; U+02245 ≅
TildeTilde; U+02248 ≈
times; U+000D7 ×
times U+000D7 ×
timesb; U+022A0 ⊠
timesbar; U+02A31 ⨱
timesd; U+02A30 ⨰
tint; U+0222D ∭
toea; U+02928 ⤨
top; U+022A4 ⊤
topbot; U+02336 ⌶
topcir; U+02AF1 ⫱
Topf; U+1D54B 𝕋
topf; U+1D565 𝕥
topfork; U+02ADA ⫚
tosa; U+02929 ⤩
tprime; U+02034 ‴
TRADE; U+02122 ™
trade; U+02122 ™
triangle; U+025B5 ▵
triangledown; U+025BF ▿
triangleleft; U+025C3 ◃
trianglelefteq; U+022B4 ⊴
triangleq; U+0225C ≜
triangleright; U+025B9 ▹
trianglerighteq; U+022B5 ⊵
tridot; U+025EC ◬
trie; U+0225C ≜
triminus; U+02A3A ⨺
TripleDot; U+020DB ◌⃛
triplus; U+02A39 ⨹
trisb; U+029CD ⧍
tritime; U+02A3B ⨻
trpezium; U+023E2 ⏢
Tscr; U+1D4AF 𝒯
tscr; U+1D4C9 𝓉
TScy; U+00426 Ц
tscy; U+00446 ц
TSHcy; U+0040B Ћ
tshcy; U+0045B ћ
Tstrok; U+00166 Ŧ
tstrok; U+00167 ŧ
twixt; U+0226C ≬
twoheadleftarrow; U+0219E ↞
twoheadrightarrow; U+021A0 ↠
Uacute; U+000DA Ú
Uacute U+000DA Ú
uacute; U+000FA ú
uacute U+000FA ú
Uarr; U+0219F ↟
uArr; U+021D1 ⇑
uarr; U+02191 ↑
Uarrocir; U+02949 ⥉
Ubrcy; U+0040E Ў
ubrcy; U+0045E ў
Ubreve; U+0016C Ŭ
ubreve; U+0016D ŭ
Ucirc; U+000DB Û
Ucirc U+000DB Û
ucirc; U+000FB û
ucirc U+000FB û
Ucy; U+00423 У
ucy; U+00443 у
udarr; U+021C5 ⇅
Udblac; U+00170 Ű
udblac; U+00171 ű
udhar; U+0296E ⥮
ufisht; U+0297E ⥾
Ufr; U+1D518 𝔘
ufr; U+1D532 𝔲
Ugrave; U+000D9 Ù
Ugrave U+000D9 Ù
ugrave; U+000F9 ù
ugrave U+000F9 ù
uHar; U+02963 ⥣
uharl; U+021BF ↿
uharr; U+021BE ↾
uhblk; U+02580 ▀
ulcorn; U+0231C ⌜
ulcorner; U+0231C ⌜
ulcrop; U+0230F ⌏
ultri; U+025F8 ◸
Umacr; U+0016A Ū
umacr; U+0016B ū
uml; U+000A8 ¨
uml U+000A8 ¨
UnderBar; U+0005F _
UnderBrace; U+023DF ⏟
UnderBracket; U+023B5 ⎵
UnderParenthesis; U+023DD ⏝
Union; U+022C3 ⋃
UnionPlus; U+0228E ⊎
Uogon; U+00172 Ų
uogon; U+00173 ų
Uopf; U+1D54C 𝕌
uopf; U+1D566 𝕦
UpArrow; U+02191 ↑
Uparrow; U+021D1 ⇑
uparrow; U+02191 ↑
UpArrowBar; U+02912 ⤒
UpArrowDownArrow; U+021C5 ⇅
UpDownArrow; U+02195 ↕
Updownarrow; U+021D5 ⇕
updownarrow; U+02195 ↕
UpEquilibrium; U+0296E ⥮
upharpoonleft; U+021BF ↿
upharpoonright; U+021BE ↾
uplus; U+0228E ⊎
UpperLeftArrow; U+02196 ↖
UpperRightArrow; U+02197 ↗
Upsi; U+003D2 ϒ
upsi; U+003C5 υ
upsih; U+003D2 ϒ
Upsilon; U+003A5 Υ
upsilon; U+003C5 υ
UpTee; U+022A5 ⊥
UpTeeArrow; U+021A5 ↥
upuparrows; U+021C8 ⇈
urcorn; U+0231D ⌝
urcorner; U+0231D ⌝
urcrop; U+0230E ⌎
Uring; U+0016E Ů
uring; U+0016F ů
urtri; U+025F9 ◹
Uscr; U+1D4B0 𝒰
uscr; U+1D4CA 𝓊
utdot; U+022F0 ⋰
Utilde; U+00168 Ũ
utilde; U+00169 ũ
utri; U+025B5 ▵
utrif; U+025B4 ▴
uuarr; U+021C8 ⇈
Uuml; U+000DC Ü
Uuml U+000DC Ü
uuml; U+000FC ü
uuml U+000FC ü
uwangle; U+029A7 ⦧
vangrt; U+0299C ⦜
varepsilon; U+003F5 ϵ
varkappa; U+003F0 ϰ
varnothing; U+02205 ∅
varphi; U+003D5 ϕ
varpi; U+003D6 ϖ
varpropto; U+0221D ∝
vArr; U+021D5 ⇕
varr; U+02195 ↕
varrho; U+003F1 ϱ
varsigma; U+003C2 ς
varsubsetneq; U+0228A U+0FE00 ⊊︀
varsubsetneqq; U+02ACB U+0FE00 ⫋︀
varsupsetneq; U+0228B U+0FE00 ⊋︀
varsupsetneqq; U+02ACC U+0FE00 ⫌︀
vartheta; U+003D1 ϑ
vartriangleleft; U+022B2 ⊲
vartriangleright; U+022B3 ⊳
Vbar; U+02AEB ⫫
vBar; U+02AE8 ⫨
vBarv; U+02AE9 ⫩
Vcy; U+00412 В
vcy; U+00432 в
VDash; U+022AB ⊫
Vdash; U+022A9 ⊩
vDash; U+022A8 ⊨
vdash; U+022A2 ⊢
Vdashl; U+02AE6 ⫦
Vee; U+022C1 ⋁
vee; U+02228 ∨
veebar; U+022BB ⊻
veeeq; U+0225A ≚
vellip; U+022EE ⋮
Verbar; U+02016 ‖
verbar; U+0007C |
Vert; U+02016 ‖
vert; U+0007C |
VerticalBar; U+02223 ∣
VerticalLine; U+0007C |
VerticalSeparator; U+02758 ❘
VerticalTilde; U+02240 ≀
VeryThinSpace; U+0200A
Vfr; U+1D519 𝔙
vfr; U+1D533 𝔳
vltri; U+022B2 ⊲
vnsub; U+02282 U+020D2 ⊂⃒
vnsup; U+02283 U+020D2 ⊃⃒
Vopf; U+1D54D 𝕍
vopf; U+1D567 𝕧
vprop; U+0221D ∝
vrtri; U+022B3 ⊳
Vscr; U+1D4B1 𝒱
vscr; U+1D4CB 𝓋
vsubnE; U+02ACB U+0FE00 ⫋︀
vsubne; U+0228A U+0FE00 ⊊︀
vsupnE; U+02ACC U+0FE00 ⫌︀
vsupne; U+0228B U+0FE00 ⊋︀
Vvdash; U+022AA ⊪
vzigzag; U+0299A ⦚
Wcirc; U+00174 Ŵ
wcirc; U+00175 ŵ
wedbar; U+02A5F ⩟
Wedge; U+022C0 ⋀
wedge; U+02227 ∧
wedgeq; U+02259 ≙
weierp; U+02118 ℘
Wfr; U+1D51A 𝔚
wfr; U+1D534 𝔴
Wopf; U+1D54E 𝕎
wopf; U+1D568 𝕨
wp; U+02118 ℘
wr; U+02240 ≀
wreath; U+02240 ≀
Wscr; U+1D4B2 𝒲
wscr; U+1D4CC 𝓌
xcap; U+022C2 ⋂
xcirc; U+025EF ◯
xcup; U+022C3 ⋃
xdtri; U+025BD ▽
Xfr; U+1D51B 𝔛
xfr; U+1D535 𝔵
xhArr; U+027FA ⟺
xharr; U+027F7 ⟷
Xi; U+0039E Ξ
xi; U+003BE ξ
xlArr; U+027F8 ⟸
xlarr; U+027F5 ⟵
xmap; U+027FC ⟼
xnis; U+022FB ⋻
xodot; U+02A00 ⨀
Xopf; U+1D54F 𝕏
xopf; U+1D569 𝕩
xoplus; U+02A01 ⨁
xotime; U+02A02 ⨂
xrArr; U+027F9 ⟹
xrarr; U+027F6 ⟶
Xscr; U+1D4B3 𝒳
xscr; U+1D4CD 𝓍
xsqcup; U+02A06 ⨆
xuplus; U+02A04 ⨄
xutri; U+025B3 △
xvee; U+022C1 ⋁
xwedge; U+022C0 ⋀
Yacute; U+000DD Ý
Yacute U+000DD Ý
yacute; U+000FD ý
yacute U+000FD ý
YAcy; U+0042F Я
yacy; U+0044F я
Ycirc; U+00176 Ŷ
ycirc; U+00177 ŷ
Ycy; U+0042B Ы
ycy; U+0044B ы
yen; U+000A5 ¥
yen U+000A5 ¥
Yfr; U+1D51C 𝔜
yfr; U+1D536 𝔶
YIcy; U+00407 Ї
yicy; U+00457 ї
Yopf; U+1D550 𝕐
yopf; U+1D56A 𝕪
Yscr; U+1D4B4 𝒴
yscr; U+1D4CE 𝓎
YUcy; U+0042E Ю
yucy; U+0044E ю
Yuml; U+00178 Ÿ
yuml; U+000FF ÿ
yuml U+000FF ÿ
Zacute; U+00179 Ź
zacute; U+0017A ź
Zcaron; U+0017D Ž
zcaron; U+0017E ž
Zcy; U+00417 З
zcy; U+00437 з
Zdot; U+0017B Ż
zdot; U+0017C ż
zeetrf; U+02128 ℨ
ZeroWidthSpace; U+0200B
Zeta; U+00396 Ζ
zeta; U+003B6 ζ
Zfr; U+02128 ℨ
zfr; U+1D537 𝔷
ZHcy; U+00416 Ж
zhcy; U+00436 ж
zigrarr; U+021DD ⇝
Zopf; U+02124 ℤ
zopf; U+1D56B 𝕫
Zscr; U+1D4B5 𝒵
zscr; U+1D4CF 𝓏
zwj; U+0200D
zwnj; U+0200C
This data is also available as a JSON file.
The glyphs displayed above are non-normative. Refer to the Unicode
specifications for formal definitions of the characters listed above.
The character reference names originate from the XML Entity Definitions
for Characters specification, though only the above is considered
normative. [[XML-ENTITY-NAMES]]
9. The XML syntax
This section only describes the rules for XML resources. Rules for
text/html resources are discussed in the section above entitled "The HTML
syntax".
9.1. Writing documents in the XML syntax
The syntax for using HTML with XML, whether in XHTML documents or embedded
in other XML documents, is defined in the XML and Namespaces in XML
specifications. [XML] [XML-NAMES]
This specification does not define any syntax-level requirements beyond
those defined for XML proper.
XML documents may contain a DOCTYPE if desired, but this is not required
to conform to this specification. This specification does not define a
public or system identifier, nor provide a formal DTD.
According to the XML specification, XML processors are not guaranteed to
process the external DTD subset referenced in the DOCTYPE. This means, for
example, that using entity references for characters in XHTML documents is
unsafe if they are defined in an external file (except for <, >,
&, " and ').
9.2. Parsing XML documents
This section describes the relationship between XML and the DOM, with a
particular emphasis on how this interacts with HTML.
An XML parser, for the purposes of this specification, is a construct that
follows the rules given in the XML specification to map a string of bytes
or characters into a Document object.
At the time of writing, no such rules actually exist.
An XML parser is either associated with a Document object when it is
created, or creates one implicitly.
This Document must then be populated with DOM nodes that represent the
tree structure of the input passed to the parser, as defined by the XML
specification, the Namespaces in XML specification, and the DOM
specification. DOM mutation events must not fire for the operations that
the XML parser performs on the Document’s tree, but the user agent must
act as if elements and attributes were individually appended and set
respectively so as to trigger rules in this specification regarding what
happens when an element is inserted into a document or has its attributes
set, and the DOM specification’s requirements regarding mutation observers
mean that mutation observers are fired (unlike mutation events). [XML]
[XML-NAMES] [DOM41] [UIEVENTS]
Between the time an element’s start tag is parsed and the time either the
element’s end tag is parsed or the parser detects a well-formedness error,
the user agent must act as if the element was in a stack of open elements.
This is used, e.g., by the object element to avoid instantiating plugins
before the param element children have been parsed.
This specification provides the following additional information that user
agents should use when retrieving an external entity: the public
identifiers given in the following list all correspond to the URL given by
this link. (This URL is a DTD containing the entity declarations for the
names listed in the §8.5 Named character references section.) [XML]
* -//W3C//DTD XHTML 1.0 Transitional//EN
* -//W3C//DTD XHTML 1.1//EN
* -//W3C//DTD XHTML 1.0 Strict//EN
* -//W3C//DTD XHTML 1.0 Frameset//EN
* -//W3C//DTD XHTML Basic 1.0//EN
* -//W3C//DTD XHTML 1.1 plus MathML 2.0//EN
* -//W3C//DTD XHTML 1.1 plus MathML 2.0 plus SVG 1.1//EN
* -//W3C//DTD MathML 2.0//EN
* -//WAPFORUM//DTD XHTML Mobile 1.0//EN
Furthermore, user agents should attempt to retrieve the above external
entity’s content when one of the above public identifiers is used, and
should not attempt to retrieve any other external entity’s content.
This is not strictly a violation of the XML specification, but it does
contradict the spirit of the XML specification’s requirements. This is
motivated by a desire for user agents to all handle entities in an
interoperable fashion without requiring any network access for handling
external subsets. [XML]
XML parsers can be invoked with XML scripting support enabled or disabled.
Except where otherwise specified, XML parsers are invoked with XML
scripting support enabled.
When an XML parser with XML scripting support enabled creates a script
element, it must be marked as being "parser-inserted" and its
"non-blocking" flag must be unset. If the parser was originally created
for the XML fragment parsing algorithm, then the element must be marked as
"already started" also. When the element’s end tag is subsequently parsed,
the user agent must perform a microtask checkpoint, and then prepare the
script element. If this causes there to be a pending parsing-blocking
script, then the user agent must run the following steps:
1. Block this instance of the XML parser, such that the event loop will
not run tasks that invoke it.
2. Spin the event loop until the parser’s Document has no style sheet
that is blocking scripts and the pending parsing-blocking script’s
"ready to be parser-executed" flag is set.
3. Unblock this instance of the XML parser, such that tasks that invoke
it can again be run.
4. Execute the pending parsing-blocking script.
5. There is no longer a pending parsing-blocking script.
Since the document.write() API is not available for XML documents, much of
the complexity in the HTML parser is not needed in the XML parser.
When the XML parser has XML scripting support disabled, none of this
happens.
When an XML parser would append a node to a template element, it must
instead append it to the template element’s template contents (a
DocumentFragment node).
This is a willful violation of the XML specification; unfortunately, XML
is not formally extensible in the manner that is needed for template
processing. [XML]
When an XML parser creates a Node object, its node document must be set to
the node document of the node into which the newly created node is to be
inserted.
Certain algorithms in this specification spoon-feed the parser characters
one string at a time. In such cases, the XML parser must act as it would
have if faced with a single string consisting of the concatenation of all
those characters.
When an XML parser reaches the end of its input, it must stop parsing,
following the same rules as the HTML parser. An XML parser can also be
aborted, which must again be done in the same way as for an HTML parser.
For the purposes of conformance checkers, if a resource is determined to
be in the XHTML syntax, then it is an XML document.
9.3. Serializing XML fragments
The XML fragment serialization algorithm for a Document or Element node
either returns a fragment of XML that represents that node or throws an
exception.
For Documents, the algorithm must return a string in the form of a
document entity, if none of the error cases below apply.
For Elements, the algorithm must return a string in the form of an
internal general parsed entity, if none of the error cases below apply.
In both cases, the string returned must be XML namespace-well-formed and
must be an isomorphic serialization of all of that node’s relevant child
nodes, in tree order. User agents may adjust prefixes and namespace
declarations in the serialization (and indeed might be forced to do so in
some cases to obtain namespace-well-formed XML). User agents may use a
combination of regular text and character references to represent Text
nodes in the DOM.
A node’s relevant child nodes are those that apply given the following
rules:
For template elements
The relevant child nodes are the child nodes of the template
element’s template contents, if any.
For all other nodes
The relevant child nodes are the child nodes of node itself, if
any.
For Elements, if any of the elements in the serialization are in no
namespace, the default namespace in scope for those elements must be
explicitly declared as the empty string. (This doesn’t apply in the
Document case.) [XML] [XML-NAMES]
For the purposes of this section, an internal general parsed entity is
considered XML namespace-well-formed if a document consisting of an
element with no namespace declarations whose contents are the internal
general parsed entity would itself be XML namespace-well-formed.
If any of the following error cases are found in the DOM subtree being
serialized, then the algorithm must throw an InvalidStateError exception
instead of returning a string:
* A Document node with no child element nodes.
* A DocumentType node that has an external subset public identifier that
contains characters that are not matched by the XML PubidChar
production. [XML]
* A DocumentType node that has an external subset system identifier that
contains both a U+0022 QUOTATION MARK (") and a U+0027 APOSTROPHE (')
or that contains characters that are not matched by the XML Char
production. [XML]
* A node with a local name containing a U+003A COLON (:).
* A node with a local name that does not match the XML Name production.
[XML]
* An Attr node with no namespace whose local name is the lowercase
string "xmlns". [XML-NAMES]
* An Element node with two or more attributes with the same local name
and namespace.
* An Attr node, Text node, Comment node, or ProcessingInstruction node
whose data contains characters that are not matched by the XML Char
production. [XML]
* A Comment node whose data contains two adjacent U+002D HYPHEN-MINUS
characters (-) or ends with such a character.
* A ProcessingInstruction node whose target name is an ASCII
case-insensitive match for the string "xml".
* A ProcessingInstruction node whose target name contains a U+003A COLON
(:).
* A ProcessingInstruction node whose data contains the string "?>".
These are the only ways to make a DOM unserialisable. The DOM enforces all
the other XML constraints; for example, trying to append two elements to a
Document node will throw a HierarchyRequestError exception.
9.4. Parsing XML fragments
The XML fragment parsing algorithm either returns a Document or throws a
"SyntaxError" DOMException. Given a string input and a context element
context, the algorithm is as follows:
1. Create a new XML parser.
2. Feed the parser just created the string corresponding to the start tag
of the context element, declaring all the namespace prefixes that are
in scope on that element in the DOM, as well as declaring the default
namespace (if any) that is in scope on that element in the DOM.
A namespace prefix is in scope if the DOM lookupNamespaceURI() method
on the element would return a non-null value for that prefix.
The default namespace is the namespace for which the DOM
isDefaultNamespace() method on the element would return true.
No DOCTYPE is passed to the parser, and therefore no external subset
is referenced, and therefore no entities will be recognized.
3. Feed the parser just created the string input.
4. Feed the parser just created the string corresponding to the end tag
of the context element.
5. If there is an XML well-formedness or XML namespace well-formedness
error, then throw a "SyntaxError" DOMException and abort these steps.
6. If the document element of the resulting Document has any sibling
nodes, then throw a "SyntaxError" DOMException and abort these steps.
7. Return the child nodes of the document element of the resulting
Document, in tree order.
10. Rendering
*User agents are not required to present HTML documents in any particular
way. However, this section provides a set of suggestions for rendering
HTML documents that, if followed, are likely to lead to a user experience
that closely resembles the experience intended by the documents' authors.
So as to avoid confusion regarding the normativity of this section, "must"
has not been used. Instead, the term "expected" is used to indicate
behavior that will lead to this experience. For the purposes of
conformance for user agents designated as supporting the suggested default
rendering, the term "expected" in this section has the same conformance
implications as "must".*
10.1. Introduction
In general, user agents are expected to support CSS, and many of the
suggestions in this section are expressed in CSS terms. User agents that
use other presentation mechanisms can derive their expected behavior by
translating from the CSS rules given in this section.
In the absence of style-layer rules to the contrary (e.g., author style
sheets), user agents are expected to render an element so that it conveys
to the user the meaning that the element represents, as described by this
specification.
The suggestions in this section generally assume a visual output medium
with a resolution of 96dpi or greater, but HTML is intended to apply to
multiple media (it is a media-independent language). User agent
implementors are encouraged to adapt the suggestions in this section to
their target media.
----------------------------------------------------------------------
An element is being rendered if it has any associated CSS layout boxes,
SVG layout boxes, or some equivalent in other styling languages.
NOTE: Just being off-screen does not mean the element is not being
rendered. The presence of the hidden attribute normally means the element
is not being rendered, though this might be overridden by the style
sheets.
----------------------------------------------------------------------
User agents that do not honor author-level CSS style sheets are
nonetheless expected to act as if they applied the CSS rules given in
these sections in a manner consistent with this specification and the
relevant CSS and Unicode specifications. [CSS-2015] [UNICODE] [BIDI]
NOTE: This is especially important for issues relating to the display,
unicode-bidi, and direction properties.
10.2. The CSS user agent style sheet and presentational hints
The CSS rules given in these subsections are, except where otherwise
specified, expected to be used as part of the user-agent level style sheet
defaults for all documents that contain HTML elements.
Some rules are intended for the author-level zero-specificity
presentational hints part of the CSS cascade; these are explicitly called
out as presentational hints.
----------------------------------------------------------------------
When the text below says that an attribute attribute on an element element
maps to the pixel length property (or properties) properties, it means
that if element has an attribute attribute set, and parsing that
attribute’s value using the rules for parsing non-negative integers
doesn’t generate an error, then the user agent is expected to use the
parsed value as a pixel length for a presentational hint for properties.
When the text below says that an attribute attribute on an element element
maps to the dimension property (or properties) properties, it means that
if element has an attribute attribute set, and parsing that attribute’s
value using the rules for parsing dimension values doesn’t generate an
error, then the user agent is expected to use the parsed dimension as the
value for a presentational hint for properties, with the value given as a
pixel length if the dimension was a length, and with the value given as a
percentage if the dimension was a percentage.
When the text below says that an attribute attribute on an element element
maps to the dimension property (ignoring zero) (or properties) properties,
it means that if element has an attribute attribute set, and parsing that
attribute’s value using the rules for parsing non-zero dimension values
doesn’t generate an error, then the user agent is expected to use the
parsed dimension as the value for a presentational hint for properties,
with the value given as a pixel length if the dimension was a length, and
with the value given as a percentage if the dimension was a percentage.
When a user agent is to align descendants of a node, the user agent is
expected to align only those descendants that have both their
margin-inline-start and margin-inline-end properties computing to a value
other than auto, that are over-constrained and that have one of those two
margins with a used value forced to a greater value, and that do not
themselves have an applicable align attribute. When multiple elements are
to align a particular descendant, the most deeply nested such element is
expected to override the others. Aligned elements are expected to be
aligned by having the used values of their margins on the line-left and
line-right sides be set accordingly. [CSS-LOGICAL-PROPS]
[CSS-WRITING-MODES-3]
10.3. Non-replaced elements
10.3.1. Hidden elements
@namespace url(http://www.w3.org/1999/xhtml);
[hidden], area, base, basefont, datalist, head, link, meta,
noembed, noframes, param, rp, script, source, style, template, track, title {
display: none;
}
embed[hidden] { display: inline; height: 0; width: 0; }
input[type=hidden i] { display: none !important; }
@media (scripting) {
noscript { display: none !important; }
}
10.3.2. The page
@namespace url(http://www.w3.org/1999/xhtml);
html, body { display: block; }
For each property in the table below, given a body element, the first
attribute that exists maps to the pixel length property on the body
element. If none of the attributes for a property are found, or if the
value of the attribute that was found cannot be parsed successfully, then
a default value of 8px is expected to be used for that property instead.
Property Source
body element’s marginheight attribute
margin-top The body element’s container frame element's marginheight
attribute
body element’s topmargin attribute
body element’s marginwidth attribute
margin-right The body element’s container frame element's marginwidth
attribute
body element’s rightmargin attribute
body element’s marginheight attribute
margin-bottom The body element’s container frame element's marginheight
attribute
body element’s bottommargin attribute
body element’s marginwidth attribute
margin-left The body element’s container frame element's marginwidth
attribute
body element’s leftmargin attribute
If the body element’s node document's browsing context is a nested
browsing context, and the browsing context container of that nested
browsing context is a frame or iframe element, then the container frame
element of the body element is that frame or iframe element. Otherwise,
there is no container frame element.
The above requirements imply that a page can change the margins of another
page (including one from another origin) using, for example, an iframe.
This is potentially a security risk, as it might in some cases allow an
attack to contrive a situation in which a page is rendered not as the
author intended, possibly for the purposes of phishing or otherwise
misleading the user.
----------------------------------------------------------------------
If a Document is in a nested browsing context, it is expected to be
positioned and sized to fit inside the content box of its browsing context
container. If a browsing context's browsing context container is not being
rendered, the browsing context is expected to have a viewport with zero
width and zero height.
If the Document is in a nested browsing context, and the browsing context
container of that nested browsing context is a frame or iframe element,
and that element has a scrolling attribute, and that attribute’s value is
an ASCII case-insensitive match for the string "off", "noscroll", or "no",
then the user agent is expected to prevent any scroll bars from being
shown for the viewport of the nested browsing context, regardless of the
overflow property that applies to that viewport.
----------------------------------------------------------------------
When a body element has a background attribute set to a non-empty value,
the new value is expected to be parsed relative to the element’s node
document, and if this is successful, the user agent is expected to treat
the attribute as a presentational hint setting the element’s
background-image property to the resulting URL string.
When a body element has a bgcolor attribute set, the new value is expected
to be parsed using the rules for parsing a legacy color value, and if that
does not return an error, the user agent is expected to treat the
attribute as a presentational hint setting the element’s background-color
property to the resulting color.
When a body element has a text attribute, its value is expected to be
parsed using the rules for parsing a legacy color value, and if that does
not return an error, the user agent is expected to treat the attribute as
a presentational hint setting the element’s color property to the
resulting color.
When a body element has a link attribute, its value is expected to be
parsed using the rules for parsing a legacy color value, and if that does
not return an error, the user agent is expected to treat the attribute as
a presentational hint setting the color property of any element in the
Document matching the :link pseudo-class to the resulting color.
When a body element has a vlink attribute, its value is expected to be
parsed using the rules for parsing a legacy color value, and if that does
not return an error, the user agent is expected to treat the attribute as
a presentational hint setting the color property of any element in the
Document matching the :visited pseudo-class to the resulting color.
When a body element has an alink attribute, its value is expected to be
parsed using the rules for parsing a legacy color value, and if that does
not return an error, the user agent is expected to treat the attribute as
a presentational hint setting the color property of any element in the
Document matching the :active pseudo-class and either the :link
pseudo-class or the :visited pseudo-class to the resulting color.
10.3.3. Flow content
@namespace url(http://www.w3.org/1999/xhtml);
address, blockquote, center, div, figure, figcaption, footer, form, header, hr,
legend, listing, main, p, plaintext, pre, xmp {
display: block;
}
blockquote, figure, listing, p, plaintext, pre, xmp {
margin-block-start: 1em; margin-block-end: 1em;
}
blockquote, figure { margin-inline-start: 40px; margin-inline-end: 40px; }
address { font-style: italic; }
listing, plaintext, pre, xmp {
font-family: monospace; white-space: pre;
}
dialog:not([open]) { display: none; }
dialog {
position: absolute;
left: 0; right: 0;
width: fit-content;
height: fit-content;
margin: auto;
border: solid;
padding: 1em;
background: white;
color: black;
}
dialog::backdrop {
background: rgba(0,0,0,0.1);
}
/* for small devices, modal dialogs go full-screen */
@media screen and (max-width: 540px) {
dialog:modal {
top: 0;
width: auto;
margin: 1em;
}
}
slot {
display: contents;
}
The following rules are also expected to apply, as presentational hints:
@namespace url(http://www.w3.org/1999/xhtml);
pre[wrap] { white-space: pre-wrap; }
In quirks mode, the following rules are also expected to apply:
@namespace url(http://www.w3.org/1999/xhtml);
form { margin-block-end: 1em; }
----------------------------------------------------------------------
The center element, and the div element when it has an align attribute
whose value is an ASCII case-insensitive match for either the string
"center" or the string "middle", are expected to center text within
themselves, as if they had their text-align property set to center in a
presentational hint, and to align descendants to the center.
The div element, when it has an align attribute whose value is an ASCII
case-insensitive match for the string "left", is expected to left-align
text within itself, as if it had its text-align property set to left in a
presentational hint, and to align descendants to the left.
The div element, when it has an align attribute whose value is an ASCII
case-insensitive match for the string "right", is expected to right-align
text within itself, as if it had its text-align property set to right in a
presentational hint, and to align descendants to the right.
The div element, when it has an align attribute whose value is an ASCII
case-insensitive match for the string "justify", is expected to
full-justify text within itself, as if it had its text-align property set
to justify in a presentational hint, and to align descendants to the left.
10.3.4. Phrasing content
@namespace url(http://www.w3.org/1999/xhtml);
cite, dfn, em, i, var { font-style: italic; }
b, strong { font-weight: bolder; }
code, kbd, samp, tt { font-family: monospace; }
big { font-size: larger; }
small { font-size: smaller; }
sub { vertical-align: sub; }
sup { vertical-align: super; }
sub, sup { line-height: normal; font-size: smaller; }
ruby { display: ruby; }
rt { display: ruby-text; }
:link { color: #0000EE; }
:visited { color: #551A8B; }
:link:active, :visited:active { color: #FF0000; }
:link, :visited { text-decoration: underline; cursor: pointer; }
a:link[rel~=help], a:visited[rel~=help],
area:link[rel~=help], area:visited[rel~=help] { cursor: help; }
:focus { outline: auto; }
mark { background: yellow; color: black; } /* this color is just a suggestion and can be changed based on implementation feedback */
abbr[title], acronym[title] { text-decoration: dotted underline; }
ins, u { text-decoration: underline; }
del, s, strike { text-decoration: line-through; }
blink { text-decoration: blink; }
q::before { content: open-quote; }
q::after { content: close-quote; }
br { display-outside: newline; } /* this also has bidi implications */
nobr { white-space: nowrap; }
wbr { display-outside: break-opportunity; } /* this also has bidi implications */
nobr wbr { white-space: normal; }
The following rules are also expected to apply, as presentational hints:
@namespace url(http://www.w3.org/1999/xhtml);
br[clear=left i] { clear: left; }
br[clear=right i] { clear: right; }
br[clear=all i], br[clear=both i] { clear: both; }
User agents that do not support correct ruby rendering are expected to
render parentheses around the text of rt elements in the absence of rp
elements. [CSS3-RUBY]
----------------------------------------------------------------------
User agents are expected to support the clear property on inline elements
(in order to render br elements with clear attributes) in the manner
described in the non-normative note to this effect in the CSS
specification.
The initial value for the color property is expected to be black. The
initial value for the background-color property is expected to be
transparent. The canvas' background is expected to be white.
----------------------------------------------------------------------
When a font element has a color attribute, its value is expected to be
parsed using the rules for parsing a legacy color value, and if that does
not return an error, the user agent is expected to treat the attribute as
a presentational hint setting the element’s color property to the
resulting color.
The font element is expected to override the color of any text decoration
that spans the text of the element to the used value of the element’s
color property.
When a font element has a face attribute, the user agent is expected to
treat the attribute as a presentational hint setting the element’s
font-family property to the attribute’s value.
When a font element has a size attribute, the user agent is expected to
use the following steps, known as the rules for parsing a legacy font
size, to treat the attribute as a presentational hint setting the
element’s font-size property:
1. Let input be the attribute’s value.
2. Let position be a pointer into input, initially pointing at the start
of the string.
3. Skip white space.
4. If position is past the end of input, there is no presentational hint.
Abort these steps.
5. If the character at position is a U+002B PLUS SIGN character (+), then
let mode be relative-plus, and advance position to the next character.
Otherwise, if the character at position is a U+002D HYPHEN-MINUS
character (-), then let mode be relative-minus, and advance position
to the next character. Otherwise, let mode be absolute.
6. Collect a sequence of characters that are ASCII digits, and let the
resulting sequence be digits.
7. If digits is the empty string, there is no presentational hint. Abort
these steps.
8. Interpret digits as a base-ten integer. Let value be the resulting
number.
9. If mode is relative-plus, then increment value by 3. If mode is
relative-minus, then let value be the result of subtracting value from
3.
10. If value is greater than 7, let it be 7.
11. If value is less than 1, let it be 1.
12. Set font-size to the keyword corresponding to the value of value
according to the following table:
value font-size keyword Notes
1 x-small
2 small
3 medium
4 large
5 x-large
6 xx-large
7 xxx-large see below
The xxx-large value is a non-CSS value used here to indicate a font
size 50% larger than xx-large.
10.3.5. Bidirectional text
@namespace url(http://www.w3.org/1999/xhtml);
[dir]:dir(ltr), bdi:dir(ltr), input[type=tel i]:dir(ltr) { direction: ltr; }
[dir]:dir(rtl), bdi:dir(rtl) { direction: rtl; }
address, blockquote, center, div, figure, figcaption, footer, form, header, hr,
legend, listing, main, p, plaintext, pre, summary, xmp, article, aside, h1, h2,
h3, h4, h5, h6, hgroup, nav, section, table, caption, colgroup, col, thead,
tbody, tfoot, tr, td, th, dir, dd, dl, dt, ol, ul, li, bdi, output,
[dir=ltr i], [dir=rtl i], [dir=auto i] {
unicode-bidi: isolate;
}
bdo, bdo[dir] { unicode-bidi: isolate-override; }
input[dir=auto i]:matches([type=search i], [type=tel i], [type=url i],
[type=email i]), textarea[dir=auto i], pre[dir=auto i] {
unicode-bidi: plaintext;
}
/* see prose for input elements whose type attribute is in the Text state */
/* the rules setting the 'content' property on <br> and <wbr> elements also has bidi implications */
When an input element’s dir attribute is in the auto state and its type
attribute is in the Text state, then the user agent is expected to act as
if it had a user-agent-level style sheet rule setting the unicode-bidi
property to plaintext.
Input fields (i.e., textarea elements, and input elements when their type
attribute is in the Text, Search, Telephone, URL, or E-mail state) are
expected to present an editing user interface with a directionality that
matches the element’s direction property.
When the document’s character encoding is ISO-8859-8, the following rules
are additionally expected to apply, following those above: [ENCODING]
@namespace url(http://www.w3.org/1999/xhtml);
address, blockquote, center, div, figure, figcaption, footer, form, header, hr,
legend, listing, main, p, plaintext, pre, summary, xmp, article, aside, h1, h2,
h3, h4, h5, h6, hgroup, nav, section, table, caption, colgroup, col, thead,
tbody, tfoot, tr, td, th, dir, dd, dl, dt, ol, ul, li, [dir=ltr i],
[dir=rtl i], [dir=auto i], *|* {
unicode-bidi: bidi-override;
}
input:not([type=submit i]):not([type=reset i]):not([type=button i]),
textarea {
unicode-bidi: normal;
}
10.3.6. Quotes
This block is automatically generated from the Unicode Common Locale Data
Repository. [CLDR]
User agents are expected to use either the block below (which will be
regularly updated) or to automatically generate their own copy directly
from the source material. The language codes are derived from the CLDR
file names. The quotes are derived from the delimiter blocks, with
fallback handled as specified in the CLDR documentation.
@namespace url(http://www.w3.org/1999/xhtml);
:root { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(af), :not(:lang(af)) > :lang(af) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(agq), :not(:lang(agq)) > :lang(agq) { quotes: '\201e' '\201d' '\201a' '\2019' } /* „ ” ‚ ’ */
:root:lang(ak), :not(:lang(ak)) > :lang(ak) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(am), :not(:lang(am)) > :lang(am) { quotes: '\00ab' '\00bb' '\2039' '\203a' } /* « » ‹ › */
:root:lang(ar), :not(:lang(ar)) > :lang(ar) { quotes: '\201d' '\201c' '\2019' '\2018' } /* ” “ ’ ‘ */
:root:lang(asa), :not(:lang(asa)) > :lang(asa) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ast), :not(:lang(ast)) > :lang(ast) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(az), :not(:lang(az)) > :lang(az) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(az-Cyrl), :not(:lang(az-Cyrl)) > :lang(az-Cyrl) { quotes: '\00ab' '\00bb' '\2039' '\203a' } /* « » ‹ › */
:root:lang(bas), :not(:lang(bas)) > :lang(bas) { quotes: '\00ab' '\00bb' '\201e' '\201c' } /* « » „ “ */
:root:lang(be), :not(:lang(be)) > :lang(be) { quotes: '\00ab' '\00bb' '\00ab' '\00bb' } /* « » « » */
:root:lang(bem), :not(:lang(bem)) > :lang(bem) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(bez), :not(:lang(bez)) > :lang(bez) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(bg), :not(:lang(bg)) > :lang(bg) { quotes: '\201e' '\201c' '\201e' '\201c' } /* „ “ „ “ */
:root:lang(bm), :not(:lang(bm)) > :lang(bm) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(bn), :not(:lang(bn)) > :lang(bn) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(br), :not(:lang(br)) > :lang(br) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(brx), :not(:lang(brx)) > :lang(brx) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(bs), :not(:lang(bs)) > :lang(bs) { quotes: '\201e' '\201c' '\2018' '\2019' } /* „ “ ‘ ’ */
:root:lang(bs-Cyrl), :not(:lang(bs-Cyrl)) > :lang(bs-Cyrl) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(ca), :not(:lang(ca)) > :lang(ca) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(cgg), :not(:lang(cgg)) > :lang(cgg) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(chr), :not(:lang(chr)) > :lang(chr) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(cs), :not(:lang(cs)) > :lang(cs) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(cy), :not(:lang(cy)) > :lang(cy) { quotes: '\2018' '\2019' '\201c' '\201d' } /* ‘ ’ “ ” */
:root:lang(da), :not(:lang(da)) > :lang(da) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(dav), :not(:lang(dav)) > :lang(dav) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(de), :not(:lang(de)) > :lang(de) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(dje), :not(:lang(dje)) > :lang(dje) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(dsb), :not(:lang(dsb)) > :lang(dsb) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(dua), :not(:lang(dua)) > :lang(dua) { quotes: '\00ab' '\00bb' '\2018' '\2019' } /* « » ‘ ’ */
:root:lang(dyo), :not(:lang(dyo)) > :lang(dyo) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(dz), :not(:lang(dz)) > :lang(dz) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ebu), :not(:lang(ebu)) > :lang(ebu) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ee), :not(:lang(ee)) > :lang(ee) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(el), :not(:lang(el)) > :lang(el) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(en), :not(:lang(en)) > :lang(en) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(es), :not(:lang(es)) > :lang(es) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(et), :not(:lang(et)) > :lang(et) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(eu), :not(:lang(eu)) > :lang(eu) { quotes: '\201c' '\201d' '\201c' '\201d' } /* “ ” “ ” */
:root:lang(ewo), :not(:lang(ewo)) > :lang(ewo) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(fa), :not(:lang(fa)) > :lang(fa) { quotes: '\00ab' '\00bb' '\2039' '\203a' } /* « » ‹ › */
:root:lang(ff), :not(:lang(ff)) > :lang(ff) { quotes: '\201e' '\201d' '\201a' '\2019' } /* „ ” ‚ ’ */
:root:lang(fi), :not(:lang(fi)) > :lang(fi) { quotes: '\201d' '\201d' '\2019' '\2019' } /* ” ” ’ ’ */
:root:lang(fil), :not(:lang(fil)) > :lang(fil) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(fo), :not(:lang(fo)) > :lang(fo) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(fr), :not(:lang(fr)) > :lang(fr) { quotes: '\00ab' '\00bb' '\00ab' '\00bb' } /* « » « » */
:root:lang(fr-CH), :not(:lang(fr-CH)) > :lang(fr-CH) { quotes: '\00ab' '\00bb' '\2039' '\203a' } /* « » ‹ › */
:root:lang(ga), :not(:lang(ga)) > :lang(ga) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(gd), :not(:lang(gd)) > :lang(gd) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(gl), :not(:lang(gl)) > :lang(gl) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(gsw), :not(:lang(gsw)) > :lang(gsw) { quotes: '\00ab' '\00bb' '\2039' '\203a' } /* « » ‹ › */
:root:lang(gu), :not(:lang(gu)) > :lang(gu) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(guz), :not(:lang(guz)) > :lang(guz) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ha), :not(:lang(ha)) > :lang(ha) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(he), :not(:lang(he)) > :lang(he) { quotes: '\201d' '\201d' '\2019' '\2019' } /* ” ” ’ ’ */
:root:lang(hi), :not(:lang(hi)) > :lang(hi) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(hr), :not(:lang(hr)) > :lang(hr) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(hsb), :not(:lang(hsb)) > :lang(hsb) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(hu), :not(:lang(hu)) > :lang(hu) { quotes: '\201e' '\201d' '\00bb' '\00ab' } /* „ ” » « */
:root:lang(hy), :not(:lang(hy)) > :lang(hy) { quotes: '\00ab' '\00bb' '\00ab' '\00bb' } /* « » « » */
:root:lang(id), :not(:lang(id)) > :lang(id) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ig), :not(:lang(ig)) > :lang(ig) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(is), :not(:lang(is)) > :lang(is) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(it), :not(:lang(it)) > :lang(it) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(ja), :not(:lang(ja)) > :lang(ja) { quotes: '\300c' '\300d' '\300e' '\300f' } /* 「 」 『 』 */
:root:lang(jgo), :not(:lang(jgo)) > :lang(jgo) { quotes: '\00ab' '\00bb' '\2039' '\203a' } /* « » ‹ › */
:root:lang(jmc), :not(:lang(jmc)) > :lang(jmc) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ka), :not(:lang(ka)) > :lang(ka) { quotes: '\201e' '\201c' '\00ab' '\00bb' } /* „ “ « » */
:root:lang(kab), :not(:lang(kab)) > :lang(kab) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(kam), :not(:lang(kam)) > :lang(kam) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(kde), :not(:lang(kde)) > :lang(kde) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(kea), :not(:lang(kea)) > :lang(kea) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(khq), :not(:lang(khq)) > :lang(khq) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ki), :not(:lang(ki)) > :lang(ki) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(kk), :not(:lang(kk)) > :lang(kk) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(kkj), :not(:lang(kkj)) > :lang(kkj) { quotes: '\00ab' '\00bb' '\2039' '\203a' } /* « » ‹ › */
:root:lang(kln), :not(:lang(kln)) > :lang(kln) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(km), :not(:lang(km)) > :lang(km) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(kn), :not(:lang(kn)) > :lang(kn) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ko), :not(:lang(ko)) > :lang(ko) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ksb), :not(:lang(ksb)) > :lang(ksb) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ksf), :not(:lang(ksf)) > :lang(ksf) { quotes: '\00ab' '\00bb' '\2018' '\2019' } /* « » ‘ ’ */
:root:lang(ky), :not(:lang(ky)) > :lang(ky) { quotes: '\00ab' '\00bb' '\201e' '\201c' } /* « » „ “ */
:root:lang(lag), :not(:lang(lag)) > :lang(lag) { quotes: '\201d' '\201d' '\2019' '\2019' } /* ” ” ’ ’ */
:root:lang(lb), :not(:lang(lb)) > :lang(lb) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(lg), :not(:lang(lg)) > :lang(lg) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ln), :not(:lang(ln)) > :lang(ln) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(lo), :not(:lang(lo)) > :lang(lo) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(lrc), :not(:lang(lrc)) > :lang(lrc) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(lt), :not(:lang(lt)) > :lang(lt) { quotes: '\201e' '\201c' '\201e' '\201c' } /* „ “ „ “ */
:root:lang(lu), :not(:lang(lu)) > :lang(lu) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(luo), :not(:lang(luo)) > :lang(luo) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(luy), :not(:lang(luy)) > :lang(luy) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(lv), :not(:lang(lv)) > :lang(lv) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(mas), :not(:lang(mas)) > :lang(mas) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(mer), :not(:lang(mer)) > :lang(mer) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(mfe), :not(:lang(mfe)) > :lang(mfe) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(mg), :not(:lang(mg)) > :lang(mg) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(mgo), :not(:lang(mgo)) > :lang(mgo) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(mk), :not(:lang(mk)) > :lang(mk) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(ml), :not(:lang(ml)) > :lang(ml) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(mn), :not(:lang(mn)) > :lang(mn) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(mr), :not(:lang(mr)) > :lang(mr) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ms), :not(:lang(ms)) > :lang(ms) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(mt), :not(:lang(mt)) > :lang(mt) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(mua), :not(:lang(mua)) > :lang(mua) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(my), :not(:lang(my)) > :lang(my) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(mzn), :not(:lang(mzn)) > :lang(mzn) { quotes: '\00ab' '\00bb' '\2039' '\203a' } /* « » ‹ › */
:root:lang(naq), :not(:lang(naq)) > :lang(naq) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(nb), :not(:lang(nb)) > :lang(nb) { quotes: '\00ab' '\00bb' '\2018' '\2019' } /* « » ‘ ’ */
:root:lang(nd), :not(:lang(nd)) > :lang(nd) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ne), :not(:lang(ne)) > :lang(ne) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(nl), :not(:lang(nl)) > :lang(nl) { quotes: '\2018' '\2019' '\201c' '\201d' } /* ‘ ’ “ ” */
:root:lang(nmg), :not(:lang(nmg)) > :lang(nmg) { quotes: '\201e' '\201d' '\00ab' '\00bb' } /* „ ” « » */
:root:lang(nn), :not(:lang(nn)) > :lang(nn) { quotes: '\00ab' '\00bb' '\2018' '\2019' } /* « » ‘ ’ */
:root:lang(nnh), :not(:lang(nnh)) > :lang(nnh) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(nus), :not(:lang(nus)) > :lang(nus) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(nyn), :not(:lang(nyn)) > :lang(nyn) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(pa), :not(:lang(pa)) > :lang(pa) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(pl), :not(:lang(pl)) > :lang(pl) { quotes: '\201e' '\201d' '\00ab' '\00bb' } /* „ ” « » */
:root:lang(pt), :not(:lang(pt)) > :lang(pt) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(pt-PT), :not(:lang(pt-PT)) > :lang(pt-PT) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(rn), :not(:lang(rn)) > :lang(rn) { quotes: '\201d' '\201d' '\2019' '\2019' } /* ” ” ’ ’ */
:root:lang(ro), :not(:lang(ro)) > :lang(ro) { quotes: '\201e' '\201d' '\00ab' '\00bb' } /* „ ” « » */
:root:lang(rof), :not(:lang(rof)) > :lang(rof) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ru), :not(:lang(ru)) > :lang(ru) { quotes: '\00ab' '\00bb' '\201e' '\201c' } /* « » „ “ */
:root:lang(rw), :not(:lang(rw)) > :lang(rw) { quotes: '\00ab' '\00bb' '\2018' '\2019' } /* « » ‘ ’ */
:root:lang(rwk), :not(:lang(rwk)) > :lang(rwk) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(saq), :not(:lang(saq)) > :lang(saq) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(sbp), :not(:lang(sbp)) > :lang(sbp) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(seh), :not(:lang(seh)) > :lang(seh) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ses), :not(:lang(ses)) > :lang(ses) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(sg), :not(:lang(sg)) > :lang(sg) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(shi), :not(:lang(shi)) > :lang(shi) { quotes: '\00ab' '\00bb' '\201e' '\201d' } /* « » „ ” */
:root:lang(shi-Latn), :not(:lang(shi-Latn)) > :lang(shi-Latn) { quotes: '\00ab' '\00bb' '\201e' '\201d' } /* « » „ ” */
:root:lang(si), :not(:lang(si)) > :lang(si) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(sk), :not(:lang(sk)) > :lang(sk) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(sl), :not(:lang(sl)) > :lang(sl) { quotes: '\201e' '\201c' '\201a' '\2018' } /* „ “ ‚ ‘ */
:root:lang(sn), :not(:lang(sn)) > :lang(sn) { quotes: '\201d' '\201d' '\2019' '\2019' } /* ” ” ’ ’ */
:root:lang(so), :not(:lang(so)) > :lang(so) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(sq), :not(:lang(sq)) > :lang(sq) { quotes: '\00ab' '\00bb' '\201c' '\201d' } /* « » “ ” */
:root:lang(sr), :not(:lang(sr)) > :lang(sr) { quotes: '\201e' '\201c' '\2018' '\2018' } /* „ “ ‘ ‘ */
:root:lang(sr-Latn), :not(:lang(sr-Latn)) > :lang(sr-Latn) { quotes: '\201e' '\201c' '\2018' '\2018' } /* „ “ ‘ ‘ */
:root:lang(sv), :not(:lang(sv)) > :lang(sv) { quotes: '\201d' '\201d' '\2019' '\2019' } /* ” ” ’ ’ */
:root:lang(sw), :not(:lang(sw)) > :lang(sw) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ta), :not(:lang(ta)) > :lang(ta) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(te), :not(:lang(te)) > :lang(te) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(teo), :not(:lang(teo)) > :lang(teo) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(th), :not(:lang(th)) > :lang(th) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(ti-ER), :not(:lang(ti-ER)) > :lang(ti-ER) { quotes: '\2018' '\2019' '\201c' '\201d' } /* ‘ ’ “ ” */
:root:lang(tk), :not(:lang(tk)) > :lang(tk) { quotes: '\201c' '\201d' '\201c' '\201d' } /* “ ” “ ” */
:root:lang(to), :not(:lang(to)) > :lang(to) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(tr), :not(:lang(tr)) > :lang(tr) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(twq), :not(:lang(twq)) > :lang(twq) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(tzm), :not(:lang(tzm)) > :lang(tzm) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(uk), :not(:lang(uk)) > :lang(uk) { quotes: '\00ab' '\00bb' '\201e' '\201c' } /* « » „ “ */
:root:lang(ur), :not(:lang(ur)) > :lang(ur) { quotes: '\201d' '\201c' '\2019' '\2018' } /* ” “ ’ ‘ */
:root:lang(uz), :not(:lang(uz)) > :lang(uz) { quotes: '\201c' '\201d' '\2019' '\2018' } /* “ ” ’ ‘ */
:root:lang(uz-Cyrl), :not(:lang(uz-Cyrl)) > :lang(uz-Cyrl) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(vai), :not(:lang(vai)) > :lang(vai) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(vai-Latn), :not(:lang(vai-Latn)) > :lang(vai-Latn) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(vi), :not(:lang(vi)) > :lang(vi) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(vun), :not(:lang(vun)) > :lang(vun) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(xog), :not(:lang(xog)) > :lang(xog) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(yav), :not(:lang(yav)) > :lang(yav) { quotes: '\00ab' '\00bb' '\00ab' '\00bb' } /* « » « » */
:root:lang(yo), :not(:lang(yo)) > :lang(yo) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(yo-BJ), :not(:lang(yo-BJ)) > :lang(yo-BJ) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(yue), :not(:lang(yue)) > :lang(yue) { quotes: '\300c' '\300d' '\300e' '\300f' } /* 「 」 『 』 */
:root:lang(zgh), :not(:lang(zgh)) > :lang(zgh) { quotes: '\00ab' '\00bb' '\201e' '\201d' } /* « » „ ” */
:root:lang(zh), :not(:lang(zh)) > :lang(zh) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
:root:lang(zh-Hant), :not(:lang(zh-Hant)) > :lang(zh-Hant) { quotes: '\300c' '\300d' '\300e' '\300f' } /* 「 」 『 』 */
:root:lang(zu), :not(:lang(zu)) > :lang(zu) { quotes: '\201c' '\201d' '\2018' '\2019' } /* “ ” ‘ ’ */
10.3.7. Sections and headings
@namespace url(http://www.w3.org/1999/xhtml);
article, aside, h1, h2, h3, h4, h5, h6, hgroup, nav, section {
display: block;
}
h1 { margin-block-start: 0.67em; margin-block-end: 0.67em; font-size: 2.00em; font-weight: bold; }
h2 { margin-block-start: 0.83em; margin-block-end: 0.83em; font-size: 1.50em; font-weight: bold; }
h3 { margin-block-start: 1.00em; margin-block-end: 1.00em; font-size: 1.17em; font-weight: bold; }
h4 { margin-block-start: 1.33em; margin-block-end: 1.33em; font-size: 1.00em; font-weight: bold; }
h5 { margin-block-start: 1.67em; margin-block-end: 1.67em; font-size: 0.83em; font-weight: bold; }
h6 { margin-block-start: 2.33em; margin-block-end: 2.33em; font-size: 0.67em; font-weight: bold; }
In the following CSS block, x is shorthand for the following selector:
:matches(article, aside, nav, section)
@namespace url(http://www.w3.org/1999/xhtml);
x h1 { margin-block-start: 0.83em; margin-block-end: 0.83em; font-size: 1.50em; }
x x h1 { margin-block-start: 1.00em; margin-block-end: 1.00em; font-size: 1.17em; }
x x x h1 { margin-block-start: 1.33em; margin-block-end: 1.33em; font-size: 1.00em; }
x x x x h1 { margin-block-start: 1.67em; margin-block-end: 1.67em; font-size: 0.83em; }
x x x x x h1 { margin-block-start: 2.33em; margin-block-end: 2.33em; font-size: 0.67em; }
x hgroup > h1 ~ h2 { margin-block-start: 1.00em; margin-block-end: 1.00em; font-size: 1.17em; }
x x hgroup > h1 ~ h2 { margin-block-start: 1.33em; margin-block-end: 1.33em; font-size: 1.00em; }
x x x hgroup > h1 ~ h2 { margin-block-start: 1.67em; margin-block-end: 1.67em; font-size: 0.83em; }
x x x x hgroup > h1 ~ h2 { margin-block-start: 2.33em; margin-block-end: 2.33em; font-size: 0.67em; }
x hgroup > h1 ~ h3 { margin-block-start: 1.33em; margin-block-end: 1.33em; font-size: 1.00em; }
x x hgroup > h1 ~ h3 { margin-block-start: 1.67em; margin-block-end: 1.67em; font-size: 0.83em; }
x x x hgroup > h1 ~ h3 { margin-block-start: 2.33em; margin-block-end: 2.33em; font-size: 0.67em; }
x hgroup > h1 ~ h4 { margin-block-start: 1.67em; margin-block-end: 1.67em; font-size: 0.83em; }
x x hgroup > h1 ~ h4 { margin-block-start: 2.33em; margin-block-end: 2.33em; font-size: 0.67em; }
x hgroup > h1 ~ h5 { margin-block-start: 2.33em; margin-block-end: 2.33em; font-size: 0.67em; }
NOTE: The shorthand is used to keep this block at least mildly readable.
10.3.8. Lists
@namespace url(http://www.w3.org/1999/xhtml);
dir, dd, dl, dt, ol, ul { display: block; }
li { display: list-item; }
dir, dl, ol, ul { margin-block-start: 1em; margin-block-end: 1em; }
:matches(dir, dl, ol, ul) :matches(dir, dl, ol, ul) {
margin-block-start: 0; margin-block-end: 0;
}
dd { margin-inline-start: 40px; }
dir, ol, ul { padding-inline-start: 40px; }
ol { list-style-type: decimal; }
dir, ul {
list-style-type: disc;
}
:matches(dir, ol, ul) :matches(dir, ul) {
list-style-type: circle;
}
:matches(dir, ol, ul) :matches(dir, ol, ul) :matches(dir, ul) {
list-style-type: square;
}
The following rules are also expected to apply, as presentational hints:
@namespace url(http://www.w3.org/1999/xhtml);
ol[type=1], li[type=1] { list-style-type: decimal; }
ol[type=a], li[type=a] { list-style-type: lower-alpha; }
ol[type=A], li[type=A] { list-style-type: upper-alpha; }
ol[type=i], li[type=i] { list-style-type: lower-roman; }
ol[type=I], li[type=I] { list-style-type: upper-roman; }
ul[type=none i], li[type=none i] { list-style-type: none; }
ul[type=disc i], li[type=disc i] { list-style-type: disc; }
ul[type=circle i], li[type=circle i] { list-style-type: circle; }
ul[type=square i], li[type=square i] { list-style-type: square; }
In the above stylesheet, the attribute selectors for the ol and li
elements are expected to be treated as case-sensitive.
When rendering li elements, non-CSS user agents are expected to use the
ordinal value of the li element to render the counter in the list item
marker.
This specification does not yet define the CSS-specific rules for
rendering li elements, because CSS doesn’t yet provide sufficient hooks
for this purpose.
10.3.9. Tables
@namespace url(http://www.w3.org/1999/xhtml);
table { display: table; }
caption { display: table-caption; }
colgroup, colgroup[hidden] { display: table-column-group; }
col, col[hidden] { display: table-column; }
thead, thead[hidden] { display: table-header-group; }
tbody, tbody[hidden] { display: table-row-group; }
tfoot, tfoot[hidden] { display: table-footer-group; }
tr, tr[hidden] { display: table-row; }
td, th, td[hidden], th[hidden] { display: table-cell; }
colgroup[hidden], col[hidden], thead[hidden], tbody[hidden],
tfoot[hidden], tr[hidden], td[hidden], th[hidden] {
visibility: collapse;
}
table {
box-sizing: border-box;
border-spacing: 2px;
border-collapse: separate;
text-indent: initial;
}
td, th { padding: 1px; }
th { font-weight: bold; }
caption { text-align: center; }
thead, tbody, tfoot, table > tr { vertical-align: middle; }
tr, td, th { vertical-align: inherit; }
table, td, th { border-color: gray; }
thead, tbody, tfoot, tr { border-color: inherit; }
table[rules=none i], table[rules=groups i], table[rules=rows i],
table[rules=cols i], table[rules=all i], table[frame=void i],
table[frame=above i], table[frame=below i], table[frame=hsides i],
table[frame=lhs i], table[frame=rhs i], table[frame=vsides i],
table[frame=box i], table[frame=border i],
table[rules=none i] > tr > td, table[rules=none i] > tr > th,
table[rules=groups i] > tr > td, table[rules=groups i] > tr > th,
table[rules=rows i] > tr > td, table[rules=rows i] > tr > th,
table[rules=cols i] > tr > td, table[rules=cols i] > tr > th,
table[rules=all i] > tr > td, table[rules=all i] > tr > th,
table[rules=none i] > thead > tr > td, table[rules=none i] > thead > tr > th,
table[rules=groups i] > thead > tr > td, table[rules=groups i] > thead > tr > th,
table[rules=rows i] > thead > tr > td, table[rules=rows i] > thead > tr > th,
table[rules=cols i] > thead > tr > td, table[rules=cols i] > thead > tr > th,
table[rules=all i] > thead > tr > td, table[rules=all i] > thead > tr > th,
table[rules=none i] > tbody > tr > td, table[rules=none i] > tbody > tr > th,
table[rules=groups i] > tbody > tr > td, table[rules=groups i] > tbody > tr > th,
table[rules=rows i] > tbody > tr > td, table[rules=rows i] > tbody > tr > th,
table[rules=cols i] > tbody > tr > td, table[rules=cols i] > tbody > tr > th,
table[rules=all i] > tbody > tr > td, table[rules=all i] > tbody > tr > th,
table[rules=none i] > tfoot > tr > td, table[rules=none i] > tfoot > tr > th,
table[rules=groups i] > tfoot > tr > td, table[rules=groups i] > tfoot > tr > th,
table[rules=rows i] > tfoot > tr > td, table[rules=rows i] > tfoot > tr > th,
table[rules=cols i] > tfoot > tr > td, table[rules=cols i] > tfoot > tr > th,
table[rules=all i] > tfoot > tr > td, table[rules=all i] > tfoot > tr > th {
border-color: black;
}
The following rules are also expected to apply, as presentational hints:
@namespace url(http://www.w3.org/1999/xhtml);
table[align=left i] { float: left; }
table[align=right i] { float: right; }
table[align=center i] { margin-inline-start: auto; margin-inline-end: auto; }
thead[align=absmiddle i], tbody[align=absmiddle i], tfoot[align=absmiddle i],
tr[align=absmiddle i], td[align=absmiddle i], th[align=absmiddle i] {
text-align: center;
}
caption[align=bottom i] { caption-side: bottom; }
p[align=left i], h1[align=left i], h2[align=left i], h3[align=left i],
h4[align=left i], h5[align=left i], h6[align=left i] {
text-align: left;
}
p[align=right i], h1[align=right i], h2[align=right i], h3[align=right i],
h4[align=right i], h5[align=right i], h6[align=right i] {
text-align: right;
}
p[align=center i], h1[align=center i], h2[align=center i], h3[align=center i],
h4[align=center i], h5[align=center i], h6[align=center i] {
text-align: center;
}
p[align=justify i], h1[align=justify i], h2[align=justify i], h3[align=justify i],
h4[align=justify i], h5[align=justify i], h6[align=justify i] {
text-align: justify;
}
thead[valign=top i], tbody[valign=top i], tfoot[valign=top i],
tr[valign=top i], td[valign=top i], th[valign=top i] {
vertical-align: top;
}
thead[valign=middle i], tbody[valign=middle i], tfoot[valign=middle i],
tr[valign=middle i], td[valign=middle i], th[valign=middle i] {
vertical-align: middle;
}
thead[valign=bottom i], tbody[valign=bottom i], tfoot[valign=bottom i],
tr[valign=bottom i], td[valign=bottom i], th[valign=bottom i] {
vertical-align: bottom;
}
thead[valign=baseline i], tbody[valign=baseline i], tfoot[valign=baseline i],
tr[valign=baseline i], td[valign=baseline i], th[valign=baseline i] {
vertical-align: baseline;
}
td[nowrap], th[nowrap] { white-space: nowrap; }
table[rules=none i], table[rules=groups i], table[rules=rows i],
table[rules=cols i], table[rules=all i] {
border-style: hidden;
border-collapse: collapse;
}
table[border] { border-style: outset; } /* only if border is not equivalent to zero */
table[frame=void i] { border-style: hidden; }
table[frame=above i] { border-style: outset hidden hidden hidden; }
table[frame=below i] { border-style: hidden hidden outset hidden; }
table[frame=hsides i] { border-style: outset hidden outset hidden; }
table[frame=lhs i] { border-style: hidden hidden hidden outset; }
table[frame=rhs i] { border-style: hidden outset hidden hidden; }
table[frame=vsides i] { border-style: hidden outset; }
table[frame=box i], table[frame=border i] { border-style: outset; }
table[border] > tr > td, table[border] > tr > th,
table[border] > thead > tr > td, table[border] > thead > tr > th,
table[border] > tbody > tr > td, table[border] > tbody > tr > th,
table[border] > tfoot > tr > td, table[border] > tfoot > tr > th {
/* only if border is not equivalent to zero */
border-width: 1px;
border-style: inset;
}
table[rules=none i] > tr > td, table[rules=none i] > tr > th,
table[rules=none i] > thead > tr > td, table[rules=none i] > thead > tr > th,
table[rules=none i] > tbody > tr > td, table[rules=none i] > tbody > tr > th,
table[rules=none i] > tfoot > tr > td, table[rules=none i] > tfoot > tr > th,
table[rules=groups i] > tr > td, table[rules=groups i] > tr > th,
table[rules=groups i] > thead > tr > td, table[rules=groups i] > thead > tr > th,
table[rules=groups i] > tbody > tr > td, table[rules=groups i] > tbody > tr > th,
table[rules=groups i] > tfoot > tr > td, table[rules=groups i] > tfoot > tr > th,
table[rules=rows i] > tr > td, table[rules=rows i] > tr > th,
table[rules=rows i] > thead > tr > td, table[rules=rows i] > thead > tr > th,
table[rules=rows i] > tbody > tr > td, table[rules=rows i] > tbody > tr > th,
table[rules=rows i] > tfoot > tr > td, table[rules=rows i] > tfoot > tr > th {
border-width: 1px;
border-style: none;
}
table[rules=cols i] > tr > td, table[rules=cols i] > tr > th,
table[rules=cols i] > thead > tr > td, table[rules=cols i] > thead > tr > th,
table[rules=cols i] > tbody > tr > td, table[rules=cols i] > tbody > tr > th,
table[rules=cols i] > tfoot > tr > td, table[rules=cols i] > tfoot > tr > th {
border-width: 1px;
block-start-style: none;
border-inline-end-style: solid;
border-block-end-style: none;
border-inline-start-style: solid;
}
table[rules=all i] > tr > td, table[rules=all i] > tr > th,
table[rules=all i] > thead > tr > td, table[rules=all i] > thead > tr > th,
table[rules=all i] > tbody > tr > td, table[rules=all i] > tbody > tr > th,
table[rules=all i] > tfoot > tr > td, table[rules=all i] > tfoot > tr > th {
border-width: 1px;
border-style: solid;
}
table[rules=groups i] > colgroup {
border-inline-start-width: 1px;
border-inline-start-style: solid;
border-inline-end-width: 1px;
border-inline-end-style: solid;
}
table[rules=groups i] > thead,
table[rules=groups i] > tbody,
table[rules=groups i] > tfoot {
border-block-start-width: 1px;
border-block-start-style: solid;
border-block-end-width: 1px;
border-block-end-style: solid;
}
table[rules=rows i] > tr, table[rules=rows i] > thead > tr,
table[rules=rows i] > tbody > tr, table[rules=rows i] > tfoot > tr {
border-block-start-width: 1px;
border-block-start-style: solid;
border-block-end-width: 1px;
border-block-end-style: solid;
}
In quirks mode, the following rules are also expected to apply:
@namespace url(http://www.w3.org/1999/xhtml);
table {
font-weight: initial;
font-style: initial;
font-variant: initial;
font-size: initial;
line-height: initial;
white-space: initial;
text-align: initial;
}
----------------------------------------------------------------------
For the purposes of the CSS table model, the col element is expected to be
treated as if it was present as many times as its span attribute
specifies.
For the purposes of the CSS table model, the colgroup element, if it
contains no col element, is expected to be treated as if it had as many
such children as its span attribute specifies.
For the purposes of the CSS table model, the colspan and rowspan
attributes on td and th elements are expected to provide the special
knowledge regarding cells spanning rows and columns.
In HTML documents, the following rules are also expected to apply:
@namespace url(http://www.w3.org/1999/xhtml);
:matches(table, thead, tbody, tfoot, tr) > form { display: none !important; }
----------------------------------------------------------------------
The table element’s cellspacing attribute maps to the pixel length
property border-spacing on the element.
The table element’s cellpadding attribute maps to the pixel length
properties padding-top, padding-right, padding-bottom, and padding-left of
any td and th elements that have corresponding cells in the table
corresponding to the table element.
The table element’s height attribute maps to the dimension property
(ignoring zero) height on the table element.
The table element’s width attribute maps to the dimension property
(ignoring zero) width on the table element.
The col element’s width attribute maps to the dimension property (ignoring
zero) width on the col element.
The tr element’s height attribute maps to the dimension property (ignoring
zero) height on the tr element.
The td and th elements' height attributes map to the dimension property
(ignoring zero) height on the element.
The td and th elements' width attributes map to the dimension property
(ignoring zero) width on the element.
----------------------------------------------------------------------
The thead, tbody, tfoot, tr, td, and th elements when they have an align
attribute whose value is an ASCII case-insensitive match for either the
string "center" or the string "middle", are expected to center text within
themselves, as if they had their text-align property set to text-align:
center in a presentational hint, and to align descendants to the center.
The thead, tbody, tfoot, tr, td, and th elements, when they have an align
attribute whose value is an ASCII case-insensitive match for the string
"left", are expected to left-align text within themselves, as if they had
their text-align property set to text-align: left in a presentational
hint, and to align descendants to the left.
The thead, tbody, tfoot, tr, td, and th elements, when they have an align
attribute whose value is an ASCII case-insensitive match for the string
"right", are expected to right-align text within themselves, as if they
had their text-align property set to text-align: right in a presentational
hint, and to align descendants to the right.
The thead, tbody, tfoot, tr, td, and th elements, when they have an align
attribute whose value is an ASCII case-insensitive match for the string
"justify", are expected to full-justify text within themselves, as if they
had their text-align property set to text-align: justify in a
presentational hint, and to align descendants to the left.
User agents are expected to have a rule in their user agent stylesheet
that matches th elements that have a parent node whose computed value for
the text-align property is its initial value, whose declaration block
consists of just a single declaration that sets the text-align property to
the value text-align: center.
----------------------------------------------------------------------
When a table, thead, tbody, tfoot, tr, td, or th element has a background
attribute set to a non-empty value, the new value is expected to be parsed
relative to the element’s node document, and if this is successful, the
user agent is expected to treat the attribute as a presentational hint
setting the element’s background-image property to the resulting URL
string.
When a table, thead, tbody, tfoot, tr, td, or th element has a bgcolor
attribute set, the new value is expected to be parsed using the rules for
parsing a legacy color value, and if that does not return an error, the
user agent is expected to treat the attribute as a presentational hint
setting the element’s background-color property to the resulting color.
When a table element has a bordercolor attribute, its value is expected to
be parsed using the rules for parsing a legacy color value, and if that
does not return an error, the user agent is expected to treat the
attribute as a presentational hint setting the element’s border-top-color,
border-right-color, border-bottom-color, and border-left-color properties
to the resulting color.
----------------------------------------------------------------------
The table element’s border attribute maps to the pixel length properties
border-top-width, border-right-width, border-bottom-width,
border-left-width on the element. If the attribute is present but parsing
the attribute’s value using the rules for parsing non-negative integers
generates an error, a default value of 1px is expected to be used for that
property instead.
Rules marked "only if border is not equivalent to zero" in the CSS block
above is expected to only be applied if the border attribute mentioned in
the selectors for the rule is not only present but, when parsed using the
rules for parsing non-negative integers, is also found to have a value
other than zero or to generate an error.
----------------------------------------------------------------------
In quirks mode, a td element or a th element that has a nowrap attribute
but also has a width attribute whose value, when parsed using the rules
for parsing non-zero dimension values, is found to be a length (not an
error or a number classified as a percentage), is expected to have a
presentational hint setting the element’s white-space property to
white-space: normal, overriding the rule in the CSS block above that sets
it to white-space: nowrap.
10.3.10. Margin collapsing quirks
A node is substantial if it is a text node that is not inter-element white
space, or if it is an element node.
A node is blank if it is an element that contains no substantial nodes.
The elements with default margins are the following elements: blockquote,
dir, dl, h1, h2, h3, h4, h5, h6, listing, ol, p, plaintext, pre, ul, xmp
In quirks mode, any element with default margins that is the child of a
body, td, or th element and has no substantial previous siblings is
expected to have a user-agent level style sheet rule that sets its
margin-block-start property to zero.
In quirks mode, any element with default margins that is the child of a
body, td, or th element, has no substantial previous siblings, and is
blank, is expected to have a user-agent level style sheet rule that sets
its margin-block-end property to zero also.
In quirks mode, any element with default margins that is the child of a td
or th element, has no substantial following siblings, and is blank, is
expected to have a user-agent level style sheet rule that sets its
margin-block-start property to zero.
In quirks mode, any p element that is the child of a td or th element and
has no substantial following siblings, is expected to have a user-agent
level style sheet rule that sets its margin-block-end property to zero.
10.3.11. Form controls
@namespace url(http://www.w3.org/1999/xhtml);
input, select, option, optgroup, button, textarea {
text-indent: initial;
}
input:matches([type=radio i], [type=checkbox i], [type=reset i], [type=button i],
[type=submit i], [type=search i]), select, button {
box-sizing: border-box;
}
textarea { white-space: pre-wrap; }
In quirks mode, the following rules are also expected to apply:
@namespace url(http://www.w3.org/1999/xhtml);
input:not([type=image i]), textarea { box-sizing: border-box; }
Each kind of form control is also described in the Widgets section, which
describes the look and feel of the control.
10.3.12. The hr element
@namespace url(http://www.w3.org/1999/xhtml);
hr {
color: gray;
border-style: inset;
border-width: 1px;
margin-block-start: 0.5em;
margin-inline-end: auto;
margin-block-end: 0.5em;
margin-inline-start: auto;
}
The following rules are also expected to apply, as presentational hints:
@namespace url(http://www.w3.org/1999/xhtml);
hr[align=left i] { margin-left: 0; margin-right: auto; }
hr[align=right i] { margin-left: auto; margin-right: 0; }
hr[align=center i] { margin-left: auto; margin-right: auto; }
hr[color], hr[noshade] { border-style: solid; }
If an hr element has either a color attribute or a noshade attribute, and
furthermore also has a size attribute, and parsing that attribute’s value
using the rules for parsing non-negative integers doesn’t generate an
error, then the user agent is expected to use the parsed value divided by
two as a pixel length for presentational hints for the properties
border-top-width, border-right-width, border-bottom-width, and
border-left-width on the element.
Otherwise, if an hr element has neither a color attribute nor a noshade
attribute, but does have a size attribute, and parsing that attribute’s
value using the rules for parsing non-negative integers doesn’t generate
an error, then: if the parsed value is one, then the user agent is
expected to use the attribute as a presentational hint setting the
element’s border-bottom-width to 0; otherwise, if the parsed value is
greater than one, then the user agent is expected to use the parsed value
minus two as a pixel length for presentational hints for the height
property on the element.
The width attribute on an hr element maps to the dimension property width
on the element.
When an hr element has a color attribute, its value is expected to be
parsed using the rules for parsing a legacy color value, and if that does
not return an error, the user agent is expected to treat the attribute as
a presentational hint setting the element’s color property to the
resulting color.
10.3.13. The fieldset and legend elements
@namespace url(http://www.w3.org/1999/xhtml);
fieldset {
display: block;
margin-inline-start: 2px;
margin-inline-end: 2px;
border: groove 2px ThreeDFace;
padding-block-start: 0.35em;
padding-inline-end: 0.625em;
padding-block-end: 0.75em;
padding-inline-start: 0.625em;
min-width: min-content;
}
legend {
padding-inline-start: 2px; padding-inline-end: 2px;
}
The fieldset element is expected to establish a new block formatting
context.
If the fieldset element has a child that matches the conditions in the
list below, then the first such child is the fieldset element’s rendered
legend:
* The child is a legend element.
* The child is not out-of-flow (e.g., not absolutely positioned or
floated).
* The child is generating a box (e.g., it is not 'display: none' or
'display: contents').
A fieldset element’s rendered legend, if any, is expected to be rendered
over the block-start border edge of the fieldset element as a block box
(overriding any explicit display value). In the absence of an explicit
inline size, the box should shrink-wrap. If the legend element in question
has an align attribute, and its value is an ASCII case-insensitive match
for one of the strings in the first column of the following table, then
the legend is expected to be rendered aligned in the inline direction over
the border edge in the position given in the corresponding cell on the
same row in the second column. If the attribute is absent or has a value
that doesn’t match any of the cases in the table, then the position is
expected to be on the right if the direction property on this element has
a computed value of rtl, and on the inline-start side.
[CSS-WRITING-MODES-3]
Attribute value Alignment position
left On the inline-left side
right On the inline-right side
center In the middle
10.4. Replaced elements
10.4.1. Embedded content
The embed, iframe, and video elements are expected to be treated as
replaced elements.
A canvas element that represents embedded content is expected to be
treated as a replaced element; the contents of such elements are the
element’s bitmap, if any, or else a transparent black bitmap with the same
intrinsic dimensions as the element. Other canvas elements are expected to
be treated as ordinary elements in the rendering model.
An object element that represents an image, plugin, or nested browsing
context is expected to be treated as a replaced element. Other object
elements are expected to be treated as ordinary elements in the rendering
model.
An applet element that represents a plugin is expected to be treated as a
replaced element. Other applet elements are expected to be treated as
ordinary elements in the rendering model.
The audio element, when it is exposing a user interface, is expected to be
treated as a replaced element about one line high, as wide as is necessary
to expose the user agent’s user interface features. When an audio element
is not exposing a user interface, the user agent is expected to force its
display property to compute to none, irrespective of CSS rules.
Whether a video element is exposing a user interface is not expected to
affect the size of the rendering; controls are expected to be overlaid
above the page content without causing any layout changes, and are
expected to disappear when the user does not need them.
When a video element represents a poster frame or frame of video, the
poster frame or frame of video is expected to be rendered at the largest
size that maintains the aspect ratio of that poster frame or frame of
video without being taller or wider than the video element itself, and is
expected to be centered in the video element.
Any subtitles or captions are expected to be overlayed directly on top of
their video element, as defined by the relevant rendering rules; for
WebVTT, those are the rules for updating the display of WebVTT text
tracks. [WEBVTT]
When the user agent starts exposing a user interface for a video element,
the user agent should run the rules for updating the text track rendering
of each of the text tracks in the video element’s list of text tracks that
are showing and whose text track kind is one of subtitles or captions
(e.g., for text tracks based on WebVTT, the rules for updating the display
of WebVTT text tracks). [WEBVTT]
Note: Resizing video and canvas elements does not interrupt video playback
or clear the canvas.
----------------------------------------------------------------------
The following CSS rules are expected to apply:
@namespace url(http://www.w3.org/1999/xhtml);
iframe { border: 2px inset; }
video { object-fit: contain; }
10.4.2. Images
User agents are expected to render img elements and input elements whose
type attributes are in the Image Button state, according to the first
applicable rules from the following list:
If the element represents an image
The user agent is expected to treat the element as a replaced
element and render the image according to the rules for doing so
defined in CSS.
If the element does not represent an image, but the element already has
intrinsic dimensions (e.g., from the dimension attributes or CSS rules),
and either:
* the user agent has reason to believe that the image will become
available and be rendered in due course, or
* the element has no alt attribute, or
* the Document is in quirks mode
The user agent is expected to treat the element as a replaced
element whose content is the text that the element represents, if
any, optionally alongside an icon indicating that the image is
being obtained (if applicable). For input elements, the element is
expected to appear button-like to indicate that the element is a
button.
If the element is an img element that represents some text and the user
agent does not expect this to change
The user agent is expected to treat the element as a non-replaced
phrasing element whose content is the text, optionally with an
icon indicating that an image is missing, so that the user can
request the image be displayed or investigate why it is not
rendering. In non-graphical contexts, such an icon should be
omitted.
If the element is an img element that represents nothing and the user
agent does not expect this to change
The user agent is expected to treat the element as an empty inline
element. (In the absence of further styles, this will cause the
element to essentially not be rendered.)
If the element is an input element that does not represent an image and
the user agent does not expect this to change
The user agent is expected to treat the element as a replaced
element consisting of a button whose content is the element’s
alternative text. The intrinsic dimensions of the button are
expected to be about one line in height and whatever width is
necessary to render the text on one line.
The icons mentioned above are expected to be relatively small so as not to
disrupt most text but be easily clickable. In a visual environment, for
instance, icons could be 16 pixels by 16 pixels square, or 1em by 1em if
the images are scalable. In an audio environment, the icon could be a
short bleep. The icons are intended to indicate to the user that they can
be used to get to whatever options the user agent provides for images.
----------------------------------------------------------------------
All animated images with the same absolute URL and the same image data are
expected to be rendered synchronized to the same timeline as a group, with
the timeline starting at the time of the least recent addition to the
group.
Note: In other words, when a second image with the same absolute URL and
animated image data is inserted into a document, it jumps to the point in
the animation cycle that is currently being displayed by the first image.
When a user agent is to restart the animation for an img element showing
an animated image, all animated images with the same absolute URL and the
same image data in that img element’s node document are expected to
restart their animation from the beginning.
----------------------------------------------------------------------
The following CSS rules are expected to apply when the Document is in
quirks mode:
@namespace url(http://www.w3.org/1999/xhtml);
img[align=left i] { margin-right: 3px; }
img[align=right i] { margin-left: 3px; }
10.4.3. Attributes for embedded content and images
The following CSS rules are expected to apply as presentational hints:
@namespace url(http://www.w3.org/1999/xhtml);
iframe[frameborder=0], iframe[frameborder=no i] { border: none; }
applet[align=left i], embed[align=left i], iframe[align=left i],
img[align=left i], input[type=image i][align=left i], object[align=left i] {
float: left;
}
applet[align=right i], embed[align=right i], iframe[align=right i],
img[align=right i], input[type=image i][align=right i], object[align=right i] {
float: right;
}
applet[align=top i], embed[align=top i], iframe[align=top i],
img[align=top i], input[type=image i][align=top i], object[align=top i] {
vertical-align: top;
}
applet[align=baseline i], embed[align=baseline i], iframe[align=baseline i],
img[align=baseline i], input[type=image i][align=baseline i], object[align=baseline i] {
vertical-align: baseline;
}
applet[align=texttop i], embed[align=texttop i], iframe[align=texttop i],
img[align=texttop i], input[type=image i][align=texttop i], object[align=texttop i] {
vertical-align: text-top;
}
applet[align=absmiddle i], embed[align=absmiddle i], iframe[align=absmiddle i],
img[align=absmiddle i], input[type=image i][align=absmiddle i], object[align=absmiddle i],
applet[align=abscenter i], embed[align=abscenter i], iframe[align=abscenter i],
img[align=abscenter i], input[type=image i][align=abscenter i], object[align=abscenter i] {
vertical-align: middle;
}
applet[align=bottom i], embed[align=bottom i], iframe[align=bottom i],
img[align=bottom i], input[type=image i][align=bottom i],
object[align=bottom i] {
vertical-align: bottom;
}
When an applet, embed, iframe, img, or object element, or an input element
whose type attribute is in the Image Button state, has an align attribute
whose value is an ASCII case-insensitive match for the string "center" or
the string "middle", the user agent is expected to act as if the element’s
vertical-align property was set to a value that aligns the vertical middle
of the element with the parent element’s baseline.
The hspace attribute of applet, embed, iframe, img, or object elements,
and input elements with a type attribute in the Image Button state, maps
to the dimension properties margin-left and margin-right on the element.
The vspace attribute of applet, embed, iframe, img, or object elements,
and input elements with a type attribute in the Image Button state, maps
to the dimension properties margin-top and margin-bottom on the element.
When an img element, object element, or input element with a type
attribute in the Image Button state has a border attribute whose value,
when parsed using the rules for parsing non-negative integers, is found to
be a number greater than zero, the user agent is expected to use the
parsed value for eight presentational hints: four setting the parsed value
as a pixel length for the element’s border-top-width, border-right-width,
border-bottom-width, and border-left-width properties, and four setting
the element’s border-top-style, border-right-style, border-bottom-style,
and border-left-style properties to the value solid.
The width and height attributes on applet, embed, iframe, img, object or
video elements, and input elements with a type attribute in the Image
Button state and that either represents an image or that the user expects
will eventually represent an image, map to the dimension properties width
and height on the element respectively.
10.4.4. Image maps
Shapes on an image map are expected to act, for the purpose of the CSS
cascade, as elements independent of the original area element that happen
to match the same style rules but inherit from the img or object element.
For the purposes of the rendering, only the cursor property is expected to
have any effect on the shape.
Thus, for example, if an area element has a style attribute that sets the
cursor property to help, then when the user designates that shape, the
cursor would change to a Help cursor.
Similarly, if an area element had a CSS rule that set its cursor property
to inherit (or if no rule setting the cursor property matched the element
at all), the shape’s cursor would be inherited from the img or object
element of the image map, not from the parent of the area element.
10.5. Widgets
10.5.1. Introduction
Exactly how user agents render the elements in this section is not
specified by this specification. User agents are encouraged to set the
appearance CSS property appropriately to achieve platform-native
appearances for widgets, and are expected to implement any relevant
animations, etc, that are appropriate for the platform. [CSS-UI-3]
10.5.2. The button element
The button element is expected to render as an inline-block box rendered
as a button whose contents are the contents of the element.
10.5.3. The details and summary elements
details > summary:first-of-type {
display: list-item;
list-style: disclosure-closed inside;
}
details[open] > summary:first-of-type {
list-style-type: disclosure-open;
}
The details element is expected to render as a block box. The element’s
shadow tree is expected to take the element’s first child summary element,
if any, and place it in a first block box container, and then take the
element’s remaining descendants, if any, and place them in a second block
box container.
The first container is expected to allow the user to request the details
be shown or hidden.
The second container is expected to be removed from the rendering when the
details element does not have an open attribute.
There are no specific rendering expecations for a summary element that is
not the first child of its parent details element
10.5.4. The input element as a text entry widget.
The input element whose type attribute is in the Text, Search, Telephone,
URL, or E-mail state, the element is expected to render as an inline-block
box rendered as a text field. Additionally, the line-height property, if
it has a computed value equivalent to a value that is less than 1.0, must
have a used value of 1.0.
An input element whose type attribute is in the Password state, the
element is expected to render as an inline-block box rendered as a text
field whose contents are obscured.
If these text fields provide a text selection, then, when the user changes
the current selection, the user agent is expected to queue a task to fire
a simple event that bubbles named select at the element, using the user
interaction task source as the task source.
If an input element whose type attribute is in one of the above states has
a size attribute, and parsing that attribute’s value using the rules for
parsing non-negative integers doesn’t generate an error, then the user
agent is expected to use the attribute as a presentational hint for the
width property on the element, with the value obtained from applying the
converting a character width to pixels algorithm to the value of the
attribute.
If an input element whose type attribute is in one of the above states
does not have a size attribute, then the user agent is expected to act as
if it had a user-agent-level style sheet rule setting the width property
on the element to the value obtained from applying the converting a
character width to pixels algorithm to the number 20.
The converting a character width to pixels algorithm returns
(size-1)×avg + max, where size is the character width to convert, avg is
the average character width of the primary font for the element for which
the algorithm is being run, in pixels, and max is the maximum character
width of that same font, also in pixels. (The element’s letter-spacing
property does not affect the result.)
10.5.5. The input element as domain-specific widgets
An input element whose type attribute is in the Date state, the element is
expected to render as an inline-block box depicting a Date control.
An input element whose type attribute is in the Month state, the element
is expected to render as an inline-block box depicting a Month control.
An input element whose type attribute is in the Week state, the element is
expected to render as an inline-block box depicting a Week control.
An input element whose type attribute is in the Time state, the element is
expected to render as an inline-block box depicting a Time control.
An input element whose type attribute is in the Local Date and Time state,
the element is expected to render as an inline-block box depicting a Local
Date and Time control.
An input element whose type attribute is in the Number state, the element
is expected to render as an inline-block box depicting a Number control.
These controls are all expected to be about one line high, and about as
wide as necessary to show the widest possible value.
10.5.6. The input element as a range control
An input element whose type attribute is in the Range state, the element
is expected to render as an inline-block box depicting a slider control.
When the control is wider than it is tall (or square), the control is
expected to be a horizontal slider, with the lowest value on the right if
the direction property on this element has a computed value of rtl, and on
the left otherwise. When the control is taller than it is wide, it is
expected to be a vertical slider, with the lowest value on the bottom.
Predefined suggested values (provided by the list attribute) are expected
to be shown as tick marks on the slider, which the slider can snap to.
User agents are expected to use the used value of the direction property
on the element to determine the direction in which the slider operates.
Typically, a left-to-right (ltr) horizontal control would have the lowest
value on the left and the highest value on the right, and vice versa.
10.5.7. The input element as a color well
An input element whose type attribute is in the Color state, the element
is expected to render as an inline-block box depicting a color well,
which, when activated, provides the user with a color picker (e.g., a
color wheel or color palette) from which the color can be changed.
Predefined suggested values (provided by the list attribute) are expected
to be shown in the color picker interface, not on the color well itself.
10.5.8. The input element as a checkbox and radio button widgets
An input element whose type attribute is in the Checkbox state, the
element is expected to render as an inline-block box containing a single
checkbox control, with no label.
An input element whose type attribute is in the Radio Button state, the
element is expected to render as an inline-block box containing a single
radio button control, with no label.
10.5.9. The input element as a file upload control
An input element whose type attribute is in the File Upload state, the
element is expected to render as an inline-block box containing a span of
text giving the file name(s) of the selected files, if any, followed by a
button that, when activated, provides the user with a file picker from
which the selection can be changed.
10.5.10. The input element as a button
An input element whose type attribute is in the Submit Button, Reset
Button, or Button state, the element is expected to render as an
inline-block box rendered as a button, about one line high, containing the
contents of the element’s value attribute, if any, or text derived from
the element’s type attribute in a user-agent-defined (and probably
locale-specific) fashion, if not.
10.5.11. The marquee element
The marquee element, while the element is turned on, the element is
expected to render in an animated fashion according to its attributes as
follows:
If the element’s behavior attribute is in the scroll state
Slide the contents of the element in the direction described by
the direction attribute as defined below, such that it begins off
the start side of the marquee, and ends flush with the inner end
side.
For example, if the direction attribute is left (the default),
then the contents would start such that their left edge are off
the side of the right edge of the marquee's content area, and the
contents would then slide up to the point where the left edge of
the contents are flush with the left inner edge of the marquee's
content area.
Once the animation has ended, the user agent is expected to
increment the marquee current loop index. If the element is still
turned on after this, then the user agent is expected to restart
the animation.
If the element’s behavior attribute is in the slide state
Slide the contents of the element in the direction described by
the direction attribute as defined below, such that it begins off
the start side of the marquee, and ends off the end side of the
marquee.
For example, if the direction attribute is left (the default),
then the contents would start such that their left edge are off
the side of the right edge of the marquee's content area, and the
contents would then slide up to the point where the right edge of
the contents are flush with the left inner edge of the marquee's
content area.
Once the animation has ended, the user agent is expected to
increment the marquee current loop index. If the element is still
turned on after this, then the user agent is expected to restart
the animation.
If the element’s behavior attribute is in the alternate state
When the marquee current loop index is even (or zero), slide the
contents of the element in the direction described by the
direction attribute as defined below, such that it begins flush
with the start side of the marquee, and ends flush with the end
side of the marquee.
When the marquee current loop index is odd, slide the contents of
the element in the opposite direction than that described by the
direction attribute as defined below, such that it begins flush
with the end side of the marquee, and ends flush with the start
side of the marquee.
For example, if the direction attribute is left (the default),
then the contents would with their right edge flush with the right
inner edge of the marquee's content area, and the contents would
then slide up to the point where the left edge of the contents are
flush with the left inner edge of the marquee's content area.
Once the animation has ended, the user agent is expected to
increment the marquee current loop index. If the element is still
turned on after this, then the user agent is expected to continue
the animation.
The direction attribute has the meanings described in the following table:
direction attribute Direction of Start edge End edge Opposite
state animation direction
left ← Right to left Right Left → Left to Right
right → Left to Right Left Right ← Right to left
up ↑ Up (Bottom to Bottom Top ↓ Down (Top to
Top) Bottom)
down ↓ Down (Top to Top Bottom ↑ Up (Bottom to
Bottom) Top)
In any case, the animation should proceed such that there is a delay given
by the marquee scroll interval between each frame, and such that the
content moves at most the distance given by the marquee scroll distance
with each frame.
When a marquee element has a bgcolor attribute set, the value is expected
to be parsed using the rules for parsing a legacy color value, and if that
does not return an error, the user agent is expected to treat the
attribute as a presentational hint setting the element’s background-color
property to the resulting color.
The width and height attributes on a marquee element map to the dimension
properties width and height on the element respectively.
The intrinsic height of a marquee element with its direction attribute in
the up or down states is 200 CSS pixels.
The vspace attribute of a marquee element maps to the dimension properties
margin-top and margin-bottom on the element. The hspace attribute of a
marquee element maps to the dimension properties margin-left and
margin-right on the element.
The overflow property on the marquee element is expected to be ignored;
overflow is expected to always be hidden.
10.5.12. The meter element
The meter element is expected to render as an inline-block box with a
height of "1em" and a width of "5em", a vertical-align of "-0.2em", and
with its contents depicting a gauge.
When the element is wider than it is tall (or square), the depiction is
expected to be of a horizontal gauge, with the minimum value on the right
if the direction property on this element has a computed value of rtl, and
on the left otherwise. When the element is taller than it is wide, it is
expected to depict a vertical gauge, with the minimum value on the bottom.
User agents are expected to use a presentation consistent with platform
conventions for gauges, if any.
Note: Requirements for what must be depicted in the gauge are included in
the definition of the meter element.
10.5.13. The progress element
The progress element is expected to render as an inline-block box with a
height of "1em" and a width of "10em", and a vertical-align of "-0.2em".
When the element is wider than it is tall, the element is expected to be
depicted as a horizontal progress bar, with the start on the right and the
end on the left if the direction property on this element has a computed
value of rtl, and with the start on the left and the end on the right
otherwise. When the element is taller than it is wide, it is expected to
be depicted as a vertical progress bar, with the lowest value on the
bottom. When the element is square, it is expected to be depicted as a
direction-independent progress widget (e.g., a circular progress ring).
User agents are expected to use a presentation consistent with platform
conventions for progress bars. In particular, user agents are expected to
use different presentations for determinate and indeterminate progress
bars. User agents are also expected to vary the presentation based on the
dimensions of the element.
For example, on some platforms for showing indeterminate progress there is
a "spinner" progress indicator with square dimensions, which could be used
when the element is square, and an indeterminate progress bar, which could
be used when the element is wide.
Note: Requirements for how to determine if the progress bar is determinate
or indeterminate, and what progress a determinate progress bar is to show,
are included in the definition of the progress element.
10.5.14. The select element
A select element whose multiple attribute is present, the element is
expected to render as a multi-select list box.
A select element whose multiple attribute is absent, and the element’s
display size is greater than 1, the element is expected to render as a
single-select list box.
When the element renders as a list box, it is expected to render as an
inline-block box whose height is the height necessary to contain as many
rows for items as given by the element’s display size, or four rows if the
attribute is absent, and whose width is the width of the select’s labels
plus the width of a scrollbar.
A select element whose multiple attribute is absent, and the element’s
display size is 1, the element is expected to render as a one-line drop
down box whose width is the width of the select’s labels.
In either case (list box or drop-down box), the element’s items are
expected to be the element’s list of options, with the element’s optgroup
element children providing headers for groups of options where applicable.
An optgroup element is expected to be rendered by displaying the element’s
label attribute.
An option element is expected to be rendered by displaying the element’s
label, indented under its optgroup element if it has one.
The width of the select’s labels is the wider of the width necessary to
render the widest optgroup, and the width necessary to render the widest
option element in the element’s list of options (including its indent, if
any).
If a select element contains a placeholder label option, the user agent is
expected to render that option in a manner that conveys that it is a
label, rather than a valid option of the control. This can include
preventing the placeholder label option from being explicitly selected by
the user. When the placeholder label option's selectedness is true, the
control is expected to be displayed in a fashion that indicates that no
valid option is currently selected.
User agents are expected to render the labels in a select in such a manner
that any alignment remains consistent whether the label is being displayed
as part of the page.
10.5.15. The textarea element
@namespace url(http://www.w3.org/1999/xhtml);
textarea { white-space: pre-wrap; }
The textarea element is expected to render as an inline-block box rendered
as a multiline text field. If this text field provides a selection, the
user agent is expected to queue a task to fire a simple event that bubbles
named select at the element, using the user interaction task source as the
task source.
If the element has a cols attribute, and parsing that attribute’s value
using the rules for parsing non-negative integers doesn’t generate an
error, then the user agent is expected to use the attribute as a
presentational hint for the width property on the element, with the value
being the textarea effective width (as defined below). Otherwise, the user
agent is expected to act as if it had a user-agent-level style sheet rule
setting the width property on the element to the textarea effective width.
The textarea effective width of a textarea element is size×avg + sbw,
where size is the element’s character width, avg is the average character
width of the primary font of the element, in CSS pixels, and sbw is the
width of a scroll bar, in CSS pixels. (The element’s letter-spacing
property does not affect the result.)
If the element has a rows attribute, and parsing that attribute’s value
using the rules for parsing non-negative integers doesn’t generate an
error, then the user agent is expected to use the attribute as a
presentational hint for the height property on the element, with the value
being the textarea effective height (as defined below). Otherwise, the
user agent is expected to act as if it had a user-agent-level style sheet
rule setting the height property on the element to the textarea effective
height.
The textarea effective height of a textarea element is the height in CSS
pixels of the number of lines specified the element’s character height,
plus the height of a scrollbar in CSS pixels.
User agents are expected to apply the white-space CSS property to textarea
elements. For historical reasons, if the element has a wrap attribute
whose value is an ASCII case-insensitive match for the string "off", then
the user agent is expected to treat the attribute as a presentational hint
setting the element’s white-space property to pre.
10.6. Frames and framesets
User agent are expected to render frameset elements as a box with the
height and width of the viewport, with a surface rendered according to the
following layout algorithm:
1. The cols and rows variables are lists of zero or more pairs consisting
of a number and a unit, the unit being one of percentage, relative,
and absolute.
Use the rules for parsing a list of dimensions to parse the value of
the element’s cols attribute, if there is one. Let cols be the result,
or an empty list if there is no such attribute.
Use the rules for parsing a list of dimensions to parse the value of
the element’s rows attribute, if there is one. Let rows be the result,
or an empty list if there is no such attribute.
2. For any of the entries in cols or rows that have the number zero and
the unit relative, change the entry’s number to one.
3. If cols has no entries, then add a single entry consisting of the
value 1 and the unit relative to cols.
If rows has no entries, then add a single entry consisting of the
value 1 and the unit relative to rows.
4. Invoke the algorithm defined below to convert a list of dimensions to
a list of pixel values using cols as the input list, and the width of
the surface that the frameset is being rendered into, in CSS pixels,
as the input dimension. Let sized cols be the resulting list.
Invoke the algorithm defined below to convert a list of dimensions to
a list of pixel values using rows as the input list, and the height of
the surface that the frameset is being rendered into, in CSS pixels,
as the input dimension. Let sized rows be the resulting list.
5. Split the surface into a grid of w×h rectangles, where w is the number
of entries in sized cols and h is the number of entries in sized rows.
Size the columns so that each column in the grid is as many CSS pixels
wide as the corresponding entry in the sized cols list.
Size the rows so that each row in the grid is as many CSS pixels high
as the corresponding entry in the sized rows list.
6. Let children be the list of frame and frameset elements that are
children of the frameset element for which the algorithm was invoked.
7. For each row of the grid of rectangles created in the previous step,
from top to bottom, run these substeps:
1. For each rectangle in the row, from left to right, run these
substeps:
1. If there are any elements left in children, take the first
element in the list, and assign it to the rectangle.
If this is a frameset element, then recurse the entire
frameset layout algorithm for that frameset element, with
the rectangle as the surface.
Otherwise, it is a frame element; render its nested browsing
context, positioned and sized to fit the rectangle.
2. If there are any elements left in children, remove the first
element from children.
8. If the frameset element has a border, draw an outer set of borders
around the rectangles, using the element’s frame border color.
For each rectangle, if there is an element assigned to that rectangle,
and that element has a border, draw an inner set of borders around
that rectangle, using the element’s frame border color.
For each (visible) border that does not abut a rectangle that is
assigned a frame element with a noresize attribute (including
rectangles in further nested frameset elements), the user agent is
expected to allow the user to move the border, resizing the rectangles
within, keeping the proportions of any nested frameset grids.
A frameset or frame element has a border if the following algorithm
returns true:
1. If the element has a frameborder attribute whose value is not the
empty string and whose first character is either a U+0031 DIGIT
ONE (1) character, a U+0079 LATIN SMALL LETTER Y character (y),
or a U+0059 LATIN CAPITAL LETTER Y character (Y), then return
true.
2. Otherwise, if the element has a frameborder attribute, return
false.
3. Otherwise, if the element has a parent element that is a frameset
element, then return true if that element has a border, and false
if it does not.
4. Otherwise, return true.
The frame border color of a frameset or frame element is the color
obtained from the following algorithm:
1. If the element has a bordercolor attribute, and applying the
rules for parsing a legacy color value to that attribute’s value
does not result in an error, then return the color so obtained.
2. Otherwise, if the element has a parent element that is a frameset
element, then return the frame border color of that element.
3. Otherwise, return gray.
The algorithm to convert a list of dimensions to a list of pixel values
consists of the following steps:
1. Let input list be the list of numbers and units passed to the
algorithm.
Let output list be a list of numbers the same length as input list,
all zero.
Entries in output list correspond to the entries in input list that
have the same position.
2. Let input dimension be the size passed to the algorithm.
3. Let count percentage be the number of entries in input list whose unit
is percentage.
Let total percentage be the sum of all the numbers in input list whose
unit is percentage.
Let count relative be the number of entries in input list whose unit
is relative.
Let total relative be the sum of all the numbers in input list whose
unit is relative.
Let count absolute be the number of entries in input list whose unit
is absolute.
Let total absolute be the sum of all the numbers in input list whose
unit is absolute.
Let remaining space be the value of input dimension.
4. If total absolute is greater than remaining space, then for each entry
in input list whose unit is absolute, set the corresponding value in
output list to the number of the entry in input list multiplied by
remaining space and divided by total absolute. Then, set remaining
space to zero.
Otherwise, for each entry in input list whose unit is absolute, set
the corresponding value in output list to the number of the entry in
input list. Then, decrement remaining space by total absolute.
5. If total percentage multiplied by the input dimension and divided by
100 is greater than remaining space, then for each entry in input list
whose unit is percentage, set the corresponding value in output list
to the number of the entry in input list multiplied by remaining space
and divided by total percentage. Then, set remaining space to zero.
Otherwise, for each entry in input list whose unit is percentage, set
the corresponding value in output list to the number of the entry in
input list multiplied by the input dimension and divided by 100. Then,
decrement remaining space by total percentage multiplied by the input
dimension and divided by 100.
6. For each entry in input list whose unit is relative, set the
corresponding value in output list to the number of the entry in input
list multiplied by remaining space and divided by total relative.
7. Return output list.
User agents working with integer values for frame widths (as opposed to
user agents that can lay frames out with subpixel accuracy) are expected
to distribute the remainder first to the last entry whose unit is
relative, then equally (not proportionally) to each entry whose unit is
percentage, then equally (not proportionally) to each entry whose unit is
absolute, and finally, failing all else, to the last entry.
----------------------------------------------------------------------
The contents of a frame element that does not have a frameset parent are
expected to be rendered as transparent black; the user agent is expected
to not render the nested browsing context in this case, and that nested
browsing context is expected to have a viewport with zero width and zero
height.
10.7. Interactive media
10.7.1. Links, forms, and navigation
User agents are expected to allow the user to control aspects of hyperlink
activation and §4.10.21 Form submission, such as which browsing context is
to be used for the subsequent navigation.
User agents are expected to allow users to discover the destination of
hyperlinks and of forms before triggering their navigation.
User agents may allow users to navigate browsing contexts to the URLs
indicated by the cite attributes on q, blockquote, ins, and del elements.
User agents may surface hyperlinks created by link elements in their user
interface.
Note: While link elements that create hyperlinks will match the :link or
:visited pseudo-classes, will react to clicks if visible, and so forth,
this does not extend to any browser interface constructs that expose those
same links. Activating a link through the browser’s interface, rather than
in the page itself, does not trigger click events and the like.
10.7.2. The title attribute
User agents are expected to expose the advisory information of elements
upon user request, and to make the user aware of the presence of such
information.
On interactive graphical systems where the user can use a pointing device,
this could take the form of a tooltip. When the user is unable to use a
pointing device, then the user agent is expected to make the content
available in some other fashion, e.g., by making the element a focusable
area and always displaying the advisory information of the currently
focused element.
U+000A LINE FEED (LF) characters are expected to cause line breaks in the
tooltip; U+0009 CHARACTER TABULATION (tab) characters are expected to
render as a non-zero horizontal shift that lines up the next glyph with
the next tab stop, with tab stops occurring at points that are multiples
of 8 times the width of a U+0020 SPACE character.
For example, a visual user agent could make elements with a title
attribute focusable, and could make any focused element with a title
attribute show its tooltip under the element while the element has focus.
This would allow a user to tab around the document to find all the
advisory text.
As another example, a screen reader could provide an audio cue when
reading an element with a tooltip, with an associated key to read the last
tooltip for which a cue was played.
10.7.3. Editing hosts
The current text editing caret (i.e., the active range, if it is empty and
in an editing host), if any, is expected to act like an inline replaced
element with the vertical dimensions of the caret and with zero width for
the purposes of the CSS rendering model.
Note: This means that even an empty block can have the caret inside it,
and that when the caret is in such an element, it prevents margins from
collapsing through the element.
10.7.4. Text rendered in native user interfaces
User agents are expected to honor the Unicode semantics of text that is
exposed in user interfaces, for example supporting the bidirectional
algorithm in text shown in dialogs, title bars, and tooltips. Text from
the contents of elements is expected to be rendered in a manner that
honors the directionality of the element from which the text was obtained.
Text from attributes is expected to be rendered in a manner that honours
the directionality of the attribute.
Consider the following markup, which has Hebrew text asking for a
programming language, the languages being text for which a left-to-right
direction is important given the punctuation in some of their names:
<p dir="rtl" lang="he">
<label>
בחר שפת תכנות:
<select>
<option dir="ltr">C++</option>
<option dir="ltr">C#</option>
<option dir="ltr">FreePascal</option>
<option dir="ltr">F#</option>
</select>
</label>
</p>
If the select element was rendered as a drop down box, a correct rendering
would ensure that the punctuation was the same both in the drop down, and
in the box showing the current selection.
The directionality of attributes depends on the attribute and on the
element’s dir attribute, as the following example demonstrates. Consider
this markup:
<table>
<tr>
<th abbr="(א" dir=ltr>A
<th abbr="(א" dir=rtl>A
<th abbr="(א" dir=auto>A
</table>
If the abbr attributes are rendered, e.g., in a tooltip or other user
interface, the first will have a left parenthesis (because the direction
is ltr), the second will have a right parenthesis (because the direction
is rtl), and the third will have a right parenthesis (because the
direction is determined from the attribute value to be rtl).
However, if instead the attribute was not a directionality-capable
attribute, the results would be different:
<table>
<tr>
<th>A
<th>A
<th>A
</table>
In this case, if the user agent were to expose the data-abbr attribute in
the user interface (e.g., in a debugging environment), the last case would
be rendered with a left parenthesis, because the direction would be
determined from the element’s contents.
A string provided by a script (e.g., the argument to window.alert()) is
expected to be treated as an independent set of one or more bidirectional
algorithm paragraphs when displayed, as defined by the bidirectional
algorithm, including, for instance, supporting the paragraph-breaking
behavior of U+000A LINE FEED (LF) characters. For the purposes of
determining the paragraph level of such text in the bidirectional
algorithm, this specification does not provide a higher-level override of
rules P2 and P3. [BIDI]
When necessary, authors can enforce a particular direction for a given
paragraph by starting it with the Unicode U+200E LEFT-TO-RIGHT MARK or
U+200F RIGHT-TO-LEFT MARK characters.
Thus, the following script:
alert('\u05DC\u05DE\u05D3 HTML \u05D4\u05D9\u05D5\u05DD!')
...would always result in a message reading "למד LMTH היום!" (not
"דמל HTML םויה!"), regardless of the language of the user agent interface
or the direction of the page or any of its elements.
For a more complex example, consider the following script:
/* Warning: this script does not handle right-to-left scripts correctly */
var s;
if (s = prompt('What is your name?')) {
alert(s + '! Ok, Fred, ' + s + ', and Wilma will get the car.');
}
When the user enters "Kitty", the user agent would alert "Kitty! Ok, Fred,
Kitty, and Wilma will get the car.". However, if the user enters
"لا أفهم", then the bidirectional algorithm will determine that the
direction of the paragraph is right-to-left, and so the output will be the
following unintended mess:
"لا أفهم! derF ,kO, لا أفهم, rac eht teg lliw amliW dna."
To force an alert that starts with user-provided text (or other text of
unknown directionality) to render left-to-right, the string can be
prefixed with a U+200E LEFT-TO-RIGHT MARK character:
var s;
if (s = prompt('What is your name?')) {
alert('\u200E' + s + '! Ok, Fred, ' + s + ', and Wilma will get the car.');
}
10.8. Print media
User agents are expected to allow the user to request the opportunity to
obtain a physical form (or a representation of a physical form) of a
Document. For example, selecting the option to print a page or convert it
to PDF format. [PDF]
When the user actually obtains a physical form (or a representation of a
physical form) of a Document, the user agent is expected to create a new
rendering of the Document for the print media.
10.9. Unstyled XML documents
HTML user agents may, in certain circumstances, find themselves rendering
non-HTML documents that use vocabularies for which they lack any built-in
knowledge. This section provides for a way for user agents to handle such
documents in a somewhat useful manner.
While a Document is an unstyled document, the user agent is expected to
render an unstyled document view.
A Document is an unstyled document while it matches the following
conditions:
* The Document has no author style sheets (whether referenced by HTTP
headers, processing instructions, elements like link, inline elements
like style, or any other mechanism).
* None of the elements in the Document have any presentational hints.
* None of the elements in the Document have any style attributes.
* None of the elements in the Document are in any of the following
namespaces: HTML namespace, SVG namespace, MathML namespace
* The Document has no focusable area (e.g., from XLink) other than the
viewport.
* The Document has no hyperlinks (e.g., from XLink).
* There exists no script whose settings object specifies this Document
as the responsible document.
* None of the elements in the Document have any registered event
listeners.
An unstyled document view is one where the DOM is not rendered according
to CSS (which would, since there are no applicable styles in this context,
just result in a wall of text), but is instead rendered in a manner that
is useful for a developer. This could consist of just showing the Document
object’s source, maybe with syntax highlighting, or it could consist of
displaying just the DOM tree, or simply a message saying that the page is
not a styled document.
Note: If a Document stops being an unstyled document, then the conditions
above stop applying, and thus a user agent following these requirements
will switch to using the regular CSS rendering.
11. Obsolete features
11.1. Obsolete but conforming features
Features listed in this section will trigger warnings in conformance
checkers.
Authors should not specify a border attribute on an img element. If the
attribute is present, its value must be the string "0". CSS should be used
instead.
Authors should not specify a language attribute on a script element. If
the attribute is present, its value must be an ASCII case-insensitive
match for the string "JavaScript" and either the type attribute must be
omitted or its value must be an ASCII case-insensitive match for the
string "text/javascript". The attribute should be entirely omitted instead
(with the value "JavaScript", it has no effect), or replaced with use of
the type attribute.
Authors should not specify the name attribute on a elements. If the
attribute is present, its value must not be the empty string and must
neither be equal to the value of any of the IDs in the element’s tree
other than the element’s own ID if any, nor be equal to the value of any
of the other name attributes on a elements in the element’s tree. If this
attribute is present and the element has an ID, then the attribute’s value
must be equal to the element’s ID. In earlier versions of the language,
this attribute was intended as a way to specify possible targets for
fragments in URLs. The id attribute should be used instead.
Authors should not, but may despite requirements to the contrary elsewhere
in this specification, specify the maxlength and size attributes on input
elements whose type attributes are in the Number state. One valid reason
for using these attributes regardless is to help legacy user agents that
do not support input elements with type="number" to still render the text
control with a useful width.
11.1.1. Warnings for obsolete but conforming features
To ease the transition from HTML Transitional documents to the language
defined in this specification, and to discourage certain features that are
only allowed in very few circumstances, conformance checkers must warn the
user when the following features are used in a document. These are
generally old obsolete features that have no effect, and are allowed only
to distinguish between likely mistakes (regular conformance errors) and
mere vestigial markup or unusual and discouraged practices (these
warnings).
The following features must be categorized as described above:
* The presence of a border attribute on an img element if its value is
the string "0".
* The presence of a language attribute on a script element if its value
is an ASCII case-insensitive match for the string "JavaScript" and if
there is no type attribute or there is and its value is an ASCII
case-insensitive match for the string "text/javascript".
* The presence of a name attribute on an a element, if its value is not
the empty string.
* The presence of a maxlength attribute on an input element whose type
attribute is in the Number state.
* The presence of a size attribute on an input element whose type
attribute is in the Number state.
Conformance checkers must distinguish between pages that have no
conformance errors and have none of these obsolete features, and pages
that have no conformance errors but do have some of these obsolete
features.
For example, a validator could report some pages as "Valid HTML" and
others as "Valid HTML with warnings".
11.2. Non-conforming features
Elements in the following list are entirely obsolete, and must not be used
by authors:
applet
Use embed or object instead.
acronym
Use abbr instead.
bgsound
Use audio instead.
dir
Use ul instead.
frame
frameset
noframes
Either use iframe and CSS instead, or use server-side includes to
generate complete pages with the various invariant parts merged
in.
isindex
Use an explicit form and text control combination instead.
listing
Use pre and code instead.
nextid
Use GUIDs instead.
noembed
Use object instead of embed when fallback is necessary.
plaintext
Use the "text/plain" MIME type instead.
rb
rtc
Providing the ruby base directly inside the ruby element or using
nested ruby elements is sufficient.
strike
Use del instead if the element is marking an edit, otherwise use s
instead.
xmp
Use pre and code instead, and escape "<" and "&" characters as
"<" and "&" respectively.
basefont
big
blink
center
font
marquee
menu
menuitem
multicol
nobr
spacer
tt
Use appropriate elements or CSS instead.
Where the tt element would have been used for marking up keyboard
input, consider the kbd element; for variables, consider the var
element; for computer code, consider the code element; and for
computer output, consider the samp element.
Similarly, if the big element is being used to denote a heading,
consider using the h1 element; if it is being used for marking up
important passages, consider the strong element; and if it is
being used for highlighting text for reference purposes, consider
the mark element.
See also the text-level semantics usage summary for more
suggestions with examples.
----------------------------------------------------------------------
The following attributes are obsolete (though the elements are still part
of the language), and must not be used by authors:
charset on a elements
charset on link elements
Use an HTTP Content-Type header on the linked resource instead.
coords on a elements
shape on a elements
Use area instead of a for image maps.
methods on a elements
methods on link elements
Use the HTTP OPTIONS feature instead.
name on a elements (except as noted in the previous section)
name on embed elements
name on img elements
name on option elements
Use the id attribute instead.
urn on a elements
urn on link elements
Specify the preferred persistent identifier using the href
attribute instead.
accept on form elements
Use the accept attribute directly on the input elements instead.
hreflang on area elements
type on area elements
These attributes do not do anything useful, and for historical
reasons there are no corresponding IDL attributes on area
elements. Omit them altogether.
nohref on area elements
Omitting the href attribute is sufficient; the nohref attribute is
unnecessary. Omit it altogether.
profile on head elements
When used for declaring which meta terms are used in the document,
unnecessary; omit it altogether, and register the names.
When used for triggering specific user agent behaviors: use a link
element instead.
version on html elements
Unnecessary. Omit it altogether.
ismap on input elements
Unnecessary. Omit it altogether. All input elements with a type
attribute in the Image Button state are processed as server-side
image maps.
usemap on input elements
Use img instead of input for image maps.
longdesc on iframe elements
longdesc on img elements
Use a regular a element to link to the description, or (in the
case of images) use an image map to provide a link from the image
to the image’s description.
lowsrc on img elements
Use a progressive JPEG image (given in the src attribute), instead
of using two separate images.
target on link elements
Unnecessary. Omit it altogether.
scheme on meta elements
If more than one scheme needs to be declared for a meta element
make the scheme declaration part of the value.
archive on object elements
classid on object elements
code on object elements
codebase on object elements
codetype on object elements
Use the data and type attributes to invoke plugins. To set
parameters with these names in particular, the param element can
be used.
declare on object elements
Repeat the object element completely each time the resource is to
be reused.
standby on object elements
Optimize the linked resource so that it loads quickly or, at
least, incrementally.
type on param elements
valuetype on param elements
Use the name and value attributes without declaring value types.
language on script elements (except as noted in the previous section)
Use the type attribute instead.
event on script elements
for on script elements
Use DOM events mechanisms to register event listeners. [DOM41]
datapagesize on table elements
Unnecessary. Omit it altogether.
summary on table elements
Use one of the techniques given in the table section instead.
abbr on td elements
Use text that begins in an unambiguous and terse manner, and
include any more elaborate text after that. The title attribute
can also be useful in including more detailed text, so that the
cell’s contents can be made terse. If it’s a heading, use th
(which has an abbr attribute).
axis on td and th elements
Use the scope attribute on the relevant th.
scope on td elements
Use th elements for heading cells.
datasrc on a, applet, button, div, frame, iframe, img, input, label,
legend, marquee, object, option, select, a, table, and textarea elements
datafld on a, applet, button, div, fieldset, frame, iframe, img, input,
label, legend, marquee, object, param, select, a, and textarea elements
dataformatas on button, div, input, label, legend, marquee, object,
option, select, a, and table elements
Use script and a mechanism such as XMLHttpRequest to populate the
page dynamically. [XHR]
alink on body elements
bgcolor on body elements
bottommargin on body elements
leftmargin on body elements
link on body elements
marginheight on body elements
marginwidth on body elements
rightmargin on body elements
text on body elements
topmargin on body elements
vlink on body elements
clear on br elements
align on caption elements
align on col elements
char on col elements
charoff on col elements
valign on col elements
width on col elements
align on div elements
compact on dl elements
align on embed elements
hspace on embed elements
vspace on embed elements
bordercolor on frame elements
align on hr elements
color on hr elements
noshade on hr elements
size on hr elements
width on hr elements
align on h1—h6 elements
align on iframe elements
allowtransparency on iframe elements
frameborder on iframe elements
framespacing on iframe elements
hspace on iframe elements
marginheight on iframe elements
marginwidth on iframe elements
scrolling on iframe elements
vspace on iframe elements
align on input elements
border on input elements
hspace on input elements
vspace on input elements
align on img elements
border on img elements (except as noted in the previous section)
hspace on img elements
vspace on img elements
align on legend elements
type on li elements
compact on menu elements
bgcolor on marquee elements
height on marquee elements
hspace on marquee elements
vspace on marquee elements
width on marquee elements
align on object elements
border on object elements
hspace on object elements
vspace on object elements
compact on ol elements
align on p elements
width on pre elements
align on table elements
bgcolor on table elements
border on table elements
bordercolor on table elements
cellpadding on table elements
cellspacing on table elements
frame on table elements
height on table elements
rules on table elements
width on table elements
align on tbody, thead, and tfoot elements
char on tbody, thead, and tfoot elements
charoff on tbody, thead, and tfoot elements
valign on tbody, thead, and tfoot elements
align on td and th elements
bgcolor on td and th elements
char on td and th elements
charoff on td and th elements
height on td and th elements
nowrap on td and th elements
valign on td and th elements
width on td and th elements
align on tr elements
bgcolor on tr elements
char on tr elements
charoff on tr elements
height on tr elements
valign on tr elements
compact on ul elements
type on ul elements
background on body, table, thead, tbody, tfoot, tr, td, and th elements
Use CSS instead.
11.3. Requirements for implementations
11.3.1. The applet element
This feature is in the process of being removed from the Web platform.
(This is a long process that takes many years.) Using the applet element
at this time is highly discouraged.
The applet element is a Java-specific variant of the embed element. The
applet element is now obsoleted so that all extension frameworks (Java,
.NET, Flash, etc) are handled in a consistent manner.
When the element matches any of the following conditions, it represents
its contents:
* The element is still in the stack of open elements of an HTML parser
or XML parser.
* The element is not in a document.
* The element’s node document is not fully active.
* The element’s node document's active sandboxing flag set has its
sandboxed plugins browsing context flag set.
* The element has an ancestor media element.
* The element has an ancestor object element that is not showing its
fallback content.
* No Java Language runtime plugin is available.
* A Java runtime plugin is available but it is disabled.
* The Should element be blocked a priori by Content Security Policy?
algorithm returns "Blocked" when executed on the element. [CSP3]
Otherwise, the user agent should instantiate a Java Language runtime
plugin, and should pass the names and values of all the attributes on the
element, in the order they were added to the element, with the attributes
added by the parser being ordered in source order, and then a parameter
named "PARAM" whose value is null, and then all the names and values of
parameters given by param elements that are children of the applet
element, in tree order, to the plugin used. If the plugin supports a
scriptable interface, the HTMLAppletElement object representing the
element should expose that interface. The applet element represents the
plugin.
The applet element is unaffected by the CSS display property. The Java
Language runtime is instantiated even if the element is hidden with a
'display:none' CSS style.
The applet element must implement the HTMLAppletElement interface.
// Note: intentionally not [HTMLConstructor]
interface HTMLAppletElement : HTMLElement {
attribute DOMString align;
attribute DOMString alt;
attribute DOMString archive;
attribute DOMString code;
attribute USVString codeBase;
attribute DOMString height;
attribute unsigned long hspace;
attribute DOMString name;
attribute USVString _object; // the underscore is not part of the identifier
attribute unsigned long vspace;
attribute DOMString width;
};
The align, alt, archive, code, height, hspace, name, object, vspace, and
width IDL attributes must reflect the respective content attributes of the
same name. For the purposes of reflection, the applet element’s object
content attribute is defined as containing a URL.
The codeBase IDL attribute must reflect the codebase content attribute,
which for the purposes of reflection is defined as containing a URL.
11.3.2. The marquee element
The marquee element is a presentational element that animates content. CSS
transitions and animations are a more appropriate mechanism.
[CSS3-ANIMATIONS] [CSS3-TRANSITIONS]
The task source for tasks mentioned in this section is the DOM
manipulation task source.
The marquee element must implement the HTMLMarqueeElement interface.
[HTMLConstructor]
interface HTMLMarqueeElement : HTMLElement {
[CEReactions] attribute DOMString behavior;
[CEReactions] attribute DOMString bgColor;
[CEReactions] attribute DOMString direction;
[CEReactions] attribute DOMString height;
[CEReactions] attribute unsigned long hspace;
[CEReactions] attribute long loop;
[CEReactions] attribute unsigned long scrollAmount;
[CEReactions] attribute unsigned long scrollDelay;
[CEReactions] attribute boolean trueSpeed;
[CEReactions] attribute unsigned long vspace;
[CEReactions] attribute DOMString width;
attribute EventHandler onbounce;
attribute EventHandler onfinish;
attribute EventHandler onstart;
void start();
void stop();
};
A marquee element can be turned on or turned off. When it is created, it
is turned on.
When the start() method is called, the marquee element must be turned on.
When the stop() method is called, the marquee element must be turned off.
When a marquee element is created, the user agent must queue a task to
fire an event named start at the element.
----------------------------------------------------------------------
The behavior content attribute on marquee elements is an enumerated
attribute with the following keywords (all non-conforming):
Keyword State
scroll scroll
slide slide
alternate alternate
The missing value default is the scroll state.
----------------------------------------------------------------------
The direction content attribute on marquee elements is an enumerated
attribute with the following keywords (all non-conforming):
Keyword State
left left
right right
up up
down down
The missing value default is the left state.
----------------------------------------------------------------------
The truespeed content attribute on marquee elements is a boolean
attribute.
----------------------------------------------------------------------
A marquee element has a marquee scroll interval, which is obtained as
follows:
1. If the element has a scrolldelay attribute, and parsing its value
using the rules for parsing non-negative integers does not return an
error, then let delay be the parsed value. Otherwise, let delay be
85. 2. If the element does not have a truespeed attribute, and the
delay value is less than 60, then let delay be 60 instead.
3. The marquee scroll interval is delay, interpreted in milliseconds.
----------------------------------------------------------------------
A marquee element has a marquee scroll distance, which, if the element has
a scrollamount attribute, and parsing its value using the rules for
parsing non-negative integers does not return an error, is the parsed
value interpreted in CSS pixels, and otherwise is 6 CSS pixels.
----------------------------------------------------------------------
A marquee element has a marquee loop count, which, if the element has a
loop content attribute, and parsing its value using the rules for parsing
integers does not return an error or a number less than 1, is the parsed
value, and otherwise is -1.
The loop IDL attribute, on getting, must return the element’s marquee loop
count; and on setting, if the new value is different than the element’s
marquee loop count and either greater than zero or equal to -1, must set
the element’s loop content attribute (adding it if necessary) to the valid
integer that represents the new value. (Other values are ignored.)
A marquee element also has a marquee current loop index, which is zero
when the element is created.
The rendering layer will occasionally increment the marquee current loop
index, which must cause the following steps to be run:
1. If the marquee loop count is -1, then abort these steps.
2. Increment the marquee current loop index by one.
3. If the marquee current loop index is now equal to or greater than the
element’s marquee loop count, turn off the marquee element and queue a
task to fire an event named finish at the marquee element.
Otherwise, if the behavior attribute is in the alternate state, then
queue a task to fire an event named bounce at the marquee element.
Otherwise, queue a task to fire an event named start at the marquee
element.
----------------------------------------------------------------------
The following are the event handlers (and their corresponding event
handler event types) that must be supported, as event handler content
attributes and event handler IDL attributes, by marquee elements:
Event handler Event handler event type
onbounce bounce
onfinish finish
onstart start
----------------------------------------------------------------------
The behavior, direction, height, hspace, vspace, and width IDL attributes
must reflect the respective content attributes of the same name.
The bgColor IDL attribute must reflect the bgcolor content attribute.
The scrollAmount IDL attribute must reflect the scrollamount content
attribute. The default value is 6.
The scrollDelay IDL attribute must reflect the scrolldelay content
attribute. The default value is 85.
The trueSpeed IDL attribute must reflect the truespeed content attribute.
11.3.3. Frames
The frameset element acts as the body element in documents that use
frames.
The frameset element must implement the HTMLFrameSetElement interface.
[HTMLConstructor]
interface HTMLFrameSetElement : HTMLElement {
[CEReactions] attribute DOMString cols;
[CEReactions] attribute DOMString rows;
};
HTMLFrameSetElement implements WindowEventHandlers;
The cols and rows content attributes for the frameset element.
The cols and rows IDL attributes of the frameset element must reflect the
respective content attributes of the same name.
The frameset element exposes as event handler content attributes a number
of the event handlers of the Window object. It also mirrors their event
handler IDL attributes.
The onblur, onerror, onfocus, onload, onresize, and onscroll event
handlers of the Window object, exposed on the frameset element, replace
the generic event handlers with the same names normally supported by HTML
elements.
----------------------------------------------------------------------
The frame element defines a nested browsing context similar to the iframe
element, but rendered within a frameset element.
A frame element is said to be an active frame element when it is in a
document.
When a frame element is created as an active frame element, or becomes an
active frame element after not having been one, the user agent must create
a new browsing context, set the element’s nested browsing context to the
newly-created browsing context, and then process the frame attributes for
the first time. If the element has a name attribute, the browsing context
name must be set to the value of this attribute; otherwise, the browsing
context name must be set to the empty string.
When a frame element stops being an active frame element, the user agent
must discard the element’s nested browsing context, and then set the
element’s nested browsing context to null..
Whenever a frame element with a non-null nested browsing context has its
src attribute set, changed, or removed, the user agent must process the
frame attributes.
When the user agent is to process the frame attributes, it must run the
first appropriate steps from the following list:
If the element has no src attribute specified, and the user agent is
processing the frame's attributes for the first time
Queue a task to fire an event named load at the frame element.
Otherwise
Run the otherwise steps for iframe or frame elements.
Any navigation required of the user agent in the process the frame
attributes algorithm must use the frame element’s node document's browsing
context as the source browsing context.
Furthermore, if the active document of the element’s nested browsing
context before such a navigation was not completely loaded at the time of
the new navigation, then the navigation must be completed with replacement
enabled.
Similarly, if the nested browsing context's session history contained only
one Document when the process the frame attributes algorithm was invoked,
and that was the about:blank Document created when the nested browsing
context was created, then any navigation required of the user agent in
that algorithm must be completed with replacement enabled.
When a Document in a frame is marked as completely loaded, the user agent
must queue a task to fire an event named load at the frame element.
The task source for the tasks above is the DOM manipulation task source.
When a frame element’s has a non-null nested browsing context, and its
nested browsing context's active document is not ready for post-load
tasks, and when anything is delaying the load event of the frame element’s
browsing context's active document, and when the frame element’s browsing
context is in the delaying load events mode, the frame must delay the load
event of its document.
Whenever the <name attribute is set and the frame element’s nested
browsing context is non-null, the nested browsing context's name must be
changed to the new value. If the attribute is removed, the browsing
context name must be set to the empty string.
The frame element must implement the HTMLFrameElement interface.
[HTMLConstructor]
interface HTMLFrameElement : HTMLElement {
[CEReactions] attribute DOMString name;
[CEReactions] attribute DOMString scrolling;
[CEReactions] attribute USVString src;
[CEReactions] attribute DOMString frameBorder;
[CEReactions] attribute USVString longDesc;
[CEReactions] attribute boolean noResize;
readonly attribute Document? contentDocument;
readonly attribute WindowProxy? contentWindow;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString marginHeight;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString marginWidth;
};
The name, scrolling, and src IDL attributes of the frame element must
reflect the respective content attributes of the same name. For the
purposes of reflection, the frame element’s src content attribute is
defined as containing a URL.
The frameBorder IDL attribute of the frame element must reflect the
element’s frameborder content attribute.
The longDesc IDL attribute of the frame element must reflect the element’s
longdesc content attribute, which for the purposes of reflection is
defined as containing a URL.
The noResize IDL attribute of the frame element must reflect the element’s
noresize content attribute.
The contentDocument IDL attribute, on getting, must return the content
document.
The contentWindow IDL attribute must return the WindowProxy object of the
frame element’s nested browsing context, if the element’s nested browsing
context is non-null, or return null otherwise.
The marginHeight IDL attribute of the frame element must reflect the
element’s marginheight content attribute.
The marginWidth IDL attribute of the frame element must reflect the
element’s marginwidth content attribute.
11.3.4. Other elements, attributes and APIs
User agents must treat acronym elements in a manner equivalent to abbr
elements in terms of semantics and for purposes of rendering.
----------------------------------------------------------------------
partial interface HTMLAnchorElement {
[CEReactions] attribute DOMString coords;
[CEReactions] attribute DOMString charset;
[CEReactions] attribute DOMString name;
[CEReactions] attribute DOMString shape;
};
The coords, charset, name, and shape IDL attributes of the th element must
reflect the respective content attributes of the same name.
----------------------------------------------------------------------
partial interface HTMLAreaElement {
[CEReactions] attribute boolean noHref;
};
The noHref IDL attribute of the area element must reflect the element’s
nohref content attribute.
----------------------------------------------------------------------
partial interface HTMLBodyElement {
[CEReactions, TreatNullAs=EmptyString] attribute DOMString text;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString link;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString vLink;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString aLink;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString bgColor;
attribute DOMString background;
};
The text IDL attribute of the body element must reflect the element’s text
content attribute.
The link IDL attribute of the body element must reflect the element’s link
content attribute.
The aLink IDL attribute of the body element must reflect the element’s
alink content attribute.
The vLink IDL attribute of the body element must reflect the element’s
vlink content attribute.
The bgColor IDL attribute of the body element must reflect the element’s
bgcolor content attribute.
The background IDL attribute of the body element must reflect the
element’s background content attribute. (The background content is not
defined to contain a URL, despite rules regarding its handling in the
Rendering section above.)
----------------------------------------------------------------------
partial interface HTMLBRElement {
[CEReactions] attribute DOMString clear;
};
The clear IDL attribute of the br element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLTableCaptionElement {
[CEReactions] attribute DOMString align;
};
The align IDL attribute of the caption element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLTableColElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString ch;
[CEReactions] attribute DOMString chOff;
[CEReactions] attribute DOMString vAlign;
[CEReactions] attribute DOMString width;
};
The align and width IDL attributes of the col element must reflect the
respective content attributes of the same name.
The ch IDL attribute of the col element must reflect the element’s char
content attribute.
The chOff IDL attribute of the col element must reflect the element’s
charoff content attribute.
The vAlign IDL attribute of the col element must reflect the element’s
valign content attribute.
----------------------------------------------------------------------
User agents must treat dir elements in a manner equivalent to ul elements
in terms of semantics and for purposes of rendering.
The dir element must implement the HTMLDirectoryElement interface.
[HTMLConstructor]
interface HTMLDirectoryElement : HTMLElement {
[CEReactions] attribute boolean compact;
};
The compact IDL attribute of the dir element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLDivElement {
[CEReactions] attribute DOMString align;
};
The align IDL attribute of the div element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLDListElement {
[CEReactions] attribute boolean compact;
};
The compact IDL attribute of the dl element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLEmbedElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString name;
};
The name and align IDL attributes of the embed element must reflect the
respective content attributes of the same name.
----------------------------------------------------------------------
The font element must implement the HTMLFontElement interface.
[HTMLConstructor]
interface HTMLFontElement : HTMLElement {
[CEReactions, TreatNullAs=EmptyString] attribute DOMString color;
[CEReactions] attribute DOMString face;
[CEReactions] attribute DOMString size;
};
The color, face, and size IDL attributes of the font element must reflect
the respective content attributes of the same name.
----------------------------------------------------------------------
partial interface HTMLHeadingElement {
[CEReactions] attribute DOMString align;
};
The align IDL attribute of the h1–h6 elements must reflect the content
attribute of the same name.
----------------------------------------------------------------------
The profile IDL attribute on head elements (with the HTMLHeadElement
interface) is intentionally omitted. Unless so required by another
applicable specification, implementations would therefore not support this
attribute. (It is mentioned here as it was defined in a previous version
of the DOM specifications.)
----------------------------------------------------------------------
partial interface HTMLHRElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString color;
[CEReactions] attribute boolean noShade;
[CEReactions] attribute DOMString size;
[CEReactions] attribute DOMString width;
};
The align, color, size, and width IDL attributes of the hr element must
reflect the respective content attributes of the same name.
The noShade IDL attribute of the hr element must reflect the element’s
noshade content attribute.
----------------------------------------------------------------------
partial interface HTMLHtmlElement {
[CEReactions] attribute DOMString version;
};
The version IDL attribute of the html element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLIFrameElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString scrolling;
[CEReactions] attribute DOMString frameBorder;
[CEReactions] attribute USVString longDesc;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString marginHeight;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString marginWidth;
};
The align and scrolling IDL attributes of the iframe element must reflect
the respective content attributes of the same name.
The frameBorder IDL attribute of the iframe element must reflect the
element’s frameborder content attribute.
The longDesc IDL attribute of the iframe element must reflect the
element’s longdesc content attribute, which for the purposes of reflection
is defined as containing a URL.
The marginHeight IDL attribute of the iframe element must reflect the
element’s marginheight content attribute.
The marginWidth IDL attribute of the iframe element must reflect the
element’s marginwidth content attribute.
----------------------------------------------------------------------
partial interface HTMLImageElement {
[CEReactions] attribute DOMString name;
[CEReactions] attribute USVString lowsrc;
[CEReactions] attribute DOMString align;
[CEReactions] attribute unsigned long hspace;
[CEReactions] attribute unsigned long vspace;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString border;
};
The name, align, border, hspace, and vspace IDL attributes of the img
element must reflect the respective content attributes of the same name.
The lowsrc IDL attribute of the img element must reflect the element’s
lowsrc content attribute, which for the purposes of reflection is defined
as containing a URL.
----------------------------------------------------------------------
partial interface HTMLInputElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString useMap;
};
The align IDL attribute of the input element must reflect the content
attribute of the same name.
The useMap IDL attribute of the input element must reflect the element’s
usemap content attribute.
----------------------------------------------------------------------
partial interface HTMLLegendElement {
[CEReactions] attribute DOMString align;
};
The align IDL attribute of the legend element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLLIElement {
[CEReactions] attribute DOMString type;
};
The type IDL attribute of the li element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLLinkElement {
[CEReactions] attribute DOMString charset;
[CEReactions] attribute DOMString target;
};
The charset and target IDL attributes of the link element must reflect the
respective content attributes of the same name.
----------------------------------------------------------------------
User agents must treat listing elements in a manner equivalent to pre
elements in terms of semantics and for purposes of rendering.
----------------------------------------------------------------------
partial interface HTMLMenuElement {
[CEReactions] attribute boolean compact;
};
The compact IDL attribute of the menu element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLMetaElement {
[CEReactions] attribute DOMString scheme;
};
User agents may treat the scheme content attribute on the meta element as
an extension of the element’s name content attribute when processing a
meta element with a name attribute whose value is one that the user agent
recognizes as supporting the scheme attribute.
User agents are encouraged to ignore the scheme attribute and instead
process the value given to the metadata name as if it had been specified
for each expected value of the scheme attribute.
For example, if the user agent acts on meta elements with name attributes
having the value "eGMS.subject.keyword", and knows that the scheme
attribute is used with this metadata name, then it could take the scheme
attribute into account, acting as if it was an extension of the name
attribute. Thus the following two meta elements could be treated as two
elements giving values for two different metadata names, one consisting of
a combination of "eGMS.subject.keyword" and "LGCL", and the other
consisting of a combination of "eGMS.subject.keyword" and "ORLY":
<!-- this markup is invalid -->
<meta name="eGMS.subject.keyword" scheme="LGCL" content="Abandoned vehicles">
<meta name="eGMS.subject.keyword" scheme="ORLY" content="Mah car: kthxbye">
The suggested processing of this markup, however, would be equivalent to
the following:
<meta name="eGMS.subject.keyword" content="Abandoned vehicles">
<meta name="eGMS.subject.keyword" content="Mah car: kthxbye">
The scheme IDL attribute of the meta element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLObjectElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString archive;
[CEReactions] attribute DOMString code;
[CEReactions] attribute boolean declare;
[CEReactions] attribute unsigned long hspace;
[CEReactions] attribute DOMString standby;
[CEReactions] attribute unsigned long vspace;
[CEReactions] attribute DOMString codeBase;
[CEReactions] attribute DOMString codeType;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString border;
};
The align, archive, border, code, declare, hspace, standby, and vspace IDL
attributes of the object element must reflect the respective content
attributes of the same name.
The codeBase IDL attribute of the object element must reflect the
element’s codebase content attribute, which for the purposes of reflection
is defined as containing a URL.
The codeType IDL attribute of the object element must reflect the
element’s codetype content attribute.
----------------------------------------------------------------------
partial interface HTMLOListElement {
[CEReactions] attribute boolean compact;
};
The compact IDL attribute of the ol element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLParagraphElement {
[CEReactions] attribute DOMString align;
};
The align IDL attribute of the p element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLParamElement {
[CEReactions] attribute DOMString type;
[CEReactions] attribute DOMString valueType;
};
The type IDL attribute of the param element must reflect the content
attribute of the same name.
The valueType IDL attribute of the param element must reflect the
element’s valuetype content attribute.
----------------------------------------------------------------------
User agents must treat plaintext elements in a manner equivalent to pre
elements in terms of semantics and for purposes of rendering. (The parser
has special behavior for this element, though.)
----------------------------------------------------------------------
partial interface HTMLPreElement {
[CEReactions] attribute long width;
};
The width IDL attribute of the pre element must reflect the content
attribute of the same name.
----------------------------------------------------------------------
partial interface HTMLScriptElement {
[CEReactions] attribute DOMString event;
[CEReactions] attribute DOMString htmlFor;
};
The event IDL attribute of the script element must reflect the element’s
event content attribute.
The htmlFor IDL attribute of the script element must reflect the element’s
for content attribute.
----------------------------------------------------------------------
partial interface HTMLTableElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString border;
[CEReactions] attribute DOMString frame;
[CEReactions] attribute DOMString rules;
[CEReactions] attribute DOMString summary;
[CEReactions] attribute DOMString width;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString bgColor;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString cellPadding;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString cellSpacing;
};
The align, border, frame, summary, rules, and width, IDL attributes of the
table element must reflect the respective content attributes of the same
name.
The bgColor IDL attribute of the table element must reflect the element’s
bgcolor content attribute.
The cellPadding IDL attribute of the table element must reflect the
element’s cellpadding content attribute.
The cellSpacing IDL attribute of the table element must reflect the
element’s cellspacing content attribute.
----------------------------------------------------------------------
partial interface HTMLTableSectionElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString ch;
[CEReactions] attribute DOMString chOff;
[CEReactions] attribute DOMString vAlign;
};
The align IDL attribute of the tbody, thead, and tfoot elements must
reflect the content attribute of the same name.
The ch IDL attribute of the tbody, thead, and tfoot elements must reflect
the elements' char content attributes.
The chOff IDL attribute of the tbody, thead, and tfoot elements must
reflect the elements' charoff content attributes.
The vAlign IDL attribute of the tbody, thead, and tfoot element must
reflect the elements' valign content attributes.
----------------------------------------------------------------------
partial interface HTMLTableCellElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString axis;
[CEReactions] attribute DOMString height;
[CEReactions] attribute DOMString width;
[CEReactions] attribute DOMString ch;
[CEReactions] attribute DOMString chOff;
[CEReactions] attribute boolean noWrap;
[CEReactions] attribute DOMString vAlign;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString bgColor;
};
The align, axis, height, and width IDL attributes of the td and th
elements must reflect the respective content attributes of the same name.
The ch IDL attribute of the td and th elements must reflect the elements'
char content attributes.
The chOff IDL attribute of the td and th elements must reflect the
elements' charoff content attributes.
The noWrap IDL attribute of the td and th elements must reflect the
elements' nowrap content attributes.
The vAlign IDL attribute of the td and th elements must reflect the
elements' valign content attributes.
The bgColor IDL attribute of the td and th elements must reflect the
elements' bgcolor content attributes.
----------------------------------------------------------------------
partial interface HTMLTableRowElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString ch;
[CEReactions] attribute DOMString chOff;
[CEReactions] attribute DOMString vAlign;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString bgColor;
};
The align IDL attribute of the tr element must reflect the content
attribute of the same name.
The ch IDL attribute of the tr element must reflect the element’s char
content attribute.
The chOff IDL attribute of the tr element must reflect the element’s
charoff content attribute.
The vAlign IDL attribute of the tr element must reflect the element’s
valign content attribute.
The bgColor IDL attribute of the tr element must reflect the element’s
bgcolor content attribute.
----------------------------------------------------------------------
partial interface HTMLUListElement {
[CEReactions] attribute boolean compact;
[CEReactions] attribute DOMString type;
};
The compact and type IDL attributes of the ul element must reflect the
respective content attributes of the same name.
----------------------------------------------------------------------
User agents must treat xmp elements in a manner equivalent to pre elements
in terms of semantics and for purposes of rendering. (The parser has
special behavior for this element though.)
----------------------------------------------------------------------
partial interface Document {
[CEReactions, TreatNullAs=EmptyString] attribute DOMString fgColor;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString linkColor;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString vlinkColor;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString alinkColor;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString bgColor;
[SameObject] readonly attribute HTMLCollection anchors;
[SameObject] readonly attribute HTMLCollection applets;
void clear();
void captureEvents();
void releaseEvents();
[SameObject] readonly attribute HTMLAllCollection all;
};
The attributes of the Document object listed in the first column of the
following table must reflect the content attribute on the body element
with the name given in the corresponding cell in the second column on the
same row, if the body element is a body element (as opposed to a frameset
element). When there is no body element or if it is a frameset element,
the attributes must instead return the empty string on getting and do
nothing on setting.
IDL attribute Content attribute
fgColor text
linkColor link
vlinkColor vlink
alinkColor alink
bgColor bgcolor
----------------------------------------------------------------------
The anchors attribute must return an HTMLCollection rooted at the Document
node, whose filter matches only a elements with name attributes.
The applets attribute must return an HTMLCollection rooted at the Document
node, whose filter matches only applet elements.
The clear(), captureEvents(), and releaseEvents() methods must do nothing.
----------------------------------------------------------------------
The all attribute must return an HTMLAllCollection rooted at the Document
node, whose filter matches all elements.
The object returned for all has several unusual behaviors:
* The user agent must act as if the ToBoolean abstract operator in
JavaScript converts the object returned for all to the false value.
* The user agent must act as if the Abstract Equality Comparison
algorithm, when given the object returned for all, returns true when
compared to the undefined and null values. (Comparisons using the
Strict Equality Comparison algorithm, and Abstract Equality
comparisons to other values such as strings or objects, are
unaffected.)
* The user agent must act such that the typeof operator in JavaScript
returns the string undefined when applied to the object returned for
all.
These requirements are a willful violation of the JavaScript specification
current at the time of writing. The JavaScript specification requires that
ToBoolean return true for all objects to the true value, and does not have
provisions for objects acting as if they were undefined for the purposes
of certain operators. This violation is motivated by a desire for
compatibility with two classes of legacy content: one that uses the
presence of document.all as a way to detect legacy user agents, and one
that only supports those legacy user agents and uses the document.all
object without testing for its presence first. [ECMA-262]
----------------------------------------------------------------------
partial interface Window {
void captureEvents();
void releaseEvents();
[Replaceable, SameObject] readonly attribute External external;
};
The captureEvents() and releaseEvents() methods must do nothing.
The external attribute of the Window interface must return an instance of
the External interface:
[NoInterfaceObject]
interface External {
void AddSearchProvider();
void IsSearchProviderInstalled();
};
The AddSearchProvider() and IsSearchProviderInstalled() methods must do
nothing.
----------------------------------------------------------------------
11.3.4.1. Plugins
This feature is in the process of being removed from the Web platform.
(This is a long process that takes many years.) Using the plugins API at
this time is highly discouraged.
Navigator implements NavigatorPlugins;
[NoInterfaceObject]
interface NavigatorPlugins {
[SameObject] readonly attribute PluginArray plugins;
[SameObject] readonly attribute MimeTypeArray mimeTypes;
boolean javaEnabled();
};
interface PluginArray {
void refresh(optional boolean reload = false);
readonly attribute unsigned long length;
getter Plugin? item(unsigned long index);
getter Plugin? namedItem(DOMString name);
};
interface MimeTypeArray {
readonly attribute unsigned long length;
getter MimeType? item(unsigned long index);
getter MimeType? namedItem(DOMString name);
};
interface Plugin {
readonly attribute DOMString name;
readonly attribute DOMString description;
readonly attribute DOMString filename;
readonly attribute unsigned long length;
getter MimeType? item(unsigned long index);
getter MimeType? namedItem(DOMString name);
};
interface MimeType {
readonly attribute DOMString type;
readonly attribute DOMString description;
readonly attribute DOMString suffixes; // comma-separated
readonly attribute Plugin enabledPlugin;
};
The plugins attribute must return a PluginArray object.
The mimeTypes attribute must return a MimeTypeArray object.
----------------------------------------------------------------------
A PluginArray object represents none, some, or all of the plugins
supported by the user agent, each of which is represented by a Plugin
object. Each of these Plugin objects may be hidden plugins. A hidden
plugin can’t be enumerated, but can still be inspected by using its name.
The fewer plugins are represented by the PluginArray object, and of those,
the more that are hidden, the more the user’s privacy will be protected.
Each exposed plugin increases the number of bits that can be derived for
fingerprinting. Hiding a plugin helps, but unless it is an extremely rare
plugin, it is likely that a site attempting to derive the list of plugins
can still determine whether the plugin is supported or not by probing for
it by name (the names of popular plugins are widely known). Therefore not
exposing a plugin at all is preferred. Unfortunately, many legacy sites
use this feature to determine, for example, which plugin to use to play
video. Not exposing any plugins at all might therefore not be entirely
plausible.
The PluginArray objects created by a user agent must not be live. The set
of plugins represented by the objects must not change once an object is
created, except when it is updated by the refresh() method.
Each plugin represented by a PluginArray can support a number of MIME
types. For each such plugin, the user agent must pick one or more of these
MIME types to be those that are explicitly supported.
The explicitly supported MIME types of a plugin are those that are exposed
through the Plugin and MimeTypeArray interfaces. As with plugins
themselves, any variation between users regarding what is exposed allows
sites to fingerprint users. User agents are therefore encouraged to expose
the same MIME types for all users of a plugin, regardless of the actual
types supported... at least, within the constraints imposed by
compatibility with legacy content.
The supported property indices of a PluginArray object are the numbers
from zero to the number of non-hidden plugins represented by the object,
if any.
The length attribute must return the number of non-hidden plugins
represented by the object.
The item() method of a PluginArray object must return null if the argument
is not one of the object’s supported property indices, and otherwise must
return the result of running the following steps, using the method’s
argument as index:
1. Let list be the Plugin objects representing the non-hidden plugins
represented by the PluginArray object.
2. Sort list alphabetically by the name of each Plugin.
3. Return the indexth entry in list.
It is important for privacy that the order of plugins not leak additional
information, e.g., the order in which plugins were installed.
The supported property names of a PluginArray object are the values of the
name attributes of all the Plugin objects represented by the PluginArray
object. The properties exposed in this way must be unenumerable.
The namedItem() method of a PluginArray object must return null if the
argument is not one of the object’s supported property names, and
otherwise must return the Plugin object, of those represented by the
PluginArray object, that has a name equal to the method’s argument.
The refresh() method of the PluginArray object of a Navigator object, when
invoked, must check to see if any plugins have been installed or
reconfigured since the user agent created the PluginArray object. If so,
and the method’s argument is true, then the user agent must act as if the
location.reload() method was called instead. Otherwise, the user agent
must update the PluginArray object and MimeTypeArray object created for
attributes of that Navigator object, and the Plugin and MimeType objects
created for those PluginArray and MimeTypeArray objects, using the same
Plugin objects for cases where the name is the same, and the same MimeType
objects for cases where the type is the same, and creating new objects for
cases where there were no matching objects immediately prior to the
refresh() call. Old Plugin and MimeType objects must continue to return
the same values that they had prior to the update, though naturally now
the data is stale and may appear inconsistent (for example, an old
MimeType entry might list as its enabledPlugin a Plugin object that no
longer lists that MimeType as a supported MimeType).
----------------------------------------------------------------------
A MimeTypeArray object represents the MIME types explicitly supported by
plugins supported by the user agent, each of which is represented by a
MimeType object.
The MimeTypeArray objects created by a user agent must not be live. The
set of MIME types represented by the objects must not change once an
object is created, except when it is updated by the PluginArray object’s
refresh() method.
The supported property indices of a MimeTypeArray object are the numbers
from zero to the number of MIME types explicitly supported by non-hidden
plugins represented by the corresponding PluginArray object, if any.
The length attribute must return the number of MIME types explicitly
supported by non-hidden plugins represented by the corresponding
PluginArray object, if any.
The item() method of a MimeTypeArray object must return null if the
argument is not one of the object’s supported property indices, and
otherwise must return the result of running the following steps, using the
method’s argument as index:
1. Let list be the MimeType objects representing the MIME types
explicitly supported by non-hidden plugins represented by the
corresponding PluginArray object, if any.
2. Sort list alphabetically by the type of each MimeType.
3. Return the indexth entry in list.
It is important for privacy that the order of MIME types not leak
additional information, e.g., the order in which plugins were installed.
The supported property names of a MimeTypeArray object are the values of
the type attributes of all the MimeType objects represented by the
MimeTypeArray object. The properties exposed in this way must be
unenumerable.
The namedItem() method of a MimeTypeArray object must return null if the
argument is not one of the object’s supported property names, and
otherwise must return the MimeType object that has a type equal to the
method’s argument.
----------------------------------------------------------------------
A Plugin object represents a plugin. It has several attributes to provide
details about the plugin, and can be enumerated to obtain the list of MIME
types that it explicitly supports.
The Plugin objects created by a user agent must not be live. The set of
MIME types represented by the objects, and the values of the objects'
attributes, must not change once an object is created, except when updated
by the PluginArray object’s refresh() method.
The reported MIME types for a Plugin object are the MIME types explicitly
supported by the corresponding plugin when this object was last created or
updated by PluginArray.refresh(), whichever happened most recently.
The supported property indices of a Plugin object are the numbers from
zero to the number of reported MIME types.
The length attribute must return the number of reported MIME types.
The item() method of a Plugin object must return null if the argument is
not one of the object’s supported property indices, and otherwise must
return the result of running the following steps, using the method’s
argument as index:
1. Let list be the MimeType objects representing the reported MIME types.
2. Sort list alphabetically by the type of each MimeType.
3. Return the indexth entry in list.
It is important for privacy that the order of MIME types not leak
additional information, e.g., the order in which plugins were installed.
The supported property names of a Plugin object are the values of the type
attributes of the MimeType objects representing the reported MIME types.
The properties exposed in this way must be unenumerable.
The namedItem() method of a Plugin object must return null if the argument
is not one of the object’s supported property names, and otherwise must
return the MimeType object that has a type equal to the method’s argument.
The name attribute must return the plugin’s name.
The description and filename attributes must return user-agent-defined
(or, in all likelihood, plugin-defined) strings. In each case, the same
string must be returned each time, except that the strings returned may
change when the PluginArray.refresh() method updates the object.
If the values returned by the description or filename attributes vary
between versions of a plugin, they can be used both as a fingerprinting
vector and, even more importantly, as a trivial way to determine what
security vulnerabilities a plugin (and thus a browser) may have. It is
thus highly recommended that the description attribute just return the
same value as the name attribute, and that the filename attribute return
the empty string.
----------------------------------------------------------------------
A MimeType object represents a MIME type that is, or was, explicitly
supported by a plugin.
The MimeType objects created by a user agent must not be live. The values
of the objects' attributes must not change once an object is created,
except when updated by the PluginArray object’s refresh() method.
The type attribute must return the valid MIME type with no parameters
describing the MIME type.
The description and suffixes attributes must return user-agent-defined
(or, in all likelihood, plugin-defined) strings. In each case, the same
string must be returned each time, except that the strings returned may
change when the PluginArray.refresh() method updates the object.
If the values returned by the description or suffixes attributes vary
between versions of a plugin, they can be used both as a fingerprinting
vector and, even more importantly, as a trivial way to determine what
security vulnerabilities a plugin (and thus a browser) may have. It is
thus highly recommended that the description attribute just return the
same value as the type attribute, and that the suffixes attribute return
the empty string.
Commas in the suffixes attribute are interpreted as separating subsequent
filename extensions, as in "htm,html".
The enabledPlugin attribute must return the Plugin object that represents
the plugin that explicitly supported the MIME type that this MimeType
object represents when this object was last created or updated by
PluginArray.refresh(), whichever happened most recently.
----------------------------------------------------------------------
The javaEnabled() attribute must return true if the user agent supports a
plugin that supports the MIME type "application/x-java-vm"; otherwise it
must return false.
12. IANA considerations
12.1. text/html
This registration is for community review and will be submitted to the
IESG for review, approval, and registration with IANA.
Type name:
text
Subtype name:
html
Required parameters:
No required parameters
Optional parameters:
charset
The charset parameter may be provided to specify the
document’s character encoding, overriding any
character encoding declarations in the document other
than a Byte Order Mark (BOM). The parameter’s value
must be one of the labels of the character encoding
used to serialize the file. [ENCODING]
Encoding considerations:
8bit (see the section on character encoding declarations)
Security considerations:
Entire novels have been written about the security considerations
that apply to HTML documents. Many are listed in this document, to
which the reader is referred for more details. Some general
concerns bear mentioning here, however:
HTML is scripted language, and has a large number of APIs (some of
which are described in this document). Script can expose the user
to potential risks of information leakage, credential leakage,
cross-site scripting attacks, cross-site request forgeries, and a
host of other problems. While the designs in this specification
are intended to be safe if implemented correctly, a full
implementation is a massive undertaking and, as with any software,
user agents are likely to have security bugs.
Even without scripting, there are specific features in HTML which,
for historical reasons, are required for broad compatibility with
legacy content but that expose the user to unfortunate security
problems. In particular, the img element can be used in
conjunction with some other features as a way to effect a port
scan from the user’s location on the Internet. This can expose
local network topologies that the attacker would otherwise not be
able to determine.
HTML relies on a compartmentalization scheme sometimes known as
the same-origin policy. An origin in most cases consists of all
the pages served from the same host, on the same port, using the
same protocol.
It is critical, therefore, to ensure that any untrusted content
that forms part of a site be hosted on a different origin than any
sensitive content on that site. Untrusted content can easily spoof
any other page on the same origin, read data from that origin,
cause scripts in that origin to execute, submit forms to and from
that origin even if they are protected from cross-site request
forgery attacks by unique tokens, and make use of any third-party
resources exposed to or rights granted to that origin.
Interoperability considerations:
Rules for processing both conforming and non-conforming content
are defined in this specification.
Published specification:
This document is the relevant specification. Labeling a resource
with the text/html type asserts that the resource is an HTML
document using the HTML syntax.
Applications that use this media type:
Web browsers, tools for processing Web content, HTML authoring
tools, search engines, validators.
Additional information:
Magic number(s):
No sequence of bytes can uniquely identify an HTML
document. More information on detecting HTML
documents is available in the MIME Sniffing
specification. [MIMESNIFF]
File extension(s):
"html" and "htm" are commonly, but certainly not
exclusively, used as the extension for HTML
documents.
Macintosh file type code(s):
TEXT
Person & email address to contact for further information:
World Wide Web Consortium <web-human@w3.org>
Intended usage:
Common
Restrictions on usage:
No restrictions apply.
Authors:
Alex Danilo <adanilo@google.com>
Arron Eicholz <arronei@microsoft.com>>
Sangwhan Moon <sangwhan@iki.fi>
Steve Faulkner <sfaulkner@paciellogroup.com>
Travis Leithead <travil@microsoft.com>
Change controller:
W3C
Fragments used with text/html resources either refer to the indicated part
of the document or provide state information for in-page scripts.
12.2. multipart/x-mixed-replace
This registration is for community review and will be submitted to the
IESG for review, approval, and registration with IANA.
Type name:
multipart
Subtype name:
x-mixed-replace
Required parameters:
* boundary (defined in RFC2046) [RFC2046]
Optional parameters:
No optional parameters.
Encoding considerations:
binary
Security considerations:
Subresources of a multipart/x-mixed-replace resource can be of any
type, including types with non-trivial security implications such
as text/html.
Interoperability considerations:
None.
Published specification:
This specification describes processing rules for Web browsers.
Conformance requirements for generating resources with this type
are the same as for multipart/mixed. [RFC2046]
Applications that use this media type:
This type is intended to be used in resources generated by Web
servers, for consumption by Web browsers.
Additional information:
Magic number(s):
No sequence of bytes can uniquely identify a
multipart/x-mixed-replace resource.
File extension(s):
No specific file extensions are recommended for this
type.
Macintosh file type code(s):
No specific Macintosh file type codes are recommended
for this type.
Person & email address to contact for further information:
Ian Hickson <ian@hixie.ch>
Intended usage:
Common
Restrictions on usage:
No restrictions apply.
Author:
Ian Hickson <ian@hixie.ch>
Change controller:
W3C
Fragments used with multipart/x-mixed-replace resources apply to each body
part as defined by the type used by that body part.
12.3. application/xhtml+xml
This registration is for community review and will be submitted to the
IESG for review, approval, and registration with IANA.
Type name:
application
Subtype name:
xhtml+xml
Required parameters:
Same as for application/xml [RFC7303]
Optional parameters:
Same as for application/xml [RFC7303]
Encoding considerations:
Same as for application/xml [RFC7303]
Security considerations:
Same as for application/xml [RFC7303]
Interoperability considerations:
Same as for application/xml [RFC7303]
Published specification:
Labeling a resource with the application/xhtml+xml type asserts
that the resource is an XML document that likely has a document
element from the HTML namespace. Thus, the relevant specifications
are the XML specification, the Namespaces in XML specification,
and this specification. [XML] [XPTR-XMLNS]
Applications that use this media type:
Same as for application/xml [RFC7303]
Additional information:
Magic number(s):
Same as for application/xml [RFC7303]
File extension(s):
"xhtml" and "xht" are sometimes used as extensions
for XML resources that have a document element from
the HTML namespace.
Macintosh file type code(s):
TEXT
Person & email address to contact for further information:
Ian Hickson <ian@hixie.ch>
Intended usage:
Common
Restrictions on usage:
No restrictions apply.
Author:
Ian Hickson <ian@hixie.ch>
Change controller:
W3C
Fragments used with application/xhtml+xml resources have the same
semantics as with any XML MIME type. [RFC7303]
12.4. web+ scheme prefix
This section describes a convention for use with the IANA URI scheme
registry. It does not itself register a specific scheme. [RFC7595]
Scheme name:
Schemes starting with the four characters "web+" followed by one
or more letters in the range a-z.
Status:
Permanent
Scheme syntax:
Scheme-specific.
Scheme semantics:
Scheme-specific.
Encoding considerations:
All "web+" schemes should use UTF-8 encodings where relevant.
Applications/protocols that use this scheme name:
Scheme-specific.
Interoperability considerations:
The scheme is expected to be used in the context of Web
applications.
Security considerations:
Any Web page is able to register a handler for all "web+" schemes.
As such, these schemes must not be used for features intended to
be core platform features (e.g., network transfer protocols like
HTTP or FTP). Similarly, such schemes must not store confidential
information in their URLs, such as usernames, passwords, personal
information, or confidential project names.
Contact:
Ian Hickson <ian@hixie.ch>
Change controller:
Ian Hickson <ian@hixie.ch>
References:
Custom scheme and content handlers, HTML Living Standard:
https://html.spec.whatwg.org/#custom-handlers
Index
Terms defined by this specification
* "", in §4.7.13
* 1, in §4.4.6
* 2d
* context for canvas, in §4.12.4
* definition of, in §4.12.4
* a
* attr-value for ol/type, in §4.4.6
* (element), in §4.5.1
* abbr
* (element), in §4.5.9
* element-attr for th, in §4.9.10
* attribute for HTMLTableHeaderCellElement, in §4.9.10
* element-attr for td, in §11.2
* abort
* event for media, in §4.7.13.16
* event for global, in §Unnumbered section
* abort a document, in §6.7.12
* abort a running script, in §7.1.3.6
* aborted, in §6.7.12
* aborted prematurely, in §7.1.3.6
* aborted the running script, in §7.1.3.6
* aborting a document, in §6.7.12
* aborting the running script, in §7.1.3.6
* abort that parser, in §8.2.6
* abort the document, in §6.7.12
* abort the image request, in §4.7.5
* abort the parser, in §8.2.6
* abort the script, in §7.1.3.6
* about:, in §2.2.2
* about:blank, in §2.2.2
* about:html-kind, in §2.5.1
* about:legacy-compat, in §2.5.1
* about:srcdoc, in §2.5.1
* about-to-be-notified rejected promises list, in §7.1.3.1
* a browsing context is discarded, in §6.3.4
* absolute-anchored, in §4.11.4
* accept
* attribute for HTMLInputElement, in §4.10.5
* element-attr for input, in §4.10.5.1.17
* element-attr for form, in §11.2
* acceptCharset, in §4.10.3
* accept-charset, in §4.10.3
* Access Key, in §4.11.3.1
* accessKey, in §5.5.3
* accesskey, in §5.5.2
* acknowledged, in §8.2.4
* acronym, in §11.2
* Action, in §4.11.3.1
* action
* element-attr for form, in §4.10.18.6
* definition of, in §4.10.18.6
* attribute for HTMLFormElement, in §4.10.18.6
* activation behavior, in §5.3
* :active, in §4.15.2
* activeCues, in §4.7.13.11.5
* active document, in §6.1
* activeElement, in §5.4.6
* active flag, in §4.7.13.11.1
* active flag was set when the script started, in §4.7.13.11.5
* active frame element, in §11.3.3
* active parser, in §3.1.2
* active range, in §5.6.4
* active sandboxing flag set, in §6.5
* actually disabled, in §4.14
* actual value, in §4.10.14
* add()
* method for HTMLSelectElement, in §4.10.7
* method for DataTransferItemList, in §5.7.3.1
* addCue(cue), in §4.7.13.11.5
* add(data), in §5.7.3.1
* add(data, type), in §5.7.3.1
* add(element)
* method for HTMLOptionsCollection, in §2.7.2.3
* method for HTMLSelectElement, in §4.10.7
* add(element, before)
* method for HTMLOptionsCollection, in §2.7.2.3
* method for HTMLSelectElement, in §4.10.7
* address, in §4.4.2
* AddSearchProvider(), in §11.3.4
* addTextTrack(), in §4.7.13.11.5
* addTextTrack(kind), in §4.7.13.11.5
* addTextTrack(kind, label), in §4.7.13.11.5
* addTextTrack(kind, label, language), in §4.7.13.11.5
* addtrack, in §4.7.13.16
* adjusted current node, in §8.2.3.2
* adjust foreign attributes, in §8.2.5.1
* adjust MathML attributes, in §8.2.5.1
* adjust SVG attributes, in §8.2.5.1
* administrative level, in §4.10.18.7.1
* adoption agency algorithm, in §8.2.5.4.7
* a drag data item kind, in §5.7.2
* a drag data item type string, in §5.7.2
* advance, in §4.9.12.1
* advanced to the next child of the table, in §4.9.12.1
* advisory information, in §3.2.5.1
* affected by a base URL change, in §2.2.2
* after after body, in §8.2.5.4.22
* after after frameset, in §8.2.5.4.23
* After attribute name state, in §8.2.4.34
* After attribute value (quoted) state, in §8.2.4.39
* after body, in §8.2.5.4.19
* After DOCTYPE name state, in §8.2.4.56
* After DOCTYPE public identifier state, in §8.2.4.61
* After DOCTYPE public keyword state, in §8.2.4.57
* After DOCTYPE system identifier state, in §8.2.4.67
* After DOCTYPE system keyword state, in §8.2.4.63
* after frameset, in §8.2.5.4.21
* after head, in §8.2.5.4.6
* afterprint, in §Unnumbered section
* afterscriptexecute, in §Unnumbered section
* a known definite encoding, in §8.2.2.1
* a label, in §4.7.13.11.1
* a language, in §4.7.13.11.1
* alert(), in §7.6.1
* alert(message), in §7.6.1
* algorithm for assigning header cells, in §4.9.12.2
* algorithm for ending a row group, in §4.9.12.1
* algorithm for extracting a character encoding from a meta element, in
§2.6.5
* algorithm for growing downward-growing cells, in §4.9.12.1
* algorithm for processing row groups, in §4.9.12.1
* algorithm for processing rows, in §4.9.12.1
* algorithm to convert a Date object to a string, in §4.10.5
* algorithm to convert a number to a string, in §4.10.5
* algorithm to convert a string to a Date object, in §4.10.5
* algorithm to convert a string to a number, in §4.10.5
* align
* element-attr for caption, in §11.2
* element-attr for col, in §11.2
* element-attr for div, in §11.2
* element-attr for embed, in §11.2
* element-attr for hr, in §11.2
* element-attr for headings, in §11.2
* element-attr for iframe, in §11.2
* element-attr for input, in §11.2
* element-attr for img, in §11.2
* element-attr for legend, in §11.2
* element-attr for object, in §11.2
* element-attr for p, in §11.2
* element-attr for table, in §11.2
* element-attr for tbody, thead, tfoot, tablesection, in §11.2
* element-attr for td, th, tablecells, in §11.2
* element-attr for tr, in §11.2
* attribute for HTMLAppletElement, in §11.3.1
* attribute for HTMLTableCaptionElement, in §11.3.4
* attribute for HTMLTableColElement, in §11.3.4
* attribute for HTMLDivElement, in §11.3.4
* attribute for HTMLEmbedElement, in §11.3.4
* attribute for HTMLHeadingElement, in §11.3.4
* attribute for HTMLHRElement, in §11.3.4
* attribute for HTMLIFrameElement, in §11.3.4
* attribute for HTMLImageElement, in §11.3.4
* attribute for HTMLInputElement, in §11.3.4
* attribute for HTMLLegendElement, in §11.3.4
* attribute for HTMLObjectElement, in §11.3.4
* attribute for HTMLParagraphElement, in §11.3.4
* attribute for HTMLTableElement, in §11.3.4
* attribute for HTMLTableSectionElement, in §11.3.4
* attribute for HTMLTableCellElement, in §11.3.4
* attribute for HTMLTableRowElement, in §11.3.4
* align descendants, in §10.2
* alink, in §11.2
* aLink, in §11.3.4
* alinkColor, in §11.3.4
* a list of zero or more cues, in §4.7.13.11.1
* all
* value for effectAllowed, in §5.7.3
* attribute for Document, in §11.3.4
* "all"-named elements, in §2.7.2.1
* Allowed ARIA role attribute values, in §3.2.3
* Allowed ARIA state and property attributes, in §3.2.3
* allowed in the body, in §4.2.4
* allowed keywords and their meanings, in §4.8.6
* allowed to navigate, in §6.1.3
* allowed to show a popup, in §6.1.5
* allowed to use, in §4.7.6
* allowed value step, in §4.10.5.3.8
* allow-forms, in §6.5
* allowfullscreen, in §4.7.6
* allowFullscreen, in §4.7.6
* allow-modals, in §6.5
* allowPaymentRequest, in §4.7.6
* allowpaymentrequest, in §4.7.6
* allow-pointer-lock, in §6.5
* allow-popups, in §6.5
* allow-popups-to-escape-sandbox, in §6.5
* allow-presentation, in §6.5
* allow-same-origin, in §6.5
* allow-scripts, in §6.5
* allow-top-navigation, in §6.5
* allowtransparency, in §11.2
* alphanumeric ASCII characters, in §2.4.1
* already started, in §4.12.1.1
* alt
* element-attr for img, in §4.7.5
* attribute for HTMLImageElement, in §4.7.5
* element-attr for area, in §4.7.15
* attribute for HTMLAreaElement, in §4.7.15
* attribute for HTMLInputElement, in §4.10.5
* element-attr for input, in §4.10.5.1.19
* attribute for HTMLAppletElement, in §11.3.1
* alternate
* element-state for link, in §4.8.6.1
* attr-value for marquee/behavior, in §11.3.2
* state for marquee/behavior, in §11.3.2
* alternative, in §4.7.13.10.1
* ambiguous ampersand, in §8.1.4
* a mode, in §4.7.13.11.1
* an alternative stylesheet, in §4.8.6.11
* ancestor, in §6.1.1
* ancestor browsing context, in §6.1.1
* ancestorOrigins, in §6.6.4
* ancestor origins array, in §6.6.4
* anchor-point, in §4.11.4.1
* anchors, in §11.3.4
* an end time, in §4.7.13.11.1
* An entry with persisted user state, in §6.6.1
* a new date object, in §2.2.2
* a new start for session storage, in §6.1.5
* an identifier, in §4.7.13.11.1
* an iframe srcdoc document, in §4.7.6
* animation frame callback identifier, in §7.9
* an in-band metadata track dispatch type, in §4.7.13.11.1
* an indicated part of the document, in §6.7.9
* annotates, in §4.8.1
* annotation pairing, in §4.5.10
* anonymous, in §2.6.6
* Anonymous, in §2.6.6
* an overridden reload, in §3.1
* An unstyled document view, in §10.9
* any, in §4.8.6.5
* API base URL, in §7.1.3.1
* APIs, in §4.10.5.4
* API URL character encoding, in §7.1.3.1
* API value, in §4.10.11
* a plausible language, in §7.7.1.2
* appCodeName, in §7.7.1.1
* applet, in §11.3.1
* applets, in §11.3.4
* applicable specification, in §2.2.3
* application-name, in §4.2.5.1
* application/x-www-form-urlencoded, in §4.10.18.6
* application/x-www-form-urlencoded encoding algorithm, in §4.10.21.6
* apply, in §4.10.5
* appName, in §7.7.1.1
* appropriate end tag token, in §8.2.4
* appropriate form encoding algorithm, in §4.10.21.3
* appropriate place for inserting a node, in §8.2.5.1
* appropriate template contents owner document, in §4.12.3
* appVersion, in §7.7.1.1
* archive
* element-attr for object, in §11.2
* attribute for HTMLAppletElement, in §11.3.1
* attribute for HTMLObjectElement, in §11.3.4
* area, in §4.7.15
* a readiness state, in §4.7.13.11.1
* areas, in §4.7.14
* a registered handler, in §7.7.1.3
* aria-*, in §2.2.2
* art directed, in §4.7.1
* art direction, in §4.7.1
* article, in §4.3.2
* as a download, in §4.8.5
* ASCII case-insensitive, in §2.3
* ASCII-compatible encoding, in §2.1.6
* ASCII digits, in §2.4.1
* ASCII hex digits, in §2.4.1
* ASCII letters, in §2.4.1
* ASCII lowercase, in §2.3
* ASCII serialization of an origin, in §6.4
* ASCII uppercase, in §2.3
* a serialization of the bitmap as a file, in §4.12.4.2
* a serialization of the canvas element’s bitmap as a file, in §4.12.4.2
* as hints for the rendering, in §10.2
* aside, in §4.3.5
* ask for a reset, in §4.10.7
* asks for a reset, in §4.10.7
* assign(), in §6.6.4
* assigned access key, in §5.5.3
* assigned media provider object, in §4.7.13.2
* assign(url), in §6.6.4
* associated, in §4.10.17.3
* associated content-type headers, in §2.6.4
* associated content-type metadata, in §2.6.4
* associated element, in §3.2.5.7
* associated inert template document, in §4.12.3
* associate section, in §4.3.9.1
* a start time, in §4.7.13.11.1
* a style sheet that is blocking scripts, in §4.2.7
* async
* element-attr for script, in §4.12.1
* attribute for HTMLScriptElement, in §4.12.1
* atob(), in §7.3
* atob(atob), in §7.2
* Attribute names, in §8.1.2.3
* Attribute name state, in §8.2.4.33
* Attributes, in §8.1.2.3
* Attributes for form submission, in §4.10.18.6
* attribute’s serialized name, in §8.3
* Attribute value (double-quoted) state, in §8.2.4.36
* Attribute values, in §8.1.2.3
* Attribute value (single-quoted) state, in §8.2.4.37
* Attribute value (unquoted) state, in §8.2.4.38
* a type change is signalled, in §4.10.5
* A type that the user agent knows it cannot render, in §4.7.13.3
* audio, in §4.7.11
* Audio(src), in §4.7.11
* AudioTrack, in §4.7.13.10.1
* AudioTrackList, in §4.7.13.10.1
* audioTracks, in §4.7.13.10
* author
* definition of, in §4.2.5.1
* element-state for link, in §4.8.6.2
* "auto", in §6.6.2
* auto
* attr-value for global/dir, in §3.2.5.5
* state for dir, in §3.2.5.5
* value for HTMLMediaElement/preload, in §4.7.13.5
* state for scope, in §4.9.10
* value for scrollRestorationMode, in §6.6.1
* enum-value for ScrollRestoration, in §6.6.2
* autocomplete
* attribute for HTMLFormElement, in §4.10.3
* element-attr for autocompleteelements, form, input, select,
textarea, in §4.10.18.7.1
* attribute for HTMLInputElement, HTMLSelectElement,
HTMLTextAreaElement, in §4.10.18.7.2
* autofill, in §4.10.18.7
* autofill anchor mantle, in §4.10.18.7.1
* Autofill detail tokens, in §4.10.18.7.1
* autofill expectation mantle, in §4.10.18.7.1
* autofill field, in §4.10.18.7.1
* autofill field name, in §4.10.18.7.2
* autofill hint set, in §4.10.18.7.2
* autofill mechanism, in §4.10.18.7
* autofill scope, in §4.10.18.7.2
* autofills form controls, in §4.10.18.7.2
* autofocus
* element-attr for formelements, input, button, select, textarea,
in §4.10.18.6.1
* attribute for HTMLInputElement, HTMLButtonElement,
HTMLSelectElement, HTMLTextAreaElement, in §4.10.18.6.1
* Automatic, in §4.7.13.5
* autoplay
* element-attr for media, in §4.7.13.7
* attribute for HTMLMediaElement, in §4.7.13.7
* autoplaying flag, in §4.7.13.5
* auxiliary browsing context, in §6.1.2
* auxiliary browsing contexts, in §6.1.2
* Available, in §4.7.5
* available
* state for img, in §4.7.5
* definition of, in §4.10.5.1.19
* await a stable state, in §7.1.4.2
* a WebSocket message has been received, in §2.2.2
* axis
* element-attr for td, in §11.2
* attribute for HTMLTableCellElement, in §11.3.4
* b, in §4.5.23
* back(), in §6.6.2
* background
* element-attr for body, table, thead, tbody, tfoot, tr, td, th,
common, in §11.2
* attribute for HTMLBodyElement, in §11.3.4
* badInput, in §4.10.20.3
* BarProp, in §6.3.6
* barred from constraint validation, in §4.10.20.1
* barring it from constraint validation, in §4.10.20.1
* base
* element-attr for xml, in §3.2.5.4
* (element), in §4.2.3
* basefont, in §11.2
* base URL, in §7.1.3.1
* base URL change steps, in §2.2.2
* bdi, in §4.5.26
* bdo, in §4.5.27
* Before attribute name state, in §8.2.4.32
* Before attribute value state, in §8.2.4.35
* Before DOCTYPE name state, in §8.2.4.54
* Before DOCTYPE public identifier state, in §8.2.4.58
* Before DOCTYPE system identifier state, in §8.2.4.64
* before head, in §8.2.5.4.3
* before html, in §8.2.5.4.2
* beforeprint, in §Unnumbered section
* beforescriptexecute, in §Unnumbered section
* beforeunload, in §Unnumbered section
* BeforeUnloadEvent, in §6.7.11.1
* behavior
* element-attr for marquee, in §11.3.2
* attribute for HTMLMarqueeElement, in §11.3.2
* being activated, in §4.15.2
* being actively pointed at, in §4.15.2
* being rendered, in §10.1
* being unloaded, in §6.7.11
* being used as relevant canvas fallback content, in §4.12.4
* best floating-point number, in §2.4.4.3
* Between DOCTYPE public and system identifiers state, in §8.2.4.62
* bgcolor
* element-attr for body, in §11.2
* element-attr for marquee, in §11.2
* element-attr for table, in §11.2
* element-attr for td, th, tablecells, in §11.2
* element-attr for tr, in §11.2
* bgColor
* attribute for HTMLMarqueeElement, in §11.3.2
* attribute for HTMLBodyElement, in §11.3.4
* attribute for HTMLTableElement, in §11.3.4
* attribute for HTMLTableCellElement, in §11.3.4
* attribute for HTMLTableRowElement, in §11.3.4
* attribute for Document, in §11.3.4
* bgsound, in §11.2
* big, in §11.2
* Big5, in §8.2.2.3
* billing, in §4.10.18.7.1
* blank, in §10.3.10
* blink, in §11.2
* blob:, in §2.2.2
* BlobCallback, in §4.12.4
* blocked by a modal dialog, in §5.2
* blocked by the modal dialog, in §5.2
* blocked media element, in §4.7.13.8
* blocked-on-parser, in §4.7.13.11.1
* blockquote, in §4.4.5
* blur, in §Unnumbered section
* blur()
* method for Window, in §5.4.6
* method for HTMLElement, in §5.4.6
* body
* attribute for Document, in §3.1.3
* (element), in §4.3.1
* body-ok, in §4.8.6
* Bogus comment state, in §8.2.4.41
* Bogus DOCTYPE state, in §8.2.4.68
* bookmark, in §4.8.6.3
* boolean attribute, in §2.4.2
* boolean attributes, in §2.4.2
* border
* element-attr for HTMLTableElement, in §4.9.1
* element-attr for input, in §11.2
* element-attr for img, in §11.2
* element-attr for object, in §11.2
* element-attr for table, in §11.2
* attribute for HTMLImageElement, in §11.3.4
* attribute for HTMLObjectElement, in §11.3.4
* attribute for HTMLTableElement, in §11.3.4
* bordercolor
* element-attr for frame, in §11.2
* element-attr for table, in §11.2
* bottommargin, in §11.2
* bounce, in §11.3.2
* br, in §4.5.29
* broken, in §4.7.5
* Broken, in §4.7.5
* browsing context, in §6.1
* browsing context container, in §6.1.1
* browsing context name, in §6.1.5
* browsing contexts, in §6.1
* browsing context scope origin, in §6.1.3
* btoa(), in §7.3
* btoa(btoa), in §7.2
* buffered, in §4.7.13.5
* Button
* element-state for input, in §4.10.5.1.21
* element-state for button/type, in §4.10.6
* button
* attr-value for input/type, in §4.10.5
* (element), in §4.10.6
* attr-value for button/type, in §4.10.6
* buttons, in §4.10.2
* calling scripts, in §7.1.3.4
* can be focused, in §5.4.3
* cancel, in §Unnumbered section
* cancelAnimationFrame(), in §7.9
* cancelAnimationFrame(handle), in §7.9
* canceled activation steps, in §5.3
* candidate for constraint validation, in §4.10.20.1
* candidates for constraint validation, in §4.10.20.1
* canplay, in §4.7.13.16
* canplaythrough, in §4.7.13.16
* CanPlayTypeResult, in §4.7.13
* canPlayType(type), in §4.7.13.3
* canvas, in §4.12.4
* canvas blob serialization task source, in §4.12.4
* canvas context mode, in §4.12.4
* caption
* attribute for HTMLTableElement, in §4.9.1
* (element), in §4.9.2
* captions
* attr-value for track/kind, in §4.7.12
* attr-value for commonTrack/kind, in §4.7.13.10.1
* dfn for track, in §4.7.13.11.1
* enum-value for TextTrackKind, in §4.7.13.11.5
* Captions, in §4.7.12
* "captions", in §4.7.13.11.5
* captureEvents()
* method for Document, in §11.3.4
* method for Window, in §11.3.4
* case-sensitive, in §2.3
* case-sensitively, in §2.3
* Categories, in §3.2.3
* causes the opener attribute to remain null, in §6.1.5
* CDATA section bracket state, in §8.2.4.70
* CDATA section end state, in §8.2.4.71
* CDATA sections, in §8.1.5
* CDATA section state, in §8.2.4.69
* cell, in §4.9.12
* cellIndex, in §4.9.11
* cellpadding, in §11.2
* cellPadding, in §11.3.4
* cells
* attribute for HTMLTableRowElement, in §4.9.8
* definition of, in §4.9.12
* cellspacing, in §11.2
* cellSpacing, in §11.3.4
* center, in §11.2
* centered alignment, in §4.11.4
* ch
* attribute for HTMLTableColElement, in §11.3.4
* attribute for HTMLTableSectionElement, in §11.3.4
* attribute for HTMLTableCellElement, in §11.3.4
* attribute for HTMLTableRowElement, in §11.3.4
* change
* definition of, in §2.1.3
* event for MediaList, in §4.7.13.16
* event for input, in §4.10.5.5
* event for global, in §Unnumbered section
* change the encoding, in §8.2.2.4
* "chapters", in §4.7.13.11.5
* Chapters, in §4.7.12
* chapters
* attr-value for track/kind, in §4.7.12
* dfn for track, in §4.7.13.11.1
* enum-value for TextTrackKind, in §4.7.13.11.5
* char
* element-attr for col, in §11.2
* element-attr for tbody, thead, tfoot, tablesection, in §11.2
* element-attr for td, th, tablecells, in §11.2
* element-attr for tr, in §11.2
* character, in §2.1.6
* character encoding, in §2.1.6
* character encoding declaration, in §4.2.5.5
* character height, in §4.10.11
* character reference code, in §8.2.4.73
* Character reference end state, in §8.2.4.79
* character references, in §8.1.4
* Character reference state, in §8.2.4.72
* character width, in §4.10.11
* charoff
* element-attr for col, in §11.2
* element-attr for tbody, thead, tfoot, tablesection, in §11.2
* element-attr for td, th, tablecells, in §11.2
* element-attr for tr, in §11.2
* _charset_, in §4.10.18.1
* charset
* element-attr for meta, in §4.2.5
* element-attr for script, in §4.12.1
* attribute for HTMLScriptElement, in §4.12.1
* element-attr for a, in §11.2
* element-attr for link, in §11.2
* attribute for HTMLAnchorElement, in §11.3.4
* attribute for HTMLLinkElement, in §11.3.4
* Checkbox, in §4.10.5.1.15
* checkbox, in §4.10.5
* checked
* element-attr for input, in §4.10.5
* attribute for HTMLInputElement, in §4.10.5.4
* :checked, in §4.15.2
* checkedness, in §4.10.17.1
* check if we can run script, in §7.1.3.4
* checkValidity()
* method for HTMLObjectElement, in §4.7.8
* method for HTMLFormElement, in §4.10.3
* method for HTMLInputElement, HTMLButtonElement,
HTMLSelectElement, HTMLTextAreaElement, HTMLOutputElement,
HTMLFieldSetElement, in §4.10.20.3
* child browsing context, in §6.1.1
* child browsing context name property set, in §6.3.3
* child browsing contexts, in §6.1.1
* child text content, in §2.1.3
* chOff
* attribute for HTMLTableColElement, in §11.3.4
* attribute for HTMLTableSectionElement, in §11.3.4
* attribute for HTMLTableCellElement, in §11.3.4
* attribute for HTMLTableRowElement, in §11.3.4
* circ, in §4.7.15
* circle, in §4.7.15
* circle state, in §4.7.15
* Circle state, in §4.7.15
* cite
* element-attr for blockquote, in §4.4.5
* attribute for HTMLQuoteElement, in §4.4.5
* (element), in §4.5.6
* element-attr for q, in §4.5.7
* element-attr for edits, in §4.6.3
* attribute for HTMLModElement, in §4.6.3
* class, in §3.2.5
* classic script, in §7.1.3.1
* classid, in §11.2
* clean up after running script, in §7.1.3.4
* cleanup Indexed Database transactions, in §2.2.2
* clear
* element-attr for br, in §11.2
* attribute for HTMLBRElement, in §11.3.4
* clear()
* method for DataTransferItemList, in §5.7.3.1
* method for Document, in §11.3.4
* clearData(), in §5.7.3
* clearData(format), in §5.7.3
* clearInterval()
* method for WindowOrWorkerGlobalScope, in §7.2
* method for WindowTimers, in §7.5
* clearInterval(handle), in §7.2
* clear the list of active formatting elements up to the last marker, in
§8.2.3.3
* clear the stack back to a table body context, in §8.2.5.4.13
* clear the stack back to a table context, in §8.2.5.4.9
* clear the stack back to a table row context, in §8.2.5.4.14
* clearTimeout()
* method for WindowOrWorkerGlobalScope, in §7.2
* method for WindowTimers, in §7.5
* clearTimeout(handle), in §7.2
* click(), in §5.3
* client message queue, in §2.2.2
* close()
* method for HTMLDialogElement, in §4.11.4
* method for Window, in §6.3.1
* method for Document, in §7.4.2
* close, in §Unnumbered section
* close a browsing context, in §6.3.5
* close a p element, in §8.2.5.4.7
* closed, in §6.3.1
* close(returnValue), in §4.11.4
* close the cell, in §8.2.5.4.15
* close the dialog, in §4.11.4
* close the WebSocket connection, in §2.2.2
* code
* (element), in §4.5.17
* attribute for MediaError, in §4.7.13.1
* element-attr for object, in §11.2
* attribute for HTMLAppletElement, in §11.3.1
* attribute for HTMLObjectElement, in §11.3.4
* codeBase
* attribute for HTMLAppletElement, in §11.3.1
* attribute for HTMLObjectElement, in §11.3.4
* codebase, in §11.2
* codetype, in §11.2
* codeType, in §11.3.4
* code unit, in §2.1.6
* code-unit length, in §2.1.6
* col
* (element), in §4.9.4
* attr-value for scope, in §4.9.10
* colgroup
* (element), in §4.9.3
* attr-value for scope, in §4.9.10
* colgroup group, in §4.9.10
* collect a sequence of characters, in §2.4.1
* colno
* dict-member for ErrorEventInit, in §7.1.3.9.2
* attribute for ErrorEvent, in §7.1.3.9.2
* Color, in §4.10.5.1.14
* color
* attr-value for input/type, in §4.10.5
* element-attr for hr, in §11.2
* attribute for HTMLFontElement, in §11.3.4
* attribute for HTMLHRElement, in §11.3.4
* cols
* element-attr for textarea, in §4.10.11
* attribute for HTMLTextAreaElement, in §4.10.11
* element-attr for frameset, in §11.3.3
* attribute for HTMLFrameSetElement, in §11.3.3
* colspan, in §4.9.11
* colSpan, in §4.9.11
* column
* state for scope, in §4.9.10
* definition of, in §4.9.12
* column group, in §4.9.12
* column group header, in §4.9.12.2
* column groups, in §4.9.12
* column header, in §4.9.12.2
* columns, in §4.9.12
* command, in §4.11.3.1
* commentary, in §4.7.13.10.1
* Comment end bang state, in §8.2.4.52
* Comment end dash state, in §8.2.4.50
* Comment end state, in §8.2.4.51
* Comment less-than sign bang dash dash state, in §8.2.4.49
* Comment less-than sign bang dash state, in §8.2.4.48
* Comment less-than sign bang state, in §8.2.4.47
* Comment less-than sign state, in §8.2.4.46
* Comments, in §8.1.6
* Comment start dash state, in §8.2.4.44
* Comment start state, in §8.2.4.43
* Comment state, in §8.2.4.45
* commit an automatic annotation, in §4.5.13
* commit an automatic base, in §4.5.10
* commit a ruby segment, in §4.5.10
* commit current annotations, in §4.5.10
* commit the base range, in §4.5.10
* compact
* element-attr for dl, in §11.2
* element-attr for menu, in §11.2
* element-attr for ol, in §11.2
* element-attr for ul, in §11.2
* attribute for HTMLDirectoryElement, in §11.3.4
* attribute for HTMLDListElement, in §11.3.4
* attribute for HTMLMenuElement, in §11.3.4
* attribute for HTMLOListElement, in §11.3.4
* attribute for HTMLUListElement, in §11.3.4
* comparing origins, in §6.4
* compatibility caseless, in §2.3
* compiled pattern regular expression, in §4.10.5.3.6
* "complete", in §3.1.1
* complete
* enum-value for DocumentReadyState, in §3.1.1
* attribute for HTMLImageElement, in §4.7.5
* Completely available, in §4.7.5
* completely available, in §4.7.5
* completely loaded, in §8.2.6
* compound microtasks, in §7.1.4.2
* compound microtask subtask, in §7.1.4.2
* computed MIME type, in §2.6.4
* computed type of a resource, in §2.6.4
* computed type of the resource, in §2.6.4
* confidence, in §8.2.2
* confirm(), in §7.6.1
* confirm(message), in §7.6.1
* conforming document, in §2.2.1
* conforming documents, in §2.2.1
* constraint validation API, in §4.10.20.3
* Constructing the form data set, in §4.10.21.4
* construct the form data set, in §4.10.21.4
* consumed, in §8.2.2.5
* container frame element, in §10.3.2
* contains(), in §2.7.3
* contains(string), in §2.7.3
* content
* element-attr for meta, in §4.2.5
* attribute for HTMLMetaElement, in §4.2.5
* attribute for HTMLTemplateElement, in §4.12.3
* Content attributes, in §3.2.3
* content categories, in §3.2.4.2
* content category, in §3.2.4.2
* content document, in §6.1.1
* contentDocument
* attribute for HTMLIFrameElement, in §4.7.6
* attribute for HTMLObjectElement, in §4.7.8
* attribute for HTMLFrameElement, in §11.3.3
* contentEditable, in §5.6.1
* contenteditable, in §5.6.1
* content-language, in §4.2.5.3
* Content model, in §3.2.3
* Content security policy state, in §4.2.5.3
* content-type
* definition of, in §2.6.4
* state for http-equiv, in §4.2.5.3
* content-type metadata, in §2.6.4
* contentWindow
* attribute for HTMLIFrameElement, in §4.7.6
* attribute for HTMLObjectElement, in §4.7.8
* attribute for HTMLFrameElement, in §11.3.3
* context, in §8.4
* context mode, in §4.12.4
* Contexts in which this element can be used, in §3.2.3
* control, in §4.10.4
* control characters, in §2.4.1
* control group, in §5.4.2
* control group owner, in §5.4.2
* control group owner object, in §5.4.2
* control group owner objects, in §5.4.2
* controls
* element-attr for mediaelements, video, audio, in §4.7.13.13
* attribute for HTMLMediaElement, in §4.7.13.13
* control’s data, in §4.10.18.7.2
* controls in the user interface that is exposed to the user, in
§4.7.13.13
* convert a list of dimensions to a list of pixel values, in §10.6
* converting a character width to pixels, in §10.5.4
* converting a string to ASCII lowercase, in §2.3
* converting a string to ASCII uppercase, in §2.3
* cookie, in §3.1.2
* cookie-averse, in §3.1.2
* cookieEnabled, in §7.7.1.4
* cookies set during the server’s opening handshake, in §2.2.2
* cookie-string, in §2.2.2
* coordinate, in §4.10.5.1.19
* coords
* element-attr for area, in §4.7.15
* attribute for HTMLAreaElement, in §4.7.15
* element-attr for a, in §11.2
* attribute for HTMLAnchorElement, in §11.3.4
* copy
* value for dropEffect, in §5.7.3
* value for effectAllowed, in §5.7.3
* value for drag, in §5.7.5
* event for global, in §Unnumbered section
* copyLink, in §5.7.3
* copyMove, in §5.7.3
* cors-same-origin, in §6.4
* CORS settings attribute, in §2.6.6
* create a classic script, in §7.1.3.3
* create a drag data store, in §5.7.2
* create a module script, in §7.1.3.3
* create an element for the token, in §8.2.5.1
* create a new browsing context, in §6.1
* create a potential-CORS request, in §2.6.1
* create a script, in §7.1.3.3
* createCaption(), in §4.9.1
* createImageBitmap(), in §7.8
* createImageBitmap(image)
* method for WindowOrWorkerGlobalScope, in §7.2
* method for ImageBitmapFactories, in §7.8
* createImageBitmap(image, sx, sy, sw, sh)
* method for WindowOrWorkerGlobalScope, in §7.2
* method for ImageBitmapFactories, in §7.8
* createTBody(), in §4.9.1
* createTFoot(), in §4.9.1
* createTHead(), in §4.9.1
* creating a classic script, in §7.1.3.3
* creating a module script, in §7.1.3.3
* creating a new browsing context, in §6.1
* creating a potential-cors request, in §2.6.1
* creating scripts, in §7.1.3.3
* creation URL, in §7.1.3.1
* creator base URL, in §6.1
* creator browsing context, in §6.1
* creator context security, in §6.1
* creator origin, in §6.1
* creator referrer policy, in §6.1
* creator URL, in §6.1
* critical subresource, in §2.1.1
* critical subresources, in §2.1.1
* crop bitmap data to the source rectangle, in §7.8
* cropped to the source rectangle, in §7.8
* crossorigin
* element-attr for link, in §4.2.4
* element-attr for img, in §4.7.5
* element-attr for media, in §4.7.13.2
* element-attr for script, in §4.12.1
* crossOrigin
* attribute for HTMLLinkElement, in §4.2.4
* attribute for HTMLImageElement, in §4.7.5
* attribute for HTMLMediaElement, in §4.7.13.2
* attribute for HTMLScriptElement, in §4.12.1
* CrossOriginFunctionWrapper, in §6.2.3.3.2
* CrossOriginGet, in §6.2.3.4
* CrossOriginGetOwnPropertyHelper, in §6.2.3.3
* CrossOriginOwnPropertyKeys, in §6.2.3.6
* CrossOriginProperties, in §6.2.3.1
* CrossOriginPropertyDescriptor, in §6.2.3.3.1
* CrossOriginPropertyDescriptorMap, in §6.2.2
* CrossOriginSet, in §6.2.3.5
* cross-origin wrapper function, in §6.2.3.3.2
* cryptographic nonce, in §7.1.3.1
* CSP list, in §3.1.1
* CSS properties, in §2.1
* CSS property, in §2.1
* cue, in §4.7.13.11.1
* cuechange, in §4.7.13.16
* cues
* definition of, in §4.7.13.11.1
* attribute for TextTrack, in §4.7.13.11.5
* Current, in §7.1.3.5
* current document readiness, in §3.1.2
* current drag operation, in §5.7.5
* current entry, in §6.6.1
* current entry of the joint session history, in §6.6.2
* current global object, in §7.1.3.5.3
* current input character, in §8.2.2.5
* currently focused area of a top-level browsing context, in §5.4.2
* currently focused area of the top-level browsing context, in §5.4.2
* currently running task, in §7.1.4.1
* current node, in §8.2.3.2
* current pixel density, in §4.7.5
* current playback position, in §4.7.13.6
* current position, in §4.7.13.6
* current request, in §4.7.5
* currentScript, in §3.1.3
* current settings object, in §7.1.3.5.3
* currentSrc
* attribute for HTMLImageElement, in §4.7.5
* attribute for HTMLMediaElement, in §4.7.13.2
* current target element, in §5.7.5
* current template insertion mode, in §8.2.3.1
* currentTime, in §4.7.13.6
* current URL, in §4.7.5
* current value, in §4.10.13
* custom data attribute, in §3.2.5.7
* customError, in §4.10.20.3
* custom validity error message, in §4.10.20.1
* cut, in §Unnumbered section
* data-, in §3.2.5.7
* data:, in §2.2.2
* data
* (element), in §4.5.15
* element-attr for object, in §4.7.8
* attribute for HTMLObjectElement, in §4.7.8
* attribute for DataCue, in §4.7.13.11.6
* data-*, in §3.2.5.7
* data block, in §4.12.1
* data blocks, in §4.12.1
* DataCue, in §4.7.13.11.6
* DataCue(startTime, endTime, data), in §4.7.13.11.6
* datafld, in §11.2
* dataformatas, in §11.2
* datalist, in §4.10.8
* datapagesize, in §11.2
* dataset, in §3.2.5.7
* datasrc, in §11.2
* Data state, in §8.2.4.1
* dataTransfer
* dict-member for DragEventInit, in §5.7.4
* attribute for DragEvent, in §5.7.4
* DataTransfer, in §5.7.3
* DataTransferItem, in §5.7.3.2
* DataTransferItemList, in §5.7.3.1
* data url, in §2.2.2
* data: url, in §2.2.2
* date
* dfn for dates, in §2.4.5.2
* attr-value for input/type, in §4.10.5
* Date, in §4.10.5.1.7
* date object, in §2.2.2
* dates, in §2.4.5.2
* datetime
* element-attr for time, in §4.5.16
* element-attr for edits, in §4.6.3
* dateTime
* attribute for HTMLTimeElement, in §4.5.16
* attribute for HTMLModElement, in §4.6.3
* datetime-local, in §4.10.5
* datetime value, in §4.5.16
* dd, in §4.4.11
* decimal, in §4.4.6
* Decimal character reference start state, in §8.2.4.75
* Decimal character reference state, in §8.2.4.77
* declare
* element-attr for object, in §11.2
* attribute for HTMLObjectElement, in §11.3.4
* dedicated media source failure steps, in §4.7.13.5
* :default, in §4.15.2
* default
* element-attr for track, in §4.7.12
* attribute for HTMLTrackElement, in §4.7.12
* attr-value for area/shape, in §4.7.15
* mode for input, in §4.10.5.4
* mode for output, in §4.10.12
* default behavior, in §5.6.5
* default button, in §4.10.21.2
* defaultChecked, in §4.10.5
* default maximum, in §4.10.5.3.7
* default minimum, in §4.10.5.3.7
* defaultMuted, in §4.7.13.13
* default object size, in §2.2.2
* default/on, in §4.10.5.4
* defaultPlaybackRate, in §4.7.13.8
* default playback start position, in §4.7.13.6
* DefaultProperties, in §6.6.4.1
* defaultSelected, in §4.10.10
* default state, in §4.7.15
* Default state, in §4.7.15
* default step, in §4.10.5.3.8
* default step base, in §4.10.5.3.8
* default-style, in §4.2.5.3
* default value
* dfn for range, in §4.10.5.1.13
* dfn for output, in §4.10.12
* defaultValue
* attribute for HTMLInputElement, in §4.10.5
* attribute for HTMLTextAreaElement, in §4.10.11
* attribute for HTMLOutputElement, in §4.10.12
* defaultView, in §6.3
* defer
* element-attr for script, in §4.12.1
* attribute for HTMLScriptElement, in §4.12.1
* defines a command, in §4.11.3.1
* defines the term, in §4.5.8
* defining term, in §4.5.8
* del, in §4.6.2
* delaying load events mode, in §6.1.1
* delaying the load event, in §8.2.6
* delaying-the-load-event flag, in §4.7.13.5
* delay the load event, in §8.2.6
* deleteCaption(), in §4.9.1
* deleteCell(index), in §4.9.8
* __deleter__(), in §3.2.5.7
* __deleter__(name), in §3.2.5.7
* deleteRow(index)
* method for HTMLTableElement, in §4.9.1
* method for HTMLTableSectionElement, in §4.9.5
* deleteTFoot(), in §4.9.1
* deleteTHead(), in §4.9.1
* delete the selection, in §5.6.4
* density-corrected intrinsic width and height, in §4.7.5
* dereferencing a javascript: url, in §6.7.1
* derived from country in some cases, in §4.10.18.7.2
* described above, in §4.7.5.1.16
* description
* definition of, in §4.2.5.1
* attribute for Plugin, in §11.3.4.1
* attribute for MimeType, in §11.3.4.1
* descriptions
* attr-value for track/kind, in §4.7.12
* attr-value for commonTrack/kind, in §4.7.13.10.1
* dfn for track, in §4.7.13.11.1
* enum-value for TextTrackKind, in §4.7.13.11.5
* "descriptions", in §4.7.13.11.5
* Descriptions, in §4.7.12
* deserialization steps, in §2.9.1
* designates, in §4.15.2
* designMode, in §5.6.2
* Detached, in §2.9.2
* detach from a media element, in §2.2.2
* details, in §4.11.1
* details notification task steps, in §4.11.1
* determining the type of the resource, in §4.2.4.2
* device-pixel-ratio, in §4.7.1
* dfn, in §4.5.8
* dialog
* attr-value for form/method, in §4.10.18.6
* dfn for state, in §4.10.18.6
* (element), in §4.11.4
* dialog focusing steps, in §4.11.4
* dialog group, in §5.4.2
* dialog group manager, in §5.4.2
* did-perform-automatic-track-selection, in §4.7.13.11.1
* Dimension attributes, in §4.7.19
* dir
* element-attr for global, in §3.2.5.5
* attribute for HTMLElement, in §3.2.5.5
* attribute for Document, in §3.2.5.5
* (element), in §11.2
* direction
* element-attr for marquee, in §11.3.2
* attribute for HTMLMarqueeElement, in §11.3.2
* directionality, in §3.2.5.5
* directionality-capable attributes, in §3.2.5.5
* directionality of an attribute, in §3.2.5.5
* directionality of the attribute, in §3.2.5.5
* direction of playback, in §4.7.13.8
* directly reachable browsing contexts, in §6.1.4
* :dir(ltr), in §4.15.2
* dirname, in §4.10.18.2
* dirName
* attribute for HTMLInputElement, in §4.10.5
* attribute for HTMLTextAreaElement, in §4.10.11
* :dir(rtl), in §4.15.2
* dirtiness, in §4.10.10
* dirty checkedness, in §4.10.5
* dirty checkedness flag, in §4.10.5
* dirty value flag
* dfn for input, in §4.10.5
* dfn for textarea, in §4.10.11
* :disabled, in §4.15.2
* disabled
* mode for track, in §4.7.13.11.1
* enum-value for TextTrackMode, in §4.7.13.11.5
* element-attr for optgroup, in §4.10.9
* attribute for HTMLOptGroupElement, in §4.10.9
* element-attr for option, in §4.10.10
* attribute for HTMLOptionElement, in §4.10.10
* element-attr for fieldset, in §4.10.15
* attribute for HTMLFieldSetElement, in §4.10.15
* element-attr for disabledformelements, input, button, select,
textarea, in §4.10.18.5
* attribute for HTMLInputElement, HTMLButtonElement,
HTMLSelectElement, HTMLTextAreaElement, in §4.10.18.5
* disabled fieldset, in §4.10.15
* Disabled State, in §4.11.3.1
* disabling, in §4.14
* discard, in §6.3.4
* discard a document, in §6.3.4
* discarded, in §6.3.4
* discard the document, in §6.3.4
* disowned its opener, in §6.1.2.1
* dispatch, in §2.1.4
* dispatched, in §2.1.4
* dispatching, in §2.1.4
* displayed, in §2.1
* display size, in §4.10.7
* display state, in §4.7.13.11.1
* display the inline content, in §6.7.8
* div, in §4.4.15
* dl, in §4.4.9
* DOCTYPE, in §8.1.1
* DOCTYPE legacy string, in §8.1.1
* DOCTYPE name state, in §8.2.4.55
* DOCTYPE public identifier (double-quoted) state, in §8.2.4.59
* DOCTYPE public identifier (single-quoted) state, in §8.2.4.60
* DOCTYPE state, in §8.2.4.53
* DOCTYPE system identifier (double-quoted) state, in §8.2.4.65
* DOCTYPE system identifier (single-quoted) state, in §8.2.4.66
* Document, in §3.1.1
* document
* definition of, in §2.1
* attribute for Window, in §6.3
* DocumentAndElementEventHandlers, in §7.1.5.2.1
* document associated with a window, in §6.1
* document base URL, in §2.5.1
* document element, in §2.2.2
* document family, in §6.1.1
* document module map, in §3.1.1
* DocumentReadyState, in §3.1.1
* document referrer policy, in §3.1.1
* documents, in §2.1
* does not apply, in §4.10.5
* doesn’t apply, in §4.10.5
* doesn’t necessarily have to affect, in §6.6.3
* domain, in §6.4.1
* DOM anchor, in §5.4.2
* DOMContentLoaded, in §Unnumbered section
* dom event dispatch logic, in §2.1.4
* DOM interface, in §3.2.3
* DOM manipulation task source, in §7.1.4.3
* DOMStringList, in §2.7.3
* DOMStringMap, in §3.2.5.7
* do not apply, in §4.10.5
* do not set, in §3.2.8.1
* do not support scripting, in §2.2.1
* don’t apply, in §4.10.5
* down
* attr-value for marquee/direction, in §10.5.11
* state for marquee, in §11.3.2
* download
* attribute for HTMLAnchorElement, in §4.5.1
* attribute for HTMLAreaElement, in §4.7.15
* element-attr for a, area, links, in §4.8.2
* definition of, in §4.8.5
* download hyperlinks, in §4.8.5
* downloads a hyperlink, in §4.8.5
* download the hyperlink, in §4.8.5
* drag, in §5.7.6
* drag-and-drop events, in §5.7.6
* drag data item kind, in §5.7.2
* drag data item type string, in §5.7.2
* drag data item type strings, in §5.7.2
* drag data store, in §5.7.2
* drag data store allowed effects state, in §5.7.2
* drag data store bitmap, in §5.7.2
* drag data store default feedback, in §5.7.2
* drag data store hot spot coordinate, in §5.7.2
* drag data store item list, in §5.7.2
* drag data store mode, in §5.7.2
* dragend, in §5.7.6
* dragenter, in §5.7.6
* DragEvent, in §5.7.4
* DragEventInit, in §5.7.4
* DragEvent(type), in §5.7.4
* DragEvent(type, eventInitDict), in §5.7.4
* dragexit, in §5.7.6
* draggable
* element-attr for global, in §5.7.7
* attribute for HTMLElement, in §5.7.7
* dragleave, in §5.7.6
* dragover, in §5.7.6
* dragstart, in §5.7.6
* drop, in §5.7.6
* dropEffect, in §5.7.3
* dt, in §4.4.10
* duration
* definition of, in §2.4.5.9
* attribute for HTMLMediaElement, in §4.7.13.6
* durationchange, in §4.7.13.16
* duration time component, in §2.4.5.9
* duration time component scale, in §2.4.5.9
* during form submission, in §4.10.21.4
* dynamic markup insertion, in §7.4
* earliest possible position, in §4.7.13.6
* earliest possible position when the script started, in §4.7.13.11.5
* editable, in §5.6.4
* editing host, in §5.6.4
* effectAllowed, in §5.7.3
* effective domain, in §6.4
* effective media volume, in §4.7.13.13
* effective playback rate, in §4.7.13.8
* ElementContentEditable, in §5.6.1
* element contents, in §3.2.4
* element has the focus, in §4.15.2
* elements
* attribute for HTMLFormElement, in §4.10.3
* attribute for HTMLFieldSetElement, in §4.10.15
* elements with default margins, in §10.3.10
* element type, in §2.1.2
* element with default margins, in §10.3.10
* em, in §4.5.2
* E-mail, in §4.10.5.1.5
* email, in §4.10.5
* embed, in §4.7.7
* embedded, in §3.2.4.2.6
* embedded content, in §3.2.4.2.6
* Embedding custom non-visible data, in §3.2.5.7
* embeds, in §3.1.3
* embed task source, in §4.7.7
* emptied, in §4.7.13.16
* empty, in §2.1.3
* empty cell, in §4.9.12.2
* :enabled, in §4.15.2
* enabled, in §4.7.13.10.1
* enabledPlugin, in §11.3.4.1
* encoding, in §4.10.18.6
* encoding declaration state, in §4.2.5.3
* encoding labels, in §2.1.6
* encoding name, in §2.1.6
* encoding sniffing algorithm, in §8.2.2.2
* enctype
* element-attr for form, in §4.10.18.6
* definition of, in §4.10.18.6
* attribute for HTMLFormElement, in §4.10.18.6
* end, in §4.10.19
* ended
* attribute for HTMLMediaElement, in §4.7.13.8
* event for media, in §4.7.13.16
* ended playback, in §4.7.13.8
* end(index), in §4.7.13.14
* End tag open state, in §8.2.4.7
* End tags, in §8.1.2.2
* endTime, in §4.7.13.11.5
* enter, in §4.7.13.16
* entrance counter, in §7.1.3.5.1
* Entry, in §7.1.3.5
* entry execution context, in §7.1.3.5.1
* entry global object, in §7.1.3.5.1
* entry Realm, in §7.1.3.5.1
* entry settings object, in §7.1.3.5.1
* entry update, in §6.7.1
* enumerated attributes, in §2.4.3
* environment settings object, in §7.1.3.1
* error
* attribute for HTMLMediaElement, in §4.7.13.1
* event for media, in §4.7.13.16
* event for source, in §4.7.13.16
* event for track, in §4.7.13.16
* dict-member for ErrorEventInit, in §7.1.3.9.2
* attribute for ErrorEvent, in §7.1.3.9.2
* event for global, in §Unnumbered section
* ERROR, in §4.7.12
* ErrorEvent, in §7.1.3.9.2
* ErrorEventInit, in §7.1.3.9.2
* ErrorEvent(type), in §7.1.3.9.2
* ErrorEvent(type, eventInitDict), in §7.1.3.9.2
* error occurs during reading of the object, in §2.2.2
* escapable raw text, in §8.1.2
* escapable raw text elements, in §8.1.2
* Escaping a string, in §8.3
* establish a WebSocket connection, in §2.2.2
* establishing the media timeline, in §4.7.13.6
* establish the media timeline, in §4.7.13.6
* EUC-KR, in §8.2.2.3
* event
* element-attr for script, in §11.2
* attribute for HTMLScriptElement, in §11.3.4
* event dispatching, in §2.1.4
* event handler, in §7.1.5.1
* EventHandler, in §7.1.5.1
* event handler content attribute, in §7.1.5.1
* event handler content attributes, in §7.1.5.1
* event handler event type, in §7.1.5.1
* event handler IDL attribute, in §7.1.5.1
* event handler IDL attributes, in §7.1.5.1
* EventHandlerNonNull, in §7.1.5.1
* event handlers, in §7.1.5.1
* event loop, in §7.1.4.1
* event loops, in §7.1.4.1
* exceptions enabled flag, in §6.7.1
* execCommand(), in §5.6.4
* execCommand(commandId), in §5.6.4
* execCommand(commandId, showUI), in §5.6.4
* execCommand(commandId, showUI, value), in §5.6.4
* execute, in §4.12.1.1
* execute a compound microtask subtask, in §7.1.4.2
* execute a script block, in §4.12.1.1
* execute the script block, in §4.12.1.1
* exit, in §4.7.13.16
* explicit content-type metadata, in §2.6.4
* explicit "EOF" character, in §8.2.2.5
* explicitly going back or forwards in the session history, in §6.6.2
* explicitly supported, in §11.3.4.1
* explicitly supported JSON type, in §6.7.1
* explicitly supported XML type, in §6.7.1
* explicitly supports, in §11.3.4.1
* expose a user interface to the user, in §4.7.13.13
* exposed, in §3.1.3
* exposes a user interface to the user, in §4.7.13.13
* exposing a user interface, in §4.7.13.13
* exposing a user interface to the user, in §4.7.13.13
* expressly inert
* definition of, in §5.4.2
* dfn for dialog, in §5.4.2
* extension, in §4.8.5
* extensions in use, in §2.2.2
* extensions to the predefined set of link type, in §4.8.6.14
* extensions to the predefined set of link types, in §4.8.6.14
* Extensions to the predefined set of pragma directives, in §4.2.5.4
* External, in §11.3.4
* external, in §11.3.4
* external resource, in §4.8.1
* external resource link, in §4.8.1
* external resources, in §4.8.1
* face, in §11.3.4
* facet command, in §4.11.3.5
* facets, in §4.11.3.1
* failed, in §4.7.13.11.1
* failed to load, in §4.7.13.11.1
* fail the WebSocket connection, in §2.2.2
* fallback base URL, in §2.5.1
* fallback content, in §3.2.4.2.6
* false-by-default, in §5.6.5
* familiar, in §6.1.3
* familiar with, in §6.1.3
* fastSeek(), in §4.7.13.9
* fastSeek(time), in §4.7.13
* feed the parser, in §9.2
* fetch a classic script, in §7.1.3.2
* fetch a classic worker script, in §7.1.3.2
* fetch a module script tree, in §7.1.3.2
* fetch a single module script, in §7.1.3.2
* fetching a classic script, in §7.1.3.2
* fetching a module script tree, in §7.1.3.2
* fetching a single module script, in §7.1.3.2
* Fetching scripts, in §7.1.3.2
* fetching the descendants of a module script, in §7.1.3.2
* fetch the descendants, in §7.1.3.2
* fetch the descendants of a module script, in §7.1.3.2
* fgColor, in §11.3.4
* fieldset, in §4.10.15
* figcaption, in §4.4.13
* figure, in §4.4.12
* file, in §4.10.5
* File, in §4.10.5.1.17
* filename
* mode for input, in §4.10.5.4
* dict-member for ErrorEventInit, in §7.1.3.9.2
* attribute for ErrorEvent, in §7.1.3.9.2
* attribute for Plugin, in §11.3.4.1
* files
* attribute for HTMLInputElement, in §4.10.5.4
* attribute for DataTransfer, in §5.7.3
* <filter-function-list>, in §2.2.2
* finish, in §11.3.2
* fire, in §2.1.4
* fire a click event, in §7.1.5.3
* fire a DND event, in §5.7.4
* fire a focus event, in §5.4.4
* fire an event, in §2.1.4
* fire a progress event, in §4.7.5
* fire a progress event or simple event, in §4.7.5
* fire a simple event, in §2.1.4
* fired, in §2.1.4
* fired unload, in §6.7.11
* fires, in §2.1.4
* fires a simple event, in §2.1.4
* firing, in §2.1.4
* firing a click event, in §7.1.5.3
* firing a simple event, in §7.1.5.3
* firing a simple event named e, in §7.1.5.3
* firing a synthetic mouse event named click, in §7.1.5.3
* Firing a synthetic mouse event named e, in §7.1.5.3
* floating date and time, in §2.4.5.5
* flow, in §3.2.4.2.2
* flow content, in §3.2.4.2.2
* focus()
* method for Window, in §5.4.6
* method for HTMLElement, in §5.4.6
* focus, in §Unnumbered section
* :focus, in §4.15.2
* focusable, in §5.4.2
* focusable area, in §5.4.2
* focus chain, in §5.4.2
* focused, in §5.4.2
* focused area, in §5.4.2
* focused area of a control group, in §5.4.2
* focused area of that focus group, in §5.4.2
* focused area of the control group, in §5.4.2
* focused dialog, in §5.4.2
* focused dialog of a dialog group, in §5.4.2
* focused dialog of its dialog group, in §5.4.2
* focused dialog of the dialog group, in §5.4.2
* Focus fixup rule one, in §5.4.4
* Focus fixup rule three, in §5.4.4
* Focus fixup rule two, in §5.4.4
* focusing steps, in §5.4.4
* focus update steps, in §5.4.4
* follow hyperlinks, in §4.8.4
* following a hyperlink, in §4.8.4
* following hyperlinks, in §4.8.4
* follows a hyperlink, in §4.8.4
* follow the hyperlink, in §4.8.4
* follow the hyperlinks, in §4.8.4
* font, in §11.2
* footer, in §4.3.8
* for
* element-attr for label, in §4.10.4
* element-attr for output, in §4.10.12
* element-attr for script, in §11.2
* forced sandboxing flag set, in §6.5
* force-quirks flag, in §8.2.4
* forces content into a unique origin, in §6.4
* forceSpellCheck(), in §5.6.5
* Foreign elements, in §8.1.2
* forget the media element’s media-resource-specific tracks, in
§4.7.13.5
* form
* (element), in §4.10.3
* element-attr for formelements, object, label, input, button,
select, textarea, output, fieldset, in §4.10.17.3
* attribute for FormIDLAttribute, HTMLObjectElement,
HTMLLabelElement, HTMLInputElement, HTMLButtonElement,
HTMLSelectElement, HTMLOptionElement, HTMLTextAreaElement,
HTMLOutputElement, HTMLFieldSetElement, HTMLLegendElement, in
§4.10.17.3
* formaction, in §4.10.18.6
* formAction, in §4.10.18.6
* form-associated, in §4.10.2
* form-associated elements, in §4.10.2
* Formatting, in §8.2.3.2
* form control maxlength attribute, in §4.10.18.3
* form control minlength attribute, in §4.10.18.4
* form element pointer, in §8.2.3.4
* formenctype, in §4.10.18.6
* formEnctype, in §4.10.18.6
* formMethod, in §4.10.18.6
* formmethod, in §4.10.18.6
* formnovalidate, in §4.10.18.6
* formNoValidate, in §4.10.18.6
* form owner, in §4.10.17.3
* Forms, in §4.10
* forms, in §3.1.3
* form submission, in §4.10.21
* form submission algorithm, in §4.10.21.3
* form submissions, in §4.10.21
* formTarget, in §4.10.18.6
* formtarget, in §4.10.18.6
* for privacy, in §1.8
* forward(), in §6.6.2
* foster parenting, in §8.2.5.1
* fragment case, in §8.4
* frame
* element-attr for table, in §11.2
* (element), in §11.3.3
* attribute for HTMLTableElement, in §11.3.4
* frameborder
* element-attr for iframe, in §11.2
* element-attr for frame, in §11.3.3
* frameBorder
* attribute for HTMLFrameElement, in §11.3.3
* attribute for HTMLIFrameElement, in §11.3.4
* frame border color, in §10.6
* frameElement, in §6.1.1.1
* FrameRequestCallback, in §6.3
* frames, in §6.3
* frameset, in §11.3.3
* frameset-ok flag, in §8.2.3.5
* framespacing, in §11.2
* from an external file, in §4.12.1.1
* frozen base URL, in §4.2.3
* fully active, in §6.1.1
* fully decodable, in §4.7.5
* FunctionStringCallback, in §5.7.3.2
* gain focus, in §5.4.2
* gb18030, in §8.2.2.3
* generate all implied end tags thoroughly, in §8.2.5.3
* generate implied end tags, in §8.2.5.3
* generator, in §4.2.5.1
* generator-unable-to-provide-required-alt, in §4.7.5.1.22
* generic raw text element parsing algorithm, in §8.2.5.2
* generic RCDATA element parsing algorithm, in §8.2.5.2
* get, in §4.10.18.6
* GET, in §4.10.18.6
* Get action URL, in §4.10.21.3
* get all-indexed, in §2.7.2.1
* get all-named, in §2.7.2.1
* get an attribute, in §8.2.2.2
* getAsFile(), in §5.7.3.2
* getAsString(callback), in §5.7.3.2
* getContext(contextId), in §4.12.4
* getContext(contextId, arguments...), in §4.12.4
* getContext(contextId, ...arguments), in §4.12.4
* getCueById(id), in §4.7.13.11.5
* getData(format), in §5.7.3
* getElementsByName(), in §3.1.3
* getElementsByName(elementName), in §3.1.3
* gets reset, in §6.7.10
* getStartDate(), in §4.7.13.6
* __getter__(), in §3.2.5.7
* __getter__(name), in §3.2.5.7
* get the current value of the event handler, in §7.1.5.1
* getting, in §2.1.4
* Getting an encoding, in §2.2.2
* getting an output encoding, in §2.2.2
* getting the current value of the event handler, in §7.1.5.1
* getTrackById()
* method for AudioTrackList, in §4.7.13.10.1
* method for VideoTrackList, in §4.7.13.10.1
* getTrackById(id)
* method for AudioTrackList, in §4.7.13.10.1
* method for VideoTrackList, in §4.7.13.10.1
* method for TextTrackList, in §4.7.13.11.5
* global aria-* attributes, in §3.2.8.3.2
* global attributes, in §3.2.5
* global date and time, in §2.4.5.7
* GlobalEventHandlers, in §7.1.5.2.1
* global object, in §7.1.3.5
* globals, in §3.2.5
* global script clean-up jobs list, in §7.1.3.4
* go(), in §6.6.2
* go(delta), in §6.6.2
* group, in §4.9.12
* Guidelines for exposing cues, in §4.7.13.11.4
* h1, in §4.3.6
* h2, in §4.3.6
* h3, in §4.3.6
* h4, in §4.3.6
* h5, in §4.3.6
* h6, in §4.3.6
* handled
* dfn for script, in §7.1.3.9
* dfn for promise, in §7.1.3.10
* handler state strings, in §7.7.1.3
* hard, in §4.10.11
* Hard, in §4.10.11
* hardware limitations, in §2.2.1
* has a border, in §10.6
* has a p element in button scope, in §8.2.3.2
* has a periodic domain, in §4.10.5.3.7
* has a reversed range, in §4.10.5.3.7
* has a style sheet that is blocking scripts, in §4.2.7
* hasFocus(), in §5.4.6
* has focus steps, in §5.4.4
* hash
* attribute for HTMLHyperlinkElementUtils, in §4.8.3
* attribute for Location, in §6.6.4
* hashchange, in §Unnumbered section
* HashChangeEvent, in §6.7.10.3
* HashChangeEventInit, in §6.7.10.3
* HashChangeEvent(type), in §6.7.10.3
* HashChangeEvent(type, eventInitDict), in §6.7.10.3
* @@hasInstance, in §2.2.2
* has no style sheet that is blocking scripts, in §4.2.7
* has range limitations, in §4.10.5.3.7
* has that element in the specific scope, in §8.2.3.2
* have an li element in list item scope, in §8.2.3.2
* have a periodic domain, in §4.10.5.3.7
* have a reversed range, in §4.10.5.3.7
* have a select element in select scope, in §8.2.3.2
* have a style sheet that is blocking scripts, in §4.2.7
* HAVE_CURRENT_DATA, in §4.7.13.7
* HAVE_ENOUGH_DATA, in §4.7.13.7
* HAVE_FUTURE_DATA, in §4.7.13.7
* HAVE_METADATA, in §4.7.13.7
* HAVE_NOTHING, in §4.7.13.7
* have range limitations, in §4.10.5.3.7
* head
* attribute for Document, in §3.1.3
* (element), in §4.2.1
* head element pointer, in §8.2.3.4
* header, in §4.3.7
* headers
* element-attr for tablecells, in §4.9.11
* attribute for HTMLTableCellElement, in §4.9.11
* headers to send appropriate cookies, in §2.2.2
* heading content, in §3.2.4.2.4
* headings, in §3.2.4.2.4
* height
* attribute for HTMLImageElement, in §4.7.5
* element-attr for media, img, iframe, embed, object, video, input,
in §4.7.19
* attribute for HTMLIFrameElement, HTMLEmbedElement,
HTMLObjectElement, HTMLVideoElement, in §4.7.19
* attribute for HTMLInputElement, in §4.10.5
* element-attr for canvas, in §4.12.4
* attribute for HTMLCanvasElement, in §4.12.4
* attribute for ImageBitmap, in §7.8
* element-attr for marquee, in §11.2
* element-attr for table, in §11.2
* element-attr for td, th, tablecells, in §11.2
* element-attr for tr, in §11.2
* attribute for HTMLAppletElement, in §11.3.1
* attribute for HTMLMarqueeElement, in §11.3.2
* attribute for HTMLTableCellElement, in §11.3.4
* help, in §4.8.6.4
* Hexadecimal character reference start state, in §8.2.4.74
* Hexadecimal character reference state, in §8.2.4.76
* hidden
* mode for track, in §4.7.13.11.1
* enum-value for TextTrackMode, in §4.7.13.11.5
* attr-value for input/type, in §4.10.5
* element-attr for global, in §5.1
* attribute for HTMLElement, in §5.1
* Hidden, in §4.10.5.1.1
* hidden plugins, in §11.3.4.1
* Hidden State, in §4.11.3.1
* high
* element-attr for meter, in §4.10.14
* attribute for HTMLMeterElement, in §4.10.14
* high boundary, in §4.10.14
* history, in §6.6.1
* History, in §6.6.2
* history traversal, in §6.7.10
* history traversal task source, in §7.1.4.3
* home control group, in §5.4.5
* home sequential focus navigation order, in §5.4.5
* honor user preferences for automatic text track selection, in
§4.7.13.11.3
* host
* attribute for HTMLHyperlinkElementUtils, in §4.8.3
* attribute for Location, in §6.6.4
* hostname
* attribute for HTMLHyperlinkElementUtils, in §4.8.3
* attribute for Location, in §6.6.4
* :hover, in §4.15.2
* hr, in §4.4.3
* href
* element-attr for base, in §4.2.3
* attribute for HTMLBaseElement, in §4.2.3
* element-attr for link, in §4.2.4
* attribute for HTMLLinkElement, in §4.2.4
* element-attr for a, area, links, in §4.8.2
* attribute for HTMLHyperlinkElementUtils, in §4.8.3
* attribute for Location, in §6.6.4
* hreflang
* element-attr for link, in §4.2.4
* attribute for HTMLLinkElement, in §4.2.4
* attribute for HTMLAnchorElement, in §4.5.1
* attribute for HTMLAreaElement, in §4.7.15
* element-attr for a, links, in §4.8.2
* element-attr for area, in §11.2
* hspace
* element-attr for embed, in §11.2
* element-attr for iframe, in §11.2
* element-attr for input, in §11.2
* element-attr for img, in §11.2
* element-attr for marquee, in §11.2
* element-attr for object, in §11.2
* attribute for HTMLAppletElement, in §11.3.1
* attribute for HTMLMarqueeElement, in §11.3.2
* attribute for HTMLImageElement, in §11.3.4
* attribute for HTMLObjectElement, in §11.3.4
* html, in §4.1.1
* HTMLAllCollection, in §2.7.2.1
* HTMLAnchorElement, in §4.5.1
* HTMLAppletElement, in §11.3.1
* HTMLAreaElement, in §4.7.15
* HTMLAudioElement, in §4.7.11
* HTMLBaseElement, in §4.2.3
* HTMLBodyElement, in §4.3.1
* HTMLBRElement, in §4.5.29
* HTMLButtonElement, in §4.10.6
* HTMLCanvasElement, in §4.12.4
* HTMLDataElement, in §4.5.15
* HTMLDataListElement, in §4.10.8
* HTMLDetailsElement, in §4.11.1
* HTMLDialogElement, in §4.11.4
* HTMLDirectoryElement, in §11.3.4
* HTMLDivElement, in §4.4.15
* HTMLDListElement, in §4.4.9
* HTMLDocument, in §6.3
* HTML document, in §2.1
* html element, in §2.1.2
* HTMLElement, in §3.2.2
* html elements, in §2.1.2
* HTMLEmbedElement, in §4.7.7
* HTMLFieldSetElement, in §4.10.15
* HTMLFontElement, in §11.3.4
* htmlFor
* attribute for HTMLLabelElement, in §4.10.4
* attribute for HTMLOutputElement, in §4.10.12
* attribute for HTMLScriptElement, in §11.3.4
* HTMLFormControlsCollection, in §2.7.2.2
* HTMLFormElement, in §4.10.3
* HTML fragment parsing algorithm, in §8.4
* HTML fragment serialization algorithm, in §8.3
* HTMLFrameElement, in §11.3.3
* HTMLFrameSetElement, in §11.3.3
* HTMLHeadElement, in §4.2.1
* HTMLHeadingElement, in §4.3.6
* HTMLHRElement, in §4.4.3
* HTMLHtmlElement, in §4.1.1
* HTMLHyperlinkElementUtils, in §4.8.3
* HTMLIFrameElement, in §4.7.6
* HTMLImageElement, in §4.7.5
* HTMLInputElement, in §4.10.5
* HTML integration point, in §8.2.5
* HTMLLabelElement, in §4.10.4
* HTMLLegendElement, in §4.10.16
* HTMLLIElement, in §4.4.8
* HTMLLinkElement, in §4.2.4
* html link types, in §4.8.6
* HTMLMapElement, in §4.7.14
* HTMLMarqueeElement, in §11.3.2
* HTMLMediaElement, in §4.7.13
* HTMLMetaElement, in §4.2.5
* HTMLMeterElement, in §4.10.14
* HTML MIME type, in §2.1.1
* HTMLModElement, in §4.6.3
* HTML namespace, in §2.8
* HTMLObjectElement, in §4.7.8
* HTMLOListElement, in §4.4.6
* HTMLOptGroupElement, in §4.10.9
* HTMLOptionElement, in §4.10.10
* HTMLOptionsCollection, in §2.7.2.3
* HTMLOrSVGScriptElement, in §3.1.1
* HTMLOutputElement, in §4.10.12
* HTMLParagraphElement, in §4.4.1
* HTMLParamElement, in §4.7.9
* HTML parser, in §8.2
* HTMLPictureElement, in §4.7.3
* HTMLPreElement, in §4.4.4
* HTMLProgressElement, in §4.10.13
* HTMLQuoteElement, in §4.4.5
* HTMLScriptElement, in §4.12.1
* HTMLSelectElement, in §4.10.7
* HTMLSourceElement, in §4.7.4
* HTMLSpanElement, in §4.5.28
* HTMLStyleElement, in §4.2.6
* HTMLTableCaptionElement, in §4.9.2
* HTMLTableCellElement, in §4.9.11
* HTMLTableColElement, in §4.9.3
* HTMLTableDataCellElement, in §4.9.9
* HTMLTableElement, in §4.9.1
* HTMLTableHeaderCellElement, in §4.9.10
* HTMLTableRowElement, in §4.9.8
* HTMLTableSectionElement, in §4.9.5
* HTMLTemplateElement, in §4.12.3
* HTMLTextAreaElement, in §4.10.11
* HTMLTimeElement, in §4.5.16
* HTMLTitleElement, in §4.2.2
* HTMLTrackElement, in §4.7.12
* HTMLUListElement, in §4.4.7
* HTMLUnknownElement, in §3.2.2
* HTMLVideoElement, in §4.7.10
* http:, in §2.2.2
* http-equiv
* element-attr for meta, in §4.2.5
* definition of, in §4.2.5.3
* httpEquiv, in §4.2.5
* HTTP GET method, in §2.6.1
* HTTP headers, in §2.6.1
* HTTP response codes, in §2.6.1
* https:, in §2.2.2
* HTTPS state
* dfn for document, in §3.1.1
* dfn for settings, in §7.1.3.1
* hyperlink, in §4.8.1
* hyperlink annotations, in §4.8.1
* hyperlinks, in §4.8.1
* i
* attr-value for ol/type, in §4.4.6
* (element), in §4.5.22
* icon, in §4.8.6.5
* id
* element-attr for global, in §3.2.5
* attribute for AudioTrack, in §4.7.13.10.1
* attribute for VideoTrack, in §4.7.13.10.1
* attribute for TextTrack, in §4.7.13.11.5
* attribute for TextTrackCue, in §4.7.13.11.5
* IDL attribute, in §2.1
* IDL attributes, in §2.1
* IDL-exposed autofill value, in §4.10.18.7.2
* if appropriate, in §5.7.4
* iframe, in §4.7.6
* iframe load event steps, in §4.7.6
* iframe load in progress, in §4.7.6
* iframe sandboxing flag set, in §6.5
* ignored, in §2.1.3
* ignore-destructive-writes counter, in §7.4.3
* ignored ruby content, in §4.5.10
* ignore higher-layer caching, in §4.7.5
* ignore-opens-during-unload counter, in §7.4.1
* Image, in §4.10.5.1.19
* image, in §4.10.5
* ImageBitmap, in §7.8
* ImageBitmapSource, in §7.8
* image candidate string, in §4.7.5
* image data, in §4.7.5
* image format-based selection, in §4.7.1
* image map, in §4.7.16.1
* image maps, in §4.7.16.1
* image request, in §4.7.5
* images
* attribute for Document, in §3.1.3
* attribute for HTMLMapElement, in §4.7.14
* image sniffing, in §2.6.4
* image sniffing rules, in §2.6.4
* image source, in §4.7.5
* Image(width, height), in §4.7.5
* img, in §4.7.5
* immediately, in §2.1
* immediate user selection, in §5.7.5
* implementation notes, in §4.10.5.2
* Implementation notes for session history, in §6.6.3
* implement the sandboxing, in §6.5
* implied, in §3.2.4.4
* implied paragraph, in §3.2.4.4
* implied paragraphs, in §3.2.4.4
* implied strong reference, in §2.7.4
* in a document, in §2.2.2
* in a formal activation state, in §4.15.2
* inappropriate for a control, in §4.10.18.7.1
* inappropriate for the control, in §4.10.18.7.1
* in-band metadata track dispatch type, in §4.7.13.11.1
* inBandMetadataTrackDispatchType, in §4.7.13.11.5
* in body, in §8.2.5.4.7
* in caption, in §8.2.5.4.11
* in cell, in §8.2.5.4.15
* inclusive ancestor, in §2.2.2
* in column group, in §8.2.5.4.12
* increment the marquee current loop index, in §11.3.2
* Incumbent, in §7.1.3.5
* incumbent global object, in §7.1.3.5.2
* incumbent Realm, in §7.1.3.5.2
* incumbent settings object, in §7.1.3.5.2
* indeterminate, in §4.10.5
* :indeterminate, in §4.15.2
* index
* dfn for option, in §4.10.10
* attribute for HTMLOptionElement, in §4.10.10
* indexed for indexed property retrieval, in §4.10.3
* indexed for named property retrieval, in §4.10.3
* indicated a coordinate, in §4.10.5.1.19
* indicated part of the document, in §6.7.9
* in error reporting mode, in §7.1.3.9
* inert, in §5.2
* inertness, in §5.2
* in foreign content, in §8.2.5.5
* in frameset, in §8.2.5.4.20
* in head, in §8.2.5.4.4
* in head noscript, in §8.2.5.4.5
* inherit-by-default, in §5.6.5
* initial, in §8.2.5.4.1
* Initializing a new Document object, in §6.7.1
* initial playback position, in §4.7.13.6
* initiated, in §5.7.5
* initiate the drag-and-drop operation, in §5.7.5
* innerText, in §3.2.6
* in parallel, in §2.1
* input
* (element), in §4.10.5
* event for input, in §4.10.5.5
* event for global, in §Unnumbered section
* input byte stream, in §8.2.2
* input stream, in §8.2.2.5
* :in-range, in §4.15.2
* in row, in §8.2.5.4.14
* ins, in §4.6.1
* in scope, in §8.2.3.2
* in select, in §8.2.5.4.16
* in select in table, in §8.2.5.4.17
* insert a character, in §8.2.5.1
* insert a comment, in §8.2.5.1
* insert a foreign element, in §8.2.5.1
* insert an HTML element, in §8.2.5.1
* insertCell(index), in §4.9.8
* inserted into, in §2.1.3
* inserted into a document, in §2.1.3
* inserted into the document, in §2.1.3
* insertion mode, in §8.2.3.1
* insertion point, in §8.2.2.5
* insertRow(index)
* method for HTMLTableElement, in §4.9.1
* method for HTMLTableSectionElement, in §4.9.5
* insert the character, in §8.2.5.1
* insert the token’s character, in §8.2.5.1
* in table, in §8.2.5.4.9
* in table body, in §8.2.5.4.13
* in table scope, in §8.2.3.2
* in table text, in §8.2.5.4.10
* in template, in §8.2.5.4.18
* interactive
* enum-value for DocumentReadyState, in §3.1.1
* definition of, in §3.2.4.2.7
* "interactive", in §3.1.1
* interactive content, in §3.2.4.2.7
* interactively validate the constraints, in §4.10.20.2
* inter-element white space, in §3.2.4
* internal algorithm for scanning and assigning header cells, in
§4.9.12.2
* internal pause steps, in §4.7.13.8
* internal raw uncompiled handler, in §7.1.5.1
* in text, in §8.2.5.4.8
* intrinsic dimensions, in §2.2.2
* intrinsic height
* dfn for css, in §2.2.2
* dfn for video, in §4.7.10
* intrinsic width
* dfn for css, in §2.2.2
* dfn for video, in §4.7.10
* invalid, in §Unnumbered section
* :invalid, in §4.15.2
* invalid value default, in §2.4.3
* invoke, in §7.1.5.1
* @@isConcatSpreadable, in §2.2.2
* isContentEditable, in §5.6.1
* isContentHandlerRegistered(), in §7.7.1.3
* isContentHandlerRegistered(mimeType, url), in §7.7.1.3
* Is environment settings object a secure context?, in §2.2.2
* isindex, in §11.2
* ismap
* element-attr for img, in §4.7.5
* element-attr for input, in §11.2
* isMap, in §4.7.5
* is not step aligned, in §4.10.5.4
* ISO-2022-JP, in §8.2.2.3
* ISO-8859-2, in §8.2.2.3
* ISO-8859-8, in §8.2.2.3
* IsPlatformObjectSameOrigin, in §6.2.3.2
* isProtocolHandlerRegistered(), in §7.7.1.3
* isProtocolHandlerRegistered(scheme, url), in §7.7.1.3
* IsSearchProviderInstalled(), in §11.3.4
* is step aligned, in §4.10.5.4
* it can also come from script, in §7.4
* item()
* method for DOMStringList, in §2.7.3
* method for PluginArray, in §11.3.4.1
* method for MimeTypeArray, in §11.3.4.1
* method for Plugin, in §11.3.4.1
* item(index)
* method for DOMStringList, in §2.7.3
* method for HTMLSelectElement, in §4.10.7
* method for PluginArray, in §11.3.4.1
* method for MimeTypeArray, in §11.3.4.1
* method for Plugin, in §11.3.4.1
* item(nameOrIndex), in §2.7.2.1
* items, in §5.7.3
* item type string, in §5.7.2
* javaEnabled(), in §11.3.4.1
* JavaScript MIME type, in §4.12.1.2
* javascript: url, in §6.7.1
* javascript: urls, in §6.7.1
* joint session history, in §6.6.2
* JSON MIME type, in §6.7.1
* kbd, in §4.5.20
* keywords, in §4.2.5.1
* kind
* element-attr for track, in §4.7.12
* attribute for HTMLTrackElement, in §4.7.12
* attribute for AudioTrack, in §4.7.13.10.1
* attribute for VideoTrack, in §4.7.13.10.1
* definition of, in §4.7.13.11.1
* attribute for TextTrack, in §4.7.13.11.5
* attribute for DataTransferItem, in §5.7.3.2
* kind of element, in §8.1.2
* kind of track, in §4.7.13.11.1
* kinds of elements, in §8.1.2
* label
* element-attr for track, in §4.7.12
* attribute for HTMLTrackElement, in §4.7.12
* attribute for AudioTrack, in §4.7.13.10.1
* attribute for VideoTrack, in §4.7.13.10.1
* attribute for TextTrack, in §4.7.13.11.5
* (element), in §4.10.4
* element-attr for optgroup, in §4.10.9
* attribute for HTMLOptGroupElement, in §4.10.9
* element-attr for option, in §4.10.10
* definition of, in §4.10.10
* attribute for HTMLOptionElement, in §4.10.10
* Label, in §4.11.3.1
* labelable, in §4.10.2
* labelable element, in §4.10.2
* labelable elements, in §4.10.2
* labeled control, in §4.10.4
* label of a track, in §4.7.13.11.1
* labels, in §4.10.4
* lack scripting support, in §2.2.1
* lang
* element-attr for global, in §3.2.5.2
* element-attr for xml, in §3.2.5.2
* attribute for HTMLElement, in §3.2.5.2
* language
* definition of, in §3.2.5.2
* attribute for AudioTrack, in §4.7.13.10.1
* attribute for VideoTrack, in §4.7.13.10.1
* attribute for TextTrack, in §4.7.13.11.5
* attribute for NavigatorLanguage, in §7.7.1.2
* element-attr for script, in §11.2
* languagechange, in §Unnumbered section
* language of a text track, in §4.7.13.11.1
* languages, in §7.7.1.2
* lastModified
* definition of, in §2.2.2
* attribute for Document, in §3.1.2
* last selected source, in §4.7.5
* latest entry, in §6.6.1
* leading and trailing white space stripped, in §2.4.1
* left
* attr-value for marquee/direction, in §10.5.11
* state for marquee, in §11.3.2
* leftmargin, in §11.2
* legacy caller operation
* dfn for embed, in §4.7.7
* dfn for object, in §4.7.8
* legend, in §4.10.16
* length
* attribute for HTMLAllCollection, in §2.7.2.1
* attribute for HTMLOptionsCollection, in §2.7.2.3
* attribute for DOMStringList, in §2.7.3
* attribute for AudioTrackList, in §4.7.13.10.1
* attribute for VideoTrackList, in §4.7.13.10.1
* attribute for TextTrackList, in §4.7.13.11.5
* attribute for TextTrackCueList, in §4.7.13.11.5
* attribute for TimeRanges, in §4.7.13.14
* attribute for HTMLFormElement, in §4.10.3
* attribute for HTMLSelectElement, in §4.10.7
* attribute for DataTransferItemList, in §5.7.3.1
* attribute for Window, in §6.3.2
* attribute for History, in §6.6.2
* attribute for PluginArray, in §11.3.4.1
* attribute for MimeTypeArray, in §11.3.4.1
* attribute for Plugin, in §11.3.4.1
* li, in §4.4.8
* license, in §4.8.6.6
* limited-quirks mode, in §2.2.2
* limited to numbers greater than zero, in §2.7.1
* limited to only known values, in §2.7.1
* limited to only non-negative numbers, in §2.7.1
* limited to only non-negative numbers greater than zero, in §2.7.1
* lineno
* dict-member for ErrorEventInit, in §7.1.3.9.2
* attribute for ErrorEvent, in §7.1.3.9.2
* :link, in §4.15.2
* link
* (element), in §4.2.4
* value for dropEffect, in §5.7.3
* value for effectAllowed, in §5.7.3
* value for drag, in §5.7.5
* element-attr for body, in §11.2
* attribute for HTMLBodyElement, in §11.3.4
* linkColor, in §11.3.4
* linkMove, in §5.7.3
* links, in §3.1.3
* links to external resources, in §4.8.1
* link type, in §4.8.6
* link types, in §4.8.6
* list
* element-attr for input, in §4.10.5.3.9
* attribute for HTMLInputElement, in §4.10.5.4
* Listed element, in §4.10.2
* Listed elements, in §4.10.2
* listing, in §11.2
* list of active formatting elements, in §8.2.3.3
* list of active timers, in §7.5
* list of animation frame callbacks, in §7.9
* list of available images, in §4.7.5
* list of cues, in §4.7.13.11.1
* list of cues of a text track, in §4.7.13.11.1
* list of dragged nodes, in §5.7.5
* list of newly introduced cues, in §4.7.13.8
* list of options, in §4.10.7
* list of pending text tracks, in §4.7.13.11.1
* list of scripts that will execute in order as soon as possible, in
§4.12.1.1
* list of scripts that will execute when the document has finished
parsing, in §4.12.1.1
* list of text tracks, in §4.7.13.11.1
* list of the descendant browsing contexts, in §6.1.1
* live, in §2.1.4
* load(), in §4.7.13.5
* load
* event for track, in §4.7.13.16
* event for global, in §Unnumbered section
* loaded, in §4.7.13.11.1
* LOADED, in §4.7.12
* loadeddata, in §4.7.13.16
* loadedmetadata, in §4.7.13.16
* loadend, in §Unnumbered section
* LOADING, in §4.7.12
* loading
* enum-value for DocumentReadyState, in §3.1.1
* state for track, in §4.7.13.11.1
* "loading", in §3.1.1
* loadstart
* event for media, in §4.7.13.16
* event for global, in §Unnumbered section
* LocalDateTime, in §4.10.5.1.11
* Location, in §6.6.4
* location
* attribute for Document, in §6.6.4
* attribute for Window, in §6.6.4
* locationbar, in §6.3.6
* location defineownproperty, in §6.6.4.1.6
* location delete, in §6.6.4.1.9
* location get, in §6.6.4.1.7
* location getownproperty, in §6.6.4.1.5
* location getprototypeof, in §6.6.4.1.1
* location isextensible, in §6.6.4.1.3
* Location-object navigate, in §6.6.4
* Location-object-setter navigate, in §6.6.4
* location ownpropertykeys, in §6.6.4.1.10
* location preventextensions, in §6.6.4.1.4
* location set, in §6.6.4.1.8
* location setprototypeof, in §6.6.4.1.2
* locked for focus, in §5.4.6
* locked for reset, in §4.10.3
* longdesc
* element-attr for iframe, in §11.2
* element-attr for img, in §11.2
* longDesc
* attribute for HTMLImageElement, in §4.7.5
* attribute for HTMLFrameElement, in §11.3.3
* attribute for HTMLIFrameElement, in §11.3.4
* loop
* element-attr for media, in §4.7.13.6
* attribute for HTMLMediaElement, in §4.7.13.6
* element-attr for marquee, in §11.3.2
* attribute for HTMLMarqueeElement, in §11.3.2
* loses focus, in §5.4.4
* low
* element-attr for meter, in §4.10.14
* attribute for HTMLMeterElement, in §4.10.14
* low boundary, in §4.10.14
* lower-alpha, in §4.4.6
* lowercase ASCII hex digits, in §2.4.1
* lowercase ASCII letters, in §2.4.1
* lower-roman, in §4.4.6
* lowsrc
* element-attr for img, in §11.2
* attribute for HTMLImageElement, in §11.3.4
* ltr
* attr-value for global/dir, in §3.2.5.5
* state for dir, in §3.2.5.5
* machine-readable equivalent of the element’s contents, in §4.5.16
* magic alignment, in §4.11.4
* magically aligned, in §4.11.4
* Mail as body, in §4.10.21.3
* mailto:, in §2.2.2
* Mail with headers, in §4.10.21.3
* main
* (element), in §4.4.14
* attr-value for commonTrack/kind, in §4.7.13.10.1
* main-desc, in §4.7.13.10.1
* manager, in §5.4.2
* manifest, in §4.1.1
* manual
* value for scrollRestorationMode, in §6.6.1
* enum-value for ScrollRestoration, in §6.6.2
* "manual", in §6.6.2
* map, in §4.7.14
* maps to the dimension properties, in §10.2
* maps to the dimension property, in §10.2
* maps to the dimension property (ignoring zero), in §10.2
* maps to the pixel length property, in §10.2
* map to the dimension property (ignoring zero), in §10.2
* marginHeight
* attribute for HTMLFrameElement, in §11.3.3
* attribute for HTMLIFrameElement, in §11.3.4
* marginheight
* element-attr for body, in §11.2
* element-attr for iframe, in §11.2
* marginwidth
* element-attr for body, in §11.2
* element-attr for iframe, in §11.2
* marginWidth
* attribute for HTMLFrameElement, in §11.3.3
* attribute for HTMLIFrameElement, in §11.3.4
* mark, in §4.5.25
* markers, in §8.2.3.3
* Markup declaration open state, in §8.2.4.42
* marquee, in §11.3.2
* marquee current loop index, in §11.3.2
* marquee loop count, in §11.3.2
* marquee scroll distance, in §11.3.2
* marquee scroll interval, in §11.3.2
* matches the environment, in §2.4.10
* match service worker registration, in §2.2.2
* match the environment, in §2.4.10
* MathML annotation-xml, in §2.2.2
* MathML math, in §2.2.2
* MathML merror, in §2.2.2
* MathML mi, in §2.2.2
* MathML mn, in §2.2.2
* MathML mo, in §2.2.2
* MathML ms, in §2.2.2
* MathML mtext, in §2.2.2
* MathML namespace, in §2.8
* MathML text integration point, in §8.2.5
* matured, in §6.7.1
* max
* attribute for HTMLInputElement, in §4.10.5
* element-attr for input, in §4.10.5.3.7
* element-attr for progress, in §4.10.13
* attribute for HTMLProgressElement, in §4.10.13
* element-attr for meter, in §4.10.14
* attribute for HTMLMeterElement, in §4.10.14
* maximum, in §4.10.5.3.7
* maximum allowed value length, in §4.10.18.3
* maximum value
* dfn for progress, in §4.10.13
* dfn for meter, in §4.10.14
* maxLength
* attribute for HTMLInputElement, in §4.10.5
* attribute for HTMLTextAreaElement, in §4.10.11
* maxlength
* element-attr for input, in §4.10.5.3.1
* element-attr for textarea, in §4.10.11
* "maybe", in §4.7.13
* maybe
* enum-value for CanPlayTypeResult, in §4.7.13
* definition of, in §4.7.13.3
* media
* element-attr for link, in §4.2.4
* attribute for HTMLLinkElement, in §4.2.4
* element-attr for style, in §4.2.6
* attribute for HTMLStyleElement, in §4.2.6
* element-attr for source, in §4.7.4
* attribute for HTMLSourceElement, in §4.7.4
* media data, in §4.7.13
* media data processing steps list, in §4.7.13.5
* media element, in §4.7.13
* media element attributes, in §4.7.13
* media element event task source, in §4.7.13
* media element load algorithm, in §4.7.13.5
* media elements, in §4.7.13
* MEDIA_ERR_ABORTED, in §4.7.13.1
* MEDIA_ERR_DECODE, in §4.7.13.1
* MEDIA_ERR_NETWORK, in §4.7.13.1
* MediaError, in §4.7.13.1
* MEDIA_ERR_SRC_NOT_SUPPORTED, in §4.7.13.1
* Media fragment syntax, in §2.2.2
* MediaProvider, in §4.7.13
* media provider object, in §4.7.13.2
* media resource, in §4.7.13
* media-resource-specific text track, in §4.7.13.11.2
* media timeline, in §4.7.13.6
* media type, in §2.1.1
* menu, in §11.2
* menubar, in §6.3.6
* menuitem, in §11.2
* message
* dict-member for ErrorEventInit, in §7.1.3.9.2
* attribute for ErrorEvent, in §7.1.3.9.2
* event for global, in §Unnumbered section
* meta, in §4.2.5
* Metadata
* state for track, in §4.7.12
* state for media, in §4.7.13.5
* "metadata", in §4.7.13.11.5
* metadata
* attr-value for track/kind, in §4.7.12
* value for HTMLMediaElement/preload, in §4.7.13.5
* dfn for track, in §4.7.13.11.1
* enum-value for TextTrackKind, in §4.7.13.11.5
* Metadata content, in §3.2.4.2.1
* metadata names, in §4.2.5.2
* meter, in §4.10.14
* method
* element-attr for form, in §4.10.18.6
* dfn for forms, in §4.10.18.6
* attribute for HTMLFormElement, in §4.10.18.6
* methods
* element-attr for a, in §11.2
* element-attr for link, in §11.2
* microtask, in §7.1.4.2
* microtask checkpoints, in §7.1.4.2
* microtask queue, in §7.1.4.2
* microtask task source, in §7.1.4.2
* mime type, in §2.1.1
* MimeType, in §11.3.4.1
* MimeTypeArray, in §11.3.4.1
* mimeTypes, in §11.3.4.1
* mime types, in §2.1.1
* min
* attribute for HTMLInputElement, in §4.10.5
* element-attr for input, in §4.10.5.3.7
* element-attr for meter, in §4.10.14
* attribute for HTMLMeterElement, in §4.10.14
* minimum, in §4.10.5.3.7
* minimum allowed value length, in §4.10.18.4
* minimum value, in §4.10.14
* minLength
* attribute for HTMLInputElement, in §4.10.5
* attribute for HTMLTextAreaElement, in §4.10.11
* minlength
* element-attr for input, in §4.10.5.3.1
* element-attr for textarea, in §4.10.11
* missing value default, in §2.4.3
* modal dialog is shown, in §4.11.4
* mode, in §4.7.13.11.5
* module map, in §7.1.3.8
* module record, in §7.1.3.1
* module script, in §7.1.3.1
* Month, in §4.10.5.1.8
* month
* definition of, in §2.4.5.1
* attr-value for input/type, in §4.10.5
* move
* value for dropEffect, in §5.7.3
* value for effectAllowed, in §5.7.3
* value for drag, in §5.7.5
* multicol, in §11.2
* multipart/form-data, in §4.10.18.6
* multipart/form-data boundary string, in §4.10.21.7
* multipart/form-data encoding algorithm, in §4.10.21.7
* multiple
* attribute for HTMLInputElement, in §4.10.5
* element-attr for input, in §4.10.5.3.5
* element-attr for select, in §4.10.7
* attribute for HTMLSelectElement, in §4.10.7
* mutable, in §4.10.17.2
* Mutate action URL, in §4.10.21.3
* mutation observers, in §2.2.2
* muted
* definition of, in §4.7.13.13
* attribute for HTMLMediaElement, in §4.7.13.13
* element-attr for media, in §4.7.13.13
* muted errors, in §7.1.3.1
* mute iframe load, in §4.7.6
* name
* event for global, in §2.2.2
* element-attr for meta, in §4.2.5
* attribute for HTMLMetaElement, in §4.2.5
* element-attr for iframe, in §4.7.6
* attribute for HTMLIFrameElement, in §4.7.6
* element-attr for object, in §4.7.8
* attribute for HTMLObjectElement, in §4.7.8
* element-attr for param, in §4.7.9
* attribute for HTMLParamElement, in §4.7.9
* element-attr for map, in §4.7.14
* attribute for HTMLMapElement, in §4.7.14
* element-attr for form, in §4.10.3
* attribute for HTMLFormElement, in §4.10.3
* element-attr for formelements, label, input, button, select,
textarea, output, fieldset, in §4.10.18.1
* attribute for HTMLInputElement, HTMLButtonElement,
HTMLSelectElement, HTMLTextAreaElement, HTMLOutputElement,
HTMLFieldSetElement, in §4.10.18.1
* attribute for Window, in §6.3.1
* element-attr for a, in §11.2
* element-attr for embed, in §11.2
* element-attr for img, in §11.2
* element-attr for option, in §11.2
* attribute for HTMLAppletElement, in §11.3.1
* element-attr for frame, in §11.3.3
* attribute for HTMLFrameElement, in §11.3.3
* attribute for HTMLAnchorElement, in §11.3.4
* attribute for HTMLEmbedElement, in §11.3.4
* attribute for HTMLImageElement, in §11.3.4
* attribute for Plugin, in §11.3.4.1
* named color, in §2.2.2
* Named elements, in §3.1.3
* named for the all collection, in §2.7.2.1
* namedItem()
* method for PluginArray, in §11.3.4.1
* method for MimeTypeArray, in §11.3.4.1
* method for Plugin, in §11.3.4.1
* namedItem(name)
* method for HTMLAllCollection, in §2.7.2.1
* method for HTMLFormControlsCollection, in §2.7.2.2
* method for HTMLSelectElement, in §4.10.7
* method for PluginArray, in §11.3.4.1
* method for MimeTypeArray, in §11.3.4.1
* method for Plugin, in §11.3.4.1
* Named objects, in §6.3.3
* naturalHeight, in §4.7.5
* naturalWidth, in §4.7.5
* nav, in §4.3.4
* navigate, in §6.7.1
* navigated, in §6.7.1
* navigate fragment, in §6.7.9
* navigating, in §6.7.1
* navigating a browsing context, in §6.7.1
* navigation, in §6.7.1
* navigation algorithm, in §6.7.1
* Navigator, in §7.7.1
* navigator, in §7.7.1
* NavigatorContentUtils, in §7.7.1.3
* NavigatorCookies, in §7.7.1.4
* NavigatorID, in §7.7.1.1
* NavigatorLanguage, in §7.7.1.2
* navigator.onLine, in §6.7.13
* NavigatorOnLine, in §6.7.13
* NavigatorPlugins, in §11.3.4.1
* nearest activatable element, in §5.3
* nearest ancestor autofocus scoping document element, in §4.10.18.6.1
* nested browsing context, in §6.1.1
* nested browsing contexts, in §6.1.1
* nested through, in §6.1.1
* NETWORK_EMPTY, in §4.7.13.4
* NETWORK_IDLE, in §4.7.13.4
* networking task source, in §7.1.4.3
* NETWORK_LOADING, in §4.7.13.4
* NETWORK_NO_SOURCE, in §4.7.13.4
* networkState, in §4.7.13.4
* newURL
* dict-member for HashChangeEventInit, in §6.7.10.3
* attribute for HashChangeEvent, in §6.7.10.3
* next, in §4.8.6.13.1
* nextid, in §11.2
* next input character, in §8.2.2.5
* next token, in §8.2.5
* nobr, in §11.2
* No CORS, in §2.6.6
* node A is removed, in §2.1.3
* noembed, in §11.2
* nofollow, in §4.8.6.7
* noframes, in §11.2
* nohref, in §11.2
* noHref, in §11.3.4
* non-blocking, in §4.12.1.1
* nonce
* element-attr for link, in §4.2.4
* attribute for HTMLLinkElement, in §4.2.4
* element-attr for style, in §4.2.6
* attribute for HTMLStyleElement, in §4.2.6
* element-attr for script, in §4.12.1
* attribute for HTMLScriptElement, in §4.12.1
* NONE, in §4.7.12
* none
* value for HTMLMediaElement/preload, in §4.7.13.5
* value for anchor-point, in §4.11.4.1
* context for canvas, in §4.12.4
* value for dropEffect, in §5.7.3
* value for effectAllowed, in §5.7.3
* value for drag, in §5.7.5
* None, in §4.7.13.5
* noopener, in §4.8.6.8
* no-quirks mode, in §2.2.2
* no-referrer, in §2.2.2
* noreferrer, in §4.8.6.9
* no-referrer-when-downgrade, in §2.2.2
* noresize, in §11.3.3
* noResize, in §11.3.3
* normal alignment, in §4.11.4
* normal elements, in §8.1.2
* normalized TimeRanges object, in §4.7.13.14
* normalize the source densities, in §4.7.5
* noscript, in §4.12.2
* noShade, in §11.3.4
* noshade, in §11.2
* not handled
* dfn for script, in §7.1.3.9
* dfn for promise, in §7.1.3.10
* nothing, in §3.2.4.1
* Nothing, in §4.12.3
* notify about rejected promises, in §7.1.3.10
* not loaded, in §4.7.13.11.1
* no-translate, in §3.2.5.3
* not yet been loaded, in §4.7.13.11.1
* novalidate, in §4.10.18.6
* noValidate, in §4.10.18.6
* no-validate state, in §4.10.18.6
* nowrap, in §11.2
* noWrap, in §11.3.4
* number, in §4.10.5
* Number, in §4.10.5.1.12
* number of bytes downloaded, in §2.6.2
* number of child browsing contexts, in §6.3.2
* number of days in month month of year year, in §2.4.5
* Numeric character reference end state, in §8.2.4.78
* Numeric character reference state, in §8.2.4.73
* object
* (element), in §4.7.8
* attribute for HTMLAppletElement, in §11.3.1
* _object, in §11.3.1
* object properties, in §2.1
* object property, in §2.1
* obtain, in §4.2.4.3
* obtain a physical form, in §10.8
* obtain the resource, in §4.2.4.3
* off
* attr-value for form/autocomplete, in §4.10.3
* state for form/autocomplete, in §4.10.3
* attr-value for forms/autocomplete, in §4.10.18.7.1
* official playback position, in §4.7.13.6
* offline, in §Unnumbered section
* ol, in §4.4.6
* oldURL
* dict-member for HashChangeEventInit, in §6.7.10.3
* attribute for HashChangeEvent, in §6.7.10.3
* omitted, in §8.1.2.4
* on
* attr-value for form/autocomplete, in §4.10.3
* state for form/autocomplete, in §4.10.3
* attr-value for forms/autocomplete, in §4.10.18.7.1
* onabort, in §7.1.5.2
* onaddtrack
* attribute for AudioTrackList, VideoTrackList, in §4.7.13.10.1
* attribute for TextTrackList, in §4.7.13.11.8
* onafterprint, in §7.1.5.2
* onauxclick, in §7.1.5.2
* onbeforeprint, in §7.1.5.2
* onbeforeunload
* attribute for OnBeforeUnloadEventHandler, in §7.1.5.2
* attribute for WindowEventHandlers, in §7.1.5.2.1
* OnBeforeUnloadEventHandler, in §7.1.5.1
* OnBeforeUnloadEventHandlerNonNull, in §7.1.5.1
* onblur, in §7.1.5.2
* onbounce, in §11.3.2
* oncancel, in §7.1.5.2
* oncanplay, in §7.1.5.2
* oncanplaythrough, in §7.1.5.2
* onchange
* attribute for AudioTrackList, VideoTrackList, in §4.7.13.10.1
* attribute for TextTrackList, in §4.7.13.11.8
* attribute for GlobalEventHandlers, in §7.1.5.2
* onclick, in §7.1.5.2
* onclose, in §7.1.5.2
* oncopy, in §7.1.5.2
* oncuechange
* attribute for TextTrack, in §4.7.13.11.8
* attribute for GlobalEventHandlers, in §7.1.5.2
* oncut, in §7.1.5.2
* ondblclick, in §7.1.5.2
* ondrag, in §7.1.5.2
* ondragend, in §7.1.5.2
* ondragenter, in §7.1.5.2
* ondragexit, in §7.1.5.2
* ondragleave, in §7.1.5.2
* ondragover, in §7.1.5.2
* ondragstart, in §7.1.5.2
* ondrop, in §7.1.5.2
* ondurationchange, in §7.1.5.2
* onemptied, in §7.1.5.2
* onended, in §7.1.5.2
* onenter, in §4.7.13.11.8
* one permitted sandboxed navigator, in §6.5
* onerror, in §7.1.5.2
* OnErrorEventHandler, in §7.1.5.1
* OnErrorEventHandlerNonNull, in §7.1.5.1
* onexit, in §4.7.13.11.8
* onfinish, in §11.3.2
* onfocus, in §7.1.5.2
* onhashchange, in §7.1.5.2
* oninput, in §7.1.5.2
* oninvalid, in §7.1.5.2
* onkeydown, in §7.1.5.2
* onkeypress, in §7.1.5.2
* onkeyup, in §7.1.5.2
* onlanguagechange, in §7.1.5.2
* online, in §Unnumbered section
* onLine, in §6.7.13
* onload, in §7.1.5.2
* onloadeddata, in §7.1.5.2
* onloadedmetadata, in §7.1.5.2
* onloadend, in §7.1.5.2
* onloadstart, in §7.1.5.2
* only if border is not equivalent to zero, in §10.3.9
* onmessage, in §7.1.5.2
* onmousedown, in §7.1.5.2
* onmouseenter, in §7.1.5.2
* onmouseleave, in §7.1.5.2
* onmousemove, in §7.1.5.2
* onmouseout, in §7.1.5.2
* onmouseover, in §7.1.5.2
* onmouseup, in §7.1.5.2
* onoffline, in §7.1.5.2
* ononline, in §7.1.5.2
* onpagehide, in §7.1.5.2
* onpageshow, in §7.1.5.2
* onpaste, in §7.1.5.2
* onpause, in §7.1.5.2
* onplay, in §7.1.5.2
* onplaying, in §7.1.5.2
* onpopstate, in §7.1.5.2
* onprogress, in §7.1.5.2
* onratechange, in §7.1.5.2
* onreadystatechange
* attribute for Document, in §3.1.1
* definition of, in §7.1.5.2
* onrejectionhandled, in §7.1.5.2
* onremovetrack
* attribute for AudioTrackList, VideoTrackList, in §4.7.13.10.1
* attribute for TextTrackList, in §4.7.13.11.8
* onreset, in §7.1.5.2
* onresize, in §7.1.5.2
* onscroll, in §7.1.5.2
* onseeked, in §7.1.5.2
* onseeking, in §7.1.5.2
* onselect, in §7.1.5.2
* onshow, in §7.1.5.2
* onstalled, in §7.1.5.2
* onstart, in §11.3.2
* onstorage, in §7.1.5.2
* onsubmit, in §7.1.5.2
* onsuspend, in §7.1.5.2
* ontimeupdate, in §7.1.5.2
* ontoggle, in §7.1.5.2
* onunhandledrejection, in §7.1.5.2
* onunload, in §7.1.5.2
* onvolumechange, in §7.1.5.2
* onwaiting, in §7.1.5.2
* onwheel, in §7.1.5.2
* opaque origin, in §6.4
* open
* element-attr for details, in §4.11.1
* attribute for HTMLDetailsElement, in §4.11.1
* element-attr for dialog, in §4.11.4
* attribute for HTMLDialogElement, in §4.11.4
* event for global, in §Unnumbered section
* open()
* method for Window, in §6.3.1
* method for Document, in §7.4.1
* opener, in §6.1.2.1
* opener browsing context, in §6.1.2
* open(type), in §7.4.1
* open(type, replace), in §7.4.1
* open(url, name, features), in §7.4.1
* open(url, name, features, replace), in §7.4.1
* optgroup, in §4.10.9
* optimum
* element-attr for meter, in §4.10.14
* attribute for HTMLMeterElement, in §4.10.14
* optimum point, in §4.10.14
* optimum value, in §4.10.14
* option, in §4.10.10
* :optional, in §4.15.2
* optionally truncate a simple dialog string, in §7.6.1
* optionally truncated, in §7.6.1
* optionally truncating, in §7.6.1
* optional start and end tags, in §8.1.2.4
* options
* attribute for HTMLSelectElement, in §4.10.7
* attribute for HTMLDataListElement, in §4.10.8
* Option(text, value, defaultSelected, selected), in §4.10.10
* ordered set of unique space-separated tokens, in §2.4.7
* ordinal value, in §4.4.8
* Ordinary, in §8.2.3.2
* or equivalent, in §2.6.1
* origin
* attribute for HTMLHyperlinkElementUtils, in §4.8.3
* dfn for concept, in §6.4
* attribute for Location, in §6.6.4
* dfn for security, in §7.1.3.1
* attribute for WindowOrWorkerGlobalScope, in §7.2
* original insertion mode, in §8.2.3.1
* origin-clean, in §4.12.4
* origin domain, in §6.4
* origin host, in §6.4
* origin port, in §6.4
* origins, in §6.4
* origin scheme, in §6.4
* Other link types, in §4.8.6.14
* otherwise steps for iframe or frame elements, in §4.7.6
* outline, in §4.3.9.1
* outline depth, in §4.3.9.1
* :out-of-range, in §4.15.2
* output, in §4.10.12
* outstanding rejected promises weak set, in §7.1.3.1
* overridden reload, in §3.1
* override URL, in §6.7.1
* owner, in §5.4.2
* p, in §4.4.1
* pagehide, in §Unnumbered section
* pageshow, in §Unnumbered section
* page showing, in §6.7.11
* PageTransitionEvent, in §6.7.10.4
* PageTransitionEventInit, in §6.7.10.4
* PageTransitionEvent(type), in §6.7.10.4
* PageTransitionEvent(type, eventInitDict), in §6.7.10.4
* paint source, in §2.2.2
* palpable content, in §3.2.4.2.8
* paragraph, in §3.2.4.4
* paragraphing, in §3.2.4.4
* paragraphs, in §3.2.4.4
* param, in §4.7.9
* parameter, in §4.7.9
* parent, in §6.1.1.1
* parent browsing context, in §6.1.1
* parse, in §2.5.2
* parse a date component, in §2.4.5.2
* parse a date or time string, in §2.4.5.10
* parse a date string, in §2.4.5.2
* parse a duration string, in §2.4.5.9
* parse a floating date and time string, in §2.4.5.5
* parse a global date and time string, in §2.4.5.7
* parse a month component, in §2.4.5.1
* parse a month string, in §2.4.5.1
* parse a referrer policy from a Referrer-Policy header, in §2.2.2
* parse a sandboxing directive, in §6.5
* parse a sizes attribute, in §4.7.5
* parse a srcset attribute, in §4.7.5
* parse a time component, in §2.4.5.4
* parse a time string, in §2.4.5.4
* parse a time-zone offset component, in §2.4.5.6
* parse a time-zone offset string, in §2.4.5.6
* parse a URL, in §2.5.2
* parse a week string, in §2.4.5.8
* parse a yearless date component, in §2.4.5.3
* parse a yearless date string, in §2.4.5.3
* parse child’s sizes attribute, in §4.7.5
* parse child’s srcset attribute, in §4.7.5
* parsed as a CSS <color> value, in §2.2.2
* parse errors, in §8.2
* parse it as an integer, in §2.4.4.1
* parser-inserted, in §4.12.1.1
* parser pause flag, in §8.2.1
* parser state, in §7.1.3.1
* parse that attribute’s value, in §2.4.4.2
* parse the sandboxing directive, in §6.5
* parse token as an integer, in §2.4.4.1
* parsing, in §2.5.2
* parsing a date, in §2.4.5.2
* parsing a date and time, in §2.4.5.7
* parsing a date string, in §2.4.5.2
* parsing a duration string, in §2.4.5.9
* parsing a floating date and time, in §2.4.5.5
* parsing a floating date and time string, in §2.4.5.5
* parsing a month, in §2.4.5.1
* parsing a month string, in §2.4.5.1
* parsing a time, in §2.4.5.4
* parsing a time string, in §2.4.5.4
* parsing a time-zone offset string, in §2.4.5.6
* parsing a week, in §2.4.5.8
* parsing a week string, in §2.4.5.8
* parsing a yearless date string, in §2.4.5.3
* parsing of relative urls, in §2.5.2
* parsing relative urls, in §2.5.2
* partially available, in §4.7.5
* Partially available, in §4.7.5
* passing its URL or data to an external software package, in §6.7.1
* Password, in §4.10.5.1.6
* password
* attribute for HTMLHyperlinkElementUtils, in §4.8.3
* attr-value for input/type, in §4.10.5
* paste, in §Unnumbered section
* past names map, in §4.10.3
* Path components, in §4.10.5.1.17
* pathname
* attribute for HTMLHyperlinkElementUtils, in §4.8.3
* attribute for Location, in §6.6.4
* pattern
* attribute for HTMLInputElement, in §4.10.5
* element-attr for input, in §4.10.5.3.6
* patternMismatch, in §4.10.20.3
* pause(), in §4.7.13.8
* Pause, in §7.1.4.2
* pause
* event for media, in §4.7.13.16
* state for useragent, in §7.1.4.2
* paused, in §4.7.13.8
* paused for in-band content, in §4.7.13.8
* paused for user interaction, in §4.7.13.8
* pause-on-exit, in §4.7.13.11.1
* pauseOnExit, in §4.7.13.11.5
* pause-on-exit flag, in §4.7.13.11.1
* pending dialog stack, in §4.11.4
* pending parsing-blocking script, in §4.12.1.1
* pending request, in §4.7.5
* pending table character tokens, in §8.2.5.4.9
* pending text track change notification flag, in §4.7.13.11.1
* perform a microtask checkpoint, in §7.1.4.2
* perform automatic text track selection, in §4.7.13.11.3
* performing a microtask checkpoint flag, in §7.1.4.1
* performs a microtask checkpoint, in §7.1.4.2
* persisted
* dict-member for PageTransitionEventInit, in §6.7.10.4
* attribute for PageTransitionEvent, in §6.7.10.4
* personalbar, in §6.3.6
* phrasing, in §3.2.4.2.5
* phrasing content, in §3.2.4.2.5
* pick an encoding for a form, in §4.10.21.5
* picked, in §4.10.7
* picking an encoding for the form, in §4.10.21.5
* picture, in §4.7.3
* placeholder
* attribute for HTMLInputElement, in §4.10.5
* element-attr for input, in §4.10.5.3.10
* element-attr for textarea, in §4.10.11
* attribute for HTMLTextAreaElement, in §4.10.11
* placeholder label option, in §4.10.7
* plaintext, in §11.2
* plain text file, in §6.7.4
* PLAINTEXT state, in §8.2.4.5
* planned navigation, in §4.10.21.3
* plan to navigate, in §4.10.21.3
* platform, in §7.7.1.1
* plausible languages, in §7.7.1.2
* play, in §4.7.13.16
* play(), in §4.7.13.8
* playback ended, in §4.7.13.8
* playback has ended, in §4.7.13.8
* playbackRate, in §4.7.13.8
* playback volume, in §4.7.13.13
* played, in §4.7.13.8
* playing, in §4.7.13.16
* Plugin, in §11.3.4.1
* plugin, in §2.1.5
* PluginArray, in §11.3.4.1
* plugin document, in §6.7.7
* plugins
* attribute for Document, in §3.1.3
* attribute for NavigatorPlugins, in §11.3.4.1
* poly, in §4.7.15
* polygon, in §4.7.15
* Polygon state, in §4.7.15
* polygon state, in §4.7.15
* popstate, in §Unnumbered section
* PopStateEvent, in §6.7.10.2
* PopStateEventInit, in §6.7.10.2
* PopStateEvent(type), in §6.7.10.2
* PopStateEvent(type, eventInitDict), in §6.7.10.2
* populate the list of pending text tracks, in §4.7.13.11.1
* popup sandboxing flag set, in §6.5
* port
* attribute for HTMLHyperlinkElementUtils, in §4.8.3
* attribute for Location, in §6.6.4
* <position>, in §4.11.4.1
* position, in §4.10.13
* possibly appropriate alternatives, in §5.7.4
* post, in §4.10.18.6
* POST, in §4.10.18.6
* poster
* element-attr for video, in §4.7.10
* attribute for HTMLVideoElement, in §4.7.10
* poster frame, in §4.7.10
* Post to data:, in §4.10.21.3
* potentially active, in §4.7.7
* potentially playing, in §4.7.13.8
* practical concerns, in §2.2.1
* pragma-set default language, in §4.2.5.3
* pre, in §4.4.4
* pre-click activation steps, in §5.3
* prefix match, in §2.3
* preload
* element-attr for media, in §4.7.13.5
* attribute for HTMLMediaElement, in §4.7.13.5
* prepare an event, in §4.7.13.8
* prepare a script, in §4.12.1.1
* prepared, in §4.12.1.1
* prepare to run script, in §7.1.3.4
* preparing, in §4.12.1.1
* prescan a byte stream to determine its encoding, in §8.2.2.2
* presentational hints, in §10.2
* preserve, in §4.10.19
* prev, in §4.8.6.13.2
* prevents content from creating new auxiliary browsing contexts, in
§6.1.5
* previous target element, in §5.7.5
* primary control group, in §5.4.5
* print(), in §7.6.2
* printing steps, in §7.6.2
* print when loaded, in §7.6.2
* probably
* enum-value for CanPlayTypeResult, in §4.7.13
* definition of, in §4.7.13.3
* "probably", in §4.7.13
* probablySupportsContext(contextId), in §4.12.4
* probablySupportsContext(contextId, arguments...), in §4.12.4
* probablySupportsContext(contextId, ...arguments), in §4.12.4
* proceed with that mechanism instead, in §6.7.1
* process an rtc element, in §4.5.13
* processing model for navigating across documents, in §6.7.1
* processing the iframe attributes, in §4.7.6
* process the frame attributes, in §11.3.3
* process the iframe attributes, in §4.7.6
* process the resource appropriately, in §6.7.1
* Process the response, in §7.1.3.2
* product, in §7.7.1.1
* profile
* element-attr for head, in §11.2
* attribute for HTMLHeadElement, in §11.3.4
* progress
* event for media, in §4.7.13.16
* (element), in §4.10.13
* event for global, in §Unnumbered section
* proleptic Gregorian calendar, in §2.4.5
* proleptic-Gregorian date, in §2.4.5
* promise
* dict-member for PromiseRejectionEventInit, in §7.1.3.10.2
* attribute for PromiseRejectionEvent, in §7.1.3.10.2
* PromiseRejectionEvent, in §7.1.3.10.2
* PromiseRejectionEventInit, in §7.1.3.10.2
* PromiseRejectionEvent(type, eventInitDict), in §7.1.3.10.2
* prompt(), in §7.6.1
* prompt(message), in §7.6.1
* prompt(message, default), in §7.6.1
* prompt to unload, in §6.7.11
* prompt to unload a document, in §6.7.11
* Protected mode, in §5.7.2
* protocol
* attribute for HTMLHyperlinkElementUtils, in §4.8.3
* attribute for Location, in §6.6.4
* proto-URL, in §7.7.1.3
* provides a stable state, in §7.1.4.2
* provide such information, in §4.9.1.1
* push onto the list of active formatting elements, in §8.2.3.3
* pushState(), in §6.6.2
* pushState(data, title), in §6.6.2
* pushState(data, title, url), in §6.6.2
* q, in §4.5.7
* queryCommandEnabled(), in §5.6.4
* queryCommandEnabled(commandId), in §5.6.4
* queryCommandIndeterm(), in §5.6.4
* queryCommandIndeterm(commandId), in §5.6.4
* queryCommandState(), in §5.6.4
* queryCommandState(commandId), in §5.6.4
* queryCommandSupported(), in §5.6.4
* queryCommandSupported(commandId), in §5.6.4
* queryCommandValue(), in §5.6.4
* queryCommandValue(commandId), in §5.6.4
* queue a microtask, in §7.1.4.2
* queue a task, in §7.1.4.1
* queued, in §7.1.4.2
* queues a task, in §7.1.4.1
* queuing, in §7.1.4.1
* quirks mode, in §2.2.2
* radio, in §4.10.5
* Radio, in §4.10.5.1.16
* radio button group, in §4.10.5.1.16
* RadioNodeList, in §2.7.2.2
* range, in §4.10.5
* Range, in §4.10.5.1.13
* rangeOverflow, in §4.10.20.3
* rangeUnderflow, in §4.10.20.3
* rank, in §4.3.6
* ratechange, in §4.7.13.16
* raw text, in §8.1.2
* raw text elements, in §8.1.2
* RAWTEXT end tag name state, in §8.2.4.14
* RAWTEXT end tag open state, in §8.2.4.13
* RAWTEXT less-than sign state, in §8.2.4.12
* RAWTEXT state, in §8.2.4.3
* raw value, in §4.10.11
* rb, in §4.5.11
* RCDATA end tag name state, in §8.2.4.11
* RCDATA end tag open state, in §8.2.4.10
* RCDATA less-than sign state, in §8.2.4.9
* RCDATA state, in §8.2.4.2
* read errors, in §2.2.2
* readiness state, in §4.7.13.11.1
* readonly
* element-attr for input, in §4.10.5.3.3
* element-attr for textarea, in §4.10.11
* :read-only, in §4.15.2
* readOnly
* attribute for HTMLInputElement, in §4.10.5
* attribute for HTMLTextAreaElement, in §4.10.11
* Read-only mode, in §5.7.2
* :read-write, in §4.15.2
* Read/write mode, in §5.7.2
* ready, in §4.7.13.11.1
* ready for post-load tasks, in §8.2.6
* readyState
* attribute for Document, in §3.1.2
* attribute for HTMLTrackElement, in §4.7.12
* attribute for HTMLMediaElement, in §4.7.13.7
* readystatechange, in §Unnumbered section
* ready to be parser-executed, in §4.12.1.1
* realm execution context, in §7.1.3.1
* reason
* dict-member for PromiseRejectionEventInit, in §7.1.3.10.2
* attribute for PromiseRejectionEvent, in §7.1.3.10.2
* reassociateable, in §4.10.2
* Reassociateable element, in §4.10.2
* Reassociateable elements, in §4.10.2
* reconstruct the active formatting elements, in §8.2.3.3
* reconsume, in §8.2.4
* rect, in §4.7.15
* rectangle, in §4.7.15
* rectangle state, in §4.7.15
* Rectangle state, in §4.7.15
* rect state, in §4.7.15
* Rect state, in §4.7.15
* reentrant, in §8.2.1
* referrer
* attribute for Document, in §3.1.2
* definition of, in §4.2.5.1
* referrerPolicy
* attribute for HTMLLinkElement, in §4.2.4
* attribute for HTMLAnchorElement, in §4.5.1
* definition of, in §4.5.1
* attribute for HTMLImageElement, in §4.7.5
* attribute for HTMLIFrameElement, in §4.7.6
* attribute for HTMLAreaElement, in §4.7.15
* referrerpolicy
* element-attr for link, in §4.2.4
* element-attr for img, in §4.7.5
* element-attr for iframe, in §4.7.6
* Referrer-Policy, in §2.2.2
* referrer policy, in §3.1.1
* referrer policy attribute, in §2.6.7
* referrer source, in §2.6.1
* reflect, in §2.7.1
* reflection, in §2.7.1
* refresh(), in §11.3.4.1
* refresh, in §4.2.5.3
* refresh(reload), in §11.3.4.1
* refused to allow the document to be unloaded, in §6.7.11
* refused to allow this document to be unloaded, in §6.7.11
* registerContentHandler(), in §7.7.1.3
* registerContentHandler(mimeType, url, title), in §7.7.1.3
* registerProtocolHandler(), in §7.7.1.3
* registerProtocolHandler(scheme, url, title), in §7.7.1.3
* register the name, in §4.2.5.2
* register the names, in §4.2.5.2
* reinitialise url, in §4.8.3
* rel
* element-attr for link, in §4.2.4
* attribute for HTMLLinkElement, in §4.2.4
* attribute for HTMLAnchorElement, in §4.5.1
* attribute for HTMLAreaElement, in §4.7.15
* element-attr for a, area, links, in §4.8.2
* releaseEvents()
* method for Document, in §11.3.4
* method for Window, in §11.3.4
* Relevant, in §7.1.3.5
* relevant child nodes, in §9.3
* relevant Document, in §6.6.4
* relevant global object, in §7.1.3.5.4
* relevant mutations, in §4.7.5
* relevant Realm, in §7.1.3.5.4
* relevant settings object, in §7.1.3.5.4
* relList
* attribute for HTMLLinkElement, in §4.2.4
* attribute for HTMLAnchorElement, in §4.5.1
* attribute for HTMLAreaElement, in §4.7.15
* reload(), in §6.6.4
* reload override buffer, in §3.1
* reload override flag, in §3.1
* reload-triggered navigation, in §6.7.1
* remove()
* method for HTMLSelectElement, in §4.10.7
* method for DataTransferItemList, in §5.7.3.1
* remove an element from a document, in §2.1.3
* removeCue(cue), in §4.7.13.11.5
* removed from, in §2.1.3
* removed from a document, in §2.1.3
* removed from the document, in §2.1.3
* remove(index)
* method for HTMLOptionsCollection, in §2.7.2.3
* method for HTMLSelectElement, in §4.10.7
* method for DataTransferItemList, in §5.7.3.1
* removetrack, in §4.7.13.16
* rendered legend, in §10.3.13
* RenderingContext, in §4.12.4
* reparsed, in §2.5.2
* replace(), in §6.6.4
* replaced element, in §2.2.2
* replacement enabled, in §6.7.10
* replacement must be enabled, in §6.7.10
* replaceState(), in §6.6.2
* replaceState(data, title), in §6.6.2
* replaceState(data, title, url), in §6.6.2
* replace(url), in §6.6.4
* report an error, in §7.1.3.9
* report an exception, in §7.1.3.9.1
* reported MIME types, in §11.3.4.1
* report the error, in §7.1.3.9
* report the exception, in §7.1.3.9.1
* reportValidity()
* method for HTMLObjectElement, in §4.7.8
* method for HTMLFormElement, in §4.10.3
* method for HTMLInputElement, HTMLButtonElement,
HTMLSelectElement, HTMLTextAreaElement, HTMLOutputElement,
HTMLFieldSetElement, in §4.10.20.3
* represent, in §3.2.2
* reprocess the iframe attributes, in §4.7.6
* requestAnimationFrame(), in §7.9
* requestAnimationFrame(callback), in §7.9
* request client, in §7.1.3.1
* request url, in §4.8.4
* _required
* attribute for HTMLInputElement, in §4.10.5
* attribute for HTMLSelectElement, in §4.10.7
* attribute for HTMLTextAreaElement, in §4.10.11
* :required, in §4.15.2
* required
* attribute for HTMLInputElement, in §4.10.5
* element-attr for input, in §4.10.5.3.4
* definition of, in §4.10.5.3.4
* element-attr for select, in §4.10.7
* attribute for HTMLSelectElement, in §4.10.7
* element-attr for textarea, in §4.10.11
* attribute for HTMLTextAreaElement, in §4.10.11
* Reset, in §4.10.5.1.20
* reset
* attr-value for input/type, in §4.10.5
* attr-value for button/type, in §4.10.6
* definition of, in §4.10.22
* event for global, in §Unnumbered section
* reset(), in §4.10.3
* reset algorithm, in §4.10.22
* reset button, in §4.10.6
* resettable, in §4.10.2
* Resettable element, in §4.10.2
* Resettable elements, in §4.10.2
* reset the form owner, in §4.10.17.3
* reset the insertion mode appropriately, in §8.2.3.1
* resolve a module specifier, in §7.1.3.8
* resolving a module specifier, in §7.1.3.8
* resource
* dfn for http, in §2.1.1
* definition of, in §4.7.13
* resource fetch algorithm, in §4.7.13.5
* resource selection algorithm, in §4.7.13.5
* responsible browsing context, in §7.1.3.1
* responsible document, in §7.1.3.1
* responsible event loop, in §7.1.3.1
* restart the animation, in §10.4.2
* restore persisted user state, in §6.7.10.1
* resulting URL record, in §2.5.2
* resulting URL records, in §2.5.2
* resulting URL string, in §2.5.2
* return state, in §8.2.4
* returnValue
* attribute for HTMLDialogElement, in §4.11.4
* attribute for BeforeUnloadEvent, in §6.7.11.1
* rev
* attribute for HTMLLinkElement, in §4.2.4
* attribute for HTMLAnchorElement, in §4.5.1
* element-attr for a, link, links, in §4.8.2
* reversed
* element-attr for ol, in §4.4.6
* attribute for HTMLOListElement, in §4.4.6
* reverse link, in §4.8.2
* Reverse links, in §4.8.2
* right
* attr-value for marquee/direction, in §10.5.11
* state for marquee, in §11.3.2
* rightmargin, in §11.2
* role, in §2.2.2
* root, in §2.2.2
* row
* attr-value for scope, in §4.9.10
* state for scope, in §4.9.10
* definition of, in §4.9.12
* rowgroup, in §4.9.10
* row group
* state for scope, in §4.9.10
* definition of, in §4.9.12
* row group header, in §4.9.12.2
* row groups, in §4.9.12
* row header, in §4.9.12.2
* rowIndex, in §4.9.8
* rows
* attribute for HTMLTableElement, in §4.9.1
* attribute for HTMLTableSectionElement, in §4.9.5
* definition of, in §4.9.12
* element-attr for textarea, in §4.10.11
* attribute for HTMLTextAreaElement, in §4.10.11
* element-attr for frameset, in §11.3.3
* attribute for HTMLFrameSetElement, in §11.3.3
* rowSpan, in §4.9.11
* rowspan, in §4.9.11
* rp, in §4.5.14
* rt, in §4.5.12
* rtc, in §4.5.13
* rtl
* attr-value for global/dir, in §3.2.5.5
* state for dir, in §3.2.5.5
* ruby, in §4.5.10
* ruby annotation container, in §4.5.10
* ruby base container, in §4.5.10
* ruby bases, in §4.5.10
* ruby segment, in §4.5.10
* ruby text annotations, in §4.5.10
* ruby text container, in §4.5.10
* rules
* element-attr for table, in §11.2
* attribute for HTMLTableElement, in §11.3.4
* rules for constructing the chapter tree from a text track, in
§4.7.13.11.7
* rules for distinguishing if a resource is text or binary, in §2.6.4
* rules for extracting the chapter title, in §4.7.13.11.1
* rules for interpreting WebVTT cue text, in §2.2.2
* rules for parsing a hash-name reference, in §2.4.9
* rules for parsing a legacy color value, in §2.4.6
* rules for parsing a legacy font size, in §10.3.4
* rules for parsing a list of dimensions, in §2.4.4.7
* rules for parsing a list of floating-point numbers, in §2.4.4.6
* rules for parsing dimension values, in §2.4.4.4
* rules for parsing floating-point number values, in §2.4.4.3
* rules for parsing integer, in §2.4.4.1
* rules for parsing integers, in §2.4.4.1
* rules for parsing non-negative integers, in §2.4.4.2
* rules for parsing non-zero dimension values, in §2.4.4.5
* rules for parsing signed integers, in §2.4.4.1
* rules for parsing simple color values, in §2.4.6
* rules for serializing simple color values, in §2.4.6
* rules for sniffing images specifically, in §2.6.4
* rules for updating the display of WebVTT text tracks, in §2.2.2
* rules for updating the text track rendering, in §4.7.13.11.1
* run a classic script, in §7.1.3.4
* run a module script, in §7.1.3.4
* run authentic click activation steps, in §5.3
* run canceled activation steps, in §5.3
* run CSS animations and send events, in §7.1.4.2
* running script, in §7.1.3.4
* running synthetic click activation steps, in §5.3
* running the classic script, in §7.1.3.4
* run post-click activation steps, in §5.3
* run pre-click activation steps, in §5.3
* runs, in §4.7.13.5
* run synthetic click activation steps, in §5.3
* run the animation frame callbacks, in §7.9
* run the classic script, in §7.1.3.4
* run the fullscreen rendering steps, in §7.1.4.2
* run the global script clean-up jobs, in §7.1.3.4
* run the module script, in §7.1.3.4
* Runtime script errors, in §7.1.3.9
* s, in §4.5.5
* safelisted schemes, in §7.7.1.3
* salvageable, in §6.7.11
* same origin, in §6.4
* same origin-domain, in §6.4
* samp, in §4.5.19
* sandbox
* element-attr for iframe, in §4.7.6
* attribute for HTMLIFrameElement, in §4.7.6
* sandbox cookies, in §3.1.2
* sandboxed automatic features browsing context flag, in §6.5
* sandboxed auxiliary navigation browsing context flag, in §6.5
* sandboxed document.domain browsing context flag, in §6.5
* sandboxed forms browsing context flag, in §6.5
* sandboxed fullscreen browsing context flag, in §6.5
* sandboxed into a unique origin, in §6.5
* sandboxed modals flag, in §6.5
* sandboxed navigation browsing context flag, in §6.5
* sandboxed origin browsing context flag, in §6.5
* sandboxed plugins browsing context flag, in §6.5
* sandboxed pointer lock browsing context flag, in §6.5
* sandboxed presentation browsing context flag, in §6.5
* sandboxed scripts browsing context flag, in §6.5
* sandboxed storage area URLs flag, in §6.5
* sandboxed top-level navigation browsing context flag, in §6.5
* sandboxing flag set, in §6.5
* sandbox propagates to auxiliary browsing contexts flag, in §6.5
* satisfies its constraints, in §4.10.20.1
* satisfy its constraints, in §4.10.20.1
* satisfy their constraints, in §4.10.20.1
* scheme
* element-attr for meta, in §11.2
* attribute for HTMLMetaElement, in §11.3.4
* scope
* element-attr for th, in §4.9.10
* attribute for HTMLTableHeaderCellElement, in §4.9.10
* element-attr for td, in §11.2
* script
* (element), in §4.12.1
* dfn for concept, in §7.1.3.1
* script-closable, in §6.3.1
* script content restrictions, in §4.12.1.3
* script-created parser, in §7.4.1
* Script data double escaped dash dash state, in §8.2.4.29
* Script data double escaped dash state, in §8.2.4.28
* Script data double escaped less-than sign state, in §8.2.4.30
* Script data double escaped state, in §8.2.4.27
* Script data double escape end state, in §8.2.4.31
* Script data double escape start state, in §8.2.4.26
* Script data end tag name state, in §8.2.4.17
* Script data end tag open state, in §8.2.4.16
* Script data escaped dash dash state, in §8.2.4.22
* Script data escaped dash state, in §8.2.4.21
* Script data escaped end tag name state, in §8.2.4.25
* Script data escaped end tag open state, in §8.2.4.24
* Script data escaped less-than sign state, in §8.2.4.23
* Script data escaped state, in §8.2.4.20
* Script data escape start dash state, in §8.2.4.19
* Script data escape start state, in §8.2.4.18
* Script data less-than sign state, in §8.2.4.15
* Script data state, in §8.2.4.4
* script documentation, in §4.12.1.4
* scripting, in §7.1.3.1
* scripting flag, in §8.2.3.5
* Scripting is disabled, in §7.1.2
* Scripting is disabled for a node, in §7.1.2
* scripting is enabled, in §7.1.2
* Scripting is enabled for a node, in §7.1.2
* scripting was enabled, in §7.1.2
* script nesting level, in §8.2.1
* scripts
* attribute for Document, in §3.1.3
* dfn for concept, in §7.1.3.1
* Script-supporting elements, in §3.2.4.2.9
* scroll
* attr-value for marquee/behavior, in §11.3.2
* state for marquee/behavior, in §11.3.2
* scrollamount, in §11.3.2
* scrollAmount, in §11.3.2
* scrollbars, in §6.3.6
* scrolldelay, in §11.3.2
* scrollDelay, in §11.3.2
* scrolling
* element-attr for iframe, in §11.2
* attribute for HTMLFrameElement, in §11.3.3
* attribute for HTMLIFrameElement, in §11.3.4
* scrollRestoration, in §6.6.2
* ScrollRestoration, in §6.6.2
* scroll restoration mode, in §6.6.1
* scroll to the fragment, in §6.7.9
* Search, in §4.10.5.1.2
* search
* attribute for HTMLHyperlinkElementUtils, in §4.8.3
* element-state for link, in §4.8.6.10
* attr-value for input/type, in §4.10.5
* attribute for Location, in §6.6.4
* second administrative level, in §4.10.18.7.1
* section
* (element), in §4.3.3
* definition of, in §4.3.9.1
* sectioning, in §3.2.4.2.3
* sectioning content, in §3.2.4.2.3
* sectioning roots, in §4.3.9
* sectionRowIndex, in §4.9.8
* secured, in §2.1.5
* Sec-WebSocket-Protocol, in §2.2.2
* seek, in §4.7.13.9
* seekable, in §4.7.13.9
* seeked, in §4.7.13.16
* seeking
* attribute for HTMLMediaElement, in §4.7.13.9
* event for media, in §4.7.13.16
* segmentation and categorization of content of a ruby, in §4.5.10
* select
* (element), in §4.10.7
* enum-value for SelectionMode, in §4.10.19
* event for global, in §Unnumbered section
* select(), in §4.10.19
* select an image source, in §4.7.5
* selected
* attribute for VideoTrack, in §4.7.13.10.1
* element-attr for option, in §4.10.10
* attribute for HTMLOptionElement, in §4.10.10
* selected coordinate, in §4.10.5.1.19
* selected files, in §4.10.5.1.17
* selectedIndex
* attribute for HTMLOptionsCollection, in §2.7.2.3
* attribute for VideoTrackList, in §4.7.13.10.1
* attribute for HTMLSelectElement, in §4.10.7
* selectedness, in §4.10.10
* selectedOptions, in §4.10.7
* selecting an image source, in §4.7.5
* selectionDirection, in §4.10.19
* selectionEnd, in §4.10.19
* SelectionMode, in §4.10.19
* selectionStart, in §4.10.19
* self, in §6.3
* self-closing flag, in §8.2.4
* Self-closing start tag state, in §8.2.4.40
* send a WebSocket Message, in §2.2.2
* send select update notifications, in §4.10.7
* sequential focus navigation, in §5.4.5
* sequential focus navigation order, in §5.4.5
* sequential focus navigation starting point, in §5.4.5
* sequential navigation search algorithm, in §5.4.5
* Serializable, in §2.9.1
* Serializable objects, in §2.9.1
* serialization steps, in §2.9.1
* Serialized state, in §6.6.1
* ServiceWorkerContainer, in §2.2.2
* session history, in §6.6.1
* session history document visibility change steps, in §6.7.10
* session history entry, in §6.6.1
* session history event loop, in §6.6.2
* session history traversal, in §6.7.10
* session history traversal queue, in §6.6.2
* set-cookie, in §4.2.5.3
* setCustomValidity(), in §4.10.20.3
* setCustomValidity(error)
* method for HTMLObjectElement, in §4.7.8
* method for HTMLInputElement, HTMLButtonElement,
HTMLSelectElement, HTMLTextAreaElement, HTMLOutputElement,
HTMLFieldSetElement, in §4.10.20.3
* setData(format, data), in §5.7.3
* setDragImage(element, x, y), in §5.7.3
* setDragImage(image, x, y), in §5.7.3
* setInterval(), in §7.5
* setInterval(handler), in §7.2
* setInterval(handler, timeout), in §7.2
* setInterval(handler, timeout, ...arguments), in §7.2
* set of comma-separated tokens, in §2.4.8
* set of scripts that will execute as soon as possible, in §4.12.1.1
* set of space-separated tokens, in §2.4.7
* setRangeText(), in §4.10.19
* setRangeText(replacement), in §4.10.19
* setRangeText(replacement, start, end), in §4.10.19
* setRangeText(replacement, start, end, selectionMode), in §4.10.19
* setSelectionRange(), in §4.10.19
* setSelectionRange(start, end), in §4.10.19
* setSelectionRange(start, end, direction), in §4.10.19
* __setter__(), in §3.2.5.7
* __setter__(name, value), in §3.2.5.7
* set the document’s address, in §6.7.1
* set the frozen base URL, in §4.2.3
* set the url, in §4.8.3
* set the value of a new indexed property, in §4.10.7
* set the value of a new indexed property or set the value of an
existing indexed property, in §2.7.2.3
* setTimeout(), in §7.5
* setTimeout(handler), in §7.2
* setTimeout(handler, timeout), in §7.2
* setTimeout(handler, timeout, ...arguments), in §7.2
* setting, in §2.1.4
* settings object, in §7.1.3.1
* setting the document’s address, in §6.7.1
* set up a browsing context environment settings object, in §6.1.6
* set up the position, in §4.11.4
* Set up the request, in §7.1.3.2
* shape
* element-attr for area, in §4.7.15
* attribute for HTMLAreaElement, in §4.7.15
* element-attr for a, in §11.2
* attribute for HTMLAnchorElement, in §11.3.4
* Shift_JIS, in §8.2.2.3
* shipping, in §4.10.18.7.1
* should be used, in §4.7.8
* show(), in §4.11.4
* show(anchor), in §4.11.4
* showing
* mode for track, in §4.7.13.11.1
* enum-value for TextTrackMode, in §4.7.13.11.5
* showModal(), in §4.11.4
* showModal(anchor), in §4.11.4
* shown, in §2.1
* show poster flag, in §4.7.13.6
* sign, in §4.7.13.10.1
* signal a type change, in §4.10.5
* simple color, in §2.4.6
* size
* definition of, in §2.6.2
* attribute for HTMLInputElement, in §4.10.5
* element-attr for input, in §4.10.5.3.2
* element-attr for select, in §4.10.7
* attribute for HTMLSelectElement, in §4.10.7
* element-attr for hr, in §11.2
* attribute for HTMLFontElement, in §11.3.4
* attribute for HTMLHRElement, in §11.3.4
* sizes
* element-attr for link, in §4.2.4
* attribute for HTMLLinkElement, in §4.2.4
* element-attr for source, in §4.7.4
* attribute for HTMLSourceElement, in §4.7.4
* element-attr for img, in §4.7.5
* attribute for HTMLImageElement, in §4.7.5
* skip white space, in §2.4.1
* slide
* attr-value for marquee/behavior, in §11.3.2
* state for marquee/behavior, in §11.3.2
* slot, in §3.2.5
* slots, in §4.9.12
* small, in §4.5.4
* sms:, in §2.2.2
* Soft, in §4.10.11
* soft, in §4.10.11
* solitary callback microtasks, in §7.1.4.2
* source, in §4.7.4
* source browsing context, in §6.7.1
* source node, in §5.7.5
* source set, in §4.7.5
* source size, in §4.7.5
* Source text, in §7.1.3.1
* space characters, in §2.4.1
* spacer, in §11.2
* span
* (element), in §4.5.28
* element-attr for colgroup, in §4.9.3
* attribute for HTMLTableColElement, in §4.9.3
* element-attr for col, in §4.9.4
* span multiple columns, in §4.9.11
* Special, in §8.2.3.2
* spellcheck
* element-attr for global, in §5.6.5
* attribute for HTMLElement, in §5.6.5
* spinning the event loop, in §7.1.4.2
* spins the event loop, in §7.1.4.2
* spin the event loop, in §7.1.4.2
* split a string on commas, in §2.4.8
* split a string on spaces, in §2.4.7
* spoon-feed the parser, in §9.2
* src
* element-attr for source, in §4.7.4
* attribute for HTMLSourceElement, in §4.7.4
* element-attr for img, in §4.7.5
* attribute for HTMLImageElement, in §4.7.5
* element-attr for iframe, in §4.7.6
* attribute for HTMLIFrameElement, in §4.7.6
* element-attr for embed, in §4.7.7
* attribute for HTMLEmbedElement, in §4.7.7
* element-attr for track, in §4.7.12
* attribute for HTMLTrackElement, in §4.7.12
* element-attr for media, in §4.7.13.2
* attribute for HTMLMediaElement, in §4.7.13.2
* attribute for HTMLInputElement, in §4.10.5
* element-attr for input, in §4.10.5.1.19
* element-attr for script, in §4.12.1
* attribute for HTMLScriptElement, in §4.12.1
* element-attr for frame, in §11.3.3
* attribute for HTMLFrameElement, in §11.3.3
* srcdoc
* element-attr for iframe, in §4.7.6
* attribute for HTMLIFrameElement, in §4.7.6
* srclang
* element-attr for track, in §4.7.12
* attribute for HTMLTrackElement, in §4.7.12
* srcObject, in §4.7.13.2
* srcset
* element-attr for source, in §4.7.4
* attribute for HTMLSourceElement, in §4.7.4
* element-attr for img, in §4.7.5
* attribute for HTMLImageElement, in §4.7.5
* stack of open elements, in §8.2.3.2
* stack of template insertion modes, in §8.2.3.1
* stalled, in §4.7.13.16
* stall timeout, in §4.7.13.5
* standby
* element-attr for object, in §11.2
* attribute for HTMLObjectElement, in §11.3.4
* start
* element-attr for ol, in §4.4.6
* attribute for HTMLOListElement, in §4.4.6
* enum-value for SelectionMode, in §4.10.19
* event for marquee, in §11.3.2
* start(), in §11.3.2
* start(index), in §4.7.13.14
* Start tags, in §8.1.2.1
* start the track processing model, in §4.7.13.11.3
* start the WebSocket closing handshake, in §2.2.2
* startTime, in §4.7.13.11.5
* state
* dfn for image, in §4.7.5
* attribute for History, in §6.6.2
* dict-member for PopStateEventInit, in §6.7.10.2
* attribute for PopStateEvent, in §6.7.10.2
* state of the type attribute, in §4.10.5.1
* states of the type attribute, in §4.10.5.1
* statically validate the constraints, in §4.10.20.2
* statically validating the constraints, in §4.10.20.2
* status, in §6.3.6
* statusbar, in §6.3.6
* step
* attribute for HTMLInputElement, in §4.10.5
* element-attr for input, in §4.10.5.3.8
* step-align, in §4.10.5.4
* step-aligned, in §4.10.5.4
* step-aligns, in §4.10.5.4
* step base, in §4.10.5.3.8
* stepDown(n), in §4.10.5.4
* stepMismatch, in §4.10.20.3
* step scale factor, in §4.10.5.3.8
* steps to expose a media-resource-specific text track, in §4.7.13.11.2
* stepUp(n), in §4.10.5.4
* stop()
* method for Window, in §6.3.1
* method for HTMLMarqueeElement, in §11.3.2
* stop parsing, in §8.2.6
* stopped due to errors, in §4.7.13.8
* storage, in §Unnumbered section
* strictly split, in §2.4.1
* strictly split a string, in §2.4.1
* strictly splitting the string, in §2.4.1
* strike, in §11.2
* stringification behavior
* dfn for HTMLHyperlinkElementUtils, in §4.8.3
* dfn for Location, in §6.6.4
* strip and collapse white space, in §2.4.1
* strip leading and trailing white space, in §2.4.1
* strip line breaks, in §2.4.1
* stripped line breaks, in §2.4.1
* stripping and collapsing white space, in §2.4.1
* stripping leading and trailing white space, in §2.4.1
* strong, in §4.5.3
* StructuredDeserialize, in §2.9.6
* StructuredDeserializeWithTransfer, in §2.9.8
* StructuredSerialize, in §2.9.4
* StructuredSerializeForStorage, in §2.9.5
* StructuredSerializeInternal, in §2.9.3
* StructuredSerializeWithTransfer, in §2.9.7
* style
* element-attr for global, in §3.2.5.6
* (element), in §4.2.6
* style data, in §4.2.6
* stylesheet, in §4.8.6.11
* style sheet ready, in §4.2.7
* sub, in §4.5.21
* sub-deserialization, in §2.9.6
* Submit, in §4.10.5.1.18
* submit(), in §4.10.3
* submit
* attr-value for input/type, in §4.10.5
* attr-value for button/type, in §4.10.6
* definition of, in §4.10.21.3
* event for global, in §Unnumbered section
* Submit as entity body, in §4.10.21.3
* submit button
* definition of, in §4.10.2
* element-state for button/type, in §4.10.6
* submit buttons, in §4.10.2
* Submit dialog, in §4.10.21.3
* submittable, in §4.10.2
* Submittable element, in §4.10.2
* Submittable elements, in §4.10.2
* submitted, in §4.10.21.3
* subprotocol in use, in §2.2.2
* sub-serialization, in §2.9.3
* substantial, in §10.3.10
* Subtitles, in §4.7.12
* subtitles
* attr-value for track/kind, in §4.7.12
* attr-value for commonTrack/kind, in §4.7.13.10.1
* dfn for track, in §4.7.13.11.1
* enum-value for TextTrackKind, in §4.7.13.11.5
* "subtitles", in §4.7.13.11.5
* suffer from a custom error, in §4.10.20.1
* suffer from an overflow, in §4.10.20.1
* suffer from an underflow, in §4.10.20.1
* suffer from a pattern mismatch, in §4.10.20.1
* suffer from a step mismatch, in §4.10.20.1
* suffer from a type mismatch, in §4.10.20.1
* suffer from bad input, in §4.10.20.1
* suffer from being missing, in §4.10.20.1
* suffer from being too long, in §4.10.20.1
* suffer from being too short, in §4.10.20.1
* suffering from a custom error, in §4.10.20.1
* suffering from an overflow, in §4.10.20.1
* suffering from an underflow, in §4.10.20.1
* suffering from a pattern mismatch, in §4.10.20.1
* suffering from a step mismatch, in §4.10.20.1
* suffering from a type mismatch, in §4.10.20.1
* suffering from bad input, in §4.10.20.1
* suffering from being missing, in §4.10.20.1
* suffering from being too long, in §4.10.20.1
* suffering from being too short, in §4.10.20.1
* suffixes, in §11.3.4.1
* suggestions source element, in §4.10.5.3.9
* suitable sequentially focusable area, in §5.4.5
* summary
* (element), in §4.11.2
* element-attr for table, in §11.2
* attribute for HTMLTableElement, in §11.3.4
* sup, in §4.5.21
* supported, in §2.1.1
* supported token, in §2.2.2
* supported tokens, in §2.2.2
* supporting the suggested default rendering, in §2.2.1
* support the suggested default rendering, in §2.2.1
* suspend, in §4.7.13.16
* SVG namespace, in §2.8
* synchronous section, in §7.1.4.2
* synchronous sections, in §7.1.4.2
* tabindex, in §5.4.3
* tabIndex, in §5.4.3
* tabindex focus flag, in §5.4.3
* table
* (element), in §4.9.1
* definition of, in §4.9.12
* table design techniques, in §4.9.1.1
* table model, in §4.9.12
* table model error, in §4.9.12
* tables, in §4.9.12
* tag, in §4.8.6.12
* Tag clouds, in §4.13.3
* tag name, in §8.1.2
* Tag name state, in §8.2.4.8
* Tag omission in text/html, in §3.2.3
* Tag open state, in §8.2.4.6
* Tags, in §8.1.2
* taintEnabled(), in §7.7.1.1
* target
* element-attr for base, in §4.2.3
* attribute for HTMLBaseElement, in §4.2.3
* attribute for HTMLAnchorElement, in §4.5.1
* attribute for HTMLAreaElement, in §4.7.15
* element-attr for a, area, links, in §4.8.2
* element-attr for form, in §4.10.18.6
* attribute for HTMLFormElement, in §4.10.18.6
* element-attr for link, in §11.2
* attribute for HTMLLinkElement, in §11.3.4
* target element, in §6.7.9
* target override, in §2.2.2
* task queues, in §7.1.4.1
* tasks, in §7.1.4.1
* task source, in §7.1.4.1
* tBodies, in §4.9.1
* tbody, in §4.9.5
* td, in §4.9.9
* tel, in §4.10.5
* Telephone, in §4.10.5.1.3
* template, in §4.12.3
* template contents, in §4.12.3
* temporary buffer, in §8.2.4
* term, in §4.5.8
* term-description groups, in §4.4.9
* termination nesting level, in §6.7.11
* Text, in §4.10.5.1.2
* text
* definition of, in §3.2.4.2.5
* attribute for HTMLTitleElement, in §4.2.2
* attribute for HTMLAnchorElement, in §4.5.1
* attr-value for input/type, in §4.10.5
* attribute for HTMLOptionElement, in §4.10.10
* attribute for HTMLScriptElement, in §4.12.1
* element-attr for body, in §11.2
* attribute for HTMLBodyElement, in §11.3.4
* textarea, in §4.10.11
* textarea effective height, in §10.5.15
* textarea effective width, in §10.5.15
* textarea wrapping transformation, in §4.10.11
* text content, in §3.2.4.2.5
* textLength, in §4.10.11
* text/plain, in §4.10.18.6
* text/plain encoding algorithm, in §4.10.21.8
* TextTrack, in §4.7.13.11.5
* TextTrackCue, in §4.7.13.11.5
* text track cue, in §4.7.13.11.1
* text track cue active flag, in §4.7.13.11.1
* text track cue data, in §4.7.13.11.1
* text track cue display state, in §4.7.13.11.1
* text track cue end time, in §4.7.13.11.1
* text track cue identifier, in §4.7.13.11.1
* TextTrackCueList, in §4.7.13.11.5
* text track cue order, in §4.7.13.11.1
* text track cue pause-on-exit flag, in §4.7.13.11.1
* text track cue start time, in §4.7.13.11.1
* text track cue writing direction, in §2.2.2
* text track failed to load, in §4.7.13.11.1
* text track in-band metadata track dispatch type, in §4.7.13.11.1
* TextTrackKind, in §4.7.13.11.5
* text track kind, in §4.7.13.11.1
* text track kinds, in §4.7.13.11.1
* text track label, in §4.7.13.11.1
* text track language, in §4.7.13.11.1
* TextTrackList, in §4.7.13.11.5
* text track list of cues, in §4.7.13.11.1
* text track loaded, in §4.7.13.11.1
* text track loading, in §4.7.13.11.1
* text track mode, in §4.7.13.11.1
* TextTrackMode, in §4.7.13.11.5
* text track not loaded, in §4.7.13.11.1
* text track readiness state, in §4.7.13.11.1
* text track rules for extracting the chapter title, in §4.7.13.11.1
* textTracks, in §4.7.13.11.5
* text tracks, in §4.7.13.11.1
* tFoot, in §4.9.1
* tfoot, in §4.9.7
* th, in §4.9.10
* thead, in §4.9.6
* tHead, in §4.9.1
* the conditions described above, in §4.7.5.1.16
* the directionality, in §3.2.5.5
* The document’s referrer, in §3.1
* The drag data item kind, in §5.7.2
* The drag data item type string, in §5.7.2
* the element’s directionality, in §3.2.5.5
* The embed element setup steps, in §4.7.7
* the empty string, in §4.7.13.3
* the environment settings object’s global object, in §7.1.3.5
* the environment settings object’s Realm, in §7.1.3.5
* The event handler processing algorithm, in §7.1.5.1
* the first 1024 bytes, in §4.2.5.5
* the global object’s Realm, in §7.1.3.5
* The HTML syntax, in §8
* the indicated part of the document, in §6.7.9
* the kind of text track, in §4.7.13.11.1
* the link is an alternative stylesheet, in §4.8.6.11
* The location bar BarProp object, in §6.3.6
* The menu bar BarProp object, in §6.3.6
* the outline’s owner, in §4.3.9.1
* The personal bar BarProp object, in §6.3.6
* the Realm’s global object, in §7.1.3.5
* the Realm’s settings object, in §7.1.3.5
* the resource’s content-type metadata, in §2.6.4
* the rules described previously, in §4.7.13.5
* The rules for choosing a browsing context given a browsing context
name, in §6.1.5
* the script is ready, in §4.12.1.1
* the script’s script, in §4.12.1.1
* the script’s type, in §4.12.1.1
* The scrollbar BarProp object, in §6.3.6
* The status bar BarProp object, in §6.3.6
* the step labeled fragments, in §6.7.1
* The template elements, in §8.1.2
* the text tracks are ready, in §4.7.13.11.1
* The toolbar BarProp object, in §6.3.6
* the WebSocket closing handshake is started, in §2.2.2
* the WebSocket connection close code, in §2.2.2
* the WebSocket connection close reason, in §2.2.2
* the WebSocket connection is closed, in §2.2.2
* the WebSocket connection is established, in §2.2.2
* the Window object is indexed for property retrieval, in §6.3.3
* The XML syntax, in §9
* third administrative level, in §4.10.18.7.1
* this
* definition of, in §1.7.2
* (element), in §1.7.2
* through which new document is nested, in §6.1.1
* throw, in §2.2.2
* throw-on-dynamic-markup-insertion counter, in §7.4
* time
* definition of, in §2.4.5.4
* (element), in §4.5.16
* attr-value for input/type, in §4.10.5
* Time, in §4.10.5.1.10
* timeline offset, in §4.7.13.6
* time marches on, in §4.7.13.8
* TimeRanges, in §4.7.13.14
* TimerHandler, in §7.2
* timer initialization steps, in §7.5
* timer nesting level, in §7.5
* timer task source, in §7.5
* timeupdate, in §4.7.13.16
* time zone, in §2.4.5.6
* time-zone offset, in §2.4.5.6
* title
* attribute for Document, in §3.1.3
* element-attr for global, figure, div, img, textarea, meter, in
§3.2.5.1
* attribute for HTMLElement, in §3.2.5.1
* (element), in §4.2.2
* element-attr for link, in §4.2.4
* element-attr for style, in §4.2.6
* element-attr for dfn, in §4.5.8
* element-attr for abbr, in §4.5.9
* element-attr for input, in §4.10.5.3.6
* toBlob(), in §4.12.4
* toBlob(callback), in §4.12.4
* toBlob(callback, type), in §4.12.4
* toBlob(callback, type, ...arguments), in §4.12.4
* toDataURL(type, ...arguments), in §4.12.4
* toggle
* definition of, in §4.10.7
* event for global, in §Unnumbered section
* toolbar, in §6.3.6
* tooLong, in §4.10.20.3
* tooShort, in §4.10.20.3
* top, in §6.1.1.1
* top-level browsing context, in §6.1.1
* topmargin, in §11.2
* @@toPrimitive, in §2.2.2
* @@toStringTag, in §2.2.2
* tr, in §4.9.8
* track
* (element), in §4.7.12
* attribute for HTMLTrackElement, in §4.7.12
* attribute for TextTrackCue, in §4.7.13.11.5
* dict-member for TrackEventInit, in §4.7.13.15
* attribute for TrackEvent, in §4.7.13.15
* TrackEvent, in §4.7.13.15
* TrackEventInit, in §4.7.13.15
* TrackEvent(type), in §4.7.13.15
* TrackEvent(type, eventInitDict), in §4.7.13.15
* track label, in §4.7.12
* track language, in §4.7.12
* track URL, in §4.7.12
* Transferable, in §2.9.2
* Transferable objects, in §2.9.2
* transfer-receiving steps, in §2.9.2
* transfer steps, in §2.9.2
* transformToDocument(), in §2.2.2
* transformToFragment(), in §2.2.2
* translatable attributes, in §3.2.5.3
* translate
* element-attr for global, in §3.2.5.3
* attribute for HTMLElement, in §3.2.5.3
* translate-enabled, in §3.2.5.3
* translation, in §4.7.13.10.1
* translation mode, in §3.2.5.3
* transparent, in §3.2.4.3
* transparently follow the redirect, in §2.6.2
* traverse the history, in §6.7.10
* traverse the history by a delta, in §6.6.2
* traversing the history, in §6.7.10
* tree, in §2.2.2
* tree construction dispatcher, in §8.2.5
* tree order, in §2.2.2
* true-by-default, in §5.6.5
* truespeed, in §11.3.2
* trueSpeed, in §11.3.2
* trusted, in §2.1.4
* trusted event, in §2.1.4
* tt, in §11.2
* tuple, in §6.4
* tuple origin, in §6.4
* turned off, in §11.3.2
* turned on, in §11.3.2
* type
* element-attr for link, in §4.2.4
* attribute for HTMLLinkElement, in §4.2.4
* element-attr for style, in §4.2.6
* attribute for HTMLStyleElement, in §4.2.6
* element-attr for ol, in §4.4.6
* attribute for HTMLOListElement, in §4.4.6
* attribute for HTMLAnchorElement, in §4.5.1
* element-attr for source, in §4.7.4
* attribute for HTMLSourceElement, in §4.7.4
* element-attr for embed, in §4.7.7
* attribute for HTMLEmbedElement, in §4.7.7
* element-attr for object, in §4.7.8
* attribute for HTMLObjectElement, in §4.7.8
* attribute for HTMLAreaElement, in §4.7.15
* element-attr for a, links, in §4.8.2
* element-attr for input, in §4.10.5
* attribute for HTMLInputElement, in §4.10.5
* element-attr for button, in §4.10.6
* attribute for HTMLButtonElement, in §4.10.6
* attribute for HTMLSelectElement, in §4.10.7
* attribute for HTMLTextAreaElement, in §4.10.11
* attribute for HTMLOutputElement, in §4.10.12
* attribute for HTMLFieldSetElement, in §4.10.15
* element-attr for script, in §4.12.1
* attribute for HTMLScriptElement, in §4.12.1
* attribute for DataTransferItem, in §5.7.3.2
* element-attr for area, in §11.2
* element-attr for param, in §11.2
* element-attr for li, in §11.2
* element-attr for ul, in §11.2
* attribute for HTMLLIElement, in §11.3.4
* attribute for HTMLParamElement, in §11.3.4
* attribute for HTMLUListElement, in §11.3.4
* attribute for MimeType, in §11.3.4.1
* type blocklist, in §7.7.1.3
* type information, in §2.6.4
* typeMismatch, in §4.10.20.3
* typeMustMatch, in §4.7.8
* typemustmatch, in §4.7.8
* type of the content, in §4.7.7
* types, in §5.7.3
* type string, in §5.7.2
* u, in §4.5.24
* ul, in §4.4.7
* Unavailable, in §4.7.5
* unavailable, in §4.7.5
* unfocusing steps, in §5.4.4
* Unhandled promise rejections, in §7.1.3.10
* Unicode character, in §2.1.6
* Unicode code point, in §2.1.6
* unicode serialization, in §6.4
* unicode serialization of an origin, in §6.4
* uninitialized, in §5.7.3
* unit of related browsing contexts, in §6.1.4
* unit of related similar-origin browsing contexts, in §6.1.4
* units of related similar-origin browsing contexts, in §6.1.4
* unload
* definition of, in §6.7.11
* event for global, in §Unnumbered section
* unload a document, in §6.7.11
* unloaded, in §6.7.11
* unloading document cleanup steps, in §6.7.11
* unloading document visibility change steps, in §6.7.11
* unordered set of unique space-separated tokens, in §2.4.7
* unquoted, in §8.1.2.3
* unregisterContentHandler(), in §7.7.1.3
* unregisterContentHandler(mimeType, url), in §7.7.1.3
* unregisterProtocolHandler(), in §7.7.1.3
* unregisterProtocolHandler(scheme, url), in §7.7.1.3
* unsafe-url, in §2.2.2
* unstyled document, in §10.9
* up
* attr-value for marquee/direction, in §10.5.11
* state for marquee, in §11.3.2
* update a style block, in §4.2.6
* update href, in §4.8.3
* update the image data, in §4.7.5
* update the session history with the new page, in §6.7.1
* update the source set, in §4.7.5
* updating the session history with the new page, in §6.7.1
* upgrade the pending request to the current request, in §4.7.5
* upper-alpha, in §4.4.6
* uppercase ASCII hex digits, in §2.4.1
* uppercase ASCII letters, in §2.4.1
* upper-roman, in §4.4.6
* URL, in §4.10.5.1.4
* url
* definition of, in §4.8.4
* attr-value for input/type, in §4.10.5
* dfn for Location, in §6.6.4
* urn
* element-attr for a, in §11.2
* element-attr for link, in §11.2
* urn:, in §2.2.2
* Use Credentials, in §2.6.6
* use-credentials, in §2.6.6
* used during the parsing, in §8.2.5.4.4
* usemap
* element-attr for img, in §4.7.5
* element-attr for common, in §4.7.16.1
* element-attr for input, in §11.2
* useMap
* attribute for HTMLImageElement, in §4.7.5
* attribute for HTMLInputElement, in §11.3.4
* userAgent, in §7.7.1.1
* User agents with no scripting support, in §2.2.1
* user interaction task source, in §7.1.4.3
* username, in §4.8.3
* use srcset or picture, in §4.7.5
* using the rules for, in §8.2.3.1
* UTF-16BE, in §8.2.2.3
* UTF-16 encoding, in §2.1.6
* UTF-16LE, in §8.2.2.3
* UTF-8, in §8.2.2.3
* UTF-8 decode, in §2.2.2
* UTF-8 decode without BOM, in §2.2.2
* UTF-8 decode without BOM or fail, in §2.2.2
* UTF-8 encode, in §2.2.2
* :valid, in §4.15.2
* valid, in §4.10.20.3
* validate the server’s response, in §2.2.2
* validationMessage
* attribute for HTMLObjectElement, in §4.7.8
* attribute for HTMLInputElement, HTMLButtonElement,
HTMLSelectElement, HTMLTextAreaElement, HTMLOutputElement,
HTMLFieldSetElement, in §4.10.20.3
* valid browsing context name, in §6.1.5
* valid browsing context name or keyword, in §6.1.5
* valid browsing context names or keywords, in §6.1.5
* valid date string, in §2.4.5.2
* valid date string with optional time, in §2.4.5.10
* valid duration string, in §2.4.5.9
* valid e-mail address, in §4.10.5.1.5
* valid e-mail address list, in §4.10.5.1.5
* valid floating date and time string, in §2.4.5.5
* valid floating-point number, in §2.4.4.3
* valid global date and time string, in §2.4.5.7
* valid hash-name reference, in §2.4.9
* valid integer, in §2.4.4.1
* valid integers, in §2.4.4.1
* validity
* attribute for HTMLObjectElement, in §4.7.8
* attribute for HTMLInputElement, HTMLButtonElement,
HTMLSelectElement, HTMLTextAreaElement, HTMLOutputElement,
HTMLFieldSetElement, in §4.10.20.3
* ValidityState, in §4.10.20.3
* validity states, in §4.10.20.1
* valid list of floating-point numbers, in §2.4.4.6
* valid lowercase simple color, in §2.4.6
* valid media query list, in §2.4.10
* valid MIME type, in §2.1.1
* valid month string, in §2.4.5.1
* valid non-empty URL, in §2.5.1
* valid non-empty URL potentially surrounded by spaces, in §2.5.1
* valid non-negative integer, in §2.4.4.2
* valid normalized floating date and time string, in §2.4.5.5
* valid normalized global date and time string, in §2.4.5.7
* valid simple color, in §2.4.6
* valid source size list, in §4.7.5
* valid time string, in §2.4.5.4
* valid time-zone offset string, in §2.4.5.6
* valid URL, in §2.5.1
* valid URL potentially surrounded by spaces, in §2.5.1
* valid week string, in §2.4.5.8
* valid yearless date string, in §2.4.5.3
* vAlign
* attribute for HTMLTableColElement, in §11.3.4
* attribute for HTMLTableSectionElement, in §11.3.4
* attribute for HTMLTableCellElement, in §11.3.4
* attribute for HTMLTableRowElement, in §11.3.4
* valign
* element-attr for col, in §11.2
* element-attr for tbody, thead, tfoot, tablesection, in §11.2
* element-attr for td, th, tablecells, in §11.2
* element-attr for tr, in §11.2
* value
* attribute for RadioNodeList, in §2.7.2.2
* element-attr for li, in §4.4.8
* attribute for HTMLLIElement, in §4.4.8
* element-attr for data, in §4.5.15
* attribute for HTMLDataElement, in §4.5.15
* element-attr for param, in §4.7.9
* attribute for HTMLParamElement, in §4.7.9
* element-attr for input, in §4.10.5
* attribute for HTMLInputElement, in §4.10.5.4
* mode for input, in §4.10.5.4
* element-attr for button, in §4.10.6
* attribute for HTMLButtonElement, in §4.10.6
* attribute for HTMLSelectElement, in §4.10.7
* element-attr for option, in §4.10.10
* attribute for HTMLOptionElement, in §4.10.10
* attribute for HTMLTextAreaElement, in §4.10.11
* mode for output, in §4.10.12
* attribute for HTMLOutputElement, in §4.10.12
* element-attr for progress, in §4.10.13
* attribute for HTMLProgressElement, in §4.10.13
* element-attr for meter, in §4.10.14
* attribute for HTMLMeterElement, in §4.10.14
* dfn for forms, in §4.10.17.1
* valueAsDate, in §4.10.5.4
* valueAsNumber, in §4.10.5.4
* valueMissing, in §4.10.20.3
* value mode flag, in §4.10.12
* value sanitization algorithm, in §4.10.5
* values are reset, in §6.7.10
* valuetype, in §11.2
* valueType, in §11.3.4
* var, in §4.5.18
* version
* element-attr for html, in §11.2
* attribute for HTMLHtmlElement, in §11.3.4
* video, in §4.7.10
* videoHeight, in §4.7.10
* VideoTrack, in §4.7.13.10.1
* VideoTrackList, in §4.7.13.10.1
* videoTracks, in §4.7.13.10
* videoWidth, in §4.7.10
* viewport, in §2.2.2
* viewport-based selection, in §4.7.1
* visible
* definition of, in §2.1
* attribute for BarProp, in §6.3.6
* :visited, in §4.15.2
* Visual user agents that support the suggested default rendering, in
§2.2.1
* vlink, in §11.2
* vLink, in §11.3.4
* vlinkColor, in §11.3.4
* Void elements, in §8.1.2
* volume, in §4.7.13.13
* volumechange, in §4.7.13.16
* vspace
* element-attr for embed, in §11.2
* element-attr for iframe, in §11.2
* element-attr for input, in §11.2
* element-attr for img, in §11.2
* element-attr for marquee, in §11.2
* element-attr for object, in §11.2
* attribute for HTMLAppletElement, in §11.3.1
* attribute for HTMLMarqueeElement, in §11.3.2
* attribute for HTMLImageElement, in §11.3.4
* attribute for HTMLObjectElement, in §11.3.4
* waiting, in §4.7.13.16
* wbr, in §4.5.30
* webgl
* context for canvas, in §4.12.4
* definition of, in §4.12.4
* WebVTT, in §2.2.2
* WebVTT file, in §2.2.2
* WebVTT file using chapter title text, in §2.2.2
* WebVTT file using cue text, in §2.2.2
* WebVTT file using only nested cues, in §2.2.2
* WebVTT parser, in §2.2.2
* week
* definition of, in §2.4.5.8
* attr-value for input/type, in §4.10.5
* Week, in §4.10.5.1.9
* week number of the last day, in §2.4.5.8
* white_space, in §2.4.1
* white_space characters, in §2.4.1
* width
* attribute for HTMLImageElement, in §4.7.5
* element-attr for media, img, iframe, embed, object, video, input,
in §4.7.19
* attribute for HTMLIFrameElement, HTMLEmbedElement,
HTMLObjectElement, HTMLVideoElement, in §4.7.19
* attribute for HTMLInputElement, in §4.10.5
* element-attr for canvas, in §4.12.4
* attribute for HTMLCanvasElement, in §4.12.4
* attribute for ImageBitmap, in §7.8
* element-attr for col, in §11.2
* element-attr for hr, in §11.2
* element-attr for marquee, in §11.2
* element-attr for pre, in §11.2
* element-attr for table, in §11.2
* element-attr for td, th, tablecells, in §11.2
* attribute for HTMLAppletElement, in §11.3.1
* attribute for HTMLMarqueeElement, in §11.3.2
* attribute for HTMLTableColElement, in §11.3.4
* attribute for HTMLHRElement, in §11.3.4
* attribute for HTMLPreElement, in §11.3.4
* attribute for HTMLTableElement, in §11.3.4
* attribute for HTMLTableCellElement, in §11.3.4
* width descriptor, in §4.7.5
* width descriptor value, in §4.7.5
* width of the select’s labels, in §10.5.14
* willful violation, in §1.5.2
* willValidate
* attribute for HTMLObjectElement, in §4.7.8
* attribute for HTMLInputElement, HTMLButtonElement,
HTMLSelectElement, HTMLTextAreaElement, HTMLOutputElement,
HTMLFieldSetElement, in §4.10.20.3
* window, in §6.3
* Window, in §6.3
* WindowEventHandlers, in §7.1.5.2.1
* WindowOrWorkerGlobalScope, in §7.2
* WindowProxy, in §6.3.7
* windowproxy defineownproperty, in §6.3.7.1.6
* windowproxy delete, in §6.3.7.1.9
* windowproxy get, in §6.3.7.1.7
* windowproxy getownproperty, in §6.3.7.1.5
* windowproxy getprototypeof, in §6.3.7.1.1
* windowproxy isextensible, in §6.3.7.1.3
* windowproxy ownpropertykeys, in §6.3.7.1.10
* windowproxy preventextensions, in §6.3.7.1.4
* windowproxy set, in §6.3.7.1.8
* windowproxy setprototypeof, in §6.3.7.1.2
* windows-1250, in §8.2.2.3
* windows-1251, in §8.2.2.3
* windows-1252, in §8.2.2.3
* windows-1254, in §8.2.2.3
* windows-1256, in §8.2.2.3
* windows-1257, in §8.2.2.3
* window slot, in §6.3.7
* wrap
* element-attr for textarea, in §4.10.11
* attribute for HTMLTextAreaElement, in §4.10.11
* wrap callbacks, in §7.1.4.2
* write(), in §7.4.3
* writeln(), in §7.4.4
* XHTML document, in §2.1
* XHTML documents, in §2.1
* XLink namespace, in §2.8
* XML-compatible, in §2.1.2
* XML document, in §2.1
* XML fragment parsing algorithm, in §9.4
* XML fragment serialization algorithm, in §9.3
* XML MIME type, in §2.1.2
* XML namespace, in §2.8
* XMLNS namespace, in §2.8
* XML parser, in §9.2
* XML scripting support disabled, in §9.2
* XML scripting support enabled, in §9.2
* xmp, in §11.2
* XSLTProcessor, in §2.2.2
* x-user-defined, in §8.2.2.3
* yearless date, in §2.4.5.3
Terms defined by reference
* [aria] defines the following terms:
* alert
* alertdialog
* application
* aria-activedescendant
* aria-atomic
* aria-autocomplete
* aria-busy
* aria-checked
* aria-colcount
* aria-colindex
* aria-colspan
* aria-controls
* aria-current
* aria-describedby
* aria-details
* aria-dialog
* aria-disabled
* aria-dropeffect
* aria-errormessage
* aria-expanded
* aria-flowto
* aria-grabbed
* aria-haspopup
* aria-hidden
* aria-invalid
* aria-keyshortcuts
* aria-label
* aria-labelledby
* aria-level
* aria-live
* aria-multiline
* aria-multiselectable
* aria-orientation
* aria-owns
* aria-placeholder
* aria-posinset
* aria-pressed
* aria-readonly
* aria-relevant
* aria-required
* aria-roledescription
* aria-rowcount
* aria-rowindex
* aria-rowspan
* aria-selected
* aria-setsize
* aria-sort
* aria-valuemax
* aria-valuemin
* aria-valuenow
* aria-valuetext
* article
* banner
* button
* cell
* checkbox
* columnheader
* combobox
* complementary
* contentinfo
* definition
* dialog
* directory
* document
* feed
* figure
* form
* grid
* gridcell
* group
* heading
* img
* link
* list
* listbox
* listitem
* log
* main
* marquee
* math
* menubar
* navigation
* none
* note
* option
* presentation
* progressbar
* radio
* radiogroup
* region
* row
* rowgroup
* rowheader
* scrollbar
* search
* searchbox
* separator
* slider
* spinbutton
* status
* switch
* tab
* table
* tablist
* tabpanel
* term
* textbox
* timer
* toolbar
* tooltip
* tree
* treegrid
* treeitem
* [COOKIES] defines the following terms:
* cookie header
* receives a set-cookie-string
* receiving a set-cookie-string
* [CSP3] defines the following terms:
* content security policy
* content security policy directive
* content security policy syntax
* directives
* enforce the policy
* enforced
* ensurecspdoesnotblockstringcompilation
* frame-ancestors
* frame-ancestors directive
* initialize a document's csp list
* initialize a global object's csp list
* is base allowed for document?
* parse a serialized content security policy
* report-uri
* sandbox
* sandbox directive
* should element be blocked a priori by content security policy?
* should element's inline behavior be blocked by content security
policy?
* valid content security policy
* [CSS-CASCADE-4] defines the following terms:
* computed value
* inherit
* specified value
* used value
* [css-color-4] defines the following terms:
* black
* transparent
* white
* [CSS-DISPLAY-3] defines the following terms:
* anonymous
* block
* display
* inline-block
* none
* table
* table-caption
* table-cell
* table-row
* [CSS-FONT-LOADING-3] defines the following terms:
* FontFace
* font source
* [CSS-FONTS-3] defines the following terms:
* font-family
* font-size
* [css-inline-3] defines the following terms:
* vertical-align
* [css-lists-3] defines the following terms:
* list-style-type
* [css-logical-1] defines the following terms:
* margin-block-end
* margin-block-start
* margin-inline-end
* margin-inline-start
* [css-position-3] defines the following terms:
* absolute
* position
* static
* top
* [css-sizing-3] defines the following terms:
* intrinsic sizing
* [CSS-STYLE-ATTR] defines the following terms:
* style attribute
* [CSS-SYNTAX-3] defines the following terms:
* <whitespace-token>
* component value
* consume a component value
* environment encoding
* function
* parse a comma-separated list of component values
* [CSS-TEXT-3] defines the following terms:
* justify
* letter-spacing
* normal
* pre
* pre-wrap
* text-align
* text-transform
* white space
* white-space
* [CSS-UI-3] defines the following terms:
* cursor
* help
* outline
* [css-ui-4] defines the following terms:
* appearance
* [CSS-VALUES] defines the following terms:
* <length>
* |
* [CSS-WRITING-MODES-3] defines the following terms:
* direction
* ltr
* plaintext
* rtl
* unicode-bidi
* [CSS2] defines the following terms:
* auto
* css2 system colors
* [css2-2] defines the following terms:
* block box
* border box
* border edge
* containing block
* content area
* content box
* in-flow
* inline box
* intrinsic width and height
* margin box
* margin collapsing
* margin edge
* out-of-flow
* [CSS22] defines the following terms:
* border-collapse
* border-spacing
* clear
* color
* float
* height
* line-height
* margin
* margin-bottom
* margin-left
* margin-right
* margin-top
* padding-bottom
* padding-left
* padding-right
* padding-top
* visibility
* width
* [css3-background] defines the following terms:
* background-color
* background-image
* border-bottom-color
* border-bottom-style
* border-bottom-width
* border-left-color
* border-left-style
* border-left-width
* border-right-color
* border-right-style
* border-right-width
* border-top-color
* border-top-style
* border-top-width
* medium
* solid
* [CSS3-CONTENT] defines the following terms:
* content
* [CSS3-IMAGES] defines the following terms:
* object-fit
* [CSS3-RUBY] defines the following terms:
* annotation
* collapse
* ruby annotation
* [CSS3-TRANSITIONS] defines the following terms:
* end time
* start time
* [CSSOM] defines the following terms:
* CSSStyleDeclaration
* LinkStyle
* StyleSheet
* alternate flag
* alternative style sheet sets
* associated css style sheet
* create a css style sheet
* css rules
* css style sheet
* cssText
* disabled flag
* location
* media
* origin-clean flag
* owner css rule
* owner node
* parent css style sheet
* preferred style sheet set
* remove a css style sheet
* serializing a css value
* style
* title
* type
* [CSSOM-VIEW] defines the following terms:
* MouseEventInit
* Screen
* clientX
* clientY
* evaluate media queries and report changes
* resize
* run the resize steps
* run the scroll steps
* screenX
* screenY
* scroll
* scroll an element into view
* scroll to the beginning of the document
* the features argument of window.open
* [custom-elements] defines the following terms:
* autonomous custom element
* create an element
* current element queue
* custom element constructor
* custom element reactions stack
* customized built-in element
* element queue
* enqueue a custom element callback reaction
* invoke custom element reactions
* looking up a custom element definition
* upgrades
* valid custom element name
* CEReactions
* HTMLConstructor
* [DOM41] defines the following terms:
* Attr
* ChildNode
* Comment
* DOMImplementation
* DOMTokenList
* DocumentFragment
* DocumentType
* Element
* Event
* EventInit
* EventTarget
* HTMLCollection
* MutationObserver
* Node
* NodeList
* ProcessingInstruction
* Text
* XMLDocument
* addEventListener(type, callback)
* adopt
* adopting steps
* append
* appendChild(node)
* bubbles
* cd data
* clone a node
* cloneNode()
* cloning steps
* collection
* content type
* createDocument(namespace, qualifiedName)
* createElement(localName)
* createElementNS(namespace, qualifiedName)
* createHTMLDocument()
* creating an element
* currentTarget
* data
* doctype
* document tree
* document url
* document's character encoding
* element attribute
* element interface
* event
* event listener
* getElementById(elementId)
* getElementsByClassName(classNames) (for Document)
* getElementsByClassName(classNames) (for Element)
* id
* id (for Element)
* importNode(node, deep)
* in a document tree
* initEvent(type, bubbles)
* initialize
* insert
* insertion steps
* isTrusted
* item(index)
* name
* node document
* other applicable specifications
* pre-insert
* publicId
* range
* range bp
* range end
* range start
* remove
* remove an attribute by name
* removing steps
* replace
* replace all
* represented by the collection
* select
* set an attribute value
* setAttribute(qualifiedName, value)
* systemId
* target (for Event)
* target (for ProcessingInstruction)
* textContent
* traverse
* type
* unique identifier
* url
* value
* [DOM-PARSING] defines the following terms:
* DOMParser
* innerHTML
* outerHTML
* [ECMA-262] defines the following terms:
* %arraybuffer%
* %arrayprototype%
* %objproto_tostring%
* %objproto_valueof%
* ArrayBuffer
* Date
* Error
* Function
* RangeError
* RegExp
* SyntaxError
* TypeError
* abstract equality comparison
* arraycreate
* automatic semicolon insertion
* call
* construct
* createdataproperty
* current realm
* current realm record
* detacharraybuffer
* directive prologue
* early error
* enqueuejob
* functionbody
* functioncreate
* get
* getactivescriptormodule
* getfunctionrealm
* hasownproperty
* hostensurecancompilestrings
* hostpromiserejectiontracker
* hostresolveimportedmodule
* initializehostdefinedrealm
* isaccessordescriptor
* iscallable
* isconstructor
* isdatadescriptor
* isdetachedbuffer
* javascript execution context
* javascript execution context stack
* javascript realm
* list
* module
* moduledeclarationinstantiation
* moduleevaluation
* newobjectenvironment
* ordinarydefineownproperty
* ordinarydelete
* ordinaryget
* ordinarygetownproperty
* ordinarygetprototypeof
* ordinaryisextensible
* ordinaryownpropertykeys
* ordinarypreventextensions
* ordinaryset
* ordinarysetprototypeof
* parsemodule
* parsescript
* pattern
* property descriptor
* propertydescriptor
* realm
* record
* runjobs
* running javascript execution context
* samevalue
* script
* scriptevaluation
* source text module record
* strict equality comparison
* the typedarray constructors
* toboolean
* tostring
* touint32
* type
* typedarraycreate
* typeof
* use strict directive
* well-known intrinsic objects
* well-known symbols
* [ENCODING] defines the following terms:
* decode
* encode code point
* encoded as utf-8
* encoding
* iso-8859-7
* windows-1255
* windows-1258
* windows-874
* [EVENTSOURCE] defines the following terms:
* EventSource
* [FETCH] defines the following terms:
* body (for request)
* body (for response)
* cache mode
* client
* cors protocol
* cors-cross-origin
* credentials mode
* cryptographic nonce metadata
* csp list
* default user-agent value
* destination
* extract a mime type
* extracting a mime type
* fetch
* fetching algorithm
* header list (for request)
* header list (for response)
* https state
* https state value
* initiator
* internal response
* method
* mode
* ok status
* omit-origin-header flag
* origin
* origin (for request)
* origin header
* parser metadata
* process response
* redirect mode
* referrer
* referrer policy
* request
* requestcredentials
* response
* response url
* same-origin data-url flag
* set
* status
* synchronous flag
* target browsing context
* terminate
* type (for request)
* type (for response)
* unsafe-request flag
* url (for request)
* url (for response)
* url list
* use-url-credentials flag
* [FILEAPI] defines the following terms:
* Blob
* File
* FileList
* [FULLSCREEN] defines the following terms:
* fullscreen enabled flag
* fully exit fullscreen
* requestFullscreen()
* top layer
* [GEOMETRY-1] defines the following terms:
* DOMMatrix
* [HR-TIME-2] defines the following terms:
* DOMHighResTimeStamp
* Performance
* now()
* [HTML] defines the following terms:
* :target
* prepare to run a callback
* [INFRA] defines the following terms:
* contain
* exist
* for each
* is empty
* list
* map
* [JLREQ] defines the following terms:
* jukugo ruby rendering
* [MATHML] defines the following terms:
* annotation-xml
* math
* mi
* mn
* mo
* ms
* mtext
* [MEDIACAPTURE-STREAMS] defines the following terms:
* MediaStream
* [mediaqueries-4] defines the following terms:
* <media-condition>
* [mediasource] defines the following terms:
* MediaSource
* [MIMESNIFF] defines the following terms:
* valid mime type with no parameters
* [PAGE-VISIBILITY] defines the following terms:
* hidden
* [paymentrequest] defines the following terms:
* paymentrequest
* [progress-events] defines the following terms:
* ProgressEvent
* [RFC1034] defines the following terms:
* rfc 1034 section 3.5
* [RFC5322] defines the following terms:
* rfc 5322 section 3.2.3
* [RFC5988] defines the following terms:
* link header
* [RFC6266] defines the following terms:
* content-disposition
* [rfc7230] defines the following terms:
* content-length
* [rfc7231] defines the following terms:
* accept
* accept-language
* content-language
* media-type
* referer
* [rfc7232] defines the following terms:
* last-modified
* [rfc7234] defines the following terms:
* cache-control
* [SELECTION-API] defines the following terms:
* Selection
* [SELECTORS4] defines the following terms:
* attribute selector
* pseudo-class
* type selector
* [SERVICE-WORKERS] defines the following terms:
* ServiceWorkerContainer
* service worker client
* [SVG11] defines the following terms:
* SVGMatrix
* [SVG2] defines the following terms:
* SVGScriptElement
* desc
* foreignobject
* script
* svg
* title
* [SVGTINY12] defines the following terms:
* process the svg script element
* [TOUCH-EVENTS] defines the following terms:
* Touch
* touch point
* [UIEVENTS] defines the following terms:
* FocusEvent
* MouseEvent
* UIEvent
* altKey
* button
* click
* ctrlKey
* dblclick
* detail
* getModifierState()
* keydown
* keypress
* keyup
* metaKey
* mousedown
* mouseenter
* mouseleave
* mousemove
* mouseout
* mouseover
* mouseup
* relatedTarget (for FocusEvent)
* relatedTarget (for MouseEvent)
* shiftKey
* view
* wheel
* [URL] defines the following terms:
* absolute url
* application/x-www-form-urlencoded serializer
* basic url parser
* default encode set
* domain
* domain to unicode
* fragment
* fragment state
* host (for host-concept)
* host (for url)
* host equals
* host parser
* host serializer
* host state
* hostname state
* ipv4
* ipv6
* network scheme
* non-relative flag
* object
* origin
* parsed urls
* password
* path
* path start state
* percent decode
* percent encode
* port
* port state
* query
* query state
* relative schemes
* relative url
* scheme
* scheme start state
* serialization
* serialize an integer
* serialized
* set the password
* set the username
* url
* url parse error
* url parser
* url record
* url serializer
* username
* utf-8 percent encode
* [WEBGL] defines the following terms:
* WebGLRenderingContext
* [WEBIDL] defines the following term:
* LegacyUnenumerableNamedProperties
* [WebIDL-20161215] defines the following terms:
* DOMException
* DOMString
* Exposed
* LenientThis
* NoInterfaceObject
* OverrideBuiltins
* PrimaryGlobal
* Promise
* PutForwards
* Replaceable
* SameObject
* TreatNonObjectAsNull
* TreatNullAs
* USVString
* Unforgeable
* boolean
* callback this value
* delete an existing named property
* determine the value of a named property
* double
* extended attribute
* long
* object
* perform a security check
* platform object
* primary interface
* set the value of a new named property
* set the value of an existing named property
* support named properties
* supported property names
* unrestricted double
* unsigned long
* unsigned short
* AbortError
* DOMString[]
* DataCloneError
* EmptyString
* HierarchyRequestError
* IndexSizeError
* InvalidAccessError
* InvalidCharacterError
* InvalidModificationError
* InvalidNodeTypeError
* InvalidStateError
* NamespaceError
* NetworkError
* NoModificationAllowedError
* NotFoundError
* NotSupportedError
* QuotaExceededError
* SecurityError
* TimeoutError
* URLMismatchError
* WrongDocumentError
* arraybufferview
* boolean
* converted
* converting
* determine the value of an indexed property
* domexception
* domstring
* double
* error
* global environment associated with
* invoke the web idl callback function
* long
* read only
* supported property indices
* unenumerable
* unrestricted double
* unsigned long
* usvstring
* [webmessaging] defines the following terms:
* MessagePort
* [whatwg] defines the following terms:
* whatwg html specification
* [workers] defines the following terms:
* Worker
* WorkerGlobalScope
* closing
* run a worker
* worker event loops
* worker processing model
* [XHR] defines the following terms:
* XMLHttpRequest
* fire a progress event named e
* lengthcomputable
* loaded
* responseXML
* total
* [xlink] defines the following terms:
* actuate
* arcrole
* href
* role
* show
* title
* type
* xlink
* [XML] defines the following terms:
* document entity
* entity declarations
* entity references
* internal general parsed entity
* name
* space
* [XML-NAMES] defines the following terms:
* xmlns
* [XML-STYLESHEET] defines the following terms:
* <?xml-stylesheet?>
Elements
This section is non-normative.
List of elements
Element Description Categories Parents† Children Attributes Interface
globals; href;
flow; phrasing*; target; download;
a Hyperlink interactive phrasing transparent* rel; hreflang; HTMLAnchorElement
type;
referrerpolicy
abbr Abbreviation flow; phrasing phrasing phrasing globals HTMLElement
address Contact flow flow flow* globals HTMLElement
information
globals; alt;
Hyperlink or coords; shape;
area dead area on an flow; phrasing phrasing* empty href; target; HTMLAreaElement
image map download; rel;
hreflang; type;
referrerpolicy
Self-contained
article syndicatable or flow; sectioning flow flow globals HTMLElement
reusable
composition
Sidebar for
aside tangentially flow; sectioning flow flow globals HTMLElement
related content
globals; src;
flow; phrasing; source*; crossorigin;
audio Audio player embedded; phrasing transparent* preload; HTMLAudioElement
interactive autoplay; loop;
muted; controls
b Keywords flow; phrasing phrasing phrasing globals HTMLElement
Base URL and
default target globals; href;
base browsing context metadata head; template empty target HTMLBaseElement
for hyperlinks
and forms
Text
bdi directionality flow; phrasing phrasing phrasing globals HTMLElement
isolation
Text
bdo directionality flow; phrasing phrasing phrasing globals HTMLElement
formatting
A section quoted flow; sectioning
blockquote from another root flow flow globals; cite HTMLQuoteElement
source
globals;
onafterprint;
onbeforeprint;
onbeforeunload;
onhashchange;
onlanguagechange;
body Document body sectioning root html flow onmessage; HTMLBodyElement
onoffline;
ononline;
onpagehide;
onpageshow;
onpopstate;
onstorage;
onunload
Line break,
br e.g., in poem or flow; phrasing phrasing empty globals HTMLBRElement
postal address
globals;
flow; phrasing; autofocus;
interactive; disabled; form;
listed; formaction;
button Button control labelable; phrasing phrasing* formenctype; HTMLButtonElement
submittable; formmethod;
reassociateable; formnovalidate;
form-associated formtarget; name;
type; value
canvas Scriptable flow; phrasing; phrasing transparent globals; width; HTMLCanvasElement
bitmap canvas embedded height
caption Table caption none table; template flow* globals HTMLTableCaptionElement
cite Title of a work flow; phrasing phrasing phrasing globals HTMLElement
code Computer code flow; phrasing phrasing phrasing globals HTMLElement
col Table column none colgroup; empty globals; span HTMLTableColElement
template
colgroup Group of columns none table; template col*; template* globals; span HTMLTableColElement
in a table
data Machine-readable flow; phrasing phrasing phrasing globals; value HTMLDataElement
equivalent
Container for
datalist options for flow; phrasing phrasing phrasing; option globals HTMLDataListElement
combo box
control
Content for
dd corresponding dt none dl; template flow globals HTMLElement
element(s)
del A removal from flow; phrasing* phrasing transparent globals; cite; HTMLModElement
the document datetime
Disclosure flow; sectioning
details control for root; interactive flow summary*; flow globals; open HTMLDetailsElement
hiding details
dfn Defining flow; phrasing phrasing phrasing* globals HTMLElement
instance
dialog Dialog box or flow; sectioning flow flow globals; open HTMLDialogElement
window root
div Generic flow flow flow flow globals HTMLDivElement
container
Association list
consisting of dt*; dd*;
dl zero or more flow flow script-supporting globals HTMLDListElement
name-value elements
groups
Legend for
dt corresponding dd none dl; template flow* globals HTMLElement
element(s)
em Stress emphasis flow; phrasing phrasing phrasing globals HTMLElement
flow; phrasing; globals; src;
embed Plugin embedded; phrasing empty type; width; HTMLEmbedElement
interactive height; any*
flow; sectioning globals;
fieldset Group of form root; listed; flow legend*; flow disabled; form; HTMLFieldSetElement
controls reassociateable; name
form-associated
figcaption Caption for none figure; template flow globals HTMLElement
figure
figure Figure with flow; sectioning flow figcaption*; flow globals HTMLElement
optional caption root
footer Footer for a flow flow flow* globals HTMLElement
page or section
globals;
accept-charset;
User-submittable action;
form form flow flow flow* autocomplete; HTMLFormElement
enctype; method;
name; novalidate;
target
h1, h2,
h3, h4, Section heading flow; headings flow phrasing globals HTMLHeadingElement
h5, h6
Container for
head document none html metadata* globals HTMLHeadElement
metadata
Introductory or
header navigational flow flow flow* globals HTMLElement
aids for a page
or section
hr Thematic break flow flow empty globals HTMLHRElement
html Root element none none* head*; body* globals; manifest HTMLHtmlElement
i Alternate voice flow; phrasing phrasing phrasing globals HTMLElement
globals; src;
flow; phrasing; srcdoc; name;
iframe Nested browsing embedded; phrasing text* sandbox; HTMLIFrameElement
context interactive allowfullscreen;
width; height;
referrerpolicy
globals; alt;
flow; phrasing; src; srcset;
embedded; crossorigin;
img Image interactive*; phrasing empty usemap; ismap; HTMLImageElement
form-associated longdesc; width;
height;
referrerpolicy
globals; accept;
alt;
autocomplete;
autofocus;
checked; dirname;
disabled; form;
flow; phrasing; formaction;
interactive*; formenctype;
listed; formmethod;
labelable; formnovalidate;
input Form control submittable; phrasing empty formtarget; HTMLInputElement
resettable; height; list;
reassociateable; max; maxlength;
form-associated min; minlength;
multiple; name;
pattern;
placeholder;
readonly;
required; size;
src; step; type;
value; width
ins An addition to flow; phrasing* phrasing transparent globals; cite; HTMLModElement
the document datetime
kbd User input flow; phrasing phrasing phrasing globals HTMLElement
flow; phrasing;
label Caption for a interactive; phrasing phrasing* globals; for HTMLLabelElement
form control reassociateable;
form-associated
legend Caption for none fieldset; phrasing globals HTMLLegendElement
fieldset template
li List item none ol; ul; template flow globals; value* HTMLLIElement
globals; href;
head; template; crossorigin; rel;
link Link metadata metadata; flow*; noscript*; empty media; HTMLLinkElement
phrasing* phrasing* referrerpolicy;
nonce; hreflang;
type; sizes
main Main content of flow flow flow* globals HTMLElement
a document
map Image map flow; phrasing* phrasing transparent; globals; name HTMLMapElement
area*
mark Highlight flow; phrasing phrasing phrasing globals HTMLElement
metadata; flow*; head; template; globals; name;
meta Text metadata phrasing* noscript*; empty http-equiv; HTMLMetaElement
phrasing* content; charset
flow; phrasing; globals; value;
meter Gauge labelable phrasing phrasing* min; max; low; HTMLMeterElement
high; optimum
Section with
nav navigational flow; sectioning flow flow globals HTMLElement
links
noscript Fallback content metadata; flow; head*; template*; varies* globals HTMLElement
for script phrasing phrasing*
flow; phrasing;
Image, nested embedded; globals; data;
browsing interactive*; param*; type;
object context, or listed; phrasing transparent typemustmatch; HTMLObjectElement
plugin submittable; name; form;
reassociateable; width; height
form-associated
li; globals;
ol Ordered list flow flow script-supporting reversed; start; HTMLOListElement
elements type
Group of options option; globals;
optgroup in a list box none select; template script-supporting disabled; label HTMLOptGroupElement
elements
Option in a list select; datalist; globals;
option box or combo box none optgroup; text* disabled; label; HTMLOptionElement
control template selected; value
flow; phrasing;
listed;
output Calculated labelable; phrasing phrasing globals; for; HTMLOutputElement
output value resettable; form; name
reassociateable;
form-associated
p Paragraph flow flow phrasing globals HTMLParagraphElement
param Parameter for none object; template empty globals; name; HTMLParamElement
object value
flow; phrasing; source*; one img;
picture Image embedded phrasing script-supporting globals HTMLPictureElement
elements
Block of
pre preformatted flow flow phrasing globals HTMLPreElement
text
progress Progress bar flow; phrasing; phrasing phrasing* globals; value; HTMLProgressElement
labelable max
q Quotation flow; phrasing phrasing phrasing globals; cite HTMLQuoteElement
rb Ruby base none ruby; template phrasing globals HTMLElement
Parenthesis for ruby; rtc;
rp ruby annotation none template phrasing globals HTMLElement
text
rt Ruby annotation none ruby; rtc; phrasing globals HTMLElement
text template
rtc Ruby annotation none ruby; template phrasing globals HTMLElement
text container
ruby Ruby flow; phrasing phrasing phrasing; rp; rt; globals HTMLElement
annotation(s) rb; rtc*
s Inaccurate text flow; phrasing phrasing phrasing globals HTMLElement
samp Computer output flow; phrasing phrasing phrasing globals HTMLElement
metadata; flow; head; phrasing; script, data, or globals; src;
script Embedded script phrasing; script-supporting script type; charset; HTMLScriptElement
script-supporting elements documentation* async; defer;
elements crossorigin nonce
Generic document
section or application flow; sectioning flow flow globals HTMLElement
section
flow; phrasing;
interactive; globals;
listed; option; optgroup; autocomplete;
select List box control labelable; phrasing script-supporting autofocus; HTMLSelectElement
submittable; elements disabled; form;
resettable; multiple; name;
reassociateable; required; size
form-associated
small Side comment flow; phrasing phrasing phrasing globals HTMLElement
Media source for
video or audio video; audio; globals; src;
source or as image none template; picture empty type; srcset; HTMLSourceElement
source for sizes; media
picture
span Generic phrasing flow; phrasing phrasing phrasing globals HTMLSpanElement
container
strong Importance flow; phrasing phrasing phrasing globals HTMLElement
style Embedded styling metadata; flow* head; noscript*; varies* globals; media; HTMLStyleElement
information flow* nonce; type
sub Subscript flow; phrasing phrasing phrasing globals HTMLElement
summary Caption for none details phrasing globals HTMLElement
details
sup Superscript flow; phrasing phrasing phrasing globals HTMLElement
caption*;
colgroup*;
table Table flow flow thead*; tbody*; globals; border HTMLTableElement
tfoot*; tr*;
script-supporting
elements
Group of rows in tr;
tbody a table none table; template script-supporting globals HTMLTableSectionElement
elements
td Table cell sectioning root tr; template flow globals; colspan; HTMLTableDataCellElement
rowspan; headers
metadata; flow; metadata;
phrasing; phrasing;
template Template script-supporting script-supporting it’s complicated* globals HTMLTemplateElement
elements elements;
colgroup*
globals;
flow; phrasing; autofocus; cols;
interactive; dirname;
listed; disabled; form;
textarea Multiline text labelable; phrasing text maxlength; HTMLTextAreaElement
field submittable; minlength; name;
resettable; placeholder;
reassociateable; readonly;
form-associated required; rows;
wrap
Group of footer tr;
tfoot rows in a table none table; template script-supporting globals HTMLTableSectionElement
elements
Table header globals; colspan;
th cell interactive* tr; template flow* rowspan; headers; HTMLTableHeaderCellElement
scope; abbr
Group of heading tr;
thead rows in a table none table; template script-supporting globals HTMLTableSectionElement
elements
Machine-readable
equivalent of
time date- or flow; phrasing phrasing phrasing globals; datetime HTMLTimeElement
time-related
data
title Document title metadata head; template text* globals HTMLTitleElement
table; thead; th*; td;
tr Table row none tbody; tfoot; script-supporting globals HTMLTableRowElement
template elements
audio; video; globals; default;
track Timed text track none template empty kind; label; src; HTMLTrackElement
srclang
u Keywords flow; phrasing phrasing phrasing globals HTMLElement
li;
ul List flow flow script-supporting globals HTMLUListElement
elements
var Variable flow; phrasing phrasing phrasing globals HTMLElement
globals; src;
flow; phrasing; crossorigin;
video Video player embedded; phrasing source*; poster; preload; HTMLVideoElement
interactive transparent* autoplay; loop;
muted; controls;
width; height
wbr Line breaking flow; phrasing phrasing empty globals HTMLElement
opportunity
An asterisk (*) in a cell indicates that the actual rules are more
complicated than indicated in the table above.
† Categories in the "Parents" column refer to parents that list the given
categories in their content model, not to elements that themselves are in
those categories. For example, the a element’s "Parents" column says
"phrasing", so any element whose content model contains the "phrasing"
category could be a parent of an a element. Since the "flow" category
includes all the "phrasing" elements, that means the th element could be a
parent to an a element.
Element content categories
This section is non-normative.
List of element content categories
Category Elements Elements with exceptions
base; link; meta; noscript;
Metadata content script; style; template; —
title
a; abbr; address; article;
aside; audio; b; bdi; bdo;
blockquote; br; button;
canvas; cite; code; data;
datalist; del; details;
dfn; dialog; div; dl; em;
embed; fieldset; figure;
footer; form; h1; h2; h3;
h4; h5; h6; header; hr; i; area (if it is a
Flow content iframe; img; input; ins; descendant of a map
kbd; label; main; map; element); link (if it is
mark; math; meter; nav; allowed in the body);
noscript; object; ol;
output; p; pre; progress;
q; ruby; s; samp; script;
section; select; small;
span; strong; sub; sup;
svg; table; template;
textarea; time; u; ul; var;
video; wbr; Text
Sectioning content article; aside; nav; —
section
Heading content h1; h2; h3; h4; h5; h6; —
a; abbr; audio; b; bdi;
bdo; br; button; canvas;
cite; code; data; datalist;
del; dfn; em; embed; i;
iframe; img; input; ins; area (if it is a
kbd; label; map; mark; descendant of a map
Phrasing content math; meter; noscript; element); link (if it is
object; output; progress; allowed in the body);
q; ruby; s; samp; script;
select; small; span;
strong; sub; sup; svg;
template; textarea; time;
u; var; video; wbr; Text
audio; canvas; embed;
Embedded content iframe; img; math; object; —
svg; video
a (if the href attribute
is present); audio (if
the controls attribute
button; details; embed; is present); img (if the
Interactive content* iframe; label; select; usemap attribute is
textarea present); input (if the
type attribute is not in
the Hidden state); video
(if the controls
attribute is present)
blockquote; body; details;
Sectioning roots dialog; fieldset; figure; —
td
Form-associated button; fieldset; input;
elements label; object; output; —
select; textarea; img
button; fieldset; input;
Listed elements object; output; select; —
textarea
Submittable elements button; input; object; —
select; textarea
Resettable elements input; output; select; —
textarea
button; input; meter;
Labelable elements output; progress; select; —
textarea
Reassociateable button; fieldset; input;
elements label; object; output; —
select; textarea
a; abbr; address; article; audio (if the controls
aside; b; bdi; bdo; attribute is present);
blockquote; button; canvas; dl (if the element’s
cite; code; data; details; children include at
dfn; div; em; embed; least one name-value
fieldset; figure; footer; group); input (if the
form; h1; h2; h3; h4; h5; type attribute is not in
h6; header; i; iframe; img; the Hidden state); ol
Palpable content ins; kbd; label; main; map; (if the element’s
mark; math; meter; nav; children include at
object; output; p; pre; least one li element);
progress; q; ruby; s; samp; ul (if the element’s
section; select; small; children include at
span; strong; sub; sup; least one li element);
svg; table; textarea; time; Text that is not
u; var; video inter-element white
space
Script-supporting script; template —
elements
* The tabindex attribute can also make any element into interactive
content.
Attributes
This section is non-normative.
List of attributes (excluding event handler content attributes)
Attribute Element(s) Description Value
Alternative label
to use for the
abbr th header cell when Text*
referencing the
cell in other
contexts
Hint for expected Set of comma-separated tokens*
accept input file type in File consisting of valid MIME types with
Upload controls no parameters or audio/*, video/*,
or image/*
Ordered set of unique
Character encodings space-separated tokens, ASCII
accept-charset form to use for form case-insensitive, consisting of
submission labels of ASCII-compatible
encodings*
Keyboard shortcut Ordered set of unique
accesskey HTML to activate or space-separated tokens,
elements focus element case-sensitive, consisting of one
Unicode code point in length
action form URL to use for form Valid non-empty URL potentially
submission surrounded by spaces
Whether to allow
allowfullscreen iframe the iframe's Boolean attribute
contents to use
requestFullscreen()
Whether to allow
the iframe's
browsing context to
allowpaymentrequest iframe use the Boolean attribute
PaymentRequest
interface to make
payment requests.
area; img; Replacement text
alt input for use when images Text*
are not available
async script Execute script Boolean attribute
asynchronously
Default setting for
autocomplete form autofill feature "on"; "off"
for controls in the
form
input; Hint for form Autofill field name and related
autocomplete select; autofill feature tokens*
textarea
button; Automatically focus
autofocus input; the form control Boolean attribute
select; when the page is
textarea loaded
Hint that the media
audio; resource can be
autoplay video started Boolean attribute
automatically when
the page is loaded
Explicit indication
that the table
border table element is not The empty string, or "1"
being used for
layout purposes
charset meta Character encoding Encoding label*
declaration
Character encoding
charset script of the external Encoding label*
script resource
Whether the command
checked input or control is Boolean attribute
checked
Link to the source
cite blockquote; of the quotation or Valid URL potentially surrounded by
del; ins; q more information spaces
about the edit
class HTML Classes to which Set of space-separated tokens
elements the element belongs
cols textarea Maximum number of Valid non-negative integer greater
characters per line than zero
Number of columns Valid non-negative integer greater
colspan td; th that the cell is to than zero
span
content meta Value of the Text*
element
contenteditable HTML Whether the element "true"; "false"
elements is editable
controls audio; Show user agent Boolean attribute
video controls
Coordinates for the Valid list of floating-point
coords area shape to be created numbers*
in an image map
audio; img; How the element
crossorigin link; handles crossorigin "anonymous"; "use-credentials"
script; requests
video
data object Address of the Valid non-empty URL potentially
resource surrounded by spaces
Date and
datetime del; ins (optionally) time Valid date string with optional time
of the change
Valid month string, valid date
string, valid yearless date string,
valid time string, valid floating
datetime time Machine-readable date and time string, valid
value time-zone offset string, valid
global date and time string, valid
week string, valid non-negative
integer, or valid duration string
Enable the track if
default track no other text track Boolean attribute
is more suitable
defer script Defer script Boolean attribute
execution
HTML The text
dir elements directionality of "ltr"; "rtl"; "auto"
the element
The text
dir bdo directionality of "ltr"; "rtl"
the element
Name of form field
input; to use for sending
dirname textarea the element’s Text*
directionality in
form submission
button;
fieldset;
input; Whether the form
disabled optgroup; control is disabled Boolean attribute
option;
select;
textarea
Whether to download
the resource
download a; area instead of Text
navigating to it,
and its file name
if so
draggable HTML Whether the element "true"; "false"
elements is draggable
Form data set
enctype form encoding type to "application/x-www-form-urlencoded";
use for form "multipart/form-data"; "text/plain"
submission
for label Associate the label ID*
with form control
Specifies controls Unordered set of unique
for output from which the space-separated tokens,
output was case-sensitive, consisting of IDs*
calculated
button;
fieldset;
input; Associates the
form label; control with a form ID*
object; element
output;
select;
textarea
formaction button; URL to use for form Valid non-empty URL potentially
input submission surrounded by spaces
Form data set
formenctype button; encoding type to "application/x-www-form-urlencoded";
input use for form "multipart/form-data"; "text/plain"
submission
formmethod button; HTTP method to use "GET"; "POST"
input for form submission
button; Bypass form control
formnovalidate input validation for form Boolean attribute
submission
formtarget button; Browsing context Valid browsing context name or
input for form submission keyword
The header cells Unordered set of unique
headers td; th for this cell space-separated tokens,
case-sensitive, consisting of IDs*
canvas;
embed;
height iframe; Vertical dimension Valid non-negative integer
img; input;
object;
video
hidden HTML Whether the element Boolean attribute
elements is relevant
high meter Low limit of high Valid floating-point number*
range
href a; area Address of the Valid URL potentially surrounded by
hyperlink spaces
href link Address of the Valid non-empty URL potentially
hyperlink surrounded by spaces
href base Document base URL Valid URL potentially surrounded by
spaces
hreflang a; area; Language of the Valid BCP 47 language tag
link linked resource
http-equiv meta Pragma directive Text*
id HTML The element’s ID Text*
elements
Whether the image
ismap img is a server-side Boolean attribute
image map
The type of text "subtitles"; "captions";
kind track track "descriptions"; "chapters";
"metadata"
optgroup;
label option; User-visible label Text
track
lang HTML Language of the Valid BCP 47 language tag or the
elements element empty string
List of
list input autocomplete ID*
options
A link to a fuller Valid non-empty URL potentially
longdesc img description of the surrounded by spaces
image
loop audio; Whether to loop the Boolean attribute
video media resource
low meter High limit of low Valid floating-point number*
range
manifest html Application cache a valid non-empty URL potentially
manifest surrounded by spaces
max input Maximum value Varies*
max meter; Upper bound of Valid floating-point number*
progress range
maxlength input; Maximum length of Valid non-negative integer
textarea value
media link; style Applicable media Valid media query list
method form HTTP method to use "get"; "post"; "dialog"
for form submission
min input Minimum value Varies*
min meter Lower bound of Valid floating-point number*
range
minlength input; Minimum length of Valid non-negative integer
textarea value
multiple input; Whether to allow Boolean attribute
select multiple values
audio; Whether to mute the
muted video media resource by Boolean attribute
default
button; Name of form
fieldset; control to use for
name input; form submission and Text*
output; in the
select; form.elements API
textarea
Name of form to use
name form in the Text*
document.forms API
name iframe; Name of nested Valid browsing context name or
object browsing context keyword
Name of image map
name map to reference from Text*
the usemap
attribute
name meta Metadata name Text*
name param Name of parameter Text
link; Cryptographic nonce
nonce script; used in Content Text
style Security Policy
checks [CSP3]
Bypass form control
novalidate form validation for form Boolean attribute
submission
open details Whether the details Boolean attribute
are visible
open dialog Whether the dialog Boolean attribute
box is showing
optimum meter Optimum value in Valid floating-point number*
gauge
Pattern to be Regular expression matching the
pattern input matched by the form JavaScript Pattern production
control’s value
input; User-visible label
placeholder textarea to be placed within Text*
the form control
Poster frame to Valid non-empty URL potentially
poster video show prior to video surrounded by spaces
playback
Hints how much
preload audio; buffering the media "none"; "metadata"; "auto"
video resource will
likely need
input; Whether to allow
readonly textarea the value to be Boolean attribute
edited by the user
a; area; Referrer policy for
referrerpolicy iframe; fetches initiated Referrer policy
img; link by the element
Relationship of
a; area; this document (or
rel link subsection/topic) Set of space-separated tokens*
to the destination
resource
input; Whether the control
required select; is required for Boolean attribute
textarea form submission
Reverse link
relationship of the
rev a; link destination Set of space-separated tokens
resource to this
document (or
subsection/topic)
reversed ol Number the list Boolean attribute
backwards
rows textarea Number of lines to Valid non-negative integer greater
show than zero
rowspan td; th Number of rows that Valid non-negative integer
the cell is to span
Unordered set of unique
space-separated tokens, ASCII
case-insensitive, consisting of
sandbox iframe Security rules for "allow-forms", "allow-pointer-lock",
nested content "allow-popups",
"allow-presentation",
"allow-same-origin", "allow-scripts
and "allow-top-navigation"
Specifies which
scope th cells the header "row"; "col"; "rowgroup"; "colgroup"
cell applies to
Whether the option
selected option is selected by Boolean attribute
default
The kind of shape
shape area to be created in an "circle"; "default"; "poly"; "rect"
image map
size input; Size of the control Valid non-negative integer greater
select than zero
Unordered set of unique
sizes link Sizes of the icons space-separated tokens, ASCII
(for rel="icon") case-insensitive, consisting of
sizes*
Image sizes for
sizes img; source different page Valid source size list
layouts
col; Number of columns Valid non-negative integer greater
span colgroup spanned by the than zero
element
Whether the element
spellcheck HTML is to have its "true"; "false"
elements spelling and
grammar checked
audio;
embed;
iframe;
src img; input; Address of the Valid non-empty URL potentially
script; resource surrounded by spaces
source;
track;
video
A document to The source of an iframe srcdoc
srcdoc iframe render in the document*
iframe
srclang track Language of the Valid BCP 47 language tag
text track
Images to use in
different
srcset img; source situations (e.g., Comma-separated list of image
high-resolution candidate strings
displays, small
monitors, etc)
start ol Ordinal value of Valid integer
the first item
Granularity to be Valid floating-point number greater
step input matched by the form than zero, or "any"
control’s value
HTML Presentational and
style elements formatting CSS declarations*
instructions
Whether the element
is focusable, and
HTML the relative order
tabindex elements of the element for Valid integer
the purposes of
sequential focus
navigation
Browsing context Valid browsing context name or
target a; area for hyperlink keyword
navigation
Default browsing
context for Valid browsing context name or
target base hyperlink keyword
navigation and form
submission
target form Browsing context Valid browsing context name or
for form submission keyword
HTML Advisory
title elements information for the Text
element
Full term or
title abbr; dfn expansion of Text
abbreviation
Description of
title input pattern (when used Text
with pattern
attribute)
title link Title of the link Text
title link; style Alternative style Text
sheet set name
Whether the element
translate HTML is to be translated "yes"; "no"
elements when the page is
localized
a; area; Hint for the type
type link of the referenced Valid MIME type
resource
type button Type of button "submit"; "reset"; "button"
embed;
object; Type of embedded
type script; resource Valid MIME type
source;
style
type input Type of form input type keyword
control
type ol Kind of list marker "1"; "a"; "A"; "i"; "I"
Whether the type
attribute and the
typemustmatch object Content-Type value Boolean attribute
need to match for
the resource to be
used
usemap img Name of image map Valid hash-name reference*
to use
value button; Value to be used Text
option for form submission
value data Machine-readable Text*
value
value input Value of the form Varies*
control
value li Ordinal value of Valid integer
the list item
value meter; Current value of Valid floating-point number
progress the element
value param Value of parameter Text
canvas;
embed;
width iframe; Horizontal Valid non-negative integer
img; input; dimension
object;
video
How the value of
wrap textarea the form control is "soft"; "hard"
to be wrapped for
form submission
An asterisk (*) in a cell indicates that the actual rules are more
complicated than indicated in the table above.
----------------------------------------------------------------------
List of event handler content attributes
Attribute Element(s) Description Value
onabort HTML elements abort event handler Event handler
content attribute
onafterprint body afterprint event handler Event handler
for Window object content attribute
onbeforeprint body beforeprint event handler Event handler
for Window object content attribute
onbeforeunload body beforeunload event Event handler
handler for Window object content attribute
onblur HTML elements blur event handler Event handler
content attribute
oncancel HTML elements cancel event handler Event handler
content attribute
oncanplay HTML elements canplay event handler Event handler
content attribute
oncanplaythrough HTML elements canplaythrough event Event handler
handler content attribute
onchange HTML elements change event handler Event handler
content attribute
onclick HTML elements click event handler Event handler
content attribute
onclose HTML elements close event handler Event handler
content attribute
oncopy HTML elements copy event handler Event handler
content attribute
oncuechange HTML elements cuechange event handler Event handler
content attribute
oncut HTML elements cut event handler Event handler
content attribute
ondblclick HTML elements dblclick event handler Event handler
content attribute
ondrag HTML elements drag event handler Event handler
content attribute
ondragend HTML elements dragend event handler Event handler
content attribute
ondragenter HTML elements dragenter event handler Event handler
content attribute
ondragexit HTML elements dragexit event handler Event handler
content attribute
ondragleave HTML elements dragleave event handler Event handler
content attribute
ondragover HTML elements dragover event handler Event handler
content attribute
ondragstart HTML elements dragstart event handler Event handler
content attribute
ondrop HTML elements drop event handler Event handler
content attribute
ondurationchange HTML elements durationchange event Event handler
handler content attribute
onended HTML elements ended event handler Event handler
content attribute
onerror HTML elements error event handler Event handler
content attribute
onfocus HTML elements focus event handler Event handler
content attribute
onhashchange body hashchange event handler Event handler
for Window object content attribute
oninput HTML elements input event handler Event handler
content attribute
oninvalid HTML elements invalid event handler Event handler
content attribute
onkeydown HTML elements keydown event handler Event handler
content attribute
onkeypress HTML elements keypress event handler Event handler
content attribute
onkeyup HTML elements keyup event handler Event handler
content attribute
onlanguagechange body languagechange event Event handler
handler for Window object content attribute
onload HTML elements load event handler Event handler
content attribute
onloadeddata HTML elements loadeddata event handler Event handler
content attribute
onloadedmetadata HTML elements loadedmetadata event Event handler
handler content attribute
onloadstart HTML elements loadstart event handler Event handler
content attribute
onmessage body message event handler for Event handler
Window object content attribute
onmousedown HTML elements mousedown event handler Event handler
content attribute
onmouseenter HTML elements mouseenter event handler Event handler
content attribute
onmouseleave HTML elements mouseleave event handler Event handler
content attribute
onmousemove HTML elements mousemove event handler Event handler
content attribute
onmouseout HTML elements mouseout event handler Event handler
content attribute
onmouseover HTML elements mouseover event handler Event handler
content attribute
onmouseup HTML elements mouseup event handler Event handler
content attribute
onwheel HTML elements wheel event handler Event handler
content attribute
onoffline body offline event handler for Event handler
Window object content attribute
ononline body online event handler for Event handler
Window object content attribute
onpagehide body pagehide event handler Event handler
for Window object content attribute
onpageshow body pageshow event handler Event handler
for Window object content attribute
onpaste HTML elements paste event handler Event handler
content attribute
onpause HTML elements pause event handler Event handler
content attribute
onplay HTML elements play event handler Event handler
content attribute
onplaying HTML elements playing event handler Event handler
content attribute
onpopstate body popstate event handler Event handler
for Window object content attribute
onprogress HTML elements progress event handler Event handler
content attribute
onratechange HTML elements ratechange event handler Event handler
content attribute
onreset HTML elements reset event handler Event handler
content attribute
onresize HTML elements resize event handler Event handler
content attribute
onscroll HTML elements scroll event handler Event handler
content attribute
onseeked HTML elements seeked event handler Event handler
content attribute
onseeking HTML elements seeking event handler Event handler
content attribute
onselect HTML elements select event handler Event handler
content attribute
onshow HTML elements show event handler Event handler
content attribute
onstalled HTML elements stalled event handler Event handler
content attribute
onstorage body storage event handler for Event handler
Window object content attribute
onsubmit HTML elements submit event handler Event handler
content attribute
onsuspend HTML elements suspend event handler Event handler
content attribute
ontimeupdate HTML elements timeupdate event handler Event handler
content attribute
ontoggle HTML elements toggle event handler Event handler
content attribute
onunload body unload event handler for Event handler
Window object content attribute
onvolumechange HTML elements volumechange event Event handler
handler content attribute
onwaiting HTML elements waiting event handler Event handler
content attribute
Element Interfaces
This section is non-normative.
List of interfaces for elements
Element(s) Interface(s)
a HTMLAnchorElement : HTMLElement
abbr HTMLElement
address HTMLElement
area HTMLAreaElement : HTMLElement
article HTMLElement
aside HTMLElement
audio HTMLAudioElement : HTMLMediaElement : HTMLElement
b HTMLElement
base HTMLBaseElement : HTMLElement
bdi HTMLElement
bdo HTMLElement
blockquote HTMLQuoteElement : HTMLElement
body HTMLBodyElement : HTMLElement
br HTMLBRElement : HTMLElement
button HTMLButtonElement : HTMLElement
canvas HTMLCanvasElement : HTMLElement
caption HTMLTableCaptionElement : HTMLElement
cite HTMLElement
code HTMLElement
col HTMLTableColElement : HTMLElement
colgroup HTMLTableColElement : HTMLElement
data HTMLDataElement : HTMLElement
datalist HTMLDataListElement : HTMLElement
dd HTMLElement
del HTMLModElement : HTMLElement
details HTMLDetailsElement : HTMLElement
dfn HTMLElement
dialog HTMLDialogElement : HTMLElement
div HTMLDivElement : HTMLElement
dl HTMLDListElement : HTMLElement
dt HTMLElement
em HTMLElement
embed HTMLEmbedElement : HTMLElement
fieldset HTMLFieldSetElement : HTMLElement
figcaption HTMLElement
figure HTMLElement
footer HTMLElement
form HTMLFormElement : HTMLElement
h1 HTMLHeadingElement : HTMLElement
h2 HTMLHeadingElement : HTMLElement
h3 HTMLHeadingElement : HTMLElement
h4 HTMLHeadingElement : HTMLElement
h5 HTMLHeadingElement : HTMLElement
h6 HTMLHeadingElement : HTMLElement
head HTMLHeadElement : HTMLElement
header HTMLElement
hr HTMLHRElement : HTMLElement
html HTMLHtmlElement : HTMLElement
i HTMLElement
iframe HTMLIFrameElement : HTMLElement
img HTMLImageElement : HTMLElement
input HTMLInputElement : HTMLElement
ins HTMLModElement : HTMLElement
kbd HTMLElement
label HTMLLabelElement : HTMLElement
legend HTMLLegendElement : HTMLElement
li HTMLLIElement : HTMLElement
link HTMLLinkElement : HTMLElement
main HTMLElement
map HTMLMapElement : HTMLElement
mark HTMLElement
meta HTMLMetaElement : HTMLElement
meter HTMLMeterElement : HTMLElement
nav HTMLElement
noscript HTMLElement
object HTMLObjectElement : HTMLElement
ol HTMLOListElement : HTMLElement
optgroup HTMLOptGroupElement : HTMLElement
option HTMLOptionElement : HTMLElement
output HTMLOutputElement : HTMLElement
p HTMLParagraphElement : HTMLElement
param HTMLParamElement : HTMLElement
picture HTMLPictureElement : HTMLElement
pre HTMLPreElement : HTMLElement
progress HTMLProgressElement : HTMLElement
q HTMLQuoteElement : HTMLElement
rb HTMLElement
rp HTMLElement
rt HTMLElement
rtc HTMLElement
ruby HTMLElement
s HTMLElement
samp HTMLElement
script HTMLScriptElement : HTMLElement
section HTMLElement
select HTMLSelectElement : HTMLElement
small HTMLElement
source HTMLSourceElement : HTMLElement
span HTMLSpanElement : HTMLElement
strong HTMLElement
style HTMLStyleElement : HTMLElement
sub HTMLElement
summary HTMLElement
sup HTMLElement
table HTMLTableElement : HTMLElement
tbody HTMLTableSectionElement : HTMLElement
td HTMLTableDataCellElement : HTMLTableCellElement : HTMLElement
template HTMLTemplateElement : HTMLElement
textarea HTMLTextAreaElement : HTMLElement
tfoot HTMLTableSectionElement : HTMLElement
th HTMLTableHeaderCellElement : HTMLTableCellElement : HTMLElement
thead HTMLTableSectionElement : HTMLElement
time HTMLTimeElement : HTMLElement
title HTMLTitleElement : HTMLElement
tr HTMLTableRowElement : HTMLElement
track HTMLTrackElement : HTMLElement
u HTMLElement
ul HTMLUListElement : HTMLElement
var HTMLElement
video HTMLVideoElement : HTMLMediaElement : HTMLElement
wbr HTMLElement
Events
This section is non-normative.
List of events
Event Interface Interesting targets Description
Fired at the
Window when the
abort Event Window download was
aborted by the
user
Fired at the
DOMContentLoaded Event Document Document once the
parser has
finished
Fired at the
afterprint Event Window Window after
printing
Fired at script
elements after the
afterscriptexecute Event script elements script runs (just
before the
corresponding load
event)
Fired at the
beforeprint Event Window Window before
printing
Fired at script
elements just
before the script
beforescriptexecute Event script elements runs; canceling
the event cancels
the running of the
script
Fired at the
Window when the
page is about to
beforeunload BeforeUnloadEvent Window be unloaded, in
case the page
would like to show
a warning prompt
blur Event Window, elements Fired at nodes
losing focus
Fired at dialog
elements when they
cancel Event dialog elements are canceled by
the user (e.g., by
pressing the
Escape key)
Fired at controls
when the user
change Event Form controls commits a value
change (see also
the input event)
Normally a mouse
event; also
synthetically
fired at an
element before its
click MouseEvent Elements activation
behavior is run,
when an element is
activated from a
non-pointer input
device (e.g., a
keyboard)
Fired at dialog
elements when they
are closed, and at
close Event dialog elements, WebSocket WebSocket elements
when the
connection is
terminated
Fired at elements
copy Event Elements when the user
copies data to the
clipboard
Fired at elements
when the user
copies the
cut Event Elements selected data on
the clipboard and
removes the
selection from the
document
Fired when
Global scope objects, unexpected errors
error Event Worker objects, elements, occur (e.g.,
networking-related objects networking errors,
script errors,
decoding errors)
focus Event Window, elements Fired at nodes
gaining focus
Fired at the
Window when the
hashchange HashChangeEvent Window fragment part of
the document’s URL
changes
Fired at controls
when the user
input Event Form controls changes the value
(see also the
change event)
Fired at controls
during form
invalid Event Form controls validation if they
do not satisfy
their constraints
Fired at the
global scope
languagechange Event Global scope objects object when the
user’s preferred
languages change
Fired at the
Window when the
document has
finished loading;
load Event Window, elements fired at an
element containing
a resource (e.g.,
img, embed) when
its resource has
finished loading
Fired at img
Event or elements after a
loadend ProgressEvent img elements successful load
(see also media
element events)
Fired at img
elements when a
loadstart ProgressEvent img elements load begins (see
also media element
events)
Window, EventSource,
WebSocket, MessagePort, Fired at an object
message MessageEvent BroadcastChannel, when it receives a
DedicatedWorkerGlobalScope, message
Worker
Fired at the
global scope
offline Event Global scope objects object when the
network
connections fails
Fired at the
global scope
online Event Global scope objects object when the
network
connections
returns
Fired at
networking-related
open Event EventSource, WebSocket objects when a
connection is
established
Fired at the
Window when the
page’s entry in
pagehide PageTransitionEvent Window the session
history stops
being the current
entry
Fired at the
Window when the
pageshow PageTransitionEvent Window page’s entry in
the session
history becomes
the current entry
Fired at elements
when the user will
insert the
paste Event Elements clipboard data in
the most suitable
format (if any)
supported for the
given context
Fired at the
popstate PopStateEvent Window Window when the
user navigates the
session history
Fired at img
elements during a
progress ProgressEvent img elements CORS-same-origin
image load (see
also media element
events)
Fired at the
Document when it
finishes parsing
readystatechange Event Document and again when all
its subresources
have finished
loading
Fired at a form
reset Event form elements element when it is
reset
Fired at form
controls when
their text
select Event Form controls selection is
adjusted (whether
by an API or by
the user)
Fired at Window
event when the
corresponding
storage StorageEvent Window localStorage or
sessionStorage
storage areas
change
Fired at a form
submit Event form elements element when it is
submitted
Fired at details
toggle Event details element elements when they
open or close
Fired at the
unload Event Window Window object when
the page is going
away
See also media element events and drag-and-drop events.
Property Index
Name Value Initial Applies Inh. %ages Media Animatable Canonical Computed
to order value
refer The specified
to value, but
width with any
[ none | all or per lengths
anchor-point <position> none elements no height visual no grammar replaced by
] of their
box; corresponding
see absolute
prose length
IDL Index
[LegacyUnenumerableNamedProperties]
interface HTMLAllCollection {
readonly attribute unsigned long length;
getter Element? (unsigned long index);
getter (HTMLCollection or Element)? namedItem(DOMString name);
legacycaller (HTMLCollection or Element)? item(optional DOMString nameOrItem);
};
interface HTMLFormControlsCollection : HTMLCollection {
// inherits length and item()
getter (RadioNodeList or Element)? namedItem(DOMString name); // shadows inherited namedItem()
};
interface RadioNodeList : NodeList {
attribute DOMString value;
};
interface HTMLOptionsCollection : HTMLCollection {
// inherits item(), namedItem()
attribute unsigned long length; // shadows inherited length
setter void (unsigned long index, HTMLOptionElement? option);
void add((HTMLOptionElement or HTMLOptGroupElement) element, optional (HTMLElement or long)? before = null);
void remove(long index);
attribute long selectedIndex;
};
interface DOMStringList {
readonly attribute unsigned long length;
getter DOMString? item(unsigned long index);
boolean contains(DOMString string);
};
enum DocumentReadyState { "loading", "interactive", "complete" };
typedef (HTMLScriptElement or SVGScriptElement) HTMLOrSVGScriptElement;
[OverrideBuiltins]
partial interface Document {
// resource metadata management
[PutForwards=href, Unforgeable] readonly attribute Location? location;
attribute USVString domain;
readonly attribute USVString referrer;
attribute USVString cookie;
readonly attribute DOMString lastModified;
readonly attribute DocumentReadyState readyState;
// DOM tree accessors
getter object (DOMString name);
[CEReactions] attribute DOMString title;
attribute DOMString dir;
attribute HTMLElement? body;
readonly attribute HTMLHeadElement? head;
[SameObject] readonly attribute HTMLCollection images;
[SameObject] readonly attribute HTMLCollection embeds;
[SameObject] readonly attribute HTMLCollection plugins;
[SameObject] readonly attribute HTMLCollection links;
[SameObject] readonly attribute HTMLCollection forms;
[SameObject] readonly attribute HTMLCollection scripts;
NodeList getElementsByName(DOMString elementName);
readonly attribute HTMLOrSVGScriptElement? currentScript; // classic scripts in a document tree only
// dynamic markup insertion
Document open(optional DOMString type = "text/html", optional DOMString replace = "");
WindowProxy open(DOMString url, DOMString name, DOMString features, optional boolean replace = false);
[CEReactions] void close();
[CEReactions] void write(DOMString... text);
[CEReactions] void writeln(DOMString... text);
// user interaction
readonly attribute WindowProxy? defaultView;
readonly attribute Element? activeElement;
boolean hasFocus();
[CEReactions] attribute DOMString designMode;
[CEReactions] boolean execCommand(DOMString commandId, optional boolean showUI = false, optional DOMString value = "");
boolean queryCommandEnabled(DOMString commandId);
boolean queryCommandIndeterm(DOMString commandId);
boolean queryCommandState(DOMString commandId);
boolean queryCommandSupported(DOMString commandId);
DOMString queryCommandValue(DOMString commandId);
// special event handler IDL attributes that only apply to Document objects
[LenientThis] attribute EventHandler onreadystatechange;
};
Document implements GlobalEventHandlers;
Document implements DocumentAndElementEventHandlers;
[HTMLConstructor]
interface HTMLElement : Element {
// metadata attributes
[CEReactions] attribute DOMString title;
[CEReactions] attribute DOMString lang;
[CEReactions] attribute boolean translate;
[CEReactions] attribute DOMString dir;
[SameObject] readonly attribute DOMStringMap dataset;
// user interaction
[CEReactions] attribute boolean hidden;
void click();
[CEReactions] attribute long tabIndex;
void focus();
void blur();
[CEReactions] attribute DOMString accessKey;
[CEReactions] attribute boolean draggable;
[CEReactions] attribute boolean spellcheck;
void forceSpellCheck();
[CEReactions, TreatNullAs=EmptyString] attribute DOMString innerText;
};
HTMLElement implements GlobalEventHandlers;
HTMLElement implements DocumentAndElementEventHandlers;
HTMLElement implements ElementContentEditable;
// Note: intentionally not [HTMLConstructor]
interface HTMLUnknownElement : HTMLElement { };
[OverrideBuiltins]
interface DOMStringMap {
getter DOMString (DOMString name);
[CEReactions] setter void (DOMString name, DOMString value);
[CEReactions] deleter void (DOMString name);
};
interface HTMLHtmlElement : HTMLElement {};
interface HTMLHeadElement : HTMLElement {};
interface HTMLTitleElement : HTMLElement {
attribute DOMString text;
};
interface HTMLBaseElement : HTMLElement {
attribute DOMString href;
attribute DOMString target;
};
interface HTMLLinkElement : HTMLElement {
[CEReactions] attribute USVString href;
[CEReactions] attribute DOMString? crossOrigin;
[CEReactions] attribute DOMString rel;
[CEReactions] attribute DOMString rev;
[CEReactions, SameObject, PutForwards=value] readonly attribute DOMTokenList relList;
[CEReactions] attribute DOMString media;
[CEReactions] attribute DOMString nonce;
[CEReactions] attribute DOMString hreflang;
[CEReactions] attribute DOMString type;
[CEReactions, SameObject, PutForwards=value] readonly attribute DOMTokenList sizes;
[CEReactions] attribute DOMString referrerPolicy;
};
HTMLLinkElement implements LinkStyle;
interface HTMLMetaElement : HTMLElement {
attribute DOMString name;
attribute DOMString httpEquiv;
attribute DOMString content;
};
interface HTMLStyleElement : HTMLElement {
attribute DOMString media;
attribute DOMString nonce;
attribute DOMString type;
};
HTMLStyleElement implements LinkStyle;
interface HTMLBodyElement : HTMLElement {
};
HTMLBodyElement implements WindowEventHandlers;
interface HTMLHeadingElement : HTMLElement {};
interface HTMLParagraphElement : HTMLElement {};
interface HTMLHRElement : HTMLElement {};
interface HTMLPreElement : HTMLElement {};
interface HTMLQuoteElement : HTMLElement {
attribute DOMString cite;
};
interface HTMLOListElement : HTMLElement {
attribute boolean reversed;
attribute long start;
attribute DOMString type;
};
interface HTMLUListElement : HTMLElement {};
interface HTMLLIElement : HTMLElement {
attribute long value;
};
interface HTMLDListElement : HTMLElement {};
interface HTMLDivElement : HTMLElement {};
interface HTMLAnchorElement : HTMLElement {
attribute DOMString target;
attribute DOMString download;
attribute DOMString rel;
attribute DOMString rev;
[SameObject, PutForwards=value] readonly attribute DOMTokenList relList;
attribute DOMString hreflang;
attribute DOMString type;
attribute DOMString text;
attribute DOMString referrerPolicy;
};
HTMLAnchorElement implements HTMLHyperlinkElementUtils;
interface HTMLDataElement : HTMLElement {
attribute DOMString value;
};
interface HTMLTimeElement : HTMLElement {
attribute DOMString dateTime;
};
interface HTMLSpanElement : HTMLElement {};
interface HTMLBRElement : HTMLElement {};
interface HTMLModElement : HTMLElement {
attribute DOMString cite;
attribute DOMString dateTime;
};
interface HTMLPictureElement : HTMLElement {};
interface HTMLSourceElement : HTMLElement {
attribute DOMString src;
attribute DOMString type;
attribute DOMString srcset;
attribute DOMString sizes;
attribute DOMString media;
};
[NamedConstructor=Image(optional unsigned long width, optional unsigned long height)]
interface HTMLImageElement : HTMLElement {
attribute DOMString alt;
attribute DOMString src;
attribute DOMString srcset;
attribute DOMString sizes;
attribute DOMString? crossOrigin;
attribute DOMString useMap;
attribute DOMString longDesc;
attribute boolean isMap;
attribute unsigned long width;
attribute unsigned long height;
readonly attribute unsigned long naturalWidth;
readonly attribute unsigned long naturalHeight;
readonly attribute boolean complete;
readonly attribute DOMString currentSrc;
attribute DOMString referrerPolicy;
};
interface HTMLIFrameElement : HTMLElement {
attribute DOMString src;
attribute DOMString srcdoc;
attribute DOMString name;
[SameObject, PutForwards=value] readonly attribute DOMTokenList sandbox;
attribute boolean allowFullscreen;
attribute boolean allowPaymentRequest;
attribute DOMString width;
attribute DOMString height;
attribute DOMString referrerPolicy;
readonly attribute Document? contentDocument;
readonly attribute WindowProxy? contentWindow;
};
interface HTMLEmbedElement : HTMLElement {
attribute DOMString src;
attribute DOMString type;
attribute DOMString width;
attribute DOMString height;
legacycaller any (any... arguments);
};
interface HTMLObjectElement : HTMLElement {
attribute DOMString data;
attribute DOMString type;
attribute boolean typeMustMatch;
attribute DOMString name;
readonly attribute HTMLFormElement? form;
attribute DOMString width;
attribute DOMString height;
readonly attribute Document? contentDocument;
readonly attribute WindowProxy? contentWindow;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
legacycaller any (any... arguments);
};
interface HTMLParamElement : HTMLElement {
attribute DOMString name;
attribute DOMString value;
};
interface HTMLVideoElement : HTMLMediaElement {
attribute unsigned long width;
attribute unsigned long height;
readonly attribute unsigned long videoWidth;
readonly attribute unsigned long videoHeight;
attribute DOMString poster;
};
[NamedConstructor=Audio(optional DOMString src)]
interface HTMLAudioElement : HTMLMediaElement {};
interface HTMLTrackElement : HTMLElement {
attribute DOMString kind;
attribute DOMString src;
attribute DOMString srclang;
attribute DOMString label;
attribute boolean default;
const unsigned short NONE = 0;
const unsigned short LOADING = 1;
const unsigned short LOADED = 2;
const unsigned short ERROR = 3;
readonly attribute unsigned short readyState;
readonly attribute TextTrack track;
};
enum CanPlayTypeResult { "" /* empty string */, "maybe", "probably" };
typedef (MediaStream or MediaSource or Blob) MediaProvider;
interface HTMLMediaElement : HTMLElement {
// error state
readonly attribute MediaError? error;
// network state
attribute DOMString src;
attribute MediaProvider? srcObject;
readonly attribute DOMString currentSrc;
attribute DOMString? crossOrigin;
const unsigned short NETWORK_EMPTY = 0;
const unsigned short NETWORK_IDLE = 1;
const unsigned short NETWORK_LOADING = 2;
const unsigned short NETWORK_NO_SOURCE = 3;
readonly attribute unsigned short networkState;
attribute DOMString preload;
readonly attribute TimeRanges buffered;
void load();
CanPlayTypeResult canPlayType(DOMString type);
// ready state
const unsigned short HAVE_NOTHING = 0;
const unsigned short HAVE_METADATA = 1;
const unsigned short HAVE_CURRENT_DATA = 2;
const unsigned short HAVE_FUTURE_DATA = 3;
const unsigned short HAVE_ENOUGH_DATA = 4;
readonly attribute unsigned short readyState;
readonly attribute boolean seeking;
// playback state
attribute double currentTime;
void fastSeek(double time);
readonly attribute unrestricted double duration;
object getStartDate();
readonly attribute boolean paused;
attribute double defaultPlaybackRate;
attribute double playbackRate;
readonly attribute TimeRanges played;
readonly attribute TimeRanges seekable;
readonly attribute boolean ended;
attribute boolean autoplay;
attribute boolean loop;
void play();
void pause();
// controls
attribute boolean controls;
attribute double volume;
attribute boolean muted;
attribute boolean defaultMuted;
// tracks
[SameObject] readonly attribute AudioTrackList audioTracks;
[SameObject] readonly attribute VideoTrackList videoTracks;
[SameObject] readonly attribute TextTrackList textTracks;
TextTrack addTextTrack(TextTrackKind kind, optional DOMString label = "", optional DOMString language = "");
};
interface MediaError {
const unsigned short MEDIA_ERR_ABORTED = 1;
const unsigned short MEDIA_ERR_NETWORK = 2;
const unsigned short MEDIA_ERR_DECODE = 3;
const unsigned short MEDIA_ERR_SRC_NOT_SUPPORTED = 4;
readonly attribute unsigned short code;
};
interface AudioTrackList : EventTarget {
readonly attribute unsigned long length;
getter AudioTrack (unsigned long index);
AudioTrack? getTrackById(DOMString id);
attribute EventHandler onchange;
attribute EventHandler onaddtrack;
attribute EventHandler onremovetrack;
};
interface AudioTrack {
readonly attribute DOMString id;
readonly attribute DOMString kind;
readonly attribute DOMString label;
readonly attribute DOMString language;
attribute boolean enabled;
};
interface VideoTrackList : EventTarget {
readonly attribute unsigned long length;
getter VideoTrack (unsigned long index);
VideoTrack? getTrackById(DOMString id);
readonly attribute long selectedIndex;
attribute EventHandler onchange;
attribute EventHandler onaddtrack;
attribute EventHandler onremovetrack;
};
interface VideoTrack {
readonly attribute DOMString id;
readonly attribute DOMString kind;
readonly attribute DOMString label;
readonly attribute DOMString language;
attribute boolean selected;
};
interface TextTrackList : EventTarget {
readonly attribute unsigned long length;
getter TextTrack (unsigned long index);
TextTrack? getTrackById(DOMString id);
attribute EventHandler onchange;
attribute EventHandler onaddtrack;
attribute EventHandler onremovetrack;
};
enum TextTrackMode { "disabled", "hidden", "showing" };
enum TextTrackKind { "subtitles", "captions", "descriptions", "chapters", "metadata" };
interface TextTrack : EventTarget {
readonly attribute TextTrackKind kind;
readonly attribute DOMString label;
readonly attribute DOMString language;
readonly attribute DOMString id;
readonly attribute DOMString inBandMetadataTrackDispatchType;
attribute TextTrackMode mode;
readonly attribute TextTrackCueList? cues;
readonly attribute TextTrackCueList? activeCues;
void addCue(TextTrackCue cue);
void removeCue(TextTrackCue cue);
attribute EventHandler oncuechange;
};
interface TextTrackCueList {
readonly attribute unsigned long length;
getter TextTrackCue (unsigned long index);
TextTrackCue? getCueById(DOMString id);
};
interface TextTrackCue : EventTarget {
readonly attribute TextTrack? track;
attribute DOMString id;
attribute double startTime;
attribute double endTime;
attribute boolean pauseOnExit;
attribute EventHandler onenter;
attribute EventHandler onexit;
};
[Constructor(double startTime, double endTime, ArrayBuffer data)]
interface DataCue : TextTrackCue {
attribute ArrayBuffer data;
};
interface TimeRanges {
readonly attribute unsigned long length;
double start(unsigned long index);
double end(unsigned long index);
};
[Constructor(DOMString type, optional TrackEventInit eventInitDict)]
interface TrackEvent : Event {
readonly attribute (VideoTrack or AudioTrack or TextTrack)? track;
};
dictionary TrackEventInit : EventInit {
(VideoTrack or AudioTrack or TextTrack)? track = null;
};
interface HTMLMapElement : HTMLElement {
attribute DOMString name;
[SameObject] readonly attribute HTMLCollection areas;
[SameObject] readonly attribute HTMLCollection images;
};
interface HTMLAreaElement : HTMLElement {
attribute DOMString alt;
attribute DOMString coords;
attribute DOMString shape;
attribute DOMString target;
attribute DOMString download;
attribute DOMString rel;
[SameObject, PutForwards=value] readonly attribute DOMTokenList relList;
attribute DOMString hreflang;
attribute DOMString type;
attribute DOMString referrerPolicy;
};
HTMLAreaElement implements HTMLHyperlinkElementUtils;
[NoInterfaceObject]
interface HTMLHyperlinkElementUtils {
stringifier attribute USVString href;
readonly attribute USVString origin;
attribute USVString protocol;
attribute USVString username;
attribute USVString password;
attribute USVString host;
attribute USVString hostname;
attribute USVString port;
attribute USVString pathname;
attribute USVString search;
attribute USVString hash;
};
interface HTMLTableElement : HTMLElement {
attribute HTMLTableCaptionElement? caption;
HTMLTableCaptionElement createCaption();
void deleteCaption();
attribute HTMLTableSectionElement? tHead;
HTMLTableSectionElement createTHead();
void deleteTHead();
attribute HTMLTableSectionElement? tFoot;
HTMLTableSectionElement createTFoot();
void deleteTFoot();
[SameObject] readonly attribute HTMLCollection tBodies;
HTMLTableSectionElement createTBody();
[SameObject] readonly attribute HTMLCollection rows;
HTMLTableRowElement insertRow(optional long index = -1);
void deleteRow(long index);
};
interface HTMLTableCaptionElement : HTMLElement {};
interface HTMLTableColElement : HTMLElement {
attribute unsigned long span;
};
interface HTMLTableSectionElement : HTMLElement {
[SameObject] readonly attribute HTMLCollection rows;
HTMLElement insertRow(optional long index = -1);
void deleteRow(long index);
};
interface HTMLTableRowElement : HTMLElement {
readonly attribute long rowIndex;
readonly attribute long sectionRowIndex;
[SameObject] readonly attribute HTMLCollection cells;
HTMLElement insertCell(optional long index = -1);
void deleteCell(long index);
};
interface HTMLTableDataCellElement : HTMLTableCellElement {};
interface HTMLTableHeaderCellElement : HTMLTableCellElement {
attribute DOMString scope;
attribute DOMString abbr;
};
interface HTMLTableCellElement : HTMLElement {
attribute unsigned long colSpan;
attribute unsigned long rowSpan;
[SameObject, PutForwards=value] readonly attribute DOMTokenList headers;
readonly attribute long cellIndex;
};
[OverrideBuiltins]
interface HTMLFormElement : HTMLElement {
attribute DOMString acceptCharset;
attribute DOMString action;
attribute DOMString autocomplete;
attribute DOMString enctype;
attribute DOMString encoding;
attribute DOMString method;
attribute DOMString name;
attribute boolean noValidate;
attribute DOMString target;
[SameObject] readonly attribute HTMLFormControlsCollection elements;
readonly attribute unsigned long length;
getter Element (unsigned long index);
getter (RadioNodeList or Element) (DOMString name);
void submit();
void reset();
boolean checkValidity();
boolean reportValidity();
};
interface HTMLLabelElement : HTMLElement {
readonly attribute HTMLFormElement? form;
attribute DOMString htmlFor;
readonly attribute HTMLElement? control;
};
interface HTMLInputElement : HTMLElement {
attribute DOMString accept;
attribute DOMString alt;
attribute DOMString autocomplete;
attribute boolean autofocus;
attribute boolean defaultChecked;
attribute boolean checked;
attribute DOMString dirName;
attribute boolean disabled;
readonly attribute HTMLFormElement? form;
readonly attribute FileList? files;
attribute DOMString formAction;
attribute DOMString formEnctype;
attribute DOMString formMethod;
attribute boolean formNoValidate;
attribute DOMString formTarget;
attribute unsigned long height;
attribute boolean indeterminate;
readonly attribute HTMLElement? list;
attribute DOMString max;
attribute long maxLength;
attribute DOMString min;
attribute long minLength;
attribute boolean multiple;
attribute DOMString name;
attribute DOMString pattern;
attribute DOMString placeholder;
attribute boolean readOnly;
attribute boolean _required;
attribute unsigned long size;
attribute DOMString src;
attribute DOMString step;
attribute DOMString type;
attribute DOMString defaultValue;
[TreatNullAs=EmptyString] attribute DOMString value;
attribute object? valueAsDate;
attribute unrestricted double valueAsNumber;
attribute unsigned long width;
void stepUp(optional long n = 1);
void stepDown(optional long n = 1);
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
[SameObject] readonly attribute NodeList labels;
void select();
attribute unsigned long? selectionStart;
attribute unsigned long? selectionEnd;
attribute DOMString? selectionDirection;
void setRangeText(DOMString replacement);
void setRangeText(DOMString replacement, unsigned long start, unsigned long end, optional SelectionMode selectionMode = "preserve");
void setSelectionRange(unsigned long start, unsigned long end, optional DOMString direction);
};
interface HTMLButtonElement : HTMLElement {
attribute boolean autofocus;
attribute boolean disabled;
readonly attribute HTMLFormElement? form;
attribute DOMString formAction;
attribute DOMString formEnctype;
attribute DOMString formMethod;
attribute boolean formNoValidate;
attribute DOMString formTarget;
attribute DOMString name;
attribute DOMString type;
attribute DOMString value;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
[SameObject] readonly attribute NodeList labels;
};
interface HTMLSelectElement : HTMLElement {
attribute DOMString autocomplete;
attribute boolean autofocus;
attribute boolean disabled;
readonly attribute HTMLFormElement? form;
attribute boolean multiple;
attribute DOMString name;
attribute boolean _required;
attribute unsigned long size;
readonly attribute DOMString type;
[SameObject] readonly attribute HTMLOptionsCollection options;
attribute unsigned long length;
getter Element? item(unsigned long index);
HTMLOptionElement? namedItem(DOMString name);
void add((HTMLOptionElement or HTMLOptGroupElement) element, optional (HTMLElement or long)? before = null);
void remove(); // ChildNode overload
void remove(long index);
setter void (unsigned long index, HTMLOptionElement? option);
[SameObject] readonly attribute HTMLCollection selectedOptions;
attribute long selectedIndex;
attribute DOMString value;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
[SameObject] readonly attribute NodeList labels;
};
interface HTMLDataListElement : HTMLElement {
[SameObject] readonly attribute HTMLCollection options;
};
interface HTMLOptGroupElement : HTMLElement {
attribute boolean disabled;
attribute DOMString label;
};
[NamedConstructor=Option(optional DOMString text = "", optional DOMString value, optional boolean defaultSelected = false, optional boolean selected = false)]
interface HTMLOptionElement : HTMLElement {
attribute boolean disabled;
readonly attribute HTMLFormElement? form;
attribute DOMString label;
attribute boolean defaultSelected;
attribute boolean selected;
attribute DOMString value;
attribute DOMString text;
readonly attribute long index;
};
interface HTMLTextAreaElement : HTMLElement {
attribute DOMString autocomplete;
attribute boolean autofocus;
attribute unsigned long cols;
attribute DOMString dirName;
attribute boolean disabled;
readonly attribute HTMLFormElement? form;
attribute long maxLength;
attribute long minLength;
attribute DOMString name;
attribute DOMString placeholder;
attribute boolean readOnly;
attribute boolean _required;
attribute unsigned long rows;
attribute DOMString wrap;
readonly attribute DOMString type;
attribute DOMString defaultValue;
[TreatNullAs=EmptyString] attribute DOMString value;
readonly attribute unsigned long textLength;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
[SameObject] readonly attribute NodeList labels;
void select();
attribute unsigned long? selectionStart;
attribute unsigned long? selectionEnd;
attribute DOMString? selectionDirection;
void setRangeText(DOMString replacement);
void setRangeText(DOMString replacement, unsigned long start, unsigned long end, optional SelectionMode selectionMode = "preserve");
void setSelectionRange(unsigned long start, unsigned long end, optional DOMString direction);
};
interface HTMLOutputElement : HTMLElement {
[SameObject, PutForwards=value] readonly attribute DOMTokenList htmlFor;
readonly attribute HTMLFormElement? form;
attribute DOMString name;
readonly attribute DOMString type;
attribute DOMString defaultValue;
attribute DOMString value;
readonly attribute boolean willValidate;
readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
[SameObject] readonly attribute NodeList labels;
};
interface HTMLProgressElement : HTMLElement {
attribute double value;
attribute double max;
readonly attribute double position;
[SameObject] readonly attribute NodeList labels;
};
interface HTMLMeterElement : HTMLElement {
attribute double value;
attribute double min;
attribute double max;
attribute double low;
attribute double high;
attribute double optimum;
[SameObject] readonly attribute NodeList labels;
};
interface HTMLFieldSetElement : HTMLElement {
attribute boolean disabled;
readonly attribute HTMLFormElement? form;
attribute DOMString name;
readonly attribute DOMString type;
[SameObject] readonly attribute HTMLCollection elements;
readonly attribute boolean willValidate;
[SameObject] readonly attribute ValidityState validity;
readonly attribute DOMString validationMessage;
boolean checkValidity();
boolean reportValidity();
void setCustomValidity(DOMString error);
};
interface HTMLLegendElement : HTMLElement {
readonly attribute HTMLFormElement? form;
};
enum SelectionMode {
"select",
"start",
"end",
"preserve" // default
};
interface ValidityState {
readonly attribute boolean valueMissing;
readonly attribute boolean typeMismatch;
readonly attribute boolean patternMismatch;
readonly attribute boolean tooLong;
readonly attribute boolean tooShort;
readonly attribute boolean rangeUnderflow;
readonly attribute boolean rangeOverflow;
readonly attribute boolean stepMismatch;
readonly attribute boolean badInput;
readonly attribute boolean customError;
readonly attribute boolean valid;
};
interface HTMLDetailsElement : HTMLElement {
attribute boolean open;
};
interface HTMLDialogElement : HTMLElement {
attribute boolean open;
attribute DOMString returnValue;
void show(optional (MouseEvent or Element) anchor);
void showModal(optional (MouseEvent or Element) anchor);
void close(optional DOMString returnValue);
};
interface HTMLScriptElement : HTMLElement {
attribute DOMString src;
attribute DOMString type;
attribute DOMString charset;
attribute boolean async;
attribute boolean defer;
attribute DOMString? crossOrigin;
attribute DOMString text;
attribute DOMString nonce;
};
[Exposed=Window,
HTMLConstructor]
interface HTMLTemplateElement : HTMLElement {
readonly attribute DocumentFragment content;
};
typedef (CanvasRenderingContext2D or WebGLRenderingContext) RenderingContext;
interface HTMLCanvasElement : HTMLElement {
attribute unsigned long width;
attribute unsigned long height;
RenderingContext? getContext(DOMString contextId, any... arguments);
boolean probablySupportsContext(DOMString contextId, any... arguments);
DOMString toDataURL(optional DOMString type, any... arguments);
void toBlob(BlobCallback _callback, optional DOMString type, any... arguments);
};
callback BlobCallback = void (Blob? blob);
[NoInterfaceObject]
interface ElementContentEditable {
attribute DOMString contentEditable;
readonly attribute boolean isContentEditable;
};
interface DataTransfer {
attribute DOMString dropEffect;
attribute DOMString effectAllowed;
[SameObject] readonly attribute DataTransferItemList items;
void setDragImage(Element image, long x, long y);
/* old interface */
[SameObject] readonly attribute DOMString[] types;
DOMString getData(DOMString format);
void setData(DOMString format, DOMString data);
void clearData(optional DOMString format);
[SameObject] readonly attribute FileList files;
};
interface DataTransferItemList {
readonly attribute unsigned long length;
getter DataTransferItem (unsigned long index);
DataTransferItem? add(DOMString data, DOMString type);
DataTransferItem? add(File data);
void remove(unsigned long index);
void clear();
};
interface DataTransferItem {
readonly attribute DOMString kind;
readonly attribute DOMString type;
void getAsString(FunctionStringCallback? _callback);
File? getAsFile();
};
callback FunctionStringCallback = void (DOMString data);
[Constructor(DOMString type, optional DragEventInit eventInitDict)]
interface DragEvent : MouseEvent {
readonly attribute DataTransfer? dataTransfer;
};
dictionary DragEventInit : MouseEventInit {
DataTransfer? dataTransfer = null;
};
[PrimaryGlobal, LegacyUnenumerableNamedProperties]
/*sealed*/ interface Window : EventTarget {
// the current browsing context
[Unforgeable] readonly attribute WindowProxy window;
[Replaceable] readonly attribute WindowProxy self;
[Unforgeable] readonly attribute Document document;
attribute DOMString name;
[PutForwards=href, Unforgeable] readonly attribute Location location;
readonly attribute History history;
[Replaceable] readonly attribute BarProp locationbar;
[Replaceable] readonly attribute BarProp menubar;
[Replaceable] readonly attribute BarProp personalbar;
[Replaceable] readonly attribute BarProp scrollbars;
[Replaceable] readonly attribute BarProp statusbar;
[Replaceable] readonly attribute BarProp toolbar;
attribute DOMString status;
void close();
readonly attribute boolean closed;
void stop();
void focus();
void blur();
// other browsing contexts
[Replaceable] readonly attribute WindowProxy frames;
[Replaceable] readonly attribute unsigned long length;
[Unforgeable] readonly attribute WindowProxy top;
attribute any opener;
[Replaceable] readonly attribute WindowProxy parent;
readonly attribute Element? frameElement;
WindowProxy open(optional DOMString url = "about:blank", optional DOMString target = "_blank", [TreatNullAs=EmptyString] optional DOMString features = "", optional boolean replace = false);
getter WindowProxy (unsigned long index);
getter object (DOMString name);
// Since this is the global object, the IDL named getter adds a NamedPropertiesObject exotic
// object on the prototype chain. Indeed, this does not make the global object an exotic object.
// Indexed access is taken care of by the WindowProxy exotic object.
// the user agent
readonly attribute Navigator navigator;
// user prompts
void alert();
void alert(DOMString message);
boolean confirm(optional DOMString message = "");
DOMString? prompt(optional DOMString message = "", optional DOMString default = "");
void print();
unsigned long requestAnimationFrame(FrameRequestCallback callback);
void cancelAnimationFrame(unsigned long handle);
};
Window implements GlobalEventHandlers;
Window implements WindowEventHandlers;
callback FrameRequestCallback = void (DOMHighResTimeStamp time);
interface BarProp {
readonly attribute boolean visible;
};
enum ScrollRestoration { "auto", "manual" };
interface History {
readonly attribute unsigned long length;
attribute ScrollRestoration scrollRestoration;
readonly attribute any state;
void go(optional long delta = 0);
void back();
void forward();
void pushState(any data, DOMString title, optional DOMString? url = null);
void replaceState(any data, DOMString title, optional DOMString? url = null);
};
interface Location {
[Unforgeable] stringifier attribute USVString href;
[Unforgeable] readonly attribute USVString origin;
[Unforgeable] attribute USVString protocol;
[Unforgeable] attribute USVString host;
[Unforgeable] attribute USVString hostname;
[Unforgeable] attribute USVString port;
[Unforgeable] attribute USVString pathname;
[Unforgeable] attribute USVString search;
[Unforgeable] attribute USVString hash;
[Unforgeable] void assign(USVString url);
[Unforgeable] void replace(USVString url);
[Unforgeable] void reload();
[Unforgeable, SameObject] readonly attribute USVString[] ancestorOrigins;
};
[Constructor(DOMString type, optional PopStateEventInit eventInitDict), Exposed=(Window,Worker)]
interface PopStateEvent : Event {
readonly attribute any state;
};
dictionary PopStateEventInit : EventInit {
any state = null;
};
[Constructor(DOMString type, optional HashChangeEventInit eventInitDict), Exposed=(Window,Worker)]
interface HashChangeEvent : Event {
readonly attribute USVString oldURL;
readonly attribute USVString newURL;
};
dictionary HashChangeEventInit : EventInit {
USVString oldURL = "";
USVString newURL = "";
};
[Constructor(DOMString type, optional PageTransitionEventInit eventInitDict), Exposed=(Window,Worker)]
interface PageTransitionEvent : Event {
readonly attribute boolean persisted;
};
dictionary PageTransitionEventInit : EventInit {
boolean persisted = false;
};
interface BeforeUnloadEvent : Event {
attribute DOMString returnValue;
};
[NoInterfaceObject, Exposed=(Window, Worker)]
interface NavigatorOnLine {
readonly attribute boolean onLine;
};
[Constructor(DOMString type, optional ErrorEventInit eventInitDict), Exposed=(Window, Worker)]
interface ErrorEvent : Event {
readonly attribute DOMString message;
readonly attribute DOMString filename;
readonly attribute unsigned long lineno;
readonly attribute unsigned long colno;
readonly attribute any error;
};
dictionary ErrorEventInit : EventInit {
DOMString message = "";
DOMString filename = "";
unsigned long lineno = 0;
unsigned long colno = 0;
any error = null;
};
[Constructor(DOMString type, PromiseRejectionEventInit eventInitDict), Exposed=(Window,Worker)]
interface PromiseRejectionEvent : Event {
readonly attribute Promise<any> promise;
readonly attribute any reason;
};
dictionary PromiseRejectionEventInit : EventInit {
required Promise<any> promise;
any reason;
};
[TreatNonObjectAsNull]
callback EventHandlerNonNull = any (Event event);
typedef EventHandlerNonNull? EventHandler;
[TreatNonObjectAsNull]
callback OnErrorEventHandlerNonNull = any ((Event or DOMString) event, optional DOMString source, optional unsigned long lineno, optional unsigned long column, optional any error);
typedef OnErrorEventHandlerNonNull? OnErrorEventHandler;
[TreatNonObjectAsNull]
callback OnBeforeUnloadEventHandlerNonNull = DOMString? (Event event);
typedef OnBeforeUnloadEventHandlerNonNull? OnBeforeUnloadEventHandler;
[NoInterfaceObject]
interface GlobalEventHandlers {
attribute EventHandler onabort;
attribute EventHandler onblur;
attribute EventHandler oncancel;
attribute EventHandler oncanplay;
attribute EventHandler oncanplaythrough;
attribute EventHandler onchange;
attribute EventHandler onclick;
attribute EventHandler onclose;
attribute EventHandler oncuechange;
attribute EventHandler ondblclick;
attribute EventHandler ondrag;
attribute EventHandler ondragend;
attribute EventHandler ondragenter;
attribute EventHandler ondragexit;
attribute EventHandler ondragleave;
attribute EventHandler ondragover;
attribute EventHandler ondragstart;
attribute EventHandler ondrop;
attribute EventHandler ondurationchange;
attribute EventHandler onemptied;
attribute EventHandler onended;
attribute OnErrorEventHandler onerror;
attribute EventHandler onfocus;
attribute EventHandler oninput;
attribute EventHandler oninvalid;
attribute EventHandler onkeydown;
attribute EventHandler onkeypress;
attribute EventHandler onkeyup;
attribute EventHandler onload;
attribute EventHandler onloadeddata;
attribute EventHandler onloadedmetadata;
attribute EventHandler onloadstart;
attribute EventHandler onmousedown;
[LenientThis] attribute EventHandler onmouseenter;
[LenientThis] attribute EventHandler onmouseleave;
attribute EventHandler onmousemove;
attribute EventHandler onmouseout;
attribute EventHandler onmouseover;
attribute EventHandler onmouseup;
attribute EventHandler onwheel;
attribute EventHandler onpause;
attribute EventHandler onplay;
attribute EventHandler onplaying;
attribute EventHandler onprogress;
attribute EventHandler onratechange;
attribute EventHandler onreset;
attribute EventHandler onresize;
attribute EventHandler onscroll;
attribute EventHandler onseeked;
attribute EventHandler onseeking;
attribute EventHandler onselect;
attribute EventHandler onshow;
attribute EventHandler onstalled;
attribute EventHandler onsubmit;
attribute EventHandler onsuspend;
attribute EventHandler ontimeupdate;
attribute EventHandler ontoggle;
attribute EventHandler onvolumechange;
attribute EventHandler onwaiting;
};
[NoInterfaceObject]
interface WindowEventHandlers {
attribute EventHandler onafterprint;
attribute EventHandler onbeforeprint;
attribute OnBeforeUnloadEventHandler onbeforeunload;
attribute EventHandler onhashchange;
attribute EventHandler onlanguagechange;
attribute EventHandler onmessage;
attribute EventHandler onoffline;
attribute EventHandler ononline;
attribute EventHandler onpagehide;
attribute EventHandler onpageshow;
attribute EventHandler onrejectionhandled;
attribute EventHandler onpopstate;
attribute EventHandler onstorage;
attribute EventHandler onunhandledrejection;
attribute EventHandler onunload;
};
[NoInterfaceObject]
interface DocumentAndElementEventHandlers {
attribute EventHandler oncopy;
attribute EventHandler oncut;
attribute EventHandler onpaste;
};
typedef (DOMString or Function) TimerHandler;
[NoInterfaceObject, Exposed=(Window, Worker)]
interface WindowOrWorkerGlobalScope {
[Replaceable] readonly attribute USVString origin;
// Base64 utility methods (WindowBase64)
DOMString btoa(DOMString btoa);
DOMString atob(DOMString atob);
// Timers (WindowTimers)
long setTimeout((Function or DOMString) handler, optional long timeout = 0, any... arguments);
void clearTimeout(optional long handle = 0);
long setInterval((Function or DOMString) handler, optional long timeout = 0, any... arguments);
void clearInterval(optional long handle = 0);
// ImageBitmap, Images (ImageBitmapFactories)
Promise<ImageBitmap> createImageBitmap(ImageBitmapSource image);
Promise<ImageBitmap> createImageBitmap(ImageBitmapSource image, long sx, long sy, long sw, long sh);
};
Window implements WindowOrWorkerGlobalScope;
WorkerGlobalScope implements WindowOrWorkerGlobalScope;
interface Navigator {
// objects implementing this interface also implement the interfaces given below
};
Navigator implements NavigatorID;
Navigator implements NavigatorLanguage;
Navigator implements NavigatorOnLine;
Navigator implements NavigatorContentUtils;
Navigator implements NavigatorCookies;
[NoInterfaceObject, Exposed=(Window, Worker)]
interface NavigatorID {
[Exposed=Window] readonly attribute DOMString appCodeName; // constant "Mozilla"
readonly attribute DOMString appName; // constant "Netscape"
readonly attribute DOMString appVersion;
readonly attribute DOMString platform;
[Exposed=Window]readonly attribute DOMString product; // constant "Gecko"
readonly attribute DOMString userAgent;
};
[NoInterfaceObject, Exposed=(Window, Worker)]
interface NavigatorLanguage {
readonly attribute DOMString? language;
readonly attribute DOMString[] languages;
};
[NoInterfaceObject]
interface NavigatorContentUtils {
// content handler registration
void registerProtocolHandler(DOMString scheme, DOMString url, DOMString title);
void registerContentHandler(DOMString mimeType, DOMString url, DOMString title);
DOMString isProtocolHandlerRegistered(DOMString scheme, DOMString url);
DOMString isContentHandlerRegistered(DOMString mimeType, DOMString url);
void unregisterProtocolHandler(DOMString scheme, DOMString url);
void unregisterContentHandler(DOMString mimeType, DOMString url);
};
[NoInterfaceObject]
interface NavigatorCookies {
readonly attribute boolean cookieEnabled;
};
[Exposed=(Window, Worker), Serializable, Transferable]
interface ImageBitmap {
readonly attribute unsigned long width;
readonly attribute unsigned long height;
};
typedef (HTMLImageElement or
HTMLVideoElement or
HTMLCanvasElement or
Blob or
ImageData or
CanvasRenderingContext2D or
ImageBitmap) ImageBitmapSource;
// Note: intentionally not [HTMLConstructor]
interface HTMLAppletElement : HTMLElement {
attribute DOMString align;
attribute DOMString alt;
attribute DOMString archive;
attribute DOMString code;
attribute USVString codeBase;
attribute DOMString height;
attribute unsigned long hspace;
attribute DOMString name;
attribute USVString _object; // the underscore is not part of the identifier
attribute unsigned long vspace;
attribute DOMString width;
};
[HTMLConstructor]
interface HTMLMarqueeElement : HTMLElement {
[CEReactions] attribute DOMString behavior;
[CEReactions] attribute DOMString bgColor;
[CEReactions] attribute DOMString direction;
[CEReactions] attribute DOMString height;
[CEReactions] attribute unsigned long hspace;
[CEReactions] attribute long loop;
[CEReactions] attribute unsigned long scrollAmount;
[CEReactions] attribute unsigned long scrollDelay;
[CEReactions] attribute boolean trueSpeed;
[CEReactions] attribute unsigned long vspace;
[CEReactions] attribute DOMString width;
attribute EventHandler onbounce;
attribute EventHandler onfinish;
attribute EventHandler onstart;
void start();
void stop();
};
[HTMLConstructor]
interface HTMLFrameSetElement : HTMLElement {
[CEReactions] attribute DOMString cols;
[CEReactions] attribute DOMString rows;
};
HTMLFrameSetElement implements WindowEventHandlers;
[HTMLConstructor]
interface HTMLFrameElement : HTMLElement {
[CEReactions] attribute DOMString name;
[CEReactions] attribute DOMString scrolling;
[CEReactions] attribute USVString src;
[CEReactions] attribute DOMString frameBorder;
[CEReactions] attribute USVString longDesc;
[CEReactions] attribute boolean noResize;
readonly attribute Document? contentDocument;
readonly attribute WindowProxy? contentWindow;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString marginHeight;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString marginWidth;
};
partial interface HTMLAnchorElement {
[CEReactions] attribute DOMString coords;
[CEReactions] attribute DOMString charset;
[CEReactions] attribute DOMString name;
[CEReactions] attribute DOMString shape;
};
partial interface HTMLAreaElement {
[CEReactions] attribute boolean noHref;
};
partial interface HTMLBodyElement {
[CEReactions, TreatNullAs=EmptyString] attribute DOMString text;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString link;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString vLink;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString aLink;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString bgColor;
attribute DOMString background;
};
partial interface HTMLBRElement {
[CEReactions] attribute DOMString clear;
};
partial interface HTMLTableCaptionElement {
[CEReactions] attribute DOMString align;
};
partial interface HTMLTableColElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString ch;
[CEReactions] attribute DOMString chOff;
[CEReactions] attribute DOMString vAlign;
[CEReactions] attribute DOMString width;
};
[HTMLConstructor]
interface HTMLDirectoryElement : HTMLElement {
[CEReactions] attribute boolean compact;
};
partial interface HTMLDivElement {
[CEReactions] attribute DOMString align;
};
partial interface HTMLDListElement {
[CEReactions] attribute boolean compact;
};
partial interface HTMLEmbedElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString name;
};
[HTMLConstructor]
interface HTMLFontElement : HTMLElement {
[CEReactions, TreatNullAs=EmptyString] attribute DOMString color;
[CEReactions] attribute DOMString face;
[CEReactions] attribute DOMString size;
};
partial interface HTMLHeadingElement {
[CEReactions] attribute DOMString align;
};
partial interface HTMLHRElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString color;
[CEReactions] attribute boolean noShade;
[CEReactions] attribute DOMString size;
[CEReactions] attribute DOMString width;
};
partial interface HTMLHtmlElement {
[CEReactions] attribute DOMString version;
};
partial interface HTMLIFrameElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString scrolling;
[CEReactions] attribute DOMString frameBorder;
[CEReactions] attribute USVString longDesc;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString marginHeight;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString marginWidth;
};
partial interface HTMLImageElement {
[CEReactions] attribute DOMString name;
[CEReactions] attribute USVString lowsrc;
[CEReactions] attribute DOMString align;
[CEReactions] attribute unsigned long hspace;
[CEReactions] attribute unsigned long vspace;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString border;
};
partial interface HTMLInputElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString useMap;
};
partial interface HTMLLegendElement {
[CEReactions] attribute DOMString align;
};
partial interface HTMLLIElement {
[CEReactions] attribute DOMString type;
};
partial interface HTMLLinkElement {
[CEReactions] attribute DOMString charset;
[CEReactions] attribute DOMString target;
};
partial interface HTMLMenuElement {
[CEReactions] attribute boolean compact;
};
partial interface HTMLMetaElement {
[CEReactions] attribute DOMString scheme;
};
partial interface HTMLObjectElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString archive;
[CEReactions] attribute DOMString code;
[CEReactions] attribute boolean declare;
[CEReactions] attribute unsigned long hspace;
[CEReactions] attribute DOMString standby;
[CEReactions] attribute unsigned long vspace;
[CEReactions] attribute DOMString codeBase;
[CEReactions] attribute DOMString codeType;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString border;
};
partial interface HTMLOListElement {
[CEReactions] attribute boolean compact;
};
partial interface HTMLParagraphElement {
[CEReactions] attribute DOMString align;
};
partial interface HTMLParamElement {
[CEReactions] attribute DOMString type;
[CEReactions] attribute DOMString valueType;
};
partial interface HTMLPreElement {
[CEReactions] attribute long width;
};
partial interface HTMLScriptElement {
[CEReactions] attribute DOMString event;
[CEReactions] attribute DOMString htmlFor;
};
partial interface HTMLTableElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString border;
[CEReactions] attribute DOMString frame;
[CEReactions] attribute DOMString rules;
[CEReactions] attribute DOMString summary;
[CEReactions] attribute DOMString width;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString bgColor;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString cellPadding;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString cellSpacing;
};
partial interface HTMLTableSectionElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString ch;
[CEReactions] attribute DOMString chOff;
[CEReactions] attribute DOMString vAlign;
};
partial interface HTMLTableCellElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString axis;
[CEReactions] attribute DOMString height;
[CEReactions] attribute DOMString width;
[CEReactions] attribute DOMString ch;
[CEReactions] attribute DOMString chOff;
[CEReactions] attribute boolean noWrap;
[CEReactions] attribute DOMString vAlign;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString bgColor;
};
partial interface HTMLTableRowElement {
[CEReactions] attribute DOMString align;
[CEReactions] attribute DOMString ch;
[CEReactions] attribute DOMString chOff;
[CEReactions] attribute DOMString vAlign;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString bgColor;
};
partial interface HTMLUListElement {
[CEReactions] attribute boolean compact;
[CEReactions] attribute DOMString type;
};
partial interface Document {
[CEReactions, TreatNullAs=EmptyString] attribute DOMString fgColor;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString linkColor;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString vlinkColor;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString alinkColor;
[CEReactions, TreatNullAs=EmptyString] attribute DOMString bgColor;
[SameObject] readonly attribute HTMLCollection anchors;
[SameObject] readonly attribute HTMLCollection applets;
void clear();
void captureEvents();
void releaseEvents();
[SameObject] readonly attribute HTMLAllCollection all;
};
partial interface Window {
void captureEvents();
void releaseEvents();
[Replaceable, SameObject] readonly attribute External external;
};
[NoInterfaceObject]
interface External {
void AddSearchProvider();
void IsSearchProviderInstalled();
};
Navigator implements NavigatorPlugins;
[NoInterfaceObject]
interface NavigatorPlugins {
[SameObject] readonly attribute PluginArray plugins;
[SameObject] readonly attribute MimeTypeArray mimeTypes;
boolean javaEnabled();
};
interface PluginArray {
void refresh(optional boolean reload = false);
readonly attribute unsigned long length;
getter Plugin? item(unsigned long index);
getter Plugin? namedItem(DOMString name);
};
interface MimeTypeArray {
readonly attribute unsigned long length;
getter MimeType? item(unsigned long index);
getter MimeType? namedItem(DOMString name);
};
interface Plugin {
readonly attribute DOMString name;
readonly attribute DOMString description;
readonly attribute DOMString filename;
readonly attribute unsigned long length;
getter MimeType? item(unsigned long index);
getter MimeType? namedItem(DOMString name);
};
interface MimeType {
readonly attribute DOMString type;
readonly attribute DOMString description;
readonly attribute DOMString suffixes; // comma-separated
readonly attribute Plugin enabledPlugin;
};
References
Normative References
[ABNF]
D. Crocker, Ed.; P. Overell. Augmented BNF for Syntax
Specifications: ABNF. January 2008. Internet Standard. URL:
https://tools.ietf.org/html/rfc5234
[BCP47]
A. Phillips; M. Davis. Tags for Identifying Languages. September
2009. IETF Best Current Practice. URL:
https://tools.ietf.org/html/bcp47
[BIDI]
Mark Davis; Aharon Lanin; Andrew Glass. Unicode Bidirectional
Algorithm. 14 May 2017. Unicode Standard Annex #9. URL:
https://www.unicode.org/reports/tr9/tr9-37.html
[CANVAS-2D]
Rik Cabanier; et al. HTML Canvas 2D Context. 19 November 2015.
REC. URL: https://www.w3.org/TR/2dcontext/
[CLDR]
Unicode Common Locale Data Repository. URL:
http://cldr.unicode.org/
[COOKIES]
A. Barth. HTTP State Management Mechanism. April 2011. Proposed
Standard. URL: https://tools.ietf.org/html/rfc6265
[CORE-AAM-1.1]
Joanmarie Diggs; et al. Core Accessibility API Mappings 1.1. 21
September 2017. CR. URL: https://www.w3.org/TR/core-aam-1.1/
[CSP3]
Mike West. Content Security Policy Level 3. 13 September 2016. WD.
URL: https://www.w3.org/TR/CSP3/
[CSS-2015]
Tab Atkins Jr.; Elika Etemad; Florian Rivoal. CSS Snapshot 2015.
13 October 2015. NOTE. URL: https://www.w3.org/TR/css-2015/
[CSS-CASCADE-4]
Elika Etemad; Tab Atkins Jr.. CSS Cascading and Inheritance Level
4. 14 January 2016. CR. URL: https://www.w3.org/TR/css-cascade-4/
[CSS-COLOR-4]
Tab Atkins Jr.; Chris Lilley. CSS Color Module Level 4. 5 July
2016. WD. URL: https://www.w3.org/TR/css-color-4/
[CSS-DISPLAY-3]
Elika Etemad. CSS Display Module Level 3. 20 July 2017. WD. URL:
https://www.w3.org/TR/css-display-3/
[CSS-FONT-LOADING-3]
Tab Atkins Jr.. CSS Font Loading Module Level 3. 22 May 2014.
LCWD. URL: https://www.w3.org/TR/css-font-loading-3/
[CSS-FONTS-3]
John Daggett. CSS Fonts Module Level 3. 3 October 2013. CR. URL:
https://www.w3.org/TR/css-fonts-3/
[CSS-INLINE-3]
Dave Cramer; Elika Etemad; Steve Zilles. CSS Inline Layout Module
Level 3. 24 May 2016. WD. URL: https://www.w3.org/TR/css-inline-3/
[CSS-LOGICAL-1]
Rossen Atanassov; Elika Etemad. CSS Logical Properties and Values
Level 1. 18 May 2017. WD. URL:
https://www.w3.org/TR/css-logical-1/
[CSS-POSITION-3]
Rossen Atanassov; Arron Eicholz. CSS Positioned Layout Module
Level 3. 17 May 2016. WD. URL:
https://www.w3.org/TR/css-position-3/
[CSS-SIZING-3]
Elika Etemad. CSS Intrinsic & Extrinsic Sizing Module Level 3. 7
February 2017. WD. URL: https://www.w3.org/TR/css-sizing-3/
[CSS-STYLE-ATTR]
Tantek Çelik; Elika Etemad. CSS Style Attributes. 7 November 2013.
REC. URL: https://www.w3.org/TR/css-style-attr
[CSS-SYNTAX-3]
Tab Atkins Jr.; Simon Sapin. CSS Syntax Module Level 3. 20
February 2014. CR. URL: https://www.w3.org/TR/css-syntax-3/
[CSS-TEXT-3]
Elika Etemad; Koji Ishii. CSS Text Module Level 3. 22 August 2017.
WD. URL: https://www.w3.org/TR/css-text-3/
[CSS-UI-3]
Tantek Çelik; Florian Rivoal. CSS Basic User Interface Module
Level 3 (CSS3 UI). 2 March 2017. CR. URL:
https://www.w3.org/TR/css-ui-3/
[CSS-UI-4]
Florian Rivoal. CSS Basic User Interface Module Level 4. 22
September 2015. WD. URL: https://www.w3.org/TR/css-ui-4/
[CSS-VALUES]
Tab Atkins Jr.; Elika Etemad. CSS Values and Units Module Level 3.
29 September 2016. CR. URL: https://www.w3.org/TR/css-values-3/
[CSS-WRITING-MODES-3]
Elika Etemad; Koji Ishii. CSS Writing Modes Level 3. 15 December
2015. CR. URL: https://www.w3.org/TR/css-writing-modes-3/
[CSS2]
Bert Bos; et al. Cascading Style Sheets Level 2 Revision 1 (CSS
2.1) Specification. 7 June 2011. REC. URL:
https://www.w3.org/TR/CSS2
[CSS22]
Bert Bos. Cascading Style Sheets Level 2 Revision 2 (CSS 2.2)
Specification. 12 April 2016. WD. URL:
https://www.w3.org/TR/CSS22/
[CSS3-BACKGROUND]
Bert Bos; Elika Etemad; Brad Kemper. CSS Backgrounds and Borders
Module Level 3. 9 September 2014. CR. URL:
https://www.w3.org/TR/css3-background/
[CSS3-CONTENT]
Elika Etemad; Dave Cramer. CSS Generated Content Module Level 3. 2
June 2016. WD. URL: https://www.w3.org/TR/css-content-3/
[CSS3-IMAGES]
Elika Etemad; Tab Atkins Jr.. CSS Image Values and Replaced
Content Module Level 3. 17 April 2012. CR. URL:
https://www.w3.org/TR/css3-images/
[CSS3-RUBY]
Elika Etemad; Koji Ishii. CSS Ruby Layout Module Level 1. 5 August
2014. WD. URL: https://www.w3.org/TR/css-ruby-1/
[CSS3-TRANSITIONS]
Dean Jackson; et al. CSS Transitions. 19 November 2013. WD. URL:
https://www.w3.org/TR/css3-transitions/
[CSS3COLOR]
Tantek Çelik; Chris Lilley; David Baron. CSS Color Module Level 3.
7 June 2011. REC. URL: https://www.w3.org/TR/css3-color
[CSSOM]
Simon Pieters; Glenn Adams. CSS Object Model (CSSOM). 17 March
2016. WD. URL: https://www.w3.org/TR/cssom-1/
[CSSOM-VIEW]
Simon Pieters. CSSOM View Module. 17 March 2016. WD. URL:
https://www.w3.org/TR/cssom-view-1/
[CUSTOM-ELEMENTS]
Domenic Denicola. Custom Elements. 13 October 2016. WD. URL:
https://www.w3.org/TR/custom-elements/
[DOM41]
Yongsheng Zhu. DOM 4.1. WD. URL: https://www.w3.org/TR/dom41/
[DOM-PARSING]
Travis Leithead. DOM Parsing and Serialization. 17 May 2016. WD.
URL: https://www.w3.org/TR/DOM-Parsing/
[ECMA-262]
ECMAScript Language Specification. URL:
https://tc39.github.io/ecma262/
[ENCODING]
Anne van Kesteren, Joshua Bell, Addison Phillips. Encoding. CR.
URL: https://www.w3.org/TR/encoding/
[EVENTSOURCE]
Ian Hickson. Server-Sent Events. 3 February 2015. REC. URL:
https://www.w3.org/TR/eventsource/
[FETCH]
Anne van Kesteren. Fetch Standard. Living Standard. URL:
https://fetch.spec.whatwg.org/
[FILEAPI]
Arun Ranganathan; Jonas Sicking. File API. 21 April 2015. WD. URL:
https://www.w3.org/TR/FileAPI/
[FULLSCREEN]
Anne van Kesteren. Fullscreen API Standard. Living Standard. URL:
https://fullscreen.spec.whatwg.org/
[GEOMETRY-1]
Simon Pieters; Dirk Schulze; Rik Cabanier. Geometry Interfaces
Module Level 1. 25 November 2014. CR. URL:
https://www.w3.org/TR/geometry-1/
[GIF]
Graphics Interchange Format. 31 July 1990. URL:
https://www.w3.org/Graphics/GIF/spec-gif89a.txt
[HR-TIME-2]
Ilya Grigorik; James Simonsen; Jatinder Mann. High Resolution Time
Level 2. 3 August 2017. CR. URL: https://www.w3.org/TR/hr-time-2/
[HTML-AAM-1.0]
Steve Faulkner; et al. HTML Accessibility API Mappings 1.0. 10
October 2017. WD. URL: https://www.w3.org/TR/html-aam-1.0/
[HTML-ARIA]
Steve Faulkner. ARIA in HTML. 13 October 2017. WD. URL:
https://www.w3.org/TR/html-aria/
[HTML-LONGDESC]
Charles McCathieNevile; Mark Sadecki. HTML5 Image Description
Extension (longdesc). 26 February 2015. REC. URL:
https://www.w3.org/TR/html-longdesc/
[HTTP]
HTTP is the union of a set of RFCs:
* Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and
Routing (URL: https://tools.ietf.org/html/rfc7230), R.
Fielding, J. Reschke. IETF.
* Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
(URL: https://tools.ietf.org/html/rfc7231), R. Fielding, J.
Reschke. IETF.
* Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
(URL: https://tools.ietf.org/html/rfc7232), R. Fielding, J.
Reschke. IETF.
* Hypertext Transfer Protocol (HTTP/1.1): Range Requests (URL:
https://tools.ietf.org/html/rfc7233), R. Fielding, Y. Lafon,
J. Reschke. IETF.
* Hypertext Transfer Protocol (HTTP/1.1): Caching (URL:
https://tools.ietf.org/html/rfc7234), R. Fielding, M.
Nottingham, J. Reschke. IETF.
* Hypertext Transfer Protocol (HTTP/1.1): Authentication (URL:
https://tools.ietf.org/html/rfc7235), R. Fielding, J.
Reschke. IETF.
[IANAPERMHEADERS]
Permanent Message Header Field Names. IANA.
[INDEXEDDB]
Nikunj Mehta; et al. Indexed Database API. 8 January 2015. REC.
URL: https://www.w3.org/TR/IndexedDB/
[INFRA]
Anne van Kesteren; Domenic Denicola. Infra Standard. Living
Standard. URL: https://infra.spec.whatwg.org/
[ISO3166]
ISO 3166: Codes for the representation of names of countries and
their subdivisions.. 2013. ISO 3166-1:2013. URL:
http://www.iso.org/iso/catalogue_detail?csnumber=63545
[ISO4217]
Currency codes - ISO 4217. 2015. International Standard. URL:
http://www.iso.org/iso/home/standards/currency_codes.htm
[JPEG]
Eric Hamilton. JPEG File Interchange Format. September 1992. URL:
https://www.w3.org/Graphics/JPEG/jfif3.pdf
[MATHML]
Patrick D F Ion; Robert R Miner. Mathematical Markup Language
(MathML) 1.01 Specification. 7 July 1999. REC. URL:
https://www.w3.org/TR/MathML/
[MEDIA-FRAGS]
Raphaël Troncy; et al. Media Fragments URI 1.0 (basic). 25
September 2012. REC. URL: https://www.w3.org/TR/media-frags/
[MEDIA-SOURCE]
Matthew Wolenetz; et al. Media Source Extensions™. 17 November
2016. REC. URL: https://www.w3.org/TR/media-source/
[MEDIACAPTURE-STREAMS]
Daniel Burnett; et al. Media Capture and Streams. 3 October 2017.
CR. URL: https://www.w3.org/TR/mediacapture-streams/
[MEDIAQ]
Florian Rivoal; et al. Media Queries. 19 June 2012. REC. URL:
https://www.w3.org/TR/css3-mediaqueries/
[MEDIAQUERIES-4]
Florian Rivoal; Tab Atkins Jr.. Media Queries Level 4. 5 September
2017. CR. URL: https://www.w3.org/TR/mediaqueries-4/
[MFREL]
Microformats Wiki: existing rel values. Microformats.
[MIMESNIFF]
As of today the Web community lacks a sufficiently complete,
reliable, interoperable, and tested specification for the manner
in which content sniffing takes place on the Web. We encourage
implementers to exercise caution in this area as the Web community
makes progress towards addressing this issue.
Gordon P. Hemsley. MIME Sniffing Standard. Living Standard. URL:
https://mimesniff.spec.whatwg.org/
[MNG]
MNG (Multiple-image Network Graphics) Format. G. Randers-Pehrson.
[MPEG2TS]
Information technology -- Generic coding of moving pictures and
associated audio information: Systems ITU-T Rec. H.222.0 / ISO/IEC
13818-1:2013. URL: http://www.itu.int/rec/T-REC-H.222.0-201206-I
[MPEG4]
ISO/IEC 14496-12: ISO base media file format. ISO/IEC.
[MPEGDASH]
ISO/IEC 23009-1:2014 Information technology -- Dynamic adaptive
streaming over HTTP (DASH) -- Part 1: Media presentation
description and segment formats. URL:
http://standards.iso.org/ittf/PubliclyAvailableStandards/c065274_ISO_IEC_23009-1_2014.zip
[OGGSKELETON]
Ogg Skeleton 4 Message Headers. 17 March 2014. URL:
https://wiki.xiph.org/SkeletonHeaders
[OPENSEARCH]
Autodiscovery in HTML/XHTML. In OpenSearch 1.1 Draft 4, Section
4.6.2. OpenSearch.org.
[ORIGIN]
A. Barth. The Web Origin Concept. December 2011. Proposed
Standard. URL: https://tools.ietf.org/html/rfc6454
[PAGE-VISIBILITY]
Jatinder Mann; Arvind Jain. Page Visibility (Second Edition). 29
October 2013. REC. URL: https://www.w3.org/TR/page-visibility/
[PAYMENT-REQUEST]
Adrian Bateman; et al. Payment Request API. 21 September 2017. CR.
URL: https://www.w3.org/TR/payment-request/
[PDF]
Document management — Portable document format — Part 1: PDF. ISO.
[PNG]
Tom Lane. Portable Network Graphics (PNG) Specification (Second
Edition). 10 November 2003. REC. URL: https://www.w3.org/TR/PNG
[POINTERLOCK]
Vincent Scheib. Pointer Lock. 27 October 2016. REC. URL:
https://www.w3.org/TR/pointerlock/
[PRESENTATION-API]
Mark Foltz; Dominik Röttsches. Presentation API. 1 June 2017. CR.
URL: https://www.w3.org/TR/presentation-api/
[PROGRESS-EVENTS]
Anne van Kesteren; Charles McCathie Nevile; Jungkee Song. Progress
Events. 11 February 2014. REC. URL:
https://www.w3.org/TR/progress-events/
[PSL]
Public Suffix List. Mozilla Foundation.
[REFERRERPOLICY]
Referrer Policy. URL: https://www.w3.org/TR/referrer-policy
[RFC1034]
P.V. Mockapetris. Domain names - concepts and facilities. November
1987. Internet Standard. URL: https://tools.ietf.org/html/rfc1034
[RFC1123]
R. Braden, Ed.. Requirements for Internet Hosts - Application and
Support. October 1989. Internet Standard. URL:
https://tools.ietf.org/html/rfc1123
[RFC2046]
N. Freed; N. Borenstein. Multipurpose Internet Mail Extensions
(MIME) Part Two: Media Types. November 1996. Draft Standard. URL:
https://tools.ietf.org/html/rfc2046
[RFC2119]
S. Bradner. Key words for use in RFCs to Indicate Requirement
Levels. March 1997. Best Current Practice. URL:
https://tools.ietf.org/html/rfc2119
[RFC2318]
H. Lie; B. Bos; C. Lilley. The text/css Media Type. March 1998.
Informational. URL: https://tools.ietf.org/html/rfc2318
[RFC2397]
L. Masinter. The "data" URL scheme. August 1998. Proposed
Standard. URL: https://tools.ietf.org/html/rfc2397
[RFC2483]
M. Mealling; R. Daniel. URI Resolution Services Necessary for URN
Resolution. January 1999. Experimental. URL:
https://tools.ietf.org/html/rfc2483
[RFC4648]
S. Josefsson. The Base16, Base32, and Base64 Data Encodings.
October 2006. Proposed Standard. URL:
https://tools.ietf.org/html/rfc4648
[RFC5322]
P. Resnick, Ed.. Internet Message Format. October 2008. Draft
Standard. URL: https://tools.ietf.org/html/rfc5322
[RFC5724]
E. Wilde; A. Vaha-Sipila. URI Scheme for Global System for Mobile
Communications (GSM) Short Message Service (SMS). January 2010.
Proposed Standard. URL: https://tools.ietf.org/html/rfc5724
[RFC5988]
M. Nottingham. Web Linking. October 2010. Proposed Standard. URL:
https://tools.ietf.org/html/rfc5988
[RFC6068]
M. Duerst; L. Masinter; J. Zawinski. The 'mailto' URI Scheme.
October 2010. Proposed Standard. URL:
https://tools.ietf.org/html/rfc6068
[RFC6266]
J. Reschke. Use of the Content-Disposition Header Field in the
Hypertext Transfer Protocol (HTTP). June 2011. Proposed Standard.
URL: https://tools.ietf.org/html/rfc6266
[RFC6350]
S. Perreault. vCard Format Specification. August 2011. Proposed
Standard. URL: https://tools.ietf.org/html/rfc6350
[RFC6381]
R. Gellens; D. Singer; P. Frojdh. The 'Codecs' and 'Profiles'
Parameters for "Bucket" Media Types. August 2011. Proposed
Standard. URL: https://tools.ietf.org/html/rfc6381
[RFC6455]
I. Fette; A. Melnikov. The WebSocket Protocol. December 2011.
Proposed Standard. URL: https://tools.ietf.org/html/rfc6455
[RFC6694]
S. Moonesamy, Ed.. The "about" URI Scheme. August 2012.
Informational. URL: https://tools.ietf.org/html/rfc6694
[RFC7230]
R. Fielding, Ed.; J. Reschke, Ed.. Hypertext Transfer Protocol
(HTTP/1.1): Message Syntax and Routing. June 2014. Proposed
Standard. URL: https://tools.ietf.org/html/rfc7230
[RFC7231]
R. Fielding, Ed.; J. Reschke, Ed.. Hypertext Transfer Protocol
(HTTP/1.1): Semantics and Content. June 2014. Proposed Standard.
URL: https://tools.ietf.org/html/rfc7231
[RFC7232]
R. Fielding, Ed.; J. Reschke, Ed.. Hypertext Transfer Protocol
(HTTP/1.1): Conditional Requests. June 2014. Proposed Standard.
URL: https://tools.ietf.org/html/rfc7232
[RFC7234]
R. Fielding, Ed.; M. Nottingham, Ed.; J. Reschke, Ed.. Hypertext
Transfer Protocol (HTTP/1.1): Caching. June 2014. Proposed
Standard. URL: https://tools.ietf.org/html/rfc7234
[RFC7303]
H. Thompson; C. Lilley. XML Media Types. July 2014. Proposed
Standard. URL: https://tools.ietf.org/html/rfc7303
[RFC7578]
L. Masinter. Returning Values from Forms: multipart/form-data.
July 2015. Proposed Standard. URL:
https://tools.ietf.org/html/rfc7578
[RFC7595]
D. Thaler, Ed.; T. Hansen; T. Hardie. Guidelines and Registration
Procedures for URI Schemes. June 2015. Best Current Practice. URL:
https://tools.ietf.org/html/rfc7595
[SECURE-CONTEXTS]
Mike West. Secure Contexts. 15 September 2016. CR. URL:
https://www.w3.org/TR/secure-contexts/
[SELECTION-API]
Ryosuke Niwa. Selection API. 28 June 2017. WD. URL:
https://www.w3.org/TR/selection-api/
[SELECTORS4]
Elika Etemad; Tab Atkins Jr.. Selectors Level 4. 2 May 2013. WD.
URL: https://www.w3.org/TR/selectors4/
[SERVICE-WORKERS]
Alex Russell; et al. Service Workers 1. 11 October 2016. WD. URL:
https://www.w3.org/TR/service-workers-1/
[SRGB]
Amendment 1 - Multimedia systems and equipment - Colour
measurement and management - Part 2-1: Colour management - Default
RGB colour space - sRGB. URL:
https://webstore.iec.ch/publication/6168
[SVG11]
Erik Dahlström; et al. Scalable Vector Graphics (SVG) 1.1 (Second
Edition). 16 August 2011. REC. URL: https://www.w3.org/TR/SVG11/
[SVG2]
Nikos Andronikos; et al. Scalable Vector Graphics (SVG) 2. 15
September 2016. CR. URL: https://www.w3.org/TR/SVG2/
[SVGTINY12]
Ola Andersson; et al. Scalable Vector Graphics (SVG) Tiny 1.2
Specification. 22 December 2008. REC. URL:
https://www.w3.org/TR/SVGTiny12/
[TOUCH-EVENTS]
Doug Schepers; et al. Touch Events. 10 October 2013. REC. URL:
https://www.w3.org/TR/touch-events/
[UIEVENTS]
Gary Kacmarcik; Travis Leithead. UI Events. 4 August 2016. WD.
URL: https://www.w3.org/TR/uievents/
[UNICODE]
The Unicode Standard. URL:
https://www.unicode.org/versions/latest/
[URL]
Note: URLs can be used in numerous different manners, in many
differing contexts. For the purpose of producing strict URLs one
may wish to consider [RFC3986] [RFC3987]. The W3C URL
specification defines the term URL, various algorithms for dealing
with URLs, and an API for constructing, parsing, and resolving
URLs. Developers of Web browsers are advised to keep abreast of
the latest URL developments by tracking the progress of
https://url.spec.whatwg.org/. We expect that the W3C URL draft
will evolve along the Recommendation track as the community
converges on a definition of URL processing.
Most of the URL-related terms used in the HTML specification (URL,
absolute URL, relative URL, relative schemes, scheme component,
scheme data, username, password, host, port, path, query,
fragment, percent encode, get the base, and UTF-8 percent encode)
can be straightforwardly mapped to the terminology of [RFC3986]
[RFC3987]. The URLUtils (formerly known as URL) collection of
attributes (e.g. href and protocol) and its required definitions
(input, query encoding, url, update steps, set the input) are
considered common practice nowadays. Some of the URL-related terms
are still being refined (e.g. URL parser, parse errors, URL
serializer, default encode set, and percent decode).
As a word of caution, there are notable differences in the manner
in which Web browsers and other software stacks outside the HTML
context handle URLs. While no changes would be accepted to URL
processing that would break existing Web content, some important
parts of URL processing should therefore be considered as
implementation-defined (e.g. parsing file: URLs or operating on
URLs that would be syntax errors under the [RFC3986] [RFC3987]
syntax).
Anne van Kesteren. URL Standard. Living Standard. URL:
https://url.spec.whatwg.org/
[URN]
P. Saint-Andre; J. Klensin. Uniform Resource Names (URNs). April
2017. Proposed Standard. URL: https://tools.ietf.org/html/rfc8141
[WAI-ARIA]
James Craig; Michael Cooper; et al. Accessible Rich Internet
Applications (WAI-ARIA) 1.0. 20 March 2014. REC. URL:
https://www.w3.org/TR/wai-aria/
[WAI-ARIA-1.1]
Joanmarie Diggs; et al. Accessible Rich Internet Applications
(WAI-ARIA) 1.1. 27 October 2016. CR. URL:
https://www.w3.org/TR/wai-aria-1.1/
[WEBGL]
Dean Jackson; Jeff Gilbert. WebGL 2.0 Specification. 12 August
2017. URL:
https://www.khronos.org/registry/webgl/specs/latest/2.0/
[WEBIDL]
Cameron McCormack; Boris Zbarsky; Tobie Langel. Web IDL. 15
December 2016. ED. URL: https://www.w3.org/TR/WebIDL-1/
[WebIDL-20161215]
Cameron McCormack. WebIDL Level 1. 15 December 2016. REC. URL:
https://www.w3.org/TR/2016/REC-WebIDL-1-20161215/
[WEBM]
WebM Container Guidelines. 26 April 2016. URL:
https://www.webmproject.org/docs/container/
[WEBSTORAGE]
Ian Hickson. Web Storage (Second Edition). 19 April 2016. REC.
URL: https://www.w3.org/TR/webstorage/
[WORKERS]
Ian Hickson. Web Workers. 24 September 2015. WD. URL:
https://www.w3.org/TR/workers/
[XLINK]
Steven DeRose; Eve Maler; David Orchard. XML Linking Language
(XLink) Version 1.0. 27 June 2001. REC. URL:
https://www.w3.org/TR/xlink/
[XML]
Tim Bray; et al. Extensible Markup Language (XML) 1.0 (Fifth
Edition). 26 November 2008. REC. URL: https://www.w3.org/TR/xml
[XML-NAMES]
Tim Bray; et al. Namespaces in XML 1.0 (Third Edition). 8 December
2009. REC. URL: https://www.w3.org/TR/xml-names
[XML-STYLESHEET]
James Clark; Simon Pieters; Henry Thompson. Associating Style
Sheets with XML documents 1.0 (Second Edition). 28 October 2010.
REC. URL: https://www.w3.org/TR/xml-stylesheet
[XMLBASE]
Jonathan Marsh. XML Base (Second Edition). 28 January 2009. REC.
URL: https://www.w3.org/TR/xmlbase/
[XPATH]
James Clark; Steven DeRose. XML Path Language (XPath) Version 1.0.
16 November 1999. REC. URL: https://www.w3.org/TR/xpath
[XPTR-XMLNS]
Steven DeRose; et al. XPointer xmlns() Scheme. 25 March 2003. REC.
URL: https://www.w3.org/TR/xptr-xmlns/
Informative References
[APNG]
S. Parmenter; V. Vukicevic; A. Smith. APNG Specification. URL:
https://wiki.mozilla.org/APNG_Specification
[ATAG20]
Jan Richards; Jeanne F Spellman; Jutta Treviranus. Authoring Tool
Accessibility Guidelines (ATAG) 2.0. 24 September 2015. REC. URL:
https://www.w3.org/TR/ATAG20/
[BATTERY-STATUS]
Anssi Kostiainen; Mounir Lamouri. Battery Status API. 7 July 2016.
CR. URL: https://www.w3.org/TR/battery-status/
[BOCU1]
M. Scherer; M. Davis. UTN #6: BOCU-1: MIME-Compatible Unicode
Compression. URL: https://www.unicode.org/notes/tn6/
[CESU8]
T. Phipps. UTR #26: Compatibility Encoding Scheme For UTF-16:
8-BIT (CESU-8). URL: https://www.unicode.org/reports/tr26/
[CHARMOD]
Martin Dürst; et al. Character Model for the World Wide Web 1.0:
Fundamentals. 15 February 2005. REC. URL:
https://www.w3.org/TR/charmod/
[COMPUTABLE]
A. Turing. On computable numbers, with an application to the
Entscheidungsproblem, Proceedings of the London Mathematical
Society, series 2, volume 42,. 1937. URL:
http://www.turingarchive.org/browse.php/B/12
[CSS-LISTS-3]
Tab Atkins Jr.. CSS Lists and Counters Module Level 3. 20 March
2014. WD. URL: https://www.w3.org/TR/css-lists-3/
[CSS-LOGICAL-PROPS]
Rossen Atanassov; Elika J. Etemad. CSS Logical Properties Level 1.
ED. URL: https://drafts.csswg.org/css-logical-props/
[CSS3-ANIMATIONS]
Dean Jackson; et al. CSS Animations. 19 February 2013. WD. URL:
https://www.w3.org/TR/css3-animations/
[DOT]
The DOT Language. URL:
http://www.graphviz.org/content/dot-language
[EDITING]
A. Gregor. HTML Editing APIs. URL:
https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html
[Extensible]
The Extensible Web Manifesto. 10 June 2013. URL:
https://extensiblewebmanifesto.org/
[GRAPHICS]
Computer Graphics: Principles and Practice in C, Second Edition,
J. Foley, A. van Dam, S. Feiner, J. Hughes. Addison-Wesley. ISBN
0-201-84840-6.
[GREGORIAN]
Inter Gravissimas, A. Lilius, C. Clavius. Gregory XIII Papal Bull,
February 1582.
[HTML]
Anne van Kesteren; et al. HTML Standard. Living Standard. URL:
https://html.spec.whatwg.org/multipage/
[HTML-RDFA]
Manu Sporny. HTML+RDFa 1.1 - Second Edition. 17 March 2015. REC.
URL: https://www.w3.org/TR/html-rdfa/
[HTML5-DIFF]
Simon Pieters. HTML5 Differences from HTML4. 9 December 2014.
NOTE. URL: https://www.w3.org/TR/html5-diff/
[INBANDTRACKS]
Silvia Pfeiffer; Bob Lund. Sourcing In-band Media Resource Tracks
from Media Containers into HTML. 26 April 2015. Unofficial Draft.
URL: https://dev.w3.org/html5/html-sourcing-inband-tracks/
[ISO8601]
Representation of dates and times. ISO 8601:2004.. 2004. ISO
8601:2004. URL:
http://www.iso.org/iso/catalogue_detail?csnumber=40874
[JLREQ]
Yasuhiro Anan; et al. Requirements for Japanese Text Layout. 3
April 2012. NOTE. URL: https://www.w3.org/TR/jlreq/
[NPAPI]
Gecko Plugin API Reference. Mozilla.
[PPUTF8]
The Properties and Promises of UTF-8, M. Dürst. University of
Zürich. In Proceedings of the 11th International Unicode
Conference.
[RDFA-LITE]
Manu Sporny. RDFa Lite 1.1 - Second Edition. 17 March 2015. REC.
URL: https://www.w3.org/TR/rdfa-lite/
[RFC2152]
D. Goldsmith; M. Davis. UTF-7 A Mail-Safe Transformation Format of
Unicode. May 1997. Informational. URL:
https://tools.ietf.org/html/rfc2152
[RFC3676]
R. Gellens. The Text/Plain Format and DelSp Parameters. February
2004. Proposed Standard. URL: https://tools.ietf.org/html/rfc3676
[RFC4287]
M. Nottingham, Ed.; R. Sayre, Ed.. The Atom Syndication Format.
December 2005. Proposed Standard. URL:
https://tools.ietf.org/html/rfc4287
[RFC4329]
B. Hoehrmann. Scripting Media Types. April 2006. Informational.
URL: https://tools.ietf.org/html/rfc4329
[RUBY-UC]
Richard Ishida. Use Cases & Exploratory Approaches for Ruby
Markup. 8 October 2013. NOTE. URL:
https://www.w3.org/TR/ruby-use-cases/
[SCSU]
UTR #6: A Standard Compression Scheme For Unicode, M. Wolf, K.
Whistler, C. Wicksteed, M. Davis, A. Freytag, M. Scherer. Unicode
Consortium.
[TIMEZONE]
Addison Phillips; et al. Working with Time Zones. 5 July 2011.
NOTE. URL: https://www.w3.org/TR/timezone
[TOR]
Tor.
[TZDATABASE]
Time Zone Database. IANA.
[UAAG20]
James Allan; et al. User Agent Accessibility Guidelines (UAAG)
2.0. 15 December 2015. NOTE. URL: https://www.w3.org/TR/UAAG20/
[UNDO]
Ryosuke Niwa. UndoManager and DOM Transaction. ED. URL:
https://dvcs.w3.org/hg/undomanager/raw-file/tip/undomanager.html
[UNICODE-SECURITY]
Mark Davis; Michel Suignard. Unicode Security Considerations. 19
September 2014. Unicode Technical Report #36. URL:
https://www.unicode.org/reports/tr36/
[UNIVCHARDET]
A composite approach to language/encoding detection, S. Li, K.
Momoi. Netscape. In Proceedings of the 19th International Unicode
Conference.
[UTF8DET]
Multilingual form encoding, M. Dürst. W3C.
[WAI-ARIA-PRACTICES-1.1]
Matthew King; et al. WAI-ARIA Authoring Practices 1.1. 28 June
2017. WD. URL: https://www.w3.org/TR/wai-aria-practices-1.1/
[WCAG20]
Ben Caldwell; et al. Web Content Accessibility Guidelines (WCAG)
2.0. 11 December 2008. REC. URL: https://www.w3.org/TR/WCAG20/
[WEBMESSAGING]
Ian Hickson. HTML5 Web Messaging. 19 May 2015. REC. URL:
https://www.w3.org/TR/webmessaging/
[WEBVTT]
Simon Pieters. WebVTT: The Web Video Text Tracks Format. 8 August
2017. WD. URL: https://www.w3.org/TR/webvtt1/
[WHATWGWIKI]
The WHATWG Wiki. WHATWG.
[XHR]
Anne van Kesteren. XMLHttpRequest Standard. Living Standard. URL:
https://xhr.spec.whatwg.org/
[XKCD-1288]
Randall Munroe. Substitutions. URL: https://xkcd.com/1288/
[XML-ENTITY-NAMES]
David Carlisle; Patrick D F Ion. XML Entity Definitions for
Characters (2nd Edition). 10 April 2014. REC. URL:
https://www.w3.org/TR/xml-entity-names/
[XSLT]
James Clark. XSL Transformations (XSLT) Version 1.0. 16 November
1999. REC. URL: https://www.w3.org/TR/xslt
[XSLTP]
DOM XSLTProcessor. URL:
https://wiki.whatwg.org/wiki/DOM_XSLTProcessor
Changes
This section summarises substantial changes since the HTML 5.1
Recommendation.
Full details of all changes since 12 January 2016 are available from the
commit log of the w3c/html github repository, including various editorial
and linking fixes.
New features
* The dialog element.
* Integration with the JavaScript module system of [ECMA-262].
* Referrer policy [REFERRERPOLICY].
* Update ARIA reference to [wai-aria-1.1], which introduces new features
to improve accessibility.
* The nonce attribute for link as used in Content Security Policy
[CSP3].
* The allowpaymentrequest attribute of iframe, for integration with the
Payment Request API [PAYMENT-REQUEST].
* The allow-presentation value for the sandbox attribute of iframe, for
integration with the Presentation API [PRESENTATION-API].
* The canonical value for the rel attribute of links.
* The noreferrer link type value for [SECURE-CONTEXTS].
* The apple-touch-icon value for the rel attribute to allow the use of
the size attribute in the link element.
* The registerContentHandler(), isContentHandlerRegistered() and
isProtocolHandlerRegistered() methods.
* The innerText IDL attribute for HTMLElement.
* Define the about:html-kind URL for MP4 media track integration.
* Integrate the Should element be blocked a priori by Content Security
Policy? of [CSP3]
Features removed
* The keygen, menu and menuitem elements.
* The inputmode attribute for textual input elements, and the dropzone
attributes.
* The showModalDialog method.
* The Plugin API has been marked as obsolete.
Fixing bugs and matching reality better
* Stop media resource requests from non-network sources delaying the
load event.
* Remove arbitrary upper limits on refresh rates.
* Coordinates for ismap no longer include the image’s border in
calculation.
* Update accesskey definition to require a single printable character.
* Fix the activation algorithm for summary to match reality.
* Fix the algorithm to determine row and column headers for table.
* Update the rendering of summary
* Reflecting a broken URL returns the unparsed value
* currentScript may return SVGScriptElement.
* Resetting a textarea resets its dirty value flag.
* document.open() and document.close() check for XML document.
* HashChangeEvent URLs are USVString instead of DOMString.
* Selection members' types are nullable.
* data: URLs are treated as a separate origin.
* Sadly, elements that are only focusable because they have a tabindex
attribute generally will not fire a click event when activated with a
non-pointer device.
* Navigation for sandboxed contexts
* Updated allowable role values in line with [html-aria]
The following constructions are now valid HTML:
style within the body.
Multiple main elements in the DOM, so long as only one is visible
to the user.
The presentation for the img element.
div as a child of a dl element.
dfn as a descendent of an li element that contains a definition of
the term defined.
Headings within legend in a fieldset.
Empty option element as a child of datalist.
Comments containing two consecutive hyphens, or ending with a
hyphen, in the HTML syntax.
Remove restrictions on BiDi algorithm section
The following constructions are no longer valid HTML:
role values for a caption element.
Inline blocks, inline tables, or floated and positioned
block-level elements as children of a p element.
Content with the HTML4 or XHTML1 strict doctype.
New concepts
* Added serialized state and creator context security.
* Added an algorithm to determine whether content is allowed to use
certain powerful, hence potentially risky, features.
* Added the WindowOrWorkerGlobalScope mixin as a convenience.
Editorial clarifications
* Browsers should represent punycode addresses as natural unicode text
for the email input type.
* Clarify the concept of last frame time for the seekable IDL attribute
* Browsers that use the the suggestions source element to filter
suggestions should implement substring matching on the label
attribute.
* Users should be able to interact with area elements whether or not
they use a pointing device.
Acknowledgements
Thanks to Tim Berners-Lee for inventing HTML, without which none of this
would exist, Dan Connolly, the many who worked to standardise HTML over
the last couple of decades or so, and the many more who worked on ideas
subsequently incorporated into HTML.
For inestimable work, and the drive to keep HTML up to date, particular
thanks are due to Ian Hickson, and the other editors of the WHATWG: Anne
van Kesteren, Domenic Denicola, Philip Jägenstedt, Simon Pieters.
Thanks to Tab Atkins, who produced the bikeshed tool used to build this
spec, and https://github.com for tools to manage its development.
With apologies to people who have undeservedly not been named, thanks to
People who have contributed to this version of HTML
to complete
"aaaxx", "Acts7", Adrian Bateman, Adrian Roselli, Addison Philips, Alan
Johnson, Alastair Campbell, Alex Danilo, Alexander Schmitz, Alexandros
Spyropoulos, Alexander Surkov, Alice Wonder, "Alohci", "alrdytaken",
Amanda Rush, Amelia Bellamy-Royds, Ana Luiza Bastos, andjc", André
Zanghelini, Andrea Rendine, Andfrew Macpherson, Andrew Romanov, Andy
Carter, Andy Jansson, Anne van Kesteren, Angelo Liao, Anne-Gaelle Colom,
Annop Chawwalitsitthikun, Anup Kumar Maharjan, "aravindxz", Arron Eicholz,
Artemiy Solopov, Artur Janc, Ashley Bischoff, Avram Eisner, "avrljk", Axel
Bocciarelli, 방성범 (Bang Seongbeom), Bert Verhelst, Ben Buchanan, Benjamin
Strauß, "bogdan0083", Boris Zbarsky, Brian Kardell, Carolyn MacLeod,
Chaals McCathie Nevile, Chad Henderson, "Chaoaretasty", Charles La Pierre,
Chris Harvey, Christophe Coevoet, Christophe Strobbe, "Comandeer", Cory
Simmons, Craig Francis, Cyril Concolato, Dan Connolly, Daniel Dafoe,
Daniel Davis, Daniel Glazman, Daniel Weck, Dave Cramer, David French,
David MacDonald, David Singer, David Storey, "dbol55", Deborah Kaplan,
Denis Ah-Kang, Derek Koziol, Diego Lopes Lima, Dmitry Shuralyov, Dom
Talbot, Domenic Denicola, Dominique Hazaël-Massieux, Don Hollander, Doug
Brunelle, Drew McLellan, "duckware", Dylan Barrell, Eli Grey, Emerson
Rocha Luiz, Emil Björklund, Emily Stark, Eric Eggert, Eric Stamper,
Fabrizio Calderan, Florens Verschelde, Florian Rivoal, François Daoust,
Fuqiao Xue, "genwilkerhan", George Gooding, Gervase Markham, Greg Schoppe,
Guido Bouman, "gunlinux", Hans Hillen, Henrik "Henke37" Andersson, Heydon
Pickering, Ian Devlin, Ian Pouncey, Ian Yang, Isadora Coffani dos Santos
Siqueira, Ivan Herman, J.C. Jones, J.S. Choi, Jacob Alvarez, Jake
Archibald, James "thx1111", James Cobban, James Craig, Jan Nelson, Janina
Saika, Jason Edelman, Jason Kiss, Jason White, "jdsmith3000", Jeanne
Spellman, Jeffrey Yasskin, Ji Seongbong, Jihye Hong, Jina Bolton, Job van
Achterberg, John Foliot, Jonathan Kingston, Jon Metz, Jonathan Neal,
Joshua Bell, Jourdan, JP DeVries, jthiyagarajan, "klensin", Kangxi "kxgio"
朕的產生器, Kevin Marks, Kevin Suttle, Lea Verou, Leif Halvard Silli, Léonie
Watson, Liam Quin, Lorenzo Scalfani, Luke Browell, Mallory van Achterberg,
Marat Talanin, Marc G. "mouvedia", Mark Amery, Mark Nottingham, Mark
Rejhon, Mark Rogers, Mark Root-Wiley, Martin Dürst, Martin Janecke, Martyn
Hoyer, Matheus Martins, Matteo Belfiore, "Mattok", Mev-Rael, Micha
Rosenbaum, Michał Miszczyszyn, "Mijabi", "mirabilos", Mike™ Smith, Mike
West, "Moonchild", Morgan Patch, Mort&Mortis, "namitos", Nathan Lorberger,
Neil "ww3", Nhan To-Doan, Nick Levinson, Nico Schneider, Nicolas Hoffmann,
Nicolas Hoizey, Nils Solanki, Pankit Gami, Patrick Dark, Patrick Lauke,
Paul Cotton, Phil Smith, Philip Jägenstedt, Philippe Le Hégaret, Prayag
Verma, Rachel Comerford, Rebeca Ruiz, Reinhardt Hierl, Rich Schwerdtfeger,
Richard Ishida, "RobBelics", Robin Berjon, Rodney Rehm, Romain Deltour,
Roy Tinker, Ruben Martinez, Russ Weakley, "r-romaniuk", Ryosuke Niwa,
Sangwhan Moon, Sara Soueidan, Sailesh Panchang, Sebastian Zartner, Sendil
Kumar N, "SelenIT", Sergei Shoshin, Sergey Artemov, Shane McCarron,
Shwetank Dixit, Šime Vidas, Simon Pieters, "spixi", "stasoid", Stefan
Judis, Steve Comstock, Steve Faulkner, Steven Atkin, Steven Lambert,
Stuart Robson, Takayoshi Kochi, Taylor Hunt, Terence Eden,
"thapliyalshivam", "TheEskhaton", Theresa O’Connor, Thierry Koblentz,
Thomas Beduneau, Thomas Higginbotham, Tim Starling, Timo Huovinen,
Tokushige Kobayashi, Tom Bonnike, Tom Byrer, Travis Leithead, Tyler Deitz,
Tzviya Siegman, "Unor", Vadim Makeev, Varun Dua, Vilmar Neto, Vitaly
Pinchuk, Vladimir Grebnev, "WebDevCA", Wes, "Wolonetz", "woowaEcho", Cindy
Wu Xiaoqian, "Xaviju", Yann Gouffon, Yaroslaw "kciray8", Zach Saucier,
"Zambonifofex", "Zelgadis87"
People who have contributed to previous revisions of HTML 5.x
Thanks to the participants of the Responsive Images Community Group and
the WHATWG for helping to develop the picture element, the srcset
attribute, and the sizes attribute. Special thanks to Bruce Lawson for
originally suggesting, Theresa O’Connor and Ian Hickson for writing the
original srcset specification, and Adrian Bateman for providing the group
with guidance. Contributions also from: David Newton, Ilya Grigorik, John
Schoenick, and Leon de Rijke.
Aankhen, Aaron Boodman, Aaron Leventhal, Adam Barth, Adam de Boor, Adam
Hepton, Adam Klein, Adam Roben, Addison Phillips, Adele Peterson, Adrian
Bateman, Adrian Roselli, Adrian Sutton, Agustín Fernández, Aharon
(Vladimir) Lanin, Ajai Tirumali, Akatsuki Kitamura, Alan Plum, Alastair
Campbell, Alejandro G. Castro, Alex Bishop, Alex Nicolaou, Alex Plescan,
Alex Rousskov, Alexander Farkas, Alexander J. Vincent, Alexander Surkov,
Alexandre Morgaut, Alexey Feldgendler, Алексей Проскуряков (Alexey
Proskuryakov), Alexis Deveria, Alice Boxhall, Allan Clements, Ami
Fischman, Amos Jeffries, Anders Carlsson, André E. Veltstra, Andrea
Rendine, Andreas, Andreas Kling, Andrei Popescu, Andres Gomez, Andrew
Barfield, Andrew Clover, Andrew Gove, Andrew Grieve, Andrew Oakley, Andrew
Sidwell, Andrew Simons, Andrew Smith, Andrew W. Hagen, Andrey V. Lukyanov,
Andry Rendy, Andy Earnshaw, Andy Heydon, Andy Palay, Anjana Vakil, Anna
Belle Leiserson, Anthony Boyd, Anthony Bryan, Anthony Hickson, Anthony
Ramine, Anthony Ricaud, Antonio Olmo Titos, Antti Koivisto, Arkadiusz
Michalski, Arne Thomassen, Aron Spohr, Arphen Lin, Arron Eicholz, Arthur
Stolyar, Arun Patole, Aryeh Gregor, Asbjørn Ulsberg, Ashley Gullen, Ashley
Sheridan, Atsushi Takayama, Aurelien Levy, Ave Wrigley, Axel Dahmen, B
Lingafelter, Bart Humphries, Ben Boyle, Ben Buchanan, Ben Godfrey, Ben
Lerner, Ben Leslie, Ben Meadowcroft, Ben Millard, Benjamin Carl Wiley
Sittler, Benjamin Hawkes-Lewis, Benoit Ren, Bert Bos, Bijan Parsia, Bil
Corry, Bill Mason, Bill McCoy, Billy Wong, Bjartur Thorlacius, Björn
Höhrmann, Blake Frantz, Bob Lund, Bob Owen, Bobby Holly, Boris Zbarsky,
Brad Fults, Brad Neuberg, Brad Spencer, Brady Eidson, Brendan Eich,
Brenton Simpson, Brett Wilson, Brett Zamir, Brian Blakely, Brian Campbell,
Brian Korver, Brian Kuhn, Brian M. Dube, Brian Ryner, Brian Smith, Brian
Wilson, Bryan Sullivan, Bruce Bailey, Bruce D’Arcus, Bruce Lawson, Bruce
Miller, Bugs Nash, C. Williams, Cameron McCormack, Cameron Zemek, Cao
Yipeng, Carlos Amengual, Carlos Gabriel Cardona, Carlos Perelló Marín,
Casey Leask, Cătălin Mariș, Chaals McCathie Nevile, Chao Cai, 윤석찬 (Channy
Yun), Charl van Niekerk, Charles Iliya Krempeaux, Charu Pandhi, Chris
Apers, Chris Cressman, Chris Evans, Chris Morris, Chris Pearce, Chris
Peterson, Chris Weber, Christian Biesinger, Christian Johansen, Christian
Schmidt, Christoph Päper, Christophe Dumez, Christopher Aillon,
Christopher Ferris, Chriswa, Chris Wilson, Clark Buehler, Cole Robison,
Colin Fine, Collin Jackson, Corey Farwell, Corprew Reed, Craig Cockburn,
Csaba Gabor, Csaba Marton, Cynthia Shelly, Dan Brickley, Dan Yoder, Daniel
Barclay, Daniel Bratell, Daniel Brooks, Daniel Brumbaugh Keeney, Daniel
Cheng, Daniel Davis, Daniel Glazman, Daniel Peng, Daniel Schattenkirchner,
Daniel Spång, Daniel Steinberg, Daniel Trebbien, Danny Sullivan, Darin
Adler, Darin Fisher, Darxus, Dave Camp, Dave Hodder, Dave Lampton, Dave
Singer, Dave Townsend, David Baron, David Bloom, David Bruant, David
Carlisle, David E. Cleary, David Egan Evans, David Fink, David Flanagan,
David Gerard, David Håsäther, David Hyatt, David I. Lehn, David John
Burrowes, David Kendal, David MacDonald, David Matja, David Remahl, David
Smith, David Storey, David Vest, David Woolley, DeWitt Clinton, Dean
Edridge, Dean Edwards, Debi Orton, Derek Featherstone, Devarshi Pant,
Devdatta, Dimitri Glazkov, Dimitry Golubovsky, Dirk Pranke, Dirk Schulze,
Dirkjan Ochtman, Divya Manian, Dmitry Titov, dolphinling, Dominic Mazzoni,
Dominique Hazaël-Massieux, Don Brutzman, Doron Rosenberg, Doug Kramer,
Doug Simpkinson, Drew Wilson, Dylan Barrell, Edmund Lai, Eduard Pascual,
Eduardo Vela, Theresa O’Connor, Edward Welbourne, Edward Z. Yang, Ehsan
Akhgari, Eira Monstad, Eitan Adler, Eliot Graff, Elisabeth Robson,
Elizabeth Castro, Elliott Regan, Elliott Sprehn, Elliotte Harold, Eric
Carlson, Eric Casler, Eric Lawrence, Eric Rescorla, Eric Semling, Erik
Arvidsson, Erik Rose, Evan Jacobs, Evan Martin, Evan Prodromou, Evan
Stade, Evert, fantasai, Felix Sasaki, Francesco Schwarz, Francis Brosnan
Blazquez, Franck "Shift" Quélain, François Remy, Frank Barchard, Frank
Liberato, Frank Olivier, Fredrik Söderquist, 鵜飼文敏 (Fumitoshi Ukai), Futomi
Hatano, Gavin Carothers, Gavin Kistner, Gareth Rees, Gary Kačmarčík,
Garrett Smith, Geoff Richards, Geoffrey Garen, Sam Sneddon, Gez Lemon,
George Lund, George Ornbo, Gianmarco Armellin, Giovanni Campagna, Giuseppe
Pascale, Glenn Adams, Glenn Maynard, Graham Klyne, Greg Botten, Greg
Houston, Greg Wilkins, Gregg Tavares, Gregory J. Rosmaita, Grey, Guilherme
Johansson Tramontina, Gytis Jakutonis, Håkon Wium Lie, Habib Virji,
Hallvord Reiar Michaelsen Steen, Hans S. Tømmerhalt, Hans Stimer, Harald
Alvestrand, Henri Sivonen, Henrik Lied, Henry Mason, Henry Story, Heydon
Pickering, Hugh Guiney, Hugh Winkler, Ian Bicking, Ian Clelland, Ian
Davis, Ian Devlin, Ian Fette, Ian Kilpatrick, Ido Green, Ignacio Javier,
Igor Oliveira, Ingvar Stepanyan, Iurii Kucherov, Ivan Enderlin, Ivo
Emanuel Gonçalves, J. King, Jacob Davies, Jacques Distler, Jake Verbaten,
Jakub Łopuszański, Jakub Wilk, James Craig, James Graham, James Greene,
James Justin Harrell, James Kozianski, James M Snell, James Perrett, James
Robinson, Jamie Lokier, Jan Molnár, Janusz Majnert, Jan-Klaas Kollhof,
Jared Jacobs, Jason Duell, Jason Kersey, Jason Kiss, Jason Lustig, Jason
White, Jasper Bryant-Greene, Jasper St. Pierre, Jatinder Mann,
Jdsmith3000, Jed Hartman, Jeff Balogh, Jeff Cutsinger, Jeff Schiller, Jeff
Walden, Jeffrey Yasskin, Jeffrey Zeldman, 胡慧鋒 (Jennifer Braithwaite), Jens
Bannmann, Jens Fendler, Jens Lindström, Jens Meiert, Jer Noble, Jeremey
Hustman, Jeremy Keith, Jeremy Orlow, Jerry Smith, Jeroen van der Meer,
Jesse Renée Beach, Jian Li, Jim Jewett, Jim Ley, Jim Meehan, Jim Michaels,
Jirka Kosek, Jjgod Jiang, João Eiras, Jochen Eisinger, Joe Clark, Joe
Gregorio, Joel Spolsky, Joel Verhagen, Johan Herland, John Boyer, John
Bussjaeger, John Carpenter, John Daggett, John Fallows, John Foliot, John
Harding, John Keiser, John Snyders, John Stockton, John-Mark Bell, Johnny
Stenback, Jon Ferraiolo, Jon Gibbins, Jon Gunderson, Jon Ribbins, Jon
Perlow, Jonas Sicking, Jonathan Cook, Jonathan Kingston, Jonathan Rees,
Jonathan Watt, Jonathan Worent, Jonny Axelsson, Jordan Tucker, Jorgen
Horstink, Jorunn Danielsen Newth, Joseph Kesselman, Joseph Mansfield,
Joseph Pecoraro, Josh Aas, Josh Hart, Josh Levenberg, Josh Matthews,
Joshua Bell, Joshua Berenhaus, Joshua Randall, Jukka K. Korpela, Jules
Clément-Ripoche, Julian Reschke, Julio Lopez, Junkee Song, Jürgen Jeka,
Justin Lebar, Justin Novosad, Justin Rogers, Justin Schuh, Justin
Sinclair, Ka-Sing Chou, Kai Hendry, 呂康豪 (KangHao Lu), Karl Dubost, Karl
Groves, Kartikaya Gupta, Kathy Walton, Keith Hall, Keith Yeung, Kelly
Ford, Kelly Norton, Kevin Benson, Kevin Gadd, Kevin Cole, Kinuko Yasuda
Kornél Pál, Kornel Lesinski, Kris Northfield, Kristof Zelechovski,
Krzysztof Maczyński, 黒澤剛志 (Kurosawa Takeshi), Kyle Barnhart, Kyle Hofmann,
Kyle Huey, Léonard Bouchet, Lachlan Hunt, Larry Masinter, Larry Page, Lars
Gunther, Lars Solberg, Laura Carlson, Laura Granka, Laura L. Carlson,
Laura Wisewell, Laurens Holst, Lawrence Forooghian, Lea Verou, Lee
Kowalkowski, Leif Halvard Silli, Leif Kornstaedt, Lenny Domnitser, Leonard
Rosenthol, Léonie Watson, Leons Petrazickis, Lobotom Dysmon, Logan, Loune,
Łukasz Pilorz, Luke Kenneth Casson Leighton, Maciej Stachowiak, Magnus
Kristiansen, Maik Merten, Majid Valipour, Malcolm Rowe, Manu Sporny,
Manuel Strehl, Manish Tripathi, Mallory van Achterberg, Marat Talanin,
Marc Hoyois, Marcus Bointon, Mark Birbeck, Mark Davis, Mark Miller, Mark
Nottingham, Mark Pilgrim, Mark Rogers, Mark Rowe, Mark Schenk, Mark
Vickers, Mark Wilton-Jones, Marquish, Martijn Wargers, Martin Atkins,
Martin Dürst, Martin Honnen, Martin Janecke, Martin Kutschker, Martin
Nilsson, Martin Thomson, Masataka Yakura, Masatoshi Kimura, Matheus
Martins, Mathias Bynens, Mathieu Henri, Matias Larsson, Matt Falkenhagen,
Matt Garrish, Matt May, Matt Rakow, Matt Schmidt, Matt Wright, Matthew
Gregan, Matthew Mastracci, Matthew Noorenberghe, Matthew Raymond, Matthew
Thomas, Mattias Waldau, Max Romantschuk, Menachem Salomon, Menno van
Slooten, Mia Lipner, Micah Dubinko, Michael "Ratt" Iannarelli, Michael A.
Nachbaur, Michael A. Puls II, Michael Carter, Michael Daskalov, Michael
Day, Michael Dyck, Michael Enright, Michael Gratton, Michael Nordman,
Michael Powers, Michael Rakowski, Michael(tm) Smith, Michael Walmsley,
Michal Zalewski, Michel Fortin, Michelangelo De Simone, Michiel Bijl,
Michiel van der Blonk, Mihai Şucan, Mihai Parparita, Mike Brown, Mike
Dierken, Mike Dixon, Mike Hearn, Mike Schinkel, Mike Shaver, Mikko
Rantalainen, Mitchell Evan, Mohamed Zergaoui, Mohammad Al Houssami, Momdo
Nakamura, Mounir Lamouri, Mount-root-yy, Ms2ger, Nadia Heninger, Nhan,
NARUSE Yui, Neil Deakin, Neil Rashbrook, Neil Soiffer, Nicholas Shanks,
Nicholas Stimpson, Nicholas Zakas, Nick Levinson, Nickolay Ponomarev,
Nicolas Gallagher, Noah Mendelsohn, Noah Slater, Noel Gordon, Nolan Waite,
NoozNooz42, Norbert Lindenberg, Ojan Vafai, Olaf Hoffmann, Olav Junker
Kjær, Oldřich Vetešník, Oli Studholme, Oliver Hunt, Oliver Rigby, Olivier
Gendrin, Olli Pettay, oSand, Pablo Flouret, Patrick Garies, Patrick H.
Lauke, Patrik Persson, Paul Adenot, Paul Cotton, Paul Norman, Per-Erik
Brodin, Perry Smith, Peter Beverloo, Peter Karlsson, Peter Kasting, Peter
Lemieux, Peter Moulder, Peter Occil, Peter Stark, Peter Van der Beken,
Peter Winnberg, Peter-Paul Koch, Phil Pickering, Philip Taylor, Philip
TAYLOR, Philippe De Ryck, Prateek Rungta, Pravir Gupta, Prayag Verma, 李普君
(Pujun Li), Rabab Gomaa, Rachid Finge, Rachel White, Rafael Weinstein,
Rafał Miłecki, Raj Doshi, Rajas Moonka, Ralf Stoltze, Ralph Giles, Raphael
Champeimont, Rebeca Ruiz, Remci Mizkur, Remco, Remy Sharp, Rene Saarsoo,
Rene Stach, Ric Hardacre, Rich Clark, Rich Doughty, Richa Rupela, Richard
Ishida, Richard Schwerdtfeger, Rigo Wenning, Rikkert Koppes, Rimantas
Liubertas, Riona Macnamara, Rob Ennals, Rob Jellinghaus, Rob S, Robert
Blaut, Robert Collins, Robert Kieffer, Robert Millan, Robert O’Callahan,
Robert Sayre, Robin Berjon, Robin Schaufler, Rodger Combs, Rodney Rehm,
Roland Steiner, Roma Matusevich, Roman Ivanov, Roy Fielding, Ruud
Steltenpool, Ryan King, Ryan Rion, Ryosuke Niwa, S. Mike Dierken, Sailesh
Panchang, Salvatore Loreto, Sam Dutton, Sam Kuper, Sam Ruby, Sam Weinig,
Samuel Bronson, Samy Kamkar, Sander van Lambalgen, Sarven Capadisli, 佐藤雅之
(SATO Masayuki), Scott González, Scott Hess, Sean Fraser, Sean Hayes, Sean
Hogan, Sean Knapp, Sebastian Markbåge, Sebastian Schnitzenbaumer, Sendil
Kumar N, Seth Call, Seth Dillingham, Shannon Moeller, Shanti Rao, Shaun
Inman, Shiki Okasaka, Shubheksha Jalan, Sierk Bornemann, Sigbjørn Finne,
Sigbjørn Vik, Silver Ghost, Silvia Pfeiffer, Šime Vidas, Simo Sutela,
Simon Montagu, Simon Spiegel, skeww, Smylers, Srirama Chandra Sekhar
Mogali, Stanton McCandlish, Stefan Götz, Stefan Håkansson, Stefan
Haustein, Stefan Santesson, Stefan Schumacher, Stefan Weiss, Steffen
Meschkat, Stephane Corlosquet, Stephen Cunliffe, Stephen Ma, Stephen
White, Steve Comstock, Steve Runyon, Steven Bennett, Steven Garrity,
Steven Tate, Steven Wood, Stewart Brodie, Stuart Ballard, Stuart P
Bentley, Stuart Langridge, Stuart Parmenter, Subramanian Peruvemba, Sunava
Dutta, Susan Borgrink, Susan Lesch, Sylvain Pasche, T. J. Crowder, Tab
Atkins-Bittner, Taiju Tsuiki, Takayoshi Kochi, Takeshi Kurosawa, Takeshi
Yoshino, Tantek Çelik, 田村健人 (TAMURA Kent), Taylor Hunt, Ted Mielczarek,
Terrence Wood, Thijs van der Vossen, Thomas Broyer, Thomas Koetter, Thomas
O’Connor, Tim Baxter, Tim Altman, Tim Johansson, TJ VanToll, Toby Inkster,
Tobi Reif, Todd Moody, Tom Baker, Tom Pike, Tommy Thorsen, Tony Ross,
Tooru Fujisawa, Travis Leithead, Trevor Saunders, triple-underscore, Tyler
Close, Unor, Victor Carbune, Vipul Snehadeep Chawathe, Vitya Muhachev,
Vladimir Katardjiev, Vladimir Vukićević, voracity, Wakaba, Wayne Carr,
Wayne Pollock, Wellington Fernando de Macedo, Wes, Weston Ruter, Wilhelm
Joys Andersen, Will Levine, William Chen, William Swanson, Wladimir
Palant, Wojciech Mach, Wolfram Kriesing, Xan Gregg, xenotheme, Yang Chen,
Ye-Kui Wang, Yehuda Katz, Yi-An Huang, Yngve Nysaeter Pettersen, Yoav
Weiss, Yonathan Randolph, Yuzo Fujishima, Zhenbin Xu, Zoltan Herczeg, and
Øistein E. Andersen,
for their useful comments, both large and small, that have led to changes
to this specification over the years.
Thanks also to everyone who has ever posted about HTML to their blogs,
public mailing lists, or forums, including all the contributors to the
various W3C HTML and Web Platform WG lists and the various WHATWG lists.
The Blue Robot Player sprite used in the canvas demo is based on a work by
JohnColburn. (CC BY-SA 3.0)
The photograph of robot 148 climbing the tower at the FIRST Robotics
Competition 2013 Silicon Valley Regional is based on a work by Lenore
Edman. (CC BY 2.0)
The fancy image of the letter O with a child sitting in it reading a book
is by Jessie Wilcox Smith and is in the Public Domain.
Parts of this specification are © Copyright 2004-2014 Apple Inc., Mozilla
Foundation, and Opera Software ASA. You are granted a license to use,
reproduce and create derivative works of this document.
#willful-violationReferenced in:
* 2.2.2. Dependencies (2)
* 2.2.4. Interactions with XPath and XSLT (2)
* 4.10.5.1.5. E-mail state (type=email)
* 7.1.3.7. Integration with the JavaScript job queue
* 9.2. Parsing XML documents (2)
* 11.3.4. Other elements, attributes and APIs
#thisReferenced in:
* 1.7.2. Typographic conventions (2)
#elementdef-thisReferenced in:
* 1.7.2. Typographic conventions
#fingerprinting-vectorReferenced in:
* 1.8. Privacy concerns
* 2.1.5. Plugins
* 2.2.1. Conformance classes
* 2.6.2. Processing model
* 3.1.2. Resource metadata management
* 4.7.13.6. Offsets into the media resource
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.20. Reset Button state (type=reset)
* 11.3.4.1. Plugins (2)
#documentReferenced in:
* 2.1. Terminology
* 10.4.2. Images
#html-documentReferenced in:
* 2.1. Terminology
* 2.2.2. Dependencies
* 2.2.4. Interactions with XPath and XSLT
* 2.5.1. Terminology
* 3.2.5. Global attributes
* 3.2.5.2. The lang and xml:lang attributes (2) (3)
* 3.2.5.4. The xml:base attribute (XML only)
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
* 4.2.5.3. Pragma directives
* 4.2.5.5. Specifying the document’s character encoding (2)
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.18. SVG
* 4.12.2. The noscript element (2) (3)
* 4.12.3. The template element (2)
* 4.15.1. Case-sensitivity (2) (3)
* 6.1. Browsing contexts
* 6.7.1. Navigating across documents
* 6.7.2. Page load processing model for HTML files
* 6.7.4. Page load processing model for text files
* 6.7.6. Page load processing model for media
* 6.7.7. Page load processing model for content that uses plugins
* 6.7.8. Page load processing model for inline content that doesn’t have
a DOM
* 7.4. Dynamic markup insertion
* 8.2. Parsing HTML documents
* 8.4. Parsing HTML fragments
* 10.3.9. Tables
* 12.1. text/html
#xml-documentReferenced in:
* 2.1. Terminology (2)
* 2.2.2. Dependencies
* 3.2.2. Elements in the DOM
* 3.2.5. Global attributes (2)
* 3.2.5.2. The lang and xml:lang attributes
* 3.2.5.4. The xml:base attribute (XML only)
* 4.2.5. The meta element
* 4.2.5.3. Pragma directives (2)
* 4.7.6. The iframe element (2)
* 4.12.2. The noscript element
* 4.15.1. Case-sensitivity (2)
* 6.7.1. Navigating across documents (2)
* 7.4. Dynamic markup insertion
* 7.4.1. Opening the input stream (2)
* 7.4.2. Closing the input stream (2)
* 7.4.3. document.write() (2)
* 7.4.4. document.writeln()
* 9.2. Parsing XML documents (2)
#in-parallelReferenced in:
* 2.6.2. Processing model
* 4.7.5. The img element (2) (3) (4) (5)
* 4.7.6. The iframe element
* 4.7.13.5. Loading the media resource (2) (3) (4) (5) (6)
* 4.7.13.9. Seeking
* 4.7.13.11.3. Sourcing out-of-band text tracks (2)
* 4.8.5. Downloading resources
* 4.8.6.5. Link type "icon"
* 4.10.5.1.17. File Upload state (type=file)
* 4.12.1. The script element (2) (3) (4) (5) (6)
* 4.12.4. The canvas element
* 6.6.2. The History interface
* 6.7.1. Navigating across documents (2) (3)
* 7.1.3.2. Fetching scripts
* 7.1.4.2. Processing model (2) (3)
* 7.5. Timers
* 7.6.2. Printing
* 7.8. Images (2) (3) (4) (5) (6) (7)
#immediatelyReferenced in:
* 4.2.3. The base element
* 4.2.7. Interactions of styling and scripting
* 4.7.13.2. Location of the media resource
* 4.7.13.5. Loading the media resource
* 4.7.13.8. Playing the media resource
* 4.7.13.11.3. Sourcing out-of-band text tracks
* 4.12.1.1. Processing model (2)
* 4.12.1.5. Interaction of script elements and XSLT
* 5.4.4. Processing model (2)
* 5.6.2. Making entire documents editable: The designMode IDL attribute
* 6.7.10. History traversal
#http-resourceReferenced in:
* 4.7.13.4. Network states (2)
#mime-typeReferenced in:
* 1.6. HTML vs XML Syntax
* 2.1.1. Resources
* 2.1.2. XML compatibility (2)
* 2.2.2. Dependencies
* 2.6.4. Determining the type of a resource
* 4.2.4. The link element
* 4.2.4.2. Processing the type attribute (2) (3)
* 4.2.6. The style element
* 4.7.5. The img element
* 4.7.7. The embed element
* 4.7.13.3. MIME types (2) (3) (4) (5)
* 4.7.13.5. Loading the media resource
* 4.7.13.10.2. Selecting specific audio and video tracks declaratively
* 4.8.2. Links created by a and area elements
* 4.8.5. Downloading resources
* 4.10.5. The input element
* 4.12.1.2. Scripting languages (2) (3) (4)
* 4.12.4.2. Serializing bitmaps to a file
* 5.7.2. The drag data store (2) (3)
* 5.7.5. Drag-and-drop processing model
* 6.7.1. Navigating across documents (2)
* 6.7.9. Navigating to a fragment
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods (2) (3)
(4) (5) (6) (7) (8) (9) (10) (11)
* 7.7.1.3.2. Sample user interface
* 11.2. Non-conforming features
* 11.3.4.1. Plugins (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
(14)
#valid-mime-typeReferenced in:
* 2.1.1. Resources
* 4.2.4. The link element
* 4.2.4.2. Processing the type attribute
* 4.2.6. The style element
* 4.7.4. The source element (2)
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.8.2. Links created by a and area elements
* 4.12.1. The script element (2)
* Attributes (2)
#html-mime-typeReferenced in:
* 2.2.1. Conformance classes
* 6.7.1. Navigating across documents
* 6.7.9. Navigating to a fragment
* 8. The HTML syntax
#critical-subresourceReferenced in:
* 4.2.4.3. Obtaining a resource from a link element (2) (3)
* 4.2.6. The style element (2) (3) (4)
#html-elementReferenced in:
* 3.1.3. DOM tree accessors
* 3.2.2. Elements in the DOM (2) (3) (4)
* 3.2.3.1. Attributes
* 3.2.4. Content models (2) (3)
* 3.2.5. Global attributes (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 3.2.5.1. The title attribute
* 3.2.5.2. The lang and xml:lang attributes (2) (3) (4) (5)
* 3.2.5.3. The translate attribute (2) (3) (4) (5)
* 3.2.5.4. The xml:base attribute (XML only) (2)
* 3.2.5.5. The dir attribute (2) (3) (4)
* 3.2.5.6. The style attribute
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
(2)
* 3.2.7.1. Authoring conformance criteria for bidirectional-algorithm
formatting characters (2)
* 3.2.8.1. ARIA Authoring Requirements
* 3.2.8.2. Conformance Checker Implementation Requirements
* 3.2.8.3. User Agent Implementation Requirements (2)
* 3.2.8.3.1. ARIA Role Attribute (2)
* 3.2.8.3.2. State and Property Attributes
* 4.3.1. The body element
* 4.4.1. The p element
* 4.15.1. Case-sensitivity (2) (3) (4) (5)
* 4.15.2. Pseudo-classes
* 5.1. The hidden attribute
* 5.5.2. The accesskey attribute
* 5.7.7. The draggable attribute
* 6.3.3. Named access on the Window object (2)
* 7.1.5.1. Event handlers
* 7.1.5.2. Event handlers on elements, Document objects, and Window
objects (2) (3)
* 8.1.2. Elements
* 8.1.2.4. Optional tags
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15) (16) (17)
* 8.2.5.4.13. The "in table body" insertion mode
* 8.2.5.4.14. The "in row" insertion mode
* 8.2.5.4.15. The "in cell" insertion mode (2) (3) (4)
* 8.2.5.4.17. The "in select in table" insertion mode
* 8.3. Serializing HTML fragments (2)
* 10.2. The CSS user agent style sheet and presentational hints
* 11.3.3. Frames
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14)
(15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26) (27) (28)
(29) (30) (31) (32) (33) (34) (35) (36) (37) (38) (39) (40) (41) (42)
(43) (44) (45) (46) (47) (48) (49) (50) (51) (52) (53) (54) (55) (56)
(57) (58) (59) (60) (61) (62) (63) (64) (65) (66) (67) (68) (69) (70)
(71) (72) (73) (74)
#element-typeReferenced in:
* 3.2.2. Elements in the DOM
* 8.2. Parsing HTML documents
#xml-compatibleReferenced in:
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
* 4.7.7. The embed element
#xml-mime-typeReferenced in:
* 1.6. HTML vs XML Syntax
* 2.1. Terminology (2)
* 4.7.8. The object element (2)
* 6.7.1. Navigating across documents
* 6.7.9. Navigating to a fragment
* 12.3. application/xhtml+xml
#ignoredReferenced in:
* 3.2.5.2. The lang and xml:lang attributes
* 4.10.5.3. Common input element attributes
#child-text-contentReferenced in:
* 3.1.3. DOM tree accessors (2)
* 4.2.2. The title element (2)
* 4.2.6. The style element
* 4.5.16. The time element
* 4.10.10. The option element
* 4.12.1. The script element (2)
* 4.12.1.1. Processing model (2)
* 4.12.2. The noscript element
#document-inserted-intoReferenced in:
* 3.2.4.2.6. Embedded content
* 4.2.5.1. Standard metadata names
* 4.2.5.3. Pragma directives (2)
* 4.2.6. The style element
* 4.7.5. The img element (2)
* 4.7.6. The iframe element
* 4.7.8. The object element
* 4.8.6.11. Link type "stylesheet"
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.17.3. Association of controls and forms (2)
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute
* 4.10.18.7.2. Processing model
* 4.12.1.1. Processing model (2) (3)
* 4.12.1.5. Interaction of script elements and XSLT
* 7.1.4.1. Definitions
* 7.1.4.3. Generic task sources
* 10.4.2. Images
#document-remove-an-element-from-a-documentReferenced in:
* 4.2.5.1. Standard metadata names
* 4.2.6. The style element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.8. The object element
* 4.7.13.8. Playing the media resource
* 4.7.13.19. Best practices for implementors of media elements
* 4.10.17.3. Association of controls and forms
* 4.11.4. The dialog element
#liveReferenced in:
* 2.7.2.2. The HTMLFormControlsCollection interface
* 3.1.3. DOM tree accessors
* 4.7.13.10. Media resources with multiple media tracks (2)
* 4.7.13.11.5. Text track API (2)
* 4.7.16.2. Processing model
* 4.10.3. The form element (2)
* 4.10.20.3. The constraint validation API
* 5.7.3. The DataTransfer interface (2)
* 11.3.4.1. Plugins (2) (3) (4)
#fireReferenced in:
* 3.1.2. Resource metadata management
* 4.2.4.3. Obtaining a resource from a link element (2)
* 4.2.6. The style element (2)
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13)
* 4.7.6. The iframe element
* 4.7.7. The embed element (2)
* 4.7.8. The object element (2) (3) (4) (5)
* 4.7.10. The video element
* 4.7.13.5. Loading the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23)
(24) (25)
* 4.7.13.6. Offsets into the media resource (2) (3)
* 4.7.13.7. Ready states (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.7.13.8. Playing the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17)
* 4.7.13.9. Seeking (2) (3) (4)
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2)
* 4.7.13.11.1. Text track model
* 4.7.13.11.2. Sourcing in-band text tracks
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5) (6)
* 4.7.13.11.5. Text track API
* 4.7.13.13. User interface
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.15. Checkbox state (type=checkbox) (2)
* 4.10.5.1.16. Radio Button state (type=radio) (2)
* 4.10.5.1.17. File Upload state (type=file) (2) (3) (4)
* 4.10.5.1.19. Image Button state (type=image) (2)
* 4.10.5.5. Common event behaviors (2) (3) (4) (5) (6) (7)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.19. APIs for text field selections (2) (3)
* 4.10.20.2. Constraint validation
* 4.10.20.3. The constraint validation API (2)
* 4.10.21.3. Form submission algorithm (2)
* 4.10.22. Resetting a form
* 4.11.1. The details element
* 4.11.4. The dialog element (2)
* 4.12.1.1. Processing model (2) (3) (4) (5)
* 5.4.4. Processing model
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.7.10. History traversal (2) (3)
* 6.7.11. Unloading documents (2)
* 6.7.12. Aborting a document load
* 6.7.13. Browser state (2)
* 7.6.2. Printing (2)
* 7.7.1.2. Language preferences
* 8.2.6. The end (2) (3)
* 10.5.4. The input element as a text entry widget.
* 10.5.15. The textarea element
* 11.3.2. The marquee element (2) (3) (4)
* 11.3.3. Frames (2)
#dispatchReferenced in:
* 2.1.4. Scripting
* 5.3. Activation
* 5.4.4. Processing model
* 5.7.4. The DragEvent interface
* 5.7.5. Drag-and-drop processing model (2)
* 6.7.11. Unloading documents
* 7.1.3.9. Runtime script errors
* 7.1.3.10. Unhandled promise rejections
* 7.1.3.10.1. The HostPromiseRejectionTracker implementation
* 7.1.5.1. Event handlers
* 7.1.5.3. Event firing (2)
* 7.1.5.4. Events and the Window object
#trustedReferenced in:
* 4.7.13.5. Loading the media resource (2)
* 4.7.13.6. Offsets into the media resource
* 4.7.13.11.2. Sourcing in-band text tracks
* 4.7.13.11.3. Sourcing out-of-band text tracks (2)
* 4.7.13.11.5. Text track API
* 4.10.7. The select element
* 4.10.22. Resetting a form
* 5.4.4. Processing model
* 5.7.4. The DragEvent interface
* 6.1.5. Browsing context names (2)
* 6.6.4. The Location interface (2)
* 6.7.10. History traversal (2) (3)
* 6.7.11. Unloading documents (2)
* 7.1.3.9. Runtime script errors
* 7.1.3.10. Unhandled promise rejections
* 7.1.3.10.1. The HostPromiseRejectionTracker implementation
* 7.1.5.3. Event firing (2)
#concept-pluginReferenced in:
* 2.1.5. Plugins (2) (3) (4) (5) (6) (7)
* 4.7.7. The embed element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18)
* 4.7.8. The object element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
* 4.7.9. The param element (2) (3) (4)
* 4.10.21.4. Constructing the form data set (2)
* 6.5. Sandboxing (2)
* 6.7.1. Navigating across documents (2) (3)
* 6.7.7. Page load processing model for content that uses plugins
* 10.4.1. Embedded content
* 11.2. Non-conforming features
* 11.3.1. The applet element (2) (3) (4) (5) (6)
* 11.3.4.1. Plugins (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
(14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26) (27)
* Elements (2)
#securedReferenced in:
* 4.7.7. The embed element (2)
* 4.7.8. The object element (2) (3)
* 6.5. Sandboxing
* 6.7.7. Page load processing model for content that uses plugins
#character-encodingReferenced in:
* 2.2.2. Dependencies (2)
* 2.5.2. Parsing URLs
* 4.2.3. The base element (2)
* 4.2.5.3. Pragma directives (2) (3)
* 4.2.5.5. Specifying the document’s character encoding (2) (3)
* 4.10.3. The form element
* 4.10.21.5. Selecting a form submission encoding
* 4.10.21.7. Multipart form data
* 4.12.1. The script element
* 6.1. Browsing contexts
* 6.1.6. Script settings for browsing contexts
* 8.2.2.2. Determining the character encoding (2)
* 12.1. text/html (2)
#encoding-labelsReferenced in:
* Attributes (2)
#utf-16-encodingReferenced in:
* 2.1.6. Character encodings (2)
* 8.2.2.2. Determining the character encoding
* 8.2.2.4. Changing the encoding while parsing (2)
#ascii-compatible-encodingReferenced in:
* 2.1.6. Character encodings
* 4.2.5.5. Specifying the document’s character encoding (2)
* 4.10.3. The form element
* 4.10.21.7. Multipart form data
* 8.2.2.2. Determining the character encoding
* Attributes
#code-unitReferenced in:
* 2.1.6. Character encodings (2) (3)
#unicode-code-pointReferenced in:
* 2.1.6. Character encodings
* 8.2.1. Overview of the parsing model
#characterReferenced in:
* 8.2.2.5. Preprocessing the input stream
#unicode-characterReferenced in:
* 2.1.6. Character encodings
* 3.2.4.2.5. Phrasing content
* 8.2.2.5. Preprocessing the input stream
#code-unit-lengthReferenced in:
* 4.10.5.3.1. The maxlength and minlength attributes
* 4.10.11. The textarea element (2)
* 4.10.18.3. Limiting user input length: the maxlength attribute (2)
* 4.10.18.4. Setting minimum input length requirements: the minlength
attribute
#conforming-documentReferenced in:
* 1.10. Conformance requirements for authors
* 2.2.1. Conformance classes
* 2.2.3. Extensibility (2) (3) (4) (5) (6)
* 4.3.1. The body element
* 4.12.2. The noscript element
#rendering-support-the-suggested-default-renderingReferenced in:
* 2.2.1. Conformance classes (2)
* 3.2.7.2. User agent conformance criteria
* 4.11.4. The dialog element
* 10. Rendering
#lack-scripting-supportReferenced in:
* 2.2.1. Conformance classes
* 8.2.1. Overview of the parsing model
#hardware-limitationsReferenced in:
* 4.7.5. The img element
* 8.2.5. Tree construction
#getting-an-encodingReferenced in:
* 2.6.5. Extracting character encodings from meta elements (2)
* 4.8.6.11. Link type "stylesheet"
* 4.10.21.5. Selecting a form submission encoding
* 4.12.1.1. Processing model (2)
* 8.2.2.2. Determining the character encoding
* 8.2.5.4.4. The "in head" insertion mode
#getting-an-output-encodingReferenced in:
* 4.10.21.5. Selecting a form submission encoding
#utf-8-decodeReferenced in:
* 2.2.2. Dependencies
* 6.7.1. Navigating across documents
* 7.1.3.2. Fetching scripts (2)
#utf-8-decode-without-bomReferenced in:
* 2.2.2. Dependencies
* 3.1.2. Resource metadata management
#utf-8-decode-without-bom-or-failReferenced in:
* 6.7.9. Navigating to a fragment
#schemedef-aboutReferenced in:
* 2.2.2. Dependencies (2)
* 2.5.1. Terminology (2)
* 6.1. Browsing contexts
* 6.3. The Window object
* 6.6.4. The Location interface
* 6.7.1. Navigating across documents
* 7.4.1. Opening the input stream
* 11.3.3. Frames
#schemedef-blobReferenced in:
* 2.2.2. Dependencies
* 7.1.3.4. Calling scripts
#schemedef-data-urlReferenced in:
* 2.6.2. Processing model (2)
* 4.10.21.3. Form submission algorithm
* 4.12.4. The canvas element (2) (3)
* 6.4. Origin
#cookie-stringReferenced in:
* 3.1.2. Resource metadata management
#referrer-policyReferenced in:
* 6.7.1. Navigating across documents
#date-objectReferenced in:
* 4.7.13.6. Offsets into the media resource
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
#hasinstanceReferenced in:
* 6.2.3.3. CrossOriginGetOwnPropertyHelper ( O, P )
#isconcatspreadableReferenced in:
* 6.2.3.3. CrossOriginGetOwnPropertyHelper ( O, P )
#toprimitiveReferenced in:
* 6.6.4. The Location interface
#tostringtagReferenced in:
* 6.2.3.3. CrossOriginGetOwnPropertyHelper ( O, P )
#treeReferenced in:
* 2.7.1. Reflecting content attributes in IDL attributes (2)
* 3.2.5. Global attributes
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.17.3. Association of controls and forms
* 8.2.5.1. Creating and inserting nodes
* 11.1. Obsolete but conforming features (2)
#tree-orderReferenced in:
* 2.1.3. DOM trees
* 2.4.9. References
* 2.5.1. Terminology
* 2.7.2.1. The HTMLAllCollection interface (2)
* 2.7.2.2. The HTMLFormControlsCollection interface (2) (3) (4) (5) (6)
* 2.7.2.3. The HTMLOptionsCollection interface (2)
* 3.1.3. DOM tree accessors (2) (3)
* 3.2.5.5. The dir attribute
* 3.2.6. The innerText IDL attribute (2)
* 4.2.3. The base element (2)
* 4.2.5.1. Standard metadata names (2)
* 4.2.6. The style element
* 4.3.9.1. Creating an outline (2)
* 4.4.6. The ol element
* 4.7.8. The object element
* 4.7.13.5. Loading the media resource
* 4.7.13.11.1. Text track model
* 4.7.16.2. Processing model (2)
* 4.8.6.1. Link type "alternate"
* 4.8.6.5. Link type "icon"
* 4.9.1. The table element (2) (3)
* 4.10.3. The form element (2) (3)
* 4.10.4. The label element (2)
* 4.10.5.3.9. The list attribute
* 4.10.7. The select element (2) (3) (4) (5) (6) (7)
* 4.10.10. The option element (2)
* 4.10.18.7.2. Processing model
* 4.10.20.2. Constraint validation (2) (3)
* 4.10.21.2. Implicit submission
* 4.10.21.4. Constructing the form data set (2)
* 4.11.3.4. Using the input element to define a command
* 4.11.3.7. Using the accesskey attribute on a legend element to define
a command
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements
* 4.11.4. The dialog element
* 4.12.1.1. Processing model
* 5.4.2. Data model (2)
* 5.4.3. The tabindex attribute (2)
* 5.4.4. Processing model
* 5.7.5. Drag-and-drop processing model
* 6.1.1. Nested browsing contexts
* 6.3.3. Named access on the Window object (2)
* 6.7.9. Navigating to a fragment (2)
* 7.1.4.2. Processing model
* 8.3. Serializing HTML fragments
* 8.4. Parsing HTML fragments
* 9.3. Serializing XML fragments
* 9.4. Parsing XML fragments
* 11.3.1. The applet element
#rootReferenced in:
* 3.1.3. DOM tree accessors (2) (3) (4)
#inclusive-ancestorReferenced in:
* 3.2.5.2. The lang and xml:lang attributes
#document-elementReferenced in:
* 3.1.3. DOM tree accessors (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12)
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute (2) (3)
* 4.1.1. The html element
* 4.2.5.1. Standard metadata names
* 4.7.5. The img element (2) (3)
* 4.7.6. The iframe element
* 4.8.6.1. Link type "alternate"
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute (2)
* 5.4.4. Processing model (2) (3)
* 5.4.6. Focus management APIs (2) (3)
* 5.6.2. Making entire documents editable: The designMode IDL attribute
* 8.1. Writing HTML documents (2) (3)
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 8.2.5.4.2. The "before html" insertion mode
* 9.4. Parsing XML fragments (2)
* 12.3. application/xhtml+xml (2)
#in-a-documentReferenced in:
* 4.2.6. The style element
* 4.7.7. The embed element (2)
* 4.7.8. The object element
* 4.7.13.8. Playing the media resource (2)
* 4.8.6.11. Link type "stylesheet" (2) (3) (4) (5)
* 4.10.17.3. Association of controls and forms
* 4.11.3.1. Facets
* 4.11.4. The dialog element
* 4.12.1.1. Processing model (2) (3) (4)
* 5.5.3. Processing model
* 11.3.1. The applet element
* 11.3.3. Frames
#quirks-modeReferenced in:
* 1.10.2. Syntax errors
* 4.8.6.11. Link type "stylesheet"
* 4.9.12.1. Forming a table
* 4.15.1. Case-sensitivity
* 8.2.5.4.1. The "initial" insertion mode (2)
* 8.2.5.4.7. The "in body" insertion mode
* 8.4. Parsing HTML fragments (2)
* 10.3.3. Flow content
* 10.3.9. Tables (2)
* 10.3.10. Margin collapsing quirks (2) (3) (4)
* 10.3.11. Form controls
* 10.4.2. Images (2)
#limited-quirks-modeReferenced in:
* 4.15.1. Case-sensitivity
* 8.2.5.4.1. The "initial" insertion mode
* 8.4. Parsing HTML fragments (2)
#no-quirks-modeReferenced in:
* 1.10.2. Syntax errors
* 4.15.1. Case-sensitivity
* 8.4. Parsing HTML fragments
#base-url-change-stepsReferenced in:
* 2.5.3. Dynamic changes to base URLs
#affected-by-a-base-url-changeReferenced in:
* 2.5.3. Dynamic changes to base URLs (2)
#supported-tokensReferenced in:
* 4.2.4. The link element (2) (3)
* 4.7.6. The iframe element
* 4.8.2. Links created by a and area elements (2) (3)
#mutation-observersReferenced in:
* 8.2.5.1. Creating and inserting nodes
#error-occurs-during-reading-of-the-objectReferenced in:
* 7.8. Images
#cleanup-indexed-database-transactionsReferenced in:
* 7.1.4.2. Processing model
#detach-from-a-media-elementReferenced in:
* 4.7.13.5. Loading the media resource
#viewportReferenced in:
* 4.7.1. Introduction (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14)
* 4.7.3. The picture element
* 4.7.5. The img element (2) (3) (4) (5)
* 4.11.4. The dialog element (2) (3) (4) (5)
* 5.4.2. Data model (2) (3) (4)
* 5.4.4. Processing model (2) (3) (4) (5)
* 5.4.6. Focus management APIs (2)
* 5.7.5. Drag-and-drop processing model
* 6.7.9. Navigating to a fragment
* 10.3.2. The page (2) (3)
* 10.6. Frames and framesets (2)
* 10.9. Unstyled XML documents
#replaced-elementReferenced in:
* 10.4.1. Embedded content (2) (3) (4) (5)
* 10.4.2. Images (2) (3)
* 10.7.3. Editing hosts
#intrinsic-dimensionsReferenced in:
* 2.2.2. Dependencies
* 4.7.5. The img element (2) (3) (4) (5) (6) (7)
* 4.7.10. The video element
* 4.12.4. The canvas element
* 10.4.1. Embedded content
* 10.4.2. Images (2)
#named-colorReferenced in:
* 2.4.6. Colors
#css-intrinsic-widthReferenced in:
* 4.7.5. The img element (2)
* 4.7.10. The video element (2) (3)
* 4.7.19. Dimension attributes (2)
* 4.12.4. The canvas element (2)
* 7.8. Images (2)
#css-intrinsic-heightReferenced in:
* 4.7.10. The video element (2) (3)
* 4.7.19. Dimension attributes (2)
* 4.12.4. The canvas element (2)
* 7.8. Images (2)
* 10.5.11. The marquee element
#paint-sourceReferenced in:
* 4.7.5. The img element
* 4.7.10. The video element
* 4.12.4. The canvas element
#default-object-sizeReferenced in:
* 4.7.10. The video element
#webvttReferenced in:
* 4.7.12. The track element (2) (3) (4)
* 4.7.13.11.1. Text track model (2)
* 4.7.13.11.3. Sourcing out-of-band text tracks
* 4.7.13.11.4. Guidelines for exposing cues in various formats as text
track cues
* 10.4.1. Embedded content
#webvtt-fileReferenced in:
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.13.11.7. Text tracks describing chapters
#webvtt-file-using-cue-textReferenced in:
* 4.7.12. The track element
#webvtt-file-using-chapter-title-textReferenced in:
* 4.7.12. The track element
#webvtt-file-using-only-nested-cuesReferenced in:
* 4.7.12. The track element
#webvtt-parserReferenced in:
* 4.7.13.11.3. Sourcing out-of-band text tracks
#rules-for-updating-the-display-of-webvtt-text-tracksReferenced in:
* 4.7.13.8. Playing the media resource
* 4.7.13.11.1. Text track model (2)
* 4.7.13.11.3. Sourcing out-of-band text tracks
* 10.4.1. Embedded content (2)
#text-track-cue-writing-directionReferenced in:
* 4.7.13.11.1. Text track model
#element-attrdef-aria-roleReferenced in:
* 3.2.5. Global attributes
* 3.2.8.1. ARIA Authoring Requirements (2)
* 3.2.8.2. Conformance Checker Implementation Requirements
* 3.2.8.3.1. ARIA Role Attribute (2)
* Changes between Working Draft 2 and the First Public Working Draft
#element-attrdef-aria-ariaReferenced in:
* 3.2.8.1. ARIA Authoring Requirements (2)
* 3.2.8.2. Conformance Checker Implementation Requirements
* 4.3.8. The footer element
#client-message-queueReferenced in:
* 8.2.6. The end
#mathml-annotation-xmlReferenced in:
* 4.7.17. MathML
#mathml-merrorReferenced in:
* 4.7.17. MathML
#mathml-miReferenced in:
* 4.7.17. MathML
#mathml-mnReferenced in:
* 4.7.17. MathML
#mathml-moReferenced in:
* 4.7.17. MathML
#mathml-msReferenced in:
* 4.7.17. MathML
#mathml-mtextReferenced in:
* 4.7.17. MathML (2)
#applicable-specificationReferenced in:
* 2.2.3. Extensibility
* 11.3.4. Other elements, attributes and APIs
#case-sensitiveReferenced in:
* 2.3. Case-sensitivity and string comparison
* 2.4.9. References
* 3.1.3. DOM tree accessors
* 4.4.6. The ol element
* 4.9.11. Attributes common to td and th elements
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.12. The output element
* 4.10.17.3. Association of controls and forms
* 4.10.19. APIs for text field selections (2)
* 4.15.1. Case-sensitivity (2) (3)
* 6.7.10. History traversal
* 8.2.4.42. Markup declaration open state
* 8.2.4.72. Character reference state
* 8.2.5.4.1. The "initial" insertion mode (2) (3)
* 10.3.8. Lists
* Attributes (2) (3)
#ascii-case-insensitiveReferenced in:
* 2.4.2. Boolean attributes
* 2.4.3. Keywords and enumerated attributes (2)
* 2.4.6. Colors (2)
* 2.6.5. Extracting character encodings from meta elements
* 3.2.5.2. The lang and xml:lang attributes (2)
* 4.2.4. The link element (2)
* 4.2.5. The meta element
* 4.2.5.1. Standard metadata names
* 4.2.5.3. Pragma directives (2) (3)
* 4.2.5.5. Specifying the document’s character encoding
* 4.7.4. The source element
* 4.7.6. The iframe element
* 4.7.8. The object element
* 4.8.6. Link types
* 4.8.6.5. Link type "icon"
* 4.10.3. The form element (2)
* 4.10.5.1.17. File Upload state (type=file) (2)
* 4.10.5.3.8. The step attribute (2)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5) (6) (7)
* 4.10.18.7.2. Processing model (2) (3) (4)
* 4.12.1. The script element (2)
* 4.12.1.1. Processing model (2) (3) (4)
* 4.15.1. Case-sensitivity (2)
* 5.6.1. Making document regions editable: The contenteditable content
attribute (2) (3)
* 5.6.2. Making entire documents editable: The designMode IDL attribute
* 6.1.5. Browsing context names
* 6.7.9. Navigating to a fragment
* 7.4.1. Opening the input stream (2) (3)
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods (2) (3)
(4) (5) (6)
* 8.1.1. The DOCTYPE (2) (3)
* 8.1.2.3. Attributes (2)
* 8.2.4.42. Markup declaration open state
* 8.2.4.56. After DOCTYPE name state (2)
* 8.2.5. Tree construction (2)
* 8.2.5.4.1. The "initial" insertion mode
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.9. The "in table" insertion mode
* 9.3. Serializing XML fragments
* 10.3.2. The page
* 10.3.3. Flow content (2) (3) (4)
* 10.3.9. Tables (2) (3) (4)
* 10.3.13. The fieldset and legend elements
* 10.4.3. Attributes for embedded content and images
* 10.5.15. The textarea element
* 11.1. Obsolete but conforming features (2)
* 11.1.1. Warnings for obsolete but conforming features (2)
* Attributes (2) (3)
#compatibility-caselessReferenced in:
* 2.4.9. References
* 4.7.14. The map element
* 4.10.5.1.16. Radio Button state (type=radio)
#ascii-uppercaseReferenced in:
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
#ascii-lowercaseReferenced in:
* 2.2.4. Interactions with XPath and XSLT (2)
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
(2)
* 4.2.5.1. Standard metadata names
* 4.10.5.1.14. Color state (type=color)
* 4.10.18.7.2. Processing model
* 4.12.4.2. Serializing bitmaps to a file
* 4.15.1. Case-sensitivity (2)
* 5.7.2. The drag data store
* 5.7.3. The DataTransfer interface (2) (3)
* 5.7.3.1. The DataTransferItemList interface (2) (3)
* 5.7.5. Drag-and-drop processing model
* 8.2.5.5. The rules for parsing tokens in foreign content (2)
#space-charactersReferenced in:
* 1.9. A quick introduction to HTML
* 2.4.1. Common parser idioms (2) (3)
* 2.4.4.6. Lists of floating-point numbers (2) (3) (4) (5)
* 2.4.4.7. Lists of dimensions (2)
* 2.4.5.9. Durations (2) (3) (4)
* 2.4.7. Space-separated tokens (2) (3) (4)
* 2.4.8. Comma-separated tokens (2)
* 2.4.10. Media queries
* 2.6.5. Extracting character encodings from meta elements (2) (3)
* 3.2.4. Content models
* 3.2.4.2.5. Phrasing content (2)
* 3.2.5. Global attributes
* 4.2.1. The head element
* 4.2.5.3. Pragma directives (2) (3) (4)
* 4.3.1. The body element
* 4.7.4. The source element (2)
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.7.6. The iframe element (2) (3)
* 4.7.14. The map element
* 4.8.6.5. Link type "icon"
* 4.11.3.5. Using the option element to define a command
* 4.12.1.1. Processing model
* 5.5.2. The accesskey attribute
* 7.3. Base64 utility methods
* 8.1. Writing HTML documents (2) (3)
* 8.1.1. The DOCTYPE (2) (3) (4)
* 8.1.2.1. Start tags (2) (3)
* 8.1.2.2. End tags
* 8.1.2.3. Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
* 8.1.2.4. Optional tags (2) (3) (4)
* 8.1.4. Character references
* 8.2.5.4.10. The "in table text" insertion mode
* 8.2.8.3. Unexpected markup in tables (2)
#white_spaceReferenced in:
* 4.9.12.2. Forming relationships between data cells and header cells
#control-charactersReferenced in:
* 2.1.3. DOM trees
* 3.2.4.2.5. Phrasing content
* 8.1.2.3. Attributes
* 8.1.4. Character references
* 8.2.2.5. Preprocessing the input stream
#uppercase-ascii-lettersReferenced in:
* 2.4.1. Common parser idioms (2)
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
(2) (3) (4)
* 4.7.7. The embed element
* 8.1. Writing HTML documents
* 8.2.4.8. Tag name state
* 8.2.4.11. RCDATA end tag name state
* 8.2.4.14. RAWTEXT end tag name state
* 8.2.4.17. Script data end tag name state
* 8.2.4.25. Script data escaped end tag name state
* 8.2.4.26. Script data double escape start state
* 8.2.4.31. Script data double escape end state
* 8.2.4.33. Attribute name state
* 8.2.4.54. Before DOCTYPE name state
* 8.2.4.55. DOCTYPE name state
#lowercase-ascii-lettersReferenced in:
* 2.4.1. Common parser idioms (2)
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
(2)
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods
* 8.1. Writing HTML documents
* 8.2.4.11. RCDATA end tag name state
* 8.2.4.14. RAWTEXT end tag name state
* 8.2.4.17. Script data end tag name state
* 8.2.4.25. Script data escaped end tag name state
* 8.2.4.26. Script data double escape start state
* 8.2.4.31. Script data double escape end state
#ascii-lettersReferenced in:
* 8.2.4.6. Tag open state
* 8.2.4.7. End tag open state
* 8.2.4.10. RCDATA end tag open state
* 8.2.4.13. RAWTEXT end tag open state
* 8.2.4.16. Script data end tag open state
* 8.2.4.23. Script data escaped less-than sign state
* 8.2.4.24. Script data escaped end tag open state
#ascii-digitsReferenced in:
* 2.4.1. Common parser idioms
* 2.4.4.1. Signed integers (2) (3)
* 2.4.4.2. Non-negative integers
* 2.4.4.3. Floating-point numbers (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 2.4.4.4. Percentages and lengths (2) (3) (4)
* 2.4.4.6. Lists of floating-point numbers
* 2.4.4.7. Lists of dimensions (2) (3)
* 2.4.5. Dates and times
* 2.4.5.1. Months (2) (3) (4)
* 2.4.5.2. Dates (2)
* 2.4.5.3. Yearless dates (2) (3) (4)
* 2.4.5.4. Times (2) (3) (4) (5) (6) (7) (8)
* 2.4.5.6. Time zones (2) (3) (4)
* 2.4.5.8. Weeks (2) (3) (4)
* 2.4.5.9. Durations (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 3.1.2. Resource metadata management (2)
* 4.2.5.3. Pragma directives (2)
* 4.5.1. The a element (2)
* 4.5.16. The time element (2)
* 4.8.6.5. Link type "icon"
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5) (6) (7) (8) (9) (10)
* 4.10.21.3. Form submission algorithm
* 4.10.21.7. Multipart form data
* 8.1.4. Character references
* 8.2.4.75. Decimal character reference start state
* 8.2.4.76. Hexadecimal character reference state
* 8.2.4.77. Decimal character reference state
* 10.3.4. Phrasing content
#alphanumeric-ascii-charactersReferenced in:
* 7.3. Base64 utility methods
* 8.1.2. Elements
* 8.1.4. Character references
* 8.2.4.72. Character reference state (2)
#ascii-hex-digitsReferenced in:
* 2.4.6. Colors (2) (3) (4)
* 8.1.4. Character references
* 8.2.4.74. Hexadecimal character reference start state
#uppercase-ascii-hex-digitsReferenced in:
* 4.7.13.11.2. Sourcing in-band text tracks
* 8.2.4.76. Hexadecimal character reference state
#lowercase-ascii-hex-digitsReferenced in:
* 2.4.6. Colors
* 8.2.4.76. Hexadecimal character reference state
#collect-a-sequence-of-charactersReferenced in:
* 2.4.1. Common parser idioms (2)
* 2.4.4.1. Signed integers
* 2.4.4.3. Floating-point numbers (2)
* 2.4.4.4. Percentages and lengths
* 2.4.4.6. Lists of floating-point numbers (2) (3) (4)
* 2.4.4.7. Lists of dimensions (2)
* 2.4.5.1. Months (2)
* 2.4.5.2. Dates
* 2.4.5.3. Yearless dates (2) (3)
* 2.4.5.4. Times (2) (3)
* 2.4.5.6. Time zones (2)
* 2.4.5.8. Weeks (2)
* 2.4.5.9. Durations (2)
* 2.4.7. Space-separated tokens
* 2.4.8. Comma-separated tokens
* 3.2.6. The innerText IDL attribute
* 4.2.5.3. Pragma directives (2) (3)
* 4.7.5. The img element (2)
* 10.3.4. Phrasing content
#skip-white-spaceReferenced in:
* 2.4.4.1. Signed integers
* 2.4.4.3. Floating-point numbers
* 2.4.4.4. Percentages and lengths
* 2.4.4.7. Lists of dimensions
* 2.4.5.9. Durations (2) (3) (4) (5) (6)
* 2.4.7. Space-separated tokens (2)
* 4.2.5.3. Pragma directives (2) (3) (4) (5) (6)
* 4.7.5. The img element
* 10.3.4. Phrasing content
#stripped-line-breaksReferenced in:
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.3.10. The placeholder attribute
#strip-leading-and-trailing-white-spaceReferenced in:
* 2.4.1. Common parser idioms (2)
* 2.4.6. Colors
* 2.4.8. Comma-separated tokens
* 2.5.1. Terminology (2)
* 4.7.4. The source element
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email) (2) (3)
* 4.11.3.5. Using the option element to define a command
* 4.12.1.1. Processing model
* 7.4.1. Opening the input stream
#stripping-and-collapsing-white-spaceReferenced in:
* 3.1.3. DOM tree accessors
* 4.10.10. The option element
#boolean-attributeReferenced in:
* 2.4.2. Boolean attributes (2)
* 2.7.1. Reflecting content attributes in IDL attributes
* 4.4.6. The ol element
* 4.7.5. The img element
* 4.7.6. The iframe element (2)
* 4.7.8. The object element
* 4.7.12. The track element
* 4.7.13.6. Offsets into the media resource
* 4.7.13.7. Ready states
* 4.7.13.13. User interface (2)
* 4.10.5. The input element
* 4.10.5.3.3. The readonly attribute
* 4.10.5.3.4. The required attribute
* 4.10.5.3.5. The multiple attribute
* 4.10.7. The select element (2)
* 4.10.9. The optgroup element
* 4.10.10. The option element (2)
* 4.10.11. The textarea element (2)
* 4.10.18.5. Enabling and disabling form controls: the disabled
attribute
* 4.10.18.6. Form submission
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute
* 4.11.1. The details element
* 4.11.4. The dialog element
* 4.12.1. The script element
* 5.1. The hidden attribute
* 11.3.2. The marquee element
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14)
(15) (16) (17) (18) (19) (20) (21) (22) (23) (24)
#enumerated-attributesReferenced in:
* 2.6.6. CORS settings attributes
* 2.6.7. Referrer policy attributes
* 2.7.1. Reflecting content attributes in IDL attributes (2)
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 4.2.5.3. Pragma directives
* 4.7.12. The track element
* 4.7.13.5. Loading the media resource
* 4.7.15. The area element
* 4.9.10. The th element
* 4.10.3. The form element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.11. The textarea element
* 4.10.18.6. Form submission (2)
* 5.6.1. Making document regions editable: The contenteditable content
attribute
* 5.6.5. Spelling and grammar checking
* 5.7.7. The draggable attribute
* 11.3.2. The marquee element (2)
#invalid-value-defaultReferenced in:
* 2.6.7. Referrer policy attributes
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
#missing-value-defaultReferenced in:
* 2.6.7. Referrer policy attributes
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
#valid-integerReferenced in:
* 1.7.1. How to read this specification (2)
* 2.4.4.1. Signed integers (2)
* 2.7.1. Reflecting content attributes in IDL attributes
* 4.4.6. The ol element
* 4.4.8. The li element
* 4.10.5.1.19. Image Button state (type=image) (2)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5)
* 5.4.3. The tabindex attribute
* 11.3.2. The marquee element
* Attributes (2) (3)
#parse-token-as-an-integerReferenced in:
* 1.7.1. How to read this specification
* 2.4.4.2. Non-negative integers
* 2.7.1. Reflecting content attributes in IDL attributes
* 4.4.6. The ol element
* 4.4.8. The li element
* 4.10.5.3.8. The step attribute
* 5.4.3. The tabindex attribute
* 11.3.2. The marquee element
#valid-non-negative-integerReferenced in:
* 2.4.4.2. Non-negative integers
* 2.7.1. Reflecting content attributes in IDL attributes (2) (3)
* 4.2.4. The link element
* 4.2.5.3. Pragma directives (2)
* 4.7.5. The img element (2) (3)
* 4.7.19. Dimension attributes
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.11. Attributes common to td and th elements (2)
* 4.10.5.3.2. The size attribute
* 4.10.7. The select element
* 4.10.11. The textarea element (2)
* 4.10.18.3. Limiting user input length: the maxlength attribute
* 4.10.18.4. Setting minimum input length requirements: the minlength
attribute
* 4.12.4. The canvas element
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
#parse-that-attributes-valueReferenced in:
* 2.7.1. Reflecting content attributes in IDL attributes (2) (3)
* 4.2.5.3. Pragma directives
* 4.7.5. The img element (2)
* 4.8.6.5. Link type "icon" (2)
* 4.9.12.1. Forming a table (2) (3) (4)
* 4.10.5.3.2. The size attribute
* 4.10.7. The select element
* 4.10.11. The textarea element (2)
* 4.10.18.3. Limiting user input length: the maxlength attribute
* 4.10.18.4. Setting minimum input length requirements: the minlength
attribute
* 4.12.4. The canvas element
* 10.2. The CSS user agent style sheet and presentational hints
* 10.3.9. Tables (2) (3) (4) (5)
* 10.3.12. The hr element (2)
* 10.4.3. Attributes for embedded content and images
* 10.5.4. The input element as a text entry widget.
* 10.5.15. The textarea element (2)
* 11.3.2. The marquee element (2)
#valid-floating-point-numberReferenced in:
* 2.4.4.3. Floating-point numbers (2)
* 2.4.4.6. Lists of floating-point numbers
* 4.7.5. The img element (2)
* 4.10.5.1.12. Number state (type=number) (2) (3) (4) (5) (6) (7)
* 4.10.5.1.13. Range state (type=range) (2) (3) (4) (5) (6) (7)
* 4.10.5.3.8. The step attribute
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute
* Attributes (2) (3) (4) (5) (6) (7)
#best-floating-point-numberReferenced in:
* 2.7.1. Reflecting content attributes in IDL attributes (2)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range) (2) (3) (4)
* 4.10.13. The progress element
* 4.10.14. The meter element (2) (3) (4) (5) (6)
#rules-for-parsing-floating-point-number-valuesReferenced in:
* 2.4.4.6. Lists of floating-point numbers
* 2.7.1. Reflecting content attributes in IDL attributes (2)
* 4.7.5. The img element
* 4.10.5.1.12. Number state (type=number) (2)
* 4.10.5.1.13. Range state (type=range) (2)
* 4.10.5.3.8. The step attribute
* 4.10.13. The progress element (2)
* 4.10.14. The meter element
#rules-for-parsing-dimension-valuesReferenced in:
* 2.4.4.5. Non-zero percentages and lengths
* 4.7.5. The img element
* 10.2. The CSS user agent style sheet and presentational hints
#rules-for-parsing-non-zero-dimension-valuesReferenced in:
* 10.2. The CSS user agent style sheet and presentational hints
* 10.3.9. Tables
#valid-list-of-floating-point-numbersReferenced in:
* 4.7.15. The area element
* Attributes
#rules-for-parsing-a-list-of-floating-point-numbersReferenced in:
* 4.7.16.2. Processing model
#rules-for-parsing-a-list-of-dimensionsReferenced in:
* 10.6. Frames and framesets (2)
#number-of-days-in-month-month-of-year-yearReferenced in:
* 2.4.5.2. Dates (2)
* 2.4.5.3. Yearless dates (2)
#proleptic-gregorian-calendarReferenced in:
* 2.4.5. Dates and times (2) (3)
* 2.4.5.7. Global dates and times
* 2.4.5.8. Weeks (2) (3)
#proleptic-gregorian-dateReferenced in:
* 2.4.5.1. Months
* 2.4.5.2. Dates
* 2.4.5.5. Floating dates and times
* 2.4.5.7. Global dates and times
#monthReferenced in:
* 4.5.16. The time element
* 4.10.5.1.8. Month state (type=month) (2) (3) (4) (5) (6) (7) (8) (9)
* 4.10.18.7.2. Processing model
#valid-month-stringReferenced in:
* 2.4.5.2. Dates
* 4.5.16. The time element
* 4.10.5.1.8. Month state (type=month) (2) (3) (4) (5) (6) (7) (8) (9)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute
* Attributes
#parsing-a-month-stringReferenced in:
* 4.5.16. The time element
* 4.10.5.1.8. Month state (type=month) (2) (3)
#parse-a-month-componentReferenced in:
* 2.4.5.1. Months
* 2.4.5.2. Dates
#dates-dateReferenced in:
* 2.4.5.10. Vaguer moments in time
* 4.5.16. The time element
* 4.6.3. Attributes common to ins and del elements (2)
* 4.10.5.1.7. Date state (type=date) (2) (3) (4) (5) (6) (7) (8) (9)
#valid-date-stringReferenced in:
* 2.4.5.5. Floating dates and times (2)
* 2.4.5.7. Global dates and times (2)
* 2.4.5.10. Vaguer moments in time
* 4.5.16. The time element
* 4.10.5.1.7. Date state (type=date) (2) (3) (4) (5) (6) (7) (8) (9)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute
* Attributes
#parsing-a-date-stringReferenced in:
* 4.5.16. The time element
* 4.10.5.1.7. Date state (type=date) (2) (3)
#parse-a-date-componentReferenced in:
* 2.4.5.2. Dates
* 2.4.5.5. Floating dates and times
* 2.4.5.7. Global dates and times
* 2.4.5.10. Vaguer moments in time
#yearless-dateReferenced in:
* 4.5.16. The time element
#valid-yearless-date-stringReferenced in:
* 4.5.16. The time element
* Attributes
#parsing-a-yearless-date-stringReferenced in:
* 4.5.16. The time element
#parse-a-yearless-date-componentReferenced in:
* 2.4.5.3. Yearless dates
#timeReferenced in:
* 2.4.5.10. Vaguer moments in time
* 4.5.16. The time element
* 4.10.5.1.10. Time state (type=time) (2) (3) (4) (5) (6) (7) (8) (9)
#valid-time-stringReferenced in:
* 2.4.5.5. Floating dates and times (2)
* 2.4.5.7. Global dates and times (2)
* 4.5.16. The time element
* 4.10.5.1.10. Time state (type=time) (2) (3) (4) (5) (6) (7) (8) (9)
* Attributes
#parsing-a-time-stringReferenced in:
* 4.5.16. The time element
* 4.10.5.1.10. Time state (type=time) (2) (3)
#parse-a-time-componentReferenced in:
* 2.4.5.4. Times
* 2.4.5.5. Floating dates and times
* 2.4.5.7. Global dates and times
* 2.4.5.10. Vaguer moments in time
#floating-date-and-timeReferenced in:
* 4.5.16. The time element
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2)
#valid-floating-date-and-time-stringReferenced in:
* 4.5.16. The time element (2)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2) (3)
(4)
* Attributes
#valid-normalized-floating-date-and-time-stringReferenced in:
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2)
#parsing-a-floating-date-and-time-stringReferenced in:
* 4.5.16. The time element (2)
#time-zoneReferenced in:
* 4.5.16. The time element (2)
* 4.10.5.1.7. Date state (type=date)
#valid-time-zone-offset-stringReferenced in:
* 2.4.5.7. Global dates and times
* 4.5.16. The time element
* Attributes
#parsing-a-time-zone-offset-stringReferenced in:
* 4.5.16. The time element
#parse-a-time-zone-offset-componentReferenced in:
* 2.4.5.6. Time zones
* 2.4.5.7. Global dates and times
* 2.4.5.10. Vaguer moments in time
#global-date-and-timeReferenced in:
* 2.4.5.6. Time zones
* 2.4.5.10. Vaguer moments in time
* 4.5.16. The time element
* 4.6.3. Attributes common to ins and del elements (2) (3)
#valid-global-date-and-time-stringReferenced in:
* 2.4.5.7. Global dates and times
* 2.4.5.10. Vaguer moments in time
* 4.5.16. The time element (2)
* Attributes
#valid-normalized-global-date-and-time-stringReferenced in:
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2) (3)
#parse-a-global-date-and-time-stringReferenced in:
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2)
#weekReferenced in:
* 2.4.5.8. Weeks
* 4.5.16. The time element
* 4.10.5.1.9. Week state (type=week) (2) (3) (4) (5) (6) (7) (8) (9)
#week-number-of-the-last-dayReferenced in:
* 2.4.5.8. Weeks (2)
#valid-week-stringReferenced in:
* 4.5.16. The time element
* 4.10.5.1.9. Week state (type=week) (2) (3) (4) (5) (6) (7) (8) (9)
* Attributes
#parsing-a-week-stringReferenced in:
* 4.5.16. The time element
* 4.10.5.1.9. Week state (type=week) (2) (3)
#durationReferenced in:
* 2.4.5.9. Durations (2) (3) (4)
* 4.5.16. The time element
#valid-duration-stringReferenced in:
* 4.5.16. The time element
* Attributes
#duration-time-componentReferenced in:
* 2.4.5.9. Durations (2)
#duration-time-component-scaleReferenced in:
* 2.4.5.9. Durations (2) (3)
#parsing-a-duration-stringReferenced in:
* 4.5.16. The time element
#valid-date-string-with-optional-timeReferenced in:
* 4.6.3. Attributes common to ins and del elements (2)
* Attributes
#parse-a-date-or-time-stringReferenced in:
* 4.6.3. Attributes common to ins and del elements
#simple-colorReferenced in:
* 2.4.6. Colors (2) (3) (4) (5) (6) (7)
* 4.10.5.1.14. Color state (type=color)
#valid-simple-colorReferenced in:
* 2.4.6. Colors
* 4.10.5.1.14. Color state (type=color) (2)
#valid-lowercase-simple-colorReferenced in:
* 2.4.6. Colors
* 4.10.5.1.14. Color state (type=color) (2)
#rules-for-parsing-simple-color-valuesReferenced in:
* 4.10.5.1.14. Color state (type=color)
#rules-for-serializing-simple-color-valuesReferenced in:
* 4.10.5.1.14. Color state (type=color)
#rules-for-parsing-a-legacy-color-valueReferenced in:
* 10.3.2. The page (2) (3) (4) (5)
* 10.3.4. Phrasing content
* 10.3.9. Tables (2)
* 10.3.12. The hr element
* 10.5.11. The marquee element
* 10.6. Frames and framesets
#set-of-space-separated-tokensReferenced in:
* 2.4.7. Space-separated tokens (2) (3) (4) (5)
* 3.2.5. Global attributes
* 3.2.8.3.1. ARIA Role Attribute
* 4.2.4. The link element
* 4.8.2. Links created by a and area elements (2)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
* Attributes (2) (3)
#unordered-set-of-unique-space-separated-tokensReferenced in:
* 4.2.4. The link element
* 4.7.6. The iframe element
* 4.9.11. Attributes common to td and th elements
* 4.10.12. The output element
* Attributes (2) (3) (4)
#ordered-set-of-unique-space-separated-tokensReferenced in:
* 4.10.3. The form element
* Attributes (2)
#split-a-string-on-spacesReferenced in:
* 2.4.1. Common parser idioms
* 4.8.6. Link types
* 4.8.6.5. Link type "icon"
* 4.9.12.2. Forming relationships between data cells and header cells
* 4.10.18.7.2. Processing model
* 4.10.21.5. Selecting a form submission encoding
* 6.5. Sandboxing
#set-of-comma-separated-tokensReferenced in:
* 2.4.8. Comma-separated tokens
* 4.2.5.1. Standard metadata names
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.17. File Upload state (type=file)
* Attributes
#split-a-string-on-commasReferenced in:
* 2.4.1. Common parser idioms
* 2.4.4.7. Lists of dimensions
* 4.2.5.1. Standard metadata names
* 4.10.5.1.5. E-mail state (type=email) (2)
* 4.10.5.1.17. File Upload state (type=file)
* 6.3.1. APIs for creating and navigating browsing contexts by name
#valid-hash-name-referenceReferenced in:
* 4.7.16.1. Authoring
* 5.1. The hidden attribute
* Attributes
#rules-for-parsing-a-hash-name-referenceReferenced in:
* 4.7.16.2. Processing model
#valid-media-query-listReferenced in:
* 4.2.4. The link element
* 4.2.6. The style element
* 4.7.4. The source element
* Attributes
#match-the-environmentReferenced in:
* 4.2.4.1. Processing the media attribute
* 4.2.6. The style element
* 4.7.5. The img element
#valid-urlReferenced in:
* 2.5.1. Terminology (2)
* 4.2.5.3. Pragma directives
* 4.10.5.1.4. URL state (type=url) (2) (3)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3)
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods
#valid-non-empty-urlReferenced in:
* 2.5.1. Terminology
* 4.7.5. The img element
#valid-url-potentially-surrounded-by-spacesReferenced in:
* 4.2.3. The base element
* 4.4.5. The blockquote element
* 4.5.7. The q element
* 4.6.3. Attributes common to ins and del elements
* 4.8.2. Links created by a and area elements
* 4.10.5.1.4. URL state (type=url)
* Attributes (2) (3)
#valid-non-empty-url-potentially-surrounded-by-spacesReferenced in:
* 4.1.1. The html element
* 4.2.4. The link element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.10. The video element
* 4.7.12. The track element
* 4.7.13.2. Location of the media resource
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.18.6. Form submission
* 4.12.1. The script element
* Attributes (2) (3) (4) (5) (6) (7) (8)
#schemedef-aboutlegacy-compatReferenced in:
* 8.2.5.4.1. The "initial" insertion mode
#schemedef-aboutsrcdocReferenced in:
* 4.7.6. The iframe element
#fallback-base-urlReferenced in:
* 2.5.1. Terminology
* 4.2.3. The base element (2) (3)
#document-base-urlReferenced in:
* 2.5.1. Terminology (2) (3)
* 2.5.2. Parsing URLs
* 2.5.3. Dynamic changes to base URLs
* 4.2.3. The base element (2) (3)
* 4.5.1. The a element
* 4.7.15. The area element
* 4.12.1.1. Processing model
* 6.1.6. Script settings for browsing contexts
* 7.1.3.1. Definitions
* Attributes
#reparsedReferenced in:
* 1.9. A quick introduction to HTML
* 2.5.3. Dynamic changes to base URLs (2)
* 2.7.1. Reflecting content attributes in IDL attributes
* 4.1.1. The html element
* 4.2.3. The base element (2)
* 4.2.4.3. Obtaining a resource from a link element
* 4.2.5.3. Pragma directives
* 4.4.5. The blockquote element
* 4.5.7. The q element
* 4.6.3. Attributes common to ins and del elements
* 4.7.5. The img element (2) (3)
* 4.7.6. The iframe element (2)
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.10. The video element
* 4.7.12. The track element
* 4.7.13.5. Loading the media resource (2) (3)
* 4.7.13.11.1. Text track model
* 4.8.3. API for a and area elements (2)
* 4.8.4. Following hyperlinks (2)
* 4.8.5. Downloading resources (2)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.21.3. Form submission algorithm
* 4.12.1.1. Processing model
* 5.7.5. Drag-and-drop processing model (2)
* 6.3.1. APIs for creating and navigating browsing contexts by name (2)
* 6.6.2. The History interface
* 6.6.4. The Location interface (2) (3)
* 7.1.3.1. Definitions
* 7.1.3.5. Realms, settings objects, and global objects
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods (2) (3)
* 10.3.2. The page
* 10.3.9. Tables
* 10.7.1. Links, forms, and navigation
#resulting-url-stringReferenced in:
* 2.5.2. Parsing URLs
* 2.7.1. Reflecting content attributes in IDL attributes
* 4.7.5. The img element (2) (3)
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.10. The video element
* 4.7.12. The track element
* 4.7.13.5. Loading the media resource (2)
* 4.8.3. API for a and area elements
* 4.8.4. Following hyperlinks
* 4.8.5. Downloading resources
* 4.8.6.11. Link type "stylesheet"
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.21.3. Form submission algorithm
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods (2) (3)
* 10.3.2. The page
* 10.3.9. Tables
#resulting-url-recordReferenced in:
* 2.5.2. Parsing URLs
* 2.6.2. Processing model
* 4.2.3. The base element
* 4.2.4.3. Obtaining a resource from a link element
* 4.2.5.3. Pragma directives
* 4.7.6. The iframe element
* 4.7.13.5. Loading the media resource (2)
* 4.10.21.3. Form submission algorithm (2)
* 4.12.1.1. Processing model
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.6.2. The History interface
* 6.6.4. The Location interface (2) (3)
* 6.7.9. Navigating to a fragment
#or-equivalentReferenced in:
* 2.6.2. Processing model (2)
#referrer-sourceReferenced in:
* 2.6.2. Processing model
#creating-a-potential-cors-requestReferenced in:
* 4.2.4.3. Obtaining a resource from a link element
* 4.7.5. The img element (2)
* 4.7.13.5. Loading the media resource
* 4.7.13.11.3. Sourcing out-of-band text tracks
* 7.1.3.2. Fetching scripts
#sizeReferenced in:
* 2.6.2. Processing model
* 2.7.3. The DOMStringList interface (2) (3)
#content-type-metadataReferenced in:
* 4.2.4.2. Processing the type attribute (2) (3) (4) (5)
* 4.2.5.5. Specifying the document’s character encoding (2)
* 4.7.5. The img element (2)
* 4.7.7. The embed element (2)
* 4.7.8. The object element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.7.13.3. MIME types
* 4.8.5. Downloading resources (2)
* 4.8.6.11. Link type "stylesheet" (2) (3)
* 4.10.5.1.19. Image Button state (type=image) (2)
* 4.12.1. The script element
* 6.7.1. Navigating across documents
* 6.7.2. Page load processing model for HTML files
* 7.1.3.2. Fetching scripts
* 8.2.2.2. Determining the character encoding
* Attributes
#computed-type-of-the-resourceReferenced in:
* 4.2.4.2. Processing the type attribute
* 4.7.8. The object element (2)
* 6.7.4. Page load processing model for text files (2)
* 6.7.6. Page load processing model for media
* 6.7.7. Page load processing model for content that uses plugins
#image-sniffing-rulesReferenced in:
* 4.2.4.2. Processing the type attribute
* 4.7.5. The img element (2)
* 4.10.5.1.19. Image Button state (type=image)
* 7.8. Images
#rules-for-distinguishing-if-a-resource-is-text-or-binaryReferenced in:
* 4.7.8. The object element
#algorithm-for-extracting-a-character-encoding-from-a-meta-elementReferenced
in:
* 8.2.2.2. Determining the character encoding
* 8.2.5.4.4. The "in head" insertion mode
#cors-settings-attributeReferenced in:
* 4.2.4. The link element
* 4.7.5. The img element (2)
* 4.7.13.2. Location of the media resource
* 4.12.1. The script element
#valdef-cors-anonymousReferenced in:
* 2.6.6. CORS settings attributes
* Attributes
#statedef-cors-anonymousReferenced in:
* 2.6.6. CORS settings attributes (2) (3)
* 4.12.1.1. Processing model
#valdef-cors-use-credentialsReferenced in:
* Attributes
#statedef-cors-use-credentialsReferenced in:
* 4.12.1.1. Processing model
#statedef-cors-no-corsReferenced in:
* 2.6.1. Terminology
* 4.7.5. The img element (2) (3)
* 4.7.13.11.3. Sourcing out-of-band text tracks
* 4.12.1.1. Processing model
#referrer-policy-attributeReferenced in:
* 2.6.7. Referrer policy attributes (2)
* 4.2.4. The link element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.8.2. Links created by a and area elements
#reflectionReferenced in:
* 2.2.3. Extensibility
* 2.6.6. CORS settings attributes
* 3.2.5.1. The title attribute
* 3.2.5.2. The lang and xml:lang attributes
* 3.2.5.5. The dir attribute (2)
* 4.2.3. The base element
* 4.2.4. The link element (2) (3) (4)
* 4.2.5. The meta element (2)
* 4.2.6. The style element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.8. The li element
* 4.5.1. The a element (2) (3)
* 4.5.15. The data element
* 4.5.16. The time element
* 4.6.3. Attributes common to ins and del elements (2)
* 4.7.4. The source element
* 4.7.5. The img element (2) (3) (4) (5) (6) (7)
* 4.7.6. The iframe element (2) (3) (4)
* 4.7.7. The embed element
* 4.7.8. The object element (2)
* 4.7.9. The param element
* 4.7.10. The video element
* 4.7.12. The track element (2)
* 4.7.13.2. Location of the media resource (2)
* 4.7.13.5. Loading the media resource
* 4.7.13.6. Offsets into the media resource
* 4.7.13.7. Ready states
* 4.7.13.13. User interface (2)
* 4.7.14. The map element
* 4.7.15. The area element (2) (3) (4)
* 4.7.19. Dimension attributes
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.10. The th element (2)
* 4.9.11. Attributes common to td and th elements (2) (3)
* 4.10.3. The form element (2) (3)
* 4.10.4. The label element
* 4.10.5. The input element (2) (3) (4) (5) (6) (7) (8) (9)
* 4.10.6. The button element (2)
* 4.10.7. The select element
* 4.10.9. The optgroup element
* 4.10.10. The option element (2)
* 4.10.11. The textarea element (2) (3) (4) (5)
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.15. The fieldset element
* 4.10.18.1. Naming form controls: the name attribute
* 4.10.18.5. Enabling and disabling form controls: the disabled
attribute
* 4.10.18.6. Form submission (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute
* 4.10.18.7.2. Processing model
* 4.11.1. The details element
* 4.11.4. The dialog element
* 4.12.1. The script element (2) (3)
* 4.12.4. The canvas element
* 5.1. The hidden attribute
* 5.4.3. The tabindex attribute
* 5.5.3. Processing model
* 11.3.1. The applet element (2)
* 11.3.2. The marquee element (2) (3) (4) (5)
* 11.3.3. Frames (2) (3) (4) (5) (6) (7)
* 11.3.4. Other elements, attributes and APIs (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21)
(22) (23) (24) (25) (26) (27) (28) (29) (30) (31) (32) (33) (34) (35)
(36) (37) (38) (39) (40) (41) (42) (43) (44) (45) (46) (47) (48) (49)
(50) (51) (52) (53) (54) (55) (56) (57) (58) (59) (60) (61) (62) (63)
(64) (65) (66)
#limited-to-only-known-valuesReferenced in:
* 3.2.5.5. The dir attribute (2)
* 4.2.4. The link element
* 4.5.1. The a element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.12. The track element
* 4.7.13.5. Loading the media resource
* 4.7.15. The area element
* 4.9.10. The th element
* 4.10.3. The form element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.18.6. Form submission (2) (3) (4)
#limited-to-only-non-negative-numbersReferenced in:
* 4.10.5. The input element (2)
* 4.10.11. The textarea element (2)
#limited-to-only-non-negative-numbers-greater-than-zeroReferenced in:
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.10.5.3.2. The size attribute
* 4.10.11. The textarea element
#limited-to-numbers-greater-than-zeroReferenced in:
* 4.10.13. The progress element
#htmlallcollectionReferenced in:
* 2.7.2. Collections
* 2.7.2.1. The HTMLAllCollection interface (2) (3) (4) (5) (6) (7) (8)
* 11.3.4. Other elements, attributes and APIs (2)
#named-for-the-all-collectionReferenced in:
* 2.7.2.1. The HTMLAllCollection interface (2) (3)
#dom-htmlallcollection-lengthReferenced in:
* 2.7.2.1. The HTMLAllCollection interface (2)
#dom-htmlallcollection-nameditemReferenced in:
* 2.7.2.1. The HTMLAllCollection interface (2) (3)
#dom-htmlallcollection-itemReferenced in:
* 2.7.2.1. The HTMLAllCollection interface (2) (3) (4)
#all-named-elementsReferenced in:
* 2.7.2.1. The HTMLAllCollection interface
#get-all-indexedReferenced in:
* 2.7.2.1. The HTMLAllCollection interface (2)
#get-all-namedReferenced in:
* 2.7.2.1. The HTMLAllCollection interface (2)
#htmlformcontrolscollectionReferenced in:
* 2.7.2. Collections
* 4.10.3. The form element (2) (3)
#radionodelistReferenced in:
* 2.7.2.2. The HTMLFormControlsCollection interface
* 4.10.3. The form element (2) (3)
#dom-htmlformcontrolscollection-nameditemReferenced in:
* 2.7.2.2. The HTMLFormControlsCollection interface
#dom-radionodelist-valueReferenced in:
* 2.7.2.2. The HTMLFormControlsCollection interface (2)
#htmloptionscollectionReferenced in:
* 2.7.2. Collections
* 2.7.2.3. The HTMLOptionsCollection interface
* 4.10.7. The select element
#dom-htmloptionscollection-lengthReferenced in:
* 2.7.2.3. The HTMLOptionsCollection interface (2)
#dom-htmloptionscollection-addReferenced in:
* 2.7.2.3. The HTMLOptionsCollection interface
#dom-htmloptionscollection-removeReferenced in:
* 2.7.2.3. The HTMLOptionsCollection interface
#dom-htmloptionscollection-selectedindexReferenced in:
* 2.7.2.3. The HTMLOptionsCollection interface
#domstringlistReferenced in:
* 2.7.3. The DOMStringList interface (2) (3) (4) (5) (6) (7) (8) (9)
#dom-domstringlist-lengthReferenced in:
* 2.7.3. The DOMStringList interface (2)
#dom-domstringlist-itemReferenced in:
* 2.7.3. The DOMStringList interface (2)
#dom-domstringlist-containsReferenced in:
* 2.7.3. The DOMStringList interface (2)
#implied-strong-referenceReferenced in:
* 6.3.4. Garbage collection and browsing contexts
#html-namespaceReferenced in:
* 2.1. Terminology (2)
* 2.1.2. XML compatibility (2)
* 2.2.1. Conformance classes
* 2.2.4. Interactions with XPath and XSLT
* 3.1.3. DOM tree accessors (2)
* 3.2.2. Elements in the DOM
* 3.2.4.2.6. Embedded content
* 3.2.5. Global attributes
* 3.2.6. The innerText IDL attribute
* 4.7.17. MathML (2)
* 4.7.18. SVG
* 4.10.10. The option element
* 4.15.1. Case-sensitivity (2)
* 8.2. Parsing HTML documents
* 8.2.3.2. The stack of open elements (2) (3) (4) (5) (6) (7) (8)
* 8.2.4.42. Markup declaration open state
* 8.2.5. Tree construction
* 8.2.5.1. Creating and inserting nodes
* 8.2.5.4.2. The "before html" insertion mode
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode (2)
* 8.2.5.5. The rules for parsing tokens in foreign content (2)
* 8.3. Serializing HTML fragments
* 10.9. Unstyled XML documents
* 12.3. application/xhtml+xml (2)
#mathml-namespaceReferenced in:
* 4.7.17. MathML
* 8.1.2. Elements
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.5. The rules for parsing tokens in foreign content
* 8.3. Serializing HTML fragments
* 10.9. Unstyled XML documents
#svg-namespaceReferenced in:
* 3.1.3. DOM tree accessors
* 4.10.10. The option element
* 8.1.2. Elements (2) (3)
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.5. The rules for parsing tokens in foreign content (2) (3)
* 8.3. Serializing HTML fragments
* 10.9. Unstyled XML documents
#xlink-namespaceReferenced in:
* 8.1.2.3. Attributes (2) (3) (4) (5) (6) (7)
* 8.2.5.1. Creating and inserting nodes (2) (3) (4) (5) (6) (7) (8)
* 8.3. Serializing HTML fragments
#xml-namespaceReferenced in:
* 2.2.2. Dependencies
* 3.2.5. Global attributes
* 3.2.5.2. The lang and xml:lang attributes (2) (3) (4) (5) (6) (7) (8)
* 4.5.22. The i element
* 8.1.2.3. Attributes (2)
* 8.2.5.1. Creating and inserting nodes (2) (3)
* 8.3. Serializing HTML fragments
#xmlns-namespaceReferenced in:
* 8.1.2.3. Attributes (2)
* 8.2.5.1. Creating and inserting nodes (2) (3) (4)
* 8.2.7. Coercing an HTML DOM into an infoset
* 8.3. Serializing HTML fragments (2)
#serializable-objectsReferenced in:
* 2.9.1. Serializable objects (2) (3) (4) (5)
* 2.9.3. StructuredSerializeInternal ( value, forStorage [ , memory ] )
(2)
* 2.9.10. Monkey patch for Blob and FileList objects (2) (3)
* 7.8. Images
#extendedattrdef-serializableReferenced in:
* 7.8. Images
#serialization-stepsReferenced in:
* 2.9.1. Serializable objects (2)
* 2.9.2. Transferable objects
* 2.9.3. StructuredSerializeInternal ( value, forStorage [ , memory ] )
(2)
* 2.9.9. Performing serialization and transferring from other
specifications
* 2.9.10. Monkey patch for Blob and FileList objects (2) (3)
* 7.8. Images
#deserialization-stepsReferenced in:
* 2.9.1. Serializable objects (2)
* 2.9.2. Transferable objects
* 2.9.6. StructuredDeserialize ( serialized, targetRealm [ , memory ] )
(2)
* 2.9.10. Monkey patch for Blob and FileList objects (2) (3)
* 7.8. Images
#transferable-objectsReferenced in:
* 2.9.2. Transferable objects (2) (3) (4) (5)
* 2.9.7. StructuredSerializeWithTransfer ( value, transferList )
* 7.8. Images
#extendedattrdef-transferableReferenced in:
* 7.8. Images
#transfer-stepsReferenced in:
* 2.9.7. StructuredSerializeWithTransfer ( value, transferList )
* 7.8. Images
#transfer-receiving-stepsReferenced in:
* 2.9.6. StructuredDeserialize ( serialized, targetRealm [ , memory ] )
* 7.8. Images
#structuredserializeinternalReferenced in:
* 2.9.3. StructuredSerializeInternal ( value, forStorage [ , memory ] )
(2) (3) (4) (5) (6) (7) (8) (9) (10)
* 2.9.4. StructuredSerialize ( value )
* 2.9.5. StructuredSerializeForStorage ( value )
* 2.9.7. StructuredSerializeWithTransfer ( value, transferList ) (2) (3)
#sub-serializationReferenced in:
* 2.9.1. Serializable objects (2)
* 2.9.3. StructuredSerializeInternal ( value, forStorage [ , memory ] )
* 2.9.10. Monkey patch for Blob and FileList objects
#structuredserializeReferenced in:
* 2.9.1. Serializable objects (2)
* 2.9.6. StructuredDeserialize ( serialized, targetRealm [ , memory ] )
* 2.9.9. Performing serialization and transferring from other
specifications (2) (3) (4)
* 4.8.3. API for a and area elements
* 6.6.2. The History interface
#structuredserializeforstorageReferenced in:
* 2.9.6. StructuredDeserialize ( serialized, targetRealm [ , memory ] )
* 2.9.9. Performing serialization and transferring from other
specifications (2) (3) (4) (5)
* 6.6.1. The session history of browsing contexts
#structureddeserializeReferenced in:
* 2.9.1. Serializable objects
* 2.9.6. StructuredDeserialize ( serialized, targetRealm [ , memory ] )
(2) (3) (4) (5) (6) (7) (8) (9)
* 2.9.8. StructuredDeserializeWithTransfer (
serializeWithTransferResult, targetRealm ) (2)
* 2.9.9. Performing serialization and transferring from other
specifications (2) (3) (4)
* 6.6.1. The session history of browsing contexts
* 6.6.2. The History interface
* 6.7.10. History traversal
#sub-deserializationReferenced in:
* 2.9.1. Serializable objects (2)
* 2.9.6. StructuredDeserialize ( serialized, targetRealm [ , memory ] )
* 2.9.10. Monkey patch for Blob and FileList objects
#the-documents-referrerReferenced in:
* 3.1.2. Resource metadata management
* 6.7.1. Navigating across documents
#reload-override-flagReferenced in:
* 3.1. Documents
* 6.6.4. The Location interface (2)
* 7.4.1. Opening the input stream
* 7.4.3. document.write()
#reload-override-bufferReferenced in:
* 3.1. Documents (2)
* 7.4.1. Opening the input stream
* 7.4.3. document.write()
#overridden-reloadReferenced in:
* 3.1. Documents
* 6.6.4. The Location interface (2)
* 6.7.1. Navigating across documents
#enumdef-documentreadystateReferenced in:
* 3.1.1. The Document object
#dom-documentreadystate-loadingReferenced in:
* 3.1.2. Resource metadata management (2)
#dom-documentreadystate-interactiveReferenced in:
* 3.1.2. Resource metadata management
#dom-documentreadystate-completeReferenced in:
* 3.1.2. Resource metadata management (2)
#typedefdef-htmlorsvgscriptelementReferenced in:
* 3.1.1. The Document object
#document-https-stateReferenced in:
* 3.1. Documents
* 4.7.6. The iframe element
* 6.1.6. Script settings for browsing contexts
* 6.7.1. Navigating across documents
#concept-document-referrer-policyReferenced in:
* 2.2.2. Dependencies
* 2.6.7. Referrer policy attributes
* 3.1. Documents
* 3.1.1. The Document object (2)
* 4.2.4. The link element (2)
* 4.2.4.3. Obtaining a resource from a link element
* 4.2.5.1. Standard metadata names (2) (3) (4)
* 4.5.1. The a element
* 4.7.5. The img element (2)
* 4.7.6. The iframe element (2)
* 4.7.15. The area element
* 4.8.2. Links created by a and area elements
* 4.8.4. Following hyperlinks
* 6.1. Browsing contexts
* 6.7.1. Navigating across documents
* 7.1.3.1. Definitions (2)
* Attributes (2)
#document-csp-listReferenced in:
* 3.1. Documents
* 4.7.6. The iframe element
#document-module-mapReferenced in:
* 6.1.6. Script settings for browsing contexts
#dom-document-referrerReferenced in:
* 3.1.1. The Document object
* 3.1.2. Resource metadata management
#dom-document-cookieReferenced in:
* 3.1.1. The Document object
* 3.1.2. Resource metadata management (2) (3)
#cookie-averseReferenced in:
* 3.1.2. Resource metadata management (2)
* 6.5. Sandboxing
#dom-document-lastmodifiedReferenced in:
* 3.1.1. The Document object
* 3.1.2. Resource metadata management
#current-document-readinessReferenced in:
* 2.2.4. Interactions with XPath and XSLT
* 3.1.2. Resource metadata management (2)
* 6.7.10. History traversal
* 7.4.1. Opening the input stream
* 8.2.6. The end (2) (3) (4)
#active-parserReferenced in:
* 6.7.12. Aborting a document load
* 7.4.1. Opening the input stream
#dom-document-readystateReferenced in:
* 3.1.1. The Document object
* 3.1.2. Resource metadata management
#dom-document-headReferenced in:
* 3.1.1. The Document object
* 3.1.3. DOM tree accessors
#dom-document-titleReferenced in:
* 3.1.1. The Document object
* 3.1.3. DOM tree accessors
#dom-document-bodyReferenced in:
* 3.1.1. The Document object
* 3.1.3. DOM tree accessors
#dom-document-imagesReferenced in:
* 3.1.1. The Document object
* 3.1.3. DOM tree accessors
#dom-document-embedsReferenced in:
* 3.1.1. The Document object
* 3.1.3. DOM tree accessors (2)
#dom-document-pluginsReferenced in:
* 3.1.1. The Document object
* 3.1.3. DOM tree accessors
#dom-document-linksReferenced in:
* 3.1.1. The Document object
* 3.1.3. DOM tree accessors
#dom-document-formsReferenced in:
* 3.1.1. The Document object
* 3.1.3. DOM tree accessors
* 4.10.3. The form element (2) (3)
#dom-document-scriptsReferenced in:
* 3.1.1. The Document object
* 3.1.3. DOM tree accessors
#dom-document-getelementsbynameReferenced in:
* 3.1.1. The Document object
* 3.1.3. DOM tree accessors
#dom-document-currentscriptReferenced in:
* 3.1.1. The Document object
* 3.1.3. DOM tree accessors (2)
* 4.12.1.1. Processing model (2) (3) (4) (5)
* Changes between Working Draft 2 and the First Public Working Draft
#named-elementsReferenced in:
* 3.1.3. DOM tree accessors (2)
#exposedReferenced in:
* 3.1.3. DOM tree accessors (2) (3) (4) (5) (6) (7)
#representReferenced in:
* 3.2.3. Element definitions
* 3.2.4.2.9. Script-supporting elements
* 3.2.5.1. The title attribute
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element (2)
* 4.3.9. Headings and sections (2)
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element
* 4.4.13. The figcaption element
* 4.4.14. The main element
* 4.4.15. The div element
* 4.5.1. The a element (2)
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.11. The rb element (2) (3)
* 4.5.12. The rt element (2) (3)
* 4.5.13. The rtc element (2) (3)
* 4.5.14. The rp element (2)
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements (2)
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.5. The img element (2) (3) (4) (5) (6) (7)
* 4.7.6. The iframe element
* 4.7.7. The embed element (2)
* 4.7.8. The object element (2) (3) (4)
* 4.7.9. The param element (2)
* 4.7.10. The video element (2) (3) (4) (5) (6) (7) (8) (9)
* 4.7.11. The audio element
* 4.7.12. The track element
* 4.7.14. The map element
* 4.7.15. The area element
* 4.8.1. Introduction
* 4.9.1. The table element
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.3. The form element (2)
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email) (2)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image) (2) (3)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.6. The button element
* 4.10.7. The select element (2) (3)
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.11.1. The details element (2) (3)
* 4.11.2. The summary element
* 4.12.1. The script element
* 4.12.2. The noscript element (2)
* 4.12.3. The template element
* 4.12.4. The canvas element (2) (3) (4) (5) (6)
* 5.7.7. The draggable attribute
* 10.1. Introduction
* 10.4.1. Embedded content (2) (3)
* 10.4.2. Images (2) (3) (4) (5)
* 11.3.1. The applet element (2)
#htmlelementReferenced in:
* 2.7.1. Reflecting content attributes in IDL attributes (2)
* 2.7.2.3. The HTMLOptionsCollection interface
* 3.1.1. The Document object
* 3.2.2. Elements in the DOM (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element
* 4.4.13. The figcaption element
* 4.4.15. The div element
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.3. Attributes common to ins and del elements
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.9. The param element
* 4.7.12. The track element
* 4.7.13. Media elements
* 4.7.14. The map element
* 4.7.15. The area element
* 4.9.1. The table element
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.5. The tbody element (2)
* 4.9.8. The tr element (2)
* 4.9.11. Attributes common to td and th elements
* 4.10.3. The form element
* 4.10.4. The label element (2)
* 4.10.5. The input element (2)
* 4.10.6. The button element
* 4.10.7. The select element (2)
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.11.1. The details element
* 4.11.2. The summary element
* 4.11.4. The dialog element
* 4.12.1. The script element
* 4.12.2. The noscript element
* 4.12.3. The template element
* 4.12.4. The canvas element
* 7.1.5.3. Event firing
* 11.3.1. The applet element
* 11.3.2. The marquee element
* 11.3.3. Frames (2)
* 11.3.4. Other elements, attributes and APIs (2)
* Elements (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15)
(16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26) (27) (28) (29)
(30) (31) (32) (33) (34) (35) (36) (37) (38) (39)
* Element Interfaces (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
(14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26) (27)
(28) (29) (30) (31) (32) (33) (34) (35) (36) (37) (38) (39) (40) (41)
(42) (43) (44) (45) (46) (47) (48) (49) (50) (51) (52) (53) (54) (55)
(56) (57) (58) (59) (60) (61) (62) (63) (64) (65) (66) (67) (68) (69)
(70) (71) (72) (73) (74) (75) (76) (77) (78) (79) (80) (81) (82) (83)
(84) (85) (86) (87) (88) (89) (90) (91) (92) (93) (94) (95) (96) (97)
(98) (99) (100) (101) (102) (103) (104) (105) (106) (107) (108) (109)
(110) (111)
#htmlunknownelementReferenced in:
* 3.2.2. Elements in the DOM (2) (3) (4) (5)
#categoriesReferenced in:
* 3.2.3. Element definitions
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element
* 4.4.13. The figcaption element
* 4.4.14. The main element
* 4.4.15. The div element
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.9. The param element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.12. The track element
* 4.7.14. The map element
* 4.7.15. The area element
* 4.9.1. The table element
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.3. The form element
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.11.1. The details element
* 4.11.2. The summary element
* 4.11.4. The dialog element
* 4.12.1. The script element
* 4.12.2. The noscript element
* 4.12.3. The template element
* 4.12.4. The canvas element
#contexts-in-which-this-element-can-be-usedReferenced in:
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element
* 4.4.13. The figcaption element
* 4.4.14. The main element
* 4.4.15. The div element
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.9. The param element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.12. The track element
* 4.7.14. The map element
* 4.7.15. The area element
* 4.9.1. The table element
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.3. The form element
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.11.1. The details element
* 4.11.2. The summary element
* 4.11.4. The dialog element
* 4.12.1. The script element
* 4.12.2. The noscript element
* 4.12.3. The template element
* 4.12.4. The canvas element
#content-modelReferenced in:
* 3.2.3. Element definitions
* 3.2.4.2.5. Phrasing content (2)
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element
* 4.4.13. The figcaption element
* 4.4.14. The main element
* 4.4.15. The div element
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.9. The param element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.12. The track element
* 4.7.14. The map element
* 4.7.15. The area element
* 4.9.1. The table element
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.3. The form element
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.11.1. The details element
* 4.11.2. The summary element
* 4.11.4. The dialog element
* 4.12.1. The script element
* 4.12.2. The noscript element
* 4.12.3. The template element
* 4.12.4. The canvas element
* 8.1.2. Elements
* 8.1.2.4. Optional tags (2)
#tag-omission-in-text-htmlReferenced in:
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element
* 4.4.13. The figcaption element
* 4.4.14. The main element
* 4.4.15. The div element
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.9. The param element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.12. The track element
* 4.7.14. The map element
* 4.7.15. The area element
* 4.9.1. The table element
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.3. The form element
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.11.1. The details element
* 4.11.2. The summary element
* 4.11.4. The dialog element
* 4.12.1. The script element
* 4.12.2. The noscript element
* 4.12.3. The template element
* 4.12.4. The canvas element
#content-attributesReferenced in:
* 2.1. Terminology
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element
* 4.4.13. The figcaption element
* 4.4.14. The main element
* 4.4.15. The div element
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.9. The param element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.12. The track element
* 4.7.14. The map element
* 4.7.15. The area element
* 4.9.1. The table element
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.3. The form element
* 4.10.4. The label element
* 4.10.5. The input element (2)
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.11.1. The details element
* 4.11.2. The summary element
* 4.11.4. The dialog element
* 4.12.1. The script element
* 4.12.2. The noscript element
* 4.12.3. The template element
* 4.12.4. The canvas element
#allowed-aria-role-attribute-valuesReferenced in:
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element
* 4.4.13. The figcaption element
* 4.4.14. The main element
* 4.4.15. The div element
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.9. The param element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.12. The track element
* 4.7.14. The map element
* 4.7.15. The area element
* 4.9.1. The table element
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.10.3. The form element
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.11.1. The details element
* 4.11.2. The summary element
* 4.11.4. The dialog element
* 4.12.1. The script element
* 4.12.2. The noscript element
* 4.12.3. The template element
* 4.12.4. The canvas element
#allowed-aria-state-and-property-attributesReferenced in:
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element
* 4.4.13. The figcaption element
* 4.4.14. The main element
* 4.4.15. The div element
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.9. The param element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.12. The track element
* 4.7.14. The map element
* 4.7.15. The area element
* 4.9.1. The table element
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.3. The form element
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.11.1. The details element
* 4.11.2. The summary element
* 4.11.4. The dialog element
* 4.12.1. The script element
* 4.12.2. The noscript element
* 4.12.3. The template element
* 4.12.4. The canvas element
#dom-interfaceReferenced in:
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element
* 4.4.13. The figcaption element
* 4.4.14. The main element
* 4.4.15. The div element
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.9. The param element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.12. The track element
* 4.7.14. The map element
* 4.7.15. The area element
* 4.9.1. The table element
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.3. The form element
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.11.1. The details element
* 4.11.2. The summary element
* 4.11.4. The dialog element
* 4.12.1. The script element
* 4.12.2. The noscript element
* 4.12.3. The template element
* 4.12.4. The canvas element
#element-contentsReferenced in:
* 3.2.4. Content models
* 3.2.4.2.8. Palpable content
* 3.2.4.4. Paragraphs
* 3.2.7.1. Authoring conformance criteria for bidirectional-algorithm
formatting characters
* 4.7.5. The img element
* 8.1.2. Elements
#inter-element-white-spaceReferenced in:
* 3.2.4. Content models (2) (3)
* 3.2.4.1. The "nothing" content model
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 3.2.4.4. Paragraphs (2)
* 4.2.2. The title element
* 4.3.3. The section element
* 4.5.10. The ruby element (2) (3) (4)
* 4.5.13. The rtc element
* 4.7.5. The img element
* 4.7.17. MathML
* 4.10.10. The option element
* 10.3.10. Margin collapsing quirks
* Element content categories
#nothingReferenced in:
* 4.2.3. The base element
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.4.3. The hr element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.7.4. The source element
* 4.7.7. The embed element
* 4.7.9. The param element
* 4.7.12. The track element
* 4.7.15. The area element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.10.5. The input element
* 4.10.10. The option element
#metadata-content-2Referenced in:
* 3.2.4.2.1. Metadata content
* 4.2.1. The head element (2)
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.4. The link element (2)
* 4.2.5. The meta element (2)
* 4.2.6. The style element (2)
* 4.12.1. The script element (2)
* 4.12.2. The noscript element
* 4.12.3. The template element (2)
* Elements (2) (3) (4) (5) (6) (7) (8) (9) (10)
* Element content categories
#flow-content-2Referenced in:
* 3.2.3. Element definitions (2) (3) (4)
* 3.2.4.2.8. Palpable content
* 3.2.4.3. Transparent content models
* 3.2.4.4. Paragraphs
* 4.2.4. The link element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element (2) (3)
* 4.3.3. The section element (2) (3)
* 4.3.4. The nav element (2) (3)
* 4.3.5. The aside element (2) (3)
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements (2)
* 4.3.7. The header element (2) (3)
* 4.3.8. The footer element (2) (3)
* 4.4.1. The p element (2)
* 4.4.2. The address element (2) (3)
* 4.4.3. The hr element (2)
* 4.4.4. The pre element (2)
* 4.4.5. The blockquote element (2) (3)
* 4.4.6. The ol element (2)
* 4.4.7. The ul element (2)
* 4.4.8. The li element
* 4.4.9. The dl element (2)
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element (2) (3) (4)
* 4.4.13. The figcaption element
* 4.4.14. The main element (2) (3)
* 4.4.15. The div element (2) (3)
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.9. The param element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.12. The track element
* 4.7.14. The map element
* 4.7.15. The area element
* 4.7.17. MathML (2)
* 4.7.18. SVG (2)
* 4.9.1. The table element (2)
* 4.9.2. The caption element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.2. Categories
* 4.10.3. The form element (2) (3)
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.8. The datalist element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element (2) (3)
* 4.11.1. The details element (2) (3)
* 4.11.4. The dialog element (2) (3)
* 4.12.1. The script element
* 4.12.2. The noscript element
* 4.12.3. The template element
* 4.12.4. The canvas element
* Elements (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15)
(16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26) (27) (28) (29)
(30) (31) (32) (33) (34) (35) (36) (37) (38) (39) (40) (41) (42) (43)
(44) (45) (46) (47) (48) (49) (50) (51) (52) (53) (54) (55) (56) (57)
(58) (59) (60) (61) (62) (63) (64) (65) (66) (67) (68) (69) (70) (71)
(72) (73) (74) (75) (76) (77) (78) (79) (80) (81) (82) (83) (84) (85)
(86) (87) (88) (89) (90) (91) (92) (93) (94) (95) (96) (97) (98) (99)
(100) (101) (102) (103) (104) (105) (106) (107) (108) (109) (110)
(111) (112) (113) (114) (115) (116) (117) (118) (119) (120) (121)
(122) (123) (124)
* Element content categories
#sectioning-content-2Referenced in:
* 3.2.4.2.3. Sectioning content (2)
* 3.2.4.2.4. Heading content
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element (2) (3)
* 4.3.7. The header element (2) (3) (4) (5)
* 4.3.8. The footer element (2) (3) (4)
* 4.3.9. Headings and sections (2) (3) (4) (5)
* 4.3.9.1. Creating an outline (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.4.2. The address element
* 4.4.8. The li element (2)
* 4.4.10. The dt element
* 4.4.14. The main element (2)
* 4.9.10. The th element
* Elements (2) (3) (4)
* Element content categories
#heading-content-2Referenced in:
* 3.2.4.2.3. Sectioning content
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.9. Headings and sections
* 4.3.9.1. Creating an outline (2) (3) (4) (5) (6)
* 4.4.2. The address element
* 4.4.10. The dt element
* 4.9.10. The th element
* 4.11.2. The summary element
* Elements
* Element content categories
#phrasing-content-2Referenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 3.2.3. Element definitions (2) (3) (4) (5)
* 3.2.4.2.5. Phrasing content (2)
* 3.2.4.2.8. Palpable content
* 3.2.4.3. Transparent content models (2) (3)
* 3.2.4.4. Paragraphs (2) (3) (4)
* 4.2.4. The link element (2) (3)
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.4.1. The p element
* 4.4.4. The pre element
* 4.5.1. The a element (2)
* 4.5.2. The em element (2) (3)
* 4.5.3. The strong element (2) (3)
* 4.5.4. The small element (2) (3)
* 4.5.5. The s element (2) (3)
* 4.5.6. The cite element (2) (3)
* 4.5.7. The q element (2) (3) (4)
* 4.5.8. The dfn element (2) (3)
* 4.5.9. The abbr element (2) (3)
* 4.5.10. The ruby element (2) (3)
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.15. The data element (2) (3)
* 4.5.16. The time element (2) (3)
* 4.5.17. The code element (2) (3)
* 4.5.18. The var element (2) (3)
* 4.5.19. The samp element (2) (3)
* 4.5.20. The kbd element (2) (3)
* 4.5.21. The sub and sup elements (2) (3)
* 4.5.22. The i element (2) (3)
* 4.5.23. The b element (2) (3)
* 4.5.24. The u element (2) (3)
* 4.5.25. The mark element (2) (3)
* 4.5.26. The bdi element (2) (3)
* 4.5.27. The bdo element (2) (3)
* 4.5.28. The span element (2) (3)
* 4.5.29. The br element (2)
* 4.5.30. The wbr element (2)
* 4.6.1. The ins element (2) (3)
* 4.6.2. The del element (2)
* 4.6.4. Edits and paragraphs
* 4.7.3. The picture element
* 4.7.5. The img element
* 4.7.6. The iframe element (2)
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.14. The map element (2)
* 4.7.15. The area element (2)
* 4.7.17. MathML (2)
* 4.7.18. SVG (2)
* 4.10.2. Categories
* 4.10.4. The label element (2) (3)
* 4.10.5. The input element (2)
* 4.10.6. The button element (2) (3)
* 4.10.7. The select element (2)
* 4.10.8. The datalist element (2) (3)
* 4.10.11. The textarea element (2)
* 4.10.12. The output element (2) (3)
* 4.10.13. The progress element (2) (3)
* 4.10.14. The meter element (2) (3)
* 4.10.16. The legend element
* 4.11.2. The summary element
* 4.12.1. The script element (2)
* 4.12.2. The noscript element (2)
* 4.12.3. The template element (2)
* 4.12.4. The canvas element
* Elements (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15)
(16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26) (27) (28) (29)
(30) (31) (32) (33) (34) (35) (36) (37) (38) (39) (40) (41) (42) (43)
(44) (45) (46) (47) (48) (49) (50) (51) (52) (53) (54) (55) (56) (57)
(58) (59) (60) (61) (62) (63) (64) (65) (66) (67) (68) (69) (70) (71)
(72) (73) (74) (75) (76) (77) (78) (79) (80) (81) (82) (83) (84) (85)
(86) (87) (88) (89) (90) (91) (92) (93) (94) (95) (96) (97) (98) (99)
(100) (101) (102) (103) (104) (105) (106) (107) (108) (109) (110)
(111) (112) (113) (114) (115) (116) (117) (118) (119) (120) (121)
(122) (123) (124) (125) (126) (127) (128) (129) (130) (131) (132)
(133) (134) (135) (136) (137) (138) (139) (140) (141) (142) (143)
(144) (145)
* Element content categories
#text-contentReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content (2) (3) (4)
* 3.2.4.2.8. Palpable content (2)
* 3.2.7.1. Authoring conformance criteria for bidirectional-algorithm
formatting characters
* 4.2.2. The title element
* 4.5.10. The ruby element
* 4.5.16. The time element
* 4.10.5. The input element
* 4.10.10. The option element (2) (3)
* 4.10.11. The textarea element
* 5.7.5. Drag-and-drop processing model (2) (3)
* 8.1.2. Elements (2) (3) (4) (5)
* 8.1.2.3. Attributes
* 8.1.4. Character references (2)
* 8.1.5. CDATA sections
* 8.1.6. Comments (2)
* 10.3.5. Bidirectional text
* Elements (2) (3)
* Element content categories (2) (3)
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14)
(15) (16) (17) (18) (19) (20) (21) (22)
#embedded-content-2Referenced in:
* 3.2.4.2.6. Embedded content
* 3.2.4.4. Paragraphs
* 4.7.3. The picture element (2)
* 4.7.5. The img element (2) (3)
* 4.7.6. The iframe element (2)
* 4.7.7. The embed element (2)
* 4.7.8. The object element (2)
* 4.7.10. The video element (2)
* 4.7.11. The audio element (2)
* 4.7.17. MathML
* 4.7.18. SVG
* 4.12.4. The canvas element (2) (3) (4) (5) (6) (7) (8)
* 10.4.1. Embedded content
* Elements (2) (3) (4) (5) (6) (7) (8)
* Element content categories
#fallback-contentReferenced in:
* 3.1.3. DOM tree accessors
* 4.7.5. The img element (2)
* 4.7.6. The iframe element
* 4.7.7. The embed element (2) (3)
* 4.7.8. The object element (2) (3) (4) (5) (6)
* 4.7.16.2. Processing model
* 4.12.4. The canvas element (2) (3) (4) (5)
* 11.3.1. The applet element
#interactive-content-2Referenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 3.2.4.2.7. Interactive content
* 3.2.5.1. The title attribute
* 4.5.1. The a element (2)
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.10.2. Categories
* 4.10.4. The label element (2) (3)
* 4.10.5. The input element
* 4.10.6. The button element (2)
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.11.1. The details element
* 5.4.3. The tabindex attribute
* Elements (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14)
* Element content categories (2)
#palpable-content-2Referenced in:
* 3.2.4.2.8. Palpable content
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.9. The dl element
* 4.4.12. The figure element
* 4.4.14. The main element
* 4.4.15. The div element
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.6.1. The ins element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.14. The map element
* 4.7.17. MathML
* 4.7.18. SVG
* 4.9.1. The table element
* 4.10.3. The form element
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.11.1. The details element
* 4.12.4. The canvas element
* Element content categories
#script-supporting-elements-2Referenced in:
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.9. The dl element (2) (3)
* 4.7.3. The picture element
* 4.9.1. The table element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.10.7. The select element
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.12.1. The script element (2)
* 4.12.3. The template element (2)
* Elements (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15)
* Element content categories
#transparentReferenced in:
* 3.2.4.3. Transparent content models
* 4.5.1. The a element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.8. The object element
* 4.7.10. The video element (2)
* 4.7.11. The audio element (2)
* 4.7.14. The map element
* 4.12.2. The noscript element (2)
* 4.12.4. The canvas element
* Elements (2) (3) (4) (5) (6) (7) (8)
#paragraphReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 3.2.4.2.5. Phrasing content
* 3.2.4.4. Paragraphs (2) (3) (4)
* 4.4.1. The p element (2)
* 4.4.3. The hr element
* 4.5.29. The br element
* 4.6.1. The ins element (2)
* 4.6.2. The del element
* 4.6.4. Edits and paragraphs (2) (3) (4)
#global-attributes-2Referenced in:
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element
* 4.4.13. The figcaption element
* 4.4.14. The main element
* 4.4.15. The div element
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element (2)
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.9. The param element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.12. The track element
* 4.7.14. The map element
* 4.7.15. The area element
* 4.9.1. The table element
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.3. The form element
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.11.1. The details element
* 4.11.2. The summary element
* 4.11.4. The dialog element
* 4.12.1. The script element
* 4.12.2. The noscript element
* 4.12.3. The template element
* 4.12.4. The canvas element
* Elements (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15)
(16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26) (27) (28) (29)
(30) (31) (32) (33) (34) (35) (36) (37) (38) (39) (40) (41) (42) (43)
(44) (45) (46) (47) (48) (49) (50) (51) (52) (53) (54) (55) (56) (57)
(58) (59) (60) (61) (62) (63) (64) (65) (66) (67) (68) (69) (70) (71)
(72) (73) (74) (75) (76) (77) (78) (79) (80) (81) (82) (83) (84) (85)
(86) (87) (88) (89) (90) (91) (92) (93) (94) (95) (96) (97) (98) (99)
(100) (101) (102) (103) (104) (105) (106)
#element-attrdef-global-classReferenced in:
* 1.5.3. Extensibility
* 2.2.2. Dependencies
* 3.2.5. Global attributes (2) (3) (4)
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
* 4.4.5. The blockquote element (2)
* 4.4.15. The div element
* 4.5.17. The code element
* 4.5.23. The b element
* 4.5.28. The span element
* 8.1.2.4. Optional tags
* 8.2.8.6. Unclosed formatting elements (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11)
#element-attrdef-global-idReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 2.4.9. References
* 2.7.1. Reflecting content attributes in IDL attributes (2) (3)
* 2.7.2.1. The HTMLAllCollection interface (2)
* 2.7.2.2. The HTMLFormControlsCollection interface (2) (3) (4) (5)
* 2.7.2.3. The HTMLOptionsCollection interface (2)
* 3.1.3. DOM tree accessors (2) (3) (4) (5) (6) (7)
* 3.2.5. Global attributes (2) (3) (4) (5)
* 4.7.13.11.5. Text track API
* 4.7.14. The map element
* 4.9.11. Attributes common to td and th elements (2)
* 4.10.3. The form element (2) (3) (4) (5) (6)
* 4.10.4. The label element
* 6.3.3. Named access on the Window object (2) (3)
* 8.2.8.4. Scripts that modify the page as it is being parsed
* 8.3. Serializing HTML fragments (2) (3)
* 11.1. Obsolete but conforming features
* 11.2. Non-conforming features
#element-attrdef-global-slotReferenced in:
* 3.2.5. Global attributes (2)
#element-attrdef-global-titleReferenced in:
* 3.2.5. Global attributes
* 3.2.5.1. The title attribute (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 4.2.4. The link element (2)
* 4.2.6. The style element (2)
* 4.4.15. The div element
* 4.5.8. The dfn element
* 4.7.5. The img element
* 4.10.14. The meter element (2)
* 4.13.3. Tag clouds
* 4.13.5. Footnotes (2) (3) (4) (5)
* 5.4.2. Data model
* 5.7.7. The draggable attribute
* 10.7.2. The title attribute (2) (3)
* 11.2. Non-conforming features
* Attributes
#advisory-informationReferenced in:
* 3.2.5.1. The title attribute (2)
* 10.7.2. The title attribute (2)
#dom-htmlelement-titleReferenced in:
* 3.2.2. Elements in the DOM
#element-attrdef-global-langReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 3.2.1. Semantics
* 3.2.5. Global attributes
* 3.2.5.2. The lang and xml:lang attributes (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19)
* 3.2.5.3. The translate attribute
* 4.1.1. The html element
* 4.2.5.1. Standard metadata names
* 4.2.5.3. Pragma directives
* 4.4.15. The div element
* 4.5.22. The i element (2)
* 4.5.28. The span element
* 4.7.12. The track element
* 4.15.1. Case-sensitivity
* 8.1.2.4. Optional tags
* 8.2.5.1. Creating and inserting nodes
#element-attrdef-xml-langReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 3.2.5.2. The lang and xml:lang attributes (2) (3)
* 8.1.2.3. Attributes
* 8.2.5.1. Creating and inserting nodes
#languageReferenced in:
* 4.2.5.1. Standard metadata names (2) (3) (4)
* 4.7.13.11.2. Sourcing in-band text tracks
* 4.8.6.1. Link type "alternate"
* 4.10.5.2. Implementation notes regarding localization of form controls
* Attributes
#dom-htmlelement-langReferenced in:
* 3.2.2. Elements in the DOM
#element-attrdef-global-translateReferenced in:
* 3.2.5. Global attributes
* 3.2.5.3. The translate attribute (2) (3) (4) (5)
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
* Attributes
#translation-modeReferenced in:
* 3.2.5.3. The translate attribute (2) (3) (4)
#translate-enabledReferenced in:
* 3.2.5.3. The translate attribute (2) (3) (4)
#no-translateReferenced in:
* 3.2.5.3. The translate attribute (2)
#translatable-attributesReferenced in:
* 3.2.5.3. The translate attribute (2)
#dom-htmlelement-translateReferenced in:
* 3.2.2. Elements in the DOM
#element-attrdef-xml-baseReferenced in:
* 3.2.5.4. The xml:base attribute (XML only) (2) (3)
#element-attrdef-global-dirReferenced in:
* 3.1.3. DOM tree accessors
* 3.2.5. Global attributes (2) (3)
* 3.2.5.5. The dir attribute (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18)
* 3.2.7.1. Authoring conformance criteria for bidirectional-algorithm
formatting characters
* 3.2.7.2. User agent conformance criteria
* 4.5.27. The bdo element
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.11. The textarea element
* 10.3.5. Bidirectional text
* 10.7.4. Text rendered in native user interfaces
#attr-valuedef-global-dir-ltrReferenced in:
* 3.2.5.5. The dir attribute (2) (3) (4)
* 4.5.27. The bdo element
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.11. The textarea element
* 4.10.21.4. Constructing the form data set
* Attributes (2)
#statedef-dir-ltrReferenced in:
* 3.2.5.5. The dir attribute (2) (3) (4) (5)
* 4.10.21.4. Constructing the form data set
* 4.15.2. Pseudo-classes
#attr-valuedef-global-dir-rtlReferenced in:
* 3.2.5. Global attributes
* 3.2.5.5. The dir attribute (2) (3) (4)
* 4.5.27. The bdo element
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.11. The textarea element
* 4.10.21.4. Constructing the form data set
* Attributes (2)
#statedef-dir-rtlReferenced in:
* 3.2.5.5. The dir attribute (2) (3)
* 4.10.21.4. Constructing the form data set
* 4.15.2. Pseudo-classes
#attr-valuedef-global-dir-autoReferenced in:
* 3.2.5.5. The dir attribute (2)
* 4.5.27. The bdo element
* Attributes
#statedef-dir-autoReferenced in:
* 3.2.5.5. The dir attribute (2) (3) (4)
* 10.3.5. Bidirectional text
#directionalityReferenced in:
* 3.2.5. Global attributes
* 3.2.5.5. The dir attribute (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17)
* 4.2.2. The title element
* 4.10.5. The input element (2)
* 4.10.11. The textarea element (2) (3)
* 4.10.18.2. Submitting element directionality: the dirname attribute
* 4.10.21.4. Constructing the form data set (2)
* 4.15.2. Pseudo-classes (2)
* 10.7.4. Text rendered in native user interfaces
* Attributes
#directionality-of-the-attributeReferenced in:
* 3.2.5.5. The dir attribute (2) (3)
* 10.7.4. Text rendered in native user interfaces
#directionality-capable-attributesReferenced in:
* 3.2.5.5. The dir attribute
* 10.7.4. Text rendered in native user interfaces
#dom-htmlelement-dirReferenced in:
* 3.2.2. Elements in the DOM
#dom-document-dirReferenced in:
* 3.1.1. The Document object
* 3.1.3. DOM tree accessors
* 3.2.5.5. The dir attribute
#element-attrdef-global-styleReferenced in:
* 1.10.1. Presentational markup (2)
* 2.2.1. Conformance classes
* 2.2.2. Dependencies
* 3.2.5. Global attributes
* 3.2.5.3. The translate attribute
* 3.2.5.6. The style attribute (2) (3) (4) (5)
* 10.4.4. Image maps
#custom-data-attributeReferenced in:
* 3.2.5. Global attributes
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
(2) (3) (4)
#element-attrdef-global-dataReferenced in:
* 1.5.3. Extensibility
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
(2) (3) (4)
#dom-htmlelement-datasetReferenced in:
* 3.2.2. Elements in the DOM
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
(2) (3)
#associated-elementReferenced in:
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
(2) (3)
#domstringmapReferenced in:
* 3.2.2. Elements in the DOM
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
(2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
#domstringmap-__getter__Referenced in:
* 3.2.5.7. Embedding custom non-visible data with the data-* attributes
(2) (3)
#dom-htmlelement-innertextReferenced in:
* 3.2.2. Elements in the DOM
* 3.2.6. The innerText IDL attribute (2) (3)
#do-not-setReferenced in:
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.12. The figure element
* 4.4.14. The main element
* 4.5.1. The a element
* 4.7.15. The area element
* 4.9.1. The table element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.3. The form element
* 4.10.5.1.2. Text (type=text) state and Search state (type=search) (2)
* 4.10.5.1.3. Telephone state (type=tel) (2)
* 4.10.5.1.4. URL state (type=url) (2)
* 4.10.5.1.5. E-mail state (type=email) (2)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.6. The button element
* 4.10.8. The datalist element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.11.1. The details element
* 4.11.4. The dialog element
#global-aria--attributesReferenced in:
* 3.2.3. Element definitions
* 3.2.5. Global attributes
* 3.2.8.4. Allowed ARIA roles, states and properties
* 4.2.1. The head element
* 4.2.2. The title element
* 4.2.3. The base element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.3.1. The body element
* 4.3.2. The article element
* 4.3.3. The section element
* 4.3.4. The nav element
* 4.3.5. The aside element
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.7. The header element
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.3. The hr element
* 4.4.4. The pre element
* 4.4.5. The blockquote element
* 4.4.6. The ol element
* 4.4.7. The ul element
* 4.4.8. The li element
* 4.4.9. The dl element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.4.12. The figure element
* 4.4.13. The figcaption element
* 4.4.14. The main element
* 4.4.15. The div element
* 4.5.1. The a element
* 4.5.2. The em element
* 4.5.3. The strong element
* 4.5.4. The small element
* 4.5.5. The s element
* 4.5.6. The cite element
* 4.5.7. The q element
* 4.5.8. The dfn element
* 4.5.9. The abbr element
* 4.5.10. The ruby element
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.15. The data element
* 4.5.16. The time element
* 4.5.17. The code element
* 4.5.18. The var element
* 4.5.19. The samp element
* 4.5.20. The kbd element
* 4.5.21. The sub and sup elements
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.26. The bdi element
* 4.5.27. The bdo element
* 4.5.28. The span element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.9. The param element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.12. The track element
* 4.7.14. The map element
* 4.7.15. The area element
* 4.9.1. The table element
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.3. The form element
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.8. The datalist element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.11.1. The details element
* 4.11.2. The summary element
* 4.11.4. The dialog element
* 4.12.2. The noscript element
* 4.12.4. The canvas element
#elementdef-htmlReferenced in:
* 1.9. A quick introduction to HTML (2)
* 3.1.3. DOM tree accessors (2) (3) (4)
* 3.2.5.2. The lang and xml:lang attributes
* 3.2.5.5. The dir attribute (2) (3) (4)
* 4.1.1. The html element (2) (3) (4) (5) (6) (7) (8)
* 4.2.1. The head element
* 4.2.3. The base element
* 4.3.1. The body element (2) (3)
* 4.7.6. The iframe element (2)
* 6.1. Browsing contexts
* 6.7.6. Page load processing model for media (2)
* 6.7.7. Page load processing model for content that uses plugins (2)
* 8.1. Writing HTML documents (2) (3) (4) (5) (6)
* 8.1.2.4. Optional tags (2) (3) (4) (5) (6) (7) (8)
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements (2) (3) (4) (5) (6) (7)
* 8.2.5.1. Creating and inserting nodes
* 8.2.5.4.2. The "before html" insertion mode
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4)
* 8.2.5.4.9. The "in table" insertion mode (2)
* 8.2.5.4.13. The "in table body" insertion mode (2)
* 8.2.5.4.14. The "in row" insertion mode (2)
* 8.2.5.4.19. The "after body" insertion mode
* 8.2.5.4.20. The "in frameset" insertion mode (2) (3)
* 8.2.8.1. Misnested tags: <b><i></b></i> (2) (3) (4)
* 8.2.8.2. Misnested tags: <b><p></b></p> (2) (3) (4) (5) (6)
* 8.2.8.3. Unexpected markup in tables (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11)
* 8.2.8.4. Scripts that modify the page as it is being parsed (2) (3)
* 8.2.8.6. Unclosed formatting elements
* 8.3. Serializing HTML fragments (2) (3) (4)
* 8.4. Parsing HTML fragments
* 11.2. Non-conforming features
* 11.3.4. Other elements, attributes and APIs
* Elements (2) (3)
* Attributes
* Element Interfaces
#htmlhtmlelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#element-attrdef-html-manifestReferenced in:
* 4.1.1. The html element (2) (3)
* 4.2.3. The base element
* Elements
* Attributes
#elementdef-headReferenced in:
* 1.9. A quick introduction to HTML (2) (3) (4)
* 3.1.3. DOM tree accessors (2) (3) (4) (5) (6) (7)
* 4.1.1. The html element
* 4.2.1. The head element (2) (3) (4) (5) (6) (7)
* 4.2.2. The title element (2)
* 4.2.3. The base element
* 4.2.4. The link element
* 4.2.5. The meta element (2) (3)
* 4.2.5.1. Standard metadata names (2)
* 4.2.5.3. Pragma directives (2)
* 4.2.5.5. Specifying the document’s character encoding
* 4.2.6. The style element (2)
* 4.7.6. The iframe element
* 4.12.2. The noscript element (2) (3) (4) (5) (6) (7)
* 6.1. Browsing contexts
* 6.6.2. The History interface
* 6.7.4. Page load processing model for text files
* 6.7.6. Page load processing model for media (2)
* 6.7.7. Page load processing model for content that uses plugins (2)
* 8.1. Writing HTML documents (2)
* 8.1.2.4. Optional tags (2) (3) (4) (5) (6)
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements
* 8.2.3.4. The element pointers (2)
* 8.2.5.4.3. The "before head" insertion mode (2)
* 8.2.5.4.4. The "in head" insertion mode (2)
* 8.2.5.4.5. The "in head noscript" insertion mode (2)
* 8.2.8.1. Misnested tags: <b><i></b></i> (2)
* 8.2.8.2. Misnested tags: <b><p></b></p> (2) (3) (4) (5)
* 8.2.8.3. Unexpected markup in tables (2) (3) (4) (5) (6) (7)
* 8.2.8.4. Scripts that modify the page as it is being parsed (2) (3)
* 8.2.8.6. Unclosed formatting elements
* 8.3. Serializing HTML fragments (2) (3) (4)
* 11.2. Non-conforming features
* 11.3.4. Other elements, attributes and APIs
* Elements (2) (3) (4) (5) (6) (7) (8) (9)
* Element Interfaces
* Changes between Working Draft 6 and Working Draft 5
#htmlheadelementReferenced in:
* 3.1.1. The Document object
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#elementdef-titleReferenced in:
* 1.9. A quick introduction to HTML (2)
* 3.1.3. DOM tree accessors (2) (3) (4) (5) (6) (7) (8) (9)
* 3.2.4.2.1. Metadata content
* 4.2.1. The head element (2) (3) (4)
* 4.2.2. The title element (2) (3) (4) (5) (6) (7)
* 4.2.5. The meta element
* 4.2.5.1. Standard metadata names
* 4.7.6. The iframe element
* 6.6.1. The session history of browsing contexts
* 6.6.2. The History interface (2)
* 6.7.4. Page load processing model for text files
* 6.7.6. Page load processing model for media
* 6.7.7. Page load processing model for content that uses plugins
* 8.1.2. Elements
* 8.2.3.2. The stack of open elements
* 8.4. Parsing HTML fragments
* Elements
* Element content categories
* Element Interfaces
#htmltitleelementReferenced in:
* Elements
* Element Interfaces
#dom-htmltitleelement-textReferenced in:
* 4.2.2. The title element
#elementdef-baseReferenced in:
* 1.9.1. Writing secure applications with HTML
* 2.5.1. Terminology (2)
* 3.2.4.2.1. Metadata content
* 4.1.1. The html element
* 4.2.1. The head element (2)
* 4.2.3. The base element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16) (17) (18) (19) (20)
* 4.2.5. The meta element
* 4.8.4. Following hyperlinks (2)
* 4.10.18.6. Form submission (2)
* 8.1.2. Elements
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* Elements
* Element content categories
* Attributes (2)
* Element Interfaces
#htmlbaseelementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-base-hrefReferenced in:
* 2.5.1. Terminology (2)
* 4.2.3. The base element (2) (3) (4) (5) (6) (7) (8) (9) (10)
* Elements
#element-attrdef-base-targetReferenced in:
* Elements
* Attributes
#frozen-base-urlReferenced in:
* 2.5.1. Terminology
* 4.2.3. The base element (2)
#set-the-frozen-base-urlReferenced in:
* 4.2.3. The base element
#dom-htmlbaseelement-hrefReferenced in:
* 4.2.3. The base element (2)
#dom-htmlbaseelement-targetReferenced in:
* 4.2.3. The base element
#elementdef-linkReferenced in:
* 3.2.4.2.1. Metadata content
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.5.1. The title attribute (2)
* 4.2.4. The link element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14)
* 4.2.4.3. Obtaining a resource from a link element (2) (3) (4) (5) (6)
* 4.2.4.5. Providing users with a means to follow hyperlinks created
using the link element (2) (3) (4) (5)
* 4.2.4.6. The LinkStyle interface
* 4.2.5. The meta element
* 4.2.5.2. Other metadata names
* 4.2.6. The style element
* 4.2.7. Interactions of styling and scripting (2)
* 4.3.1. The body element
* 4.8.1. Introduction (2) (3)
* 4.8.2. Links created by a and area elements
* 4.8.6. Link types (2)
* 4.8.6.1. Link type "alternate" (2) (3) (4) (5)
* 4.8.6.2. Link type "author" (2) (3)
* 4.8.6.4. Link type "help" (2)
* 4.8.6.5. Link type "icon"
* 4.8.6.6. Link type "license"
* 4.8.6.10. Link type "search" (2)
* 4.8.6.11. Link type "stylesheet" (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.8.6.13.1. Link type "next"
* 4.8.6.13.2. Link type "prev"
* 4.8.6.14. Other link types (2) (3) (4) (5)
* 4.12.2. The noscript element (2) (3)
* 4.15.2. Pseudo-classes (2)
* 5.4.3. The tabindex attribute
* 8.1.2. Elements
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 10.7.1. Links, forms, and navigation (2)
* 10.9. Unstyled XML documents
* 11.2. Non-conforming features (2) (3) (4) (5)
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element content categories (2) (3)
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* Element Interfaces
* Changes between Working Draft 8 and Working Draft 7
* Changes between Working Draft 2 and the First Public Working Draft
#htmllinkelementReferenced in:
* 4.2.4. The link element
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#element-attrdef-link-hrefReferenced in:
* 4.2.4. The link element
* 4.2.4.3. Obtaining a resource from a link element (2)
* 4.2.4.5. Providing users with a means to follow hyperlinks created
using the link element
* 4.8.6.11. Link type "stylesheet"
* 4.15.2. Pseudo-classes (2)
* 5.4.3. The tabindex attribute
* 11.2. Non-conforming features
* Elements
#element-attrdef-link-crossoriginReferenced in:
* 4.2.4. The link element
* 4.2.4.3. Obtaining a resource from a link element
* Elements
#element-attrdef-link-relReferenced in:
* 1.5.3. Extensibility
* 4.2.4. The link element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
* 4.2.4.5. Providing users with a means to follow hyperlinks created
using the link element
* 4.8.1. Introduction (2)
* 4.8.2. Links created by a and area elements
* 4.8.6. Link types
* 4.8.6.1. Link type "alternate"
* 4.8.6.5. Link type "icon"
* Elements
* Attributes
* Changes between Working Draft 7 and Working Draft 6
#allowed-in-the-bodyReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 4.2.4. The link element (2) (3)
* 4.8.6. Link types
* Element content categories (2)
#element-attrdef-link-mediaReferenced in:
* 4.2.4.1. Processing the media attribute (2) (3)
* 4.2.4.5. Providing users with a means to follow hyperlinks created
using the link element
* 4.8.6.11. Link type "stylesheet"
* Elements
#element-attrdef-link-nonceReferenced in:
* 4.2.4.3. Obtaining a resource from a link element
* Elements
* Changes between Working Draft 2 and the First Public Working Draft
#element-attrdef-link-hreflangReferenced in:
* 4.2.4.5. Providing users with a means to follow hyperlinks created
using the link element
* Elements
#element-attrdef-link-typeReferenced in:
* 4.2.4. The link element
* 4.2.4.2. Processing the type attribute (2) (3) (4)
* 4.2.4.5. Providing users with a means to follow hyperlinks created
using the link element
* Elements
#element-attrdef-link-referrerpolicyReferenced in:
* 4.2.4.3. Obtaining a resource from a link element
* 4.7.15. The area element
* Elements (2) (3)
#element-attrdef-link-titleReferenced in:
* 4.2.4. The link element (2) (3)
* 4.2.4.5. Providing users with a means to follow hyperlinks created
using the link element
* 4.2.6. The style element
* 4.8.6.11. Link type "stylesheet" (2)
* Attributes (2)
#element-attrdef-link-sizesReferenced in:
* 4.8.6.5. Link type "icon"
* Elements
#dom-htmllinkelement-hrefReferenced in:
* 4.2.4. The link element
#dom-htmllinkelement-hreflangReferenced in:
* 4.2.4. The link element (2)
#dom-htmllinkelement-mediaReferenced in:
* 4.2.4. The link element
#dom-htmllinkelement-nonceReferenced in:
* 4.2.4. The link element
#dom-htmllinkelement-relReferenced in:
* 4.2.4. The link element
#dom-htmllinkelement-revReferenced in:
* 4.2.4. The link element
#dom-htmllinkelement-sizesReferenced in:
* 4.2.4. The link element
#dom-htmllinkelement-typeReferenced in:
* 4.2.4. The link element
#dom-htmllinkelement-crossoriginReferenced in:
* 4.2.4. The link element
#dom-htmllinkelement-referrerpolicyReferenced in:
* 4.2.4. The link element
#dom-htmllinkelement-rellistReferenced in:
* 4.2.4. The link element
#determining-the-type-of-the-resourceReferenced in:
* 4.8.6.5. Link type "icon"
#obtainReferenced in:
* 4.2.4. The link element
* 4.2.4.2. Processing the type attribute (2) (3) (4)
* 4.8.6.11. Link type "stylesheet" (2) (3) (4) (5)
#elementdef-metaReferenced in:
* 1.5.3. Extensibility
* 2.6.5. Extracting character encodings from meta elements (2)
* 2.6.7. Referrer policy attributes
* 2.7.2.1. The HTMLAllCollection interface (2)
* 3.2.4.2.1. Metadata content
* 3.2.5.2. The lang and xml:lang attributes
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 4.2.5. The meta element (2) (3) (4) (5) (6) (7)
* 4.2.5.1. Standard metadata names (2) (3) (4) (5) (6) (7)
* 4.2.5.2. Other metadata names
* 4.2.5.3. Pragma directives (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20)
* 4.2.5.5. Specifying the document’s character encoding (2) (3) (4)
* 4.3.1. The body element
* 4.12.2. The noscript element (2) (3)
* 8.1.2. Elements
* 8.1.2.4. Optional tags
* 8.2.2.4. Changing the encoding while parsing
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 11.2. Non-conforming features (2)
* 11.3.4. Other elements, attributes and APIs (2) (3) (4) (5)
* Elements
* Element content categories
* Attributes (2) (3) (4)
* Element Interfaces
#htmlmetaelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#element-attrdef-meta-http-equivReferenced in:
* 4.2.5. The meta element
* 4.2.5.3. Pragma directives
* 8.2.2.2. Determining the character encoding
* 8.2.5.4.4. The "in head" insertion mode
* Elements
#element-attrdef-meta-charsetReferenced in:
* 8.2.2.2. Determining the character encoding
* 8.2.5.4.4. The "in head" insertion mode
* Elements
#element-attrdef-meta-contentReferenced in:
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 4.2.5.3. Pragma directives (2) (3) (4)
* 8.2.2.2. Determining the character encoding
* 8.2.5.4.4. The "in head" insertion mode
* Elements
#element-attrdef-meta-nameReferenced in:
* 2.7.2.1. The HTMLAllCollection interface
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 11.3.4. Other elements, attributes and APIs (2) (3) (4)
* Elements
#dom-htmlmetaelement-nameReferenced in:
* 4.2.5. The meta element
#dom-htmlmetaelement-contentReferenced in:
* 4.2.5. The meta element
#dom-htmlmetaelement-httpequivReferenced in:
* 4.2.5. The meta element
#referrerReferenced in:
* 2.6.7. Referrer policy attributes
* 4.8.6.9. Link type "noreferrer"
* 6.1. Browsing contexts
* 7.1.3.2. Fetching scripts
#register-the-namesReferenced in:
* 1.5.3. Extensibility
* 4.2.5.4. Other pragma directives
* 11.2. Non-conforming features
#statedef-http-equiv-content-languageReferenced in:
* 4.2.5.3. Pragma directives
#pragma-set-default-languageReferenced in:
* 3.2.5.2. The lang and xml:lang attributes (2)
* 4.2.5.3. Pragma directives (2)
#statedef-http-equiv-content-typeReferenced in:
* 4.2.5. The meta element (2) (3)
* 4.2.5.3. Pragma directives (2) (3) (4) (5) (6) (7)
* 4.2.5.5. Specifying the document’s character encoding (2)
#statedef-http-equiv-default-styleReferenced in:
* 4.2.5.3. Pragma directives
#statedef-http-equiv-refreshReferenced in:
* 4.2.5.3. Pragma directives (2) (3)
#statedef-http-equiv-set-cookieReferenced in:
* 4.2.5.3. Pragma directives
#statedef-http-equiv-content-security-policy-stateReferenced in:
* 4.2.5.3. Pragma directives
#character-encoding-declarationReferenced in:
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.5. The meta element (2) (3)
* 4.2.5.3. Pragma directives (2)
* 4.2.5.5. Specifying the document’s character encoding (2)
* 8.1. Writing HTML documents
* 12.1. text/html (2)
* Attributes
#the-first-1024-bytesReferenced in:
* 8.2.2.2. Determining the character encoding (2)
#elementdef-styleReferenced in:
* 1.10.1. Presentational markup (2)
* 3.2.4.2.1. Metadata content
* 3.2.4.2.2. Flow content
* 3.2.5.1. The title attribute
* 3.2.5.5. The dir attribute
* 4.2.5. The meta element
* 4.2.6. The style element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19)
* 4.2.7. Interactions of styling and scripting (2) (3)
* 4.3.1. The body element
* 4.12.2. The noscript element (2) (3)
* 8.1.2. Elements
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments (2) (3)
* 8.4. Parsing HTML fragments
* 10.9. Unstyled XML documents
* Elements
* Element content categories
* Attributes (2) (3)
* Element Interfaces
* Changes between Working Draft 6 and Working Draft 5 (2) (3)
#htmlstyleelementReferenced in:
* 4.2.6. The style element
* Elements
* Element Interfaces
#element-attrdef-style-typeReferenced in:
* 4.2.6. The style element
* Elements
#element-attrdef-style-mediaReferenced in:
* 4.2.6. The style element
* Elements
#element-attrdef-style-nonceReferenced in:
* 4.2.6. The style element
* Elements
#element-attrdef-style-titleReferenced in:
* 4.2.6. The style element (2) (3) (4)
* Attributes
#update-a-style-blockReferenced in:
* 4.2.6. The style element
#style-dataReferenced in:
* 4.2.6. The style element (2) (3)
#dom-htmlstyleelement-mediaReferenced in:
* 4.2.6. The style element
#dom-htmlstyleelement-nonceReferenced in:
* 4.2.6. The style element
#dom-htmlstyleelement-typeReferenced in:
* 4.2.6. The style element
#style-sheet-readyReferenced in:
* 4.2.7. Interactions of styling and scripting (2)
#a-style-sheet-that-is-blocking-scriptsReferenced in:
* 4.2.7. Interactions of styling and scripting
* 4.12.1.1. Processing model
#have-a-style-sheet-that-is-blocking-scriptsReferenced in:
* 4.2.7. Interactions of styling and scripting (2)
* 4.12.1.1. Processing model
* 8.2.5.4.8. The "text" insertion mode
#has-no-style-sheet-that-is-blocking-scriptsReferenced in:
* 8.2.5.4.8. The "text" insertion mode
* 8.2.6. The end
* 9.2. Parsing XML documents
#elementdef-bodyReferenced in:
* 1.9. A quick introduction to HTML (2) (3) (4) (5) (6) (7)
* 3.1.3. DOM tree accessors (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13)
* 3.2.5. Global attributes
* 4.1.1. The html element
* 4.2.6. The style element
* 4.3.1. The body element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16)
* 4.3.7. The header element (2) (3) (4)
* 4.3.8. The footer element (2) (3) (4)
* 4.3.9. Headings and sections
* 4.3.9.1. Creating an outline
* 4.3.10. Usage summary
* 4.4.14. The main element
* 4.7.6. The iframe element (2)
* 5.2. Inert subtrees (2)
* 5.4.4. Processing model (2)
* 5.4.6. Focus management APIs (2)
* 6.1. Browsing contexts
* 6.7.6. Page load processing model for media (2)
* 6.7.7. Page load processing model for content that uses plugins (2)
* 7.1.5.1. Event handlers
* 7.1.5.2. Event handlers on elements, Document objects, and Window
objects (2) (3)
* 8.1. Writing HTML documents
* 8.1.2.4. Optional tags (2) (3) (4) (5) (6) (7) (8) (9)
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6)
* 8.2.8.1. Misnested tags: <b><i></b></i> (2) (3) (4)
* 8.2.8.2. Misnested tags: <b><p></b></p> (2) (3) (4) (5) (6) (7)
* 8.2.8.3. Unexpected markup in tables (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11)
* 8.2.8.4. Scripts that modify the page as it is being parsed (2) (3)
* 8.2.8.6. Unclosed formatting elements
* 8.3. Serializing HTML fragments (2) (3) (4)
* 10.3.2. The page (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
(14) (15) (16) (17) (18) (19) (20) (21) (22)
* 10.3.10. Margin collapsing quirks (2)
* 11.2. Non-conforming features (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12)
* 11.3.3. Frames
* 11.3.4. Other elements, attributes and APIs (2) (3) (4) (5) (6) (7)
(8) (9) (10)
* Elements (2)
* Element content categories
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
* Element Interfaces
* Changes between Working Draft 6 and Working Draft 5 (2)
#htmlbodyelementReferenced in:
* 4.3.1. The body element
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#elementdef-articleReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.3. Sectioning content
* 3.2.4.2.8. Palpable content
* 4.3.2. The article element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13)
* 4.3.3. The section element (2)
* 4.3.7. The header element
* 4.3.10. Usage summary
* 4.3.10.1. Article or section? (2) (3) (4)
* 4.4.1. The p element
* 4.4.5. The blockquote element
* 4.4.12. The figure element
* 4.4.14. The main element (2)
* 4.4.15. The div element
* 4.8.6.2. Link type "author"
* 4.8.6.3. Link type "bookmark" (2)
* 4.8.6.12. Link type "tag"
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-sectionReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 3.2.4.2.2. Flow content
* 3.2.4.2.3. Sectioning content
* 3.2.4.2.8. Palpable content
* 4.3.3. The section element (2) (3) (4) (5) (6) (7) (8) (9)
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.9.1. Creating an outline
* 4.3.10. Usage summary
* 4.3.10.1. Article or section? (2)
* 4.4.1. The p element
* 4.4.3. The hr element
* 4.4.15. The div element
* 4.5.8. The dfn element
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-navReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.3. Sectioning content
* 3.2.4.2.8. Palpable content
* 4.3.4. The nav element (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.3.5. The aside element
* 4.3.9.1. Creating an outline
* 4.3.10. Usage summary
* 4.4.1. The p element
* 4.4.14. The main element (2) (3)
* 4.4.15. The div element
* 4.13.2. Bread crumb navigation
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-asideReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.3. Sectioning content
* 3.2.4.2.8. Palpable content
* 4.3.5. The aside element (2) (3) (4) (5) (6)
* 4.3.7. The header element
* 4.3.9.1. Creating an outline
* 4.3.10. Usage summary
* 4.4.1. The p element
* 4.4.12. The figure element (2)
* 4.4.14. The main element (2) (3) (4) (5) (6) (7)
* 4.6.1. The ins element
* 4.13.5. Footnotes (2) (3)
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-h1Referenced in:
* 1.9. A quick introduction to HTML (2)
* 1.10.2. Syntax errors
* 3.2.1. Semantics
* 3.2.4.2.2. Flow content
* 3.2.4.2.4. Heading content
* 3.2.4.2.8. Palpable content
* 4.3.2. The article element
* 4.3.10. Usage summary
* 4.4.1. The p element
* 4.10.16. The legend element
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 10.3.10. Margin collapsing quirks
* 11.2. Non-conforming features
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-h2Referenced in:
* 1.10.2. Syntax errors
* 3.2.1. Semantics
* 3.2.4.2.2. Flow content
* 3.2.4.2.4. Heading content
* 3.2.4.2.8. Palpable content
* 4.4.1. The p element
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 10.3.10. Margin collapsing quirks
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-h3Referenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.4. Heading content
* 3.2.4.2.8. Palpable content
* 4.4.1. The p element
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 10.3.10. Margin collapsing quirks
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-h4Referenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.4. Heading content
* 3.2.4.2.8. Palpable content
* 4.4.1. The p element
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 10.3.10. Margin collapsing quirks
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-h5Referenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.4. Heading content
* 3.2.4.2.8. Palpable content
* 4.4.1. The p element
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 10.3.10. Margin collapsing quirks
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-h6Referenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.4. Heading content
* 3.2.4.2.8. Palpable content
* 4.3.2. The article element
* 4.4.1. The p element
* 4.10.16. The legend element
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 10.3.10. Margin collapsing quirks
* 11.2. Non-conforming features
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element content categories (2) (3)
* Element Interfaces
#htmlheadingelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces (2) (3) (4) (5) (6)
#rankReferenced in:
* 4.3.6. The h1, h2, h3, h4, h5, and h6 elements
* 4.3.9. Headings and sections (2) (3) (4)
* 4.3.9.1. Creating an outline (2) (3) (4)
#elementdef-headerReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 4.3.7. The header element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19)
* 4.3.8. The footer element (2)
* 4.3.10. Usage summary
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.10. The dt element
* 4.4.14. The main element (2) (3) (4) (5) (6)
* 4.9.10. The th element
* 4.13.1. Subheadings, subtitles, alternative titles and taglines (2)
(3)
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* Elements
* Element content categories (2)
* Element Interfaces
#elementdef-footerReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 4.3.4. The nav element
* 4.3.7. The header element (2)
* 4.3.8. The footer element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13)
* 4.3.10. Usage summary
* 4.4.1. The p element
* 4.4.2. The address element
* 4.4.5. The blockquote element (2)
* 4.4.10. The dt element
* 4.4.14. The main element (2) (3) (4) (5) (6)
* 4.9.10. The th element
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* Elements
* Element content categories (2)
* Element Interfaces
#sectioning-rootsReferenced in:
* 3.2.4.2.3. Sectioning content
* 4.3.1. The body element
* 4.3.7. The header element (2)
* 4.3.8. The footer element (2)
* 4.3.9. Headings and sections
* 4.3.9.1. Creating an outline (2) (3) (4) (5) (6) (7) (8) (9)
* 4.4.5. The blockquote element
* 4.4.12. The figure element
* 4.9.9. The td element
* 4.10.15. The fieldset element
* 4.11.1. The details element
* 4.11.4. The dialog element
* Elements (2) (3) (4) (5) (6) (7)
* Element content categories
#outlineReferenced in:
* 2.2.1. Conformance classes
* 3.2.4.2.3. Sectioning content (2)
* 4.3.3. The section element
* 4.3.7. The header element
* 4.3.9.1. Creating an outline (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16)
* 4.4.3. The hr element
* 4.4.14. The main element
#sectionReferenced in:
* 4.3.9.1. Creating an outline (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19)
#associate-sectionReferenced in:
* 4.8.6.3. Link type "bookmark"
#outline-depthReferenced in:
* 4.3.9.1. Creating an outline
#elementdef-pReferenced in:
* 1.9. A quick introduction to HTML (2)
* 1.10.2. Syntax errors (2) (3) (4)
* 1.10.3. Restrictions on content models and on attribute values
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 3.2.4.3. Transparent content models
* 3.2.4.4. Paragraphs (2) (3) (4) (5)
* 3.2.5.5. The dir attribute
* 3.2.6. The innerText IDL attribute
* 4.4.1. The p element (2) (3) (4) (5) (6) (7)
* 4.4.5. The blockquote element
* 4.5.8. The dfn element
* 4.6.4. Edits and paragraphs (2) (3)
* 4.12.3. The template element
* 4.13.1. Subheadings, subtitles, alternative titles and taglines (2)
(3)
* 4.13.4. Conversations
* 4.15.2. Pseudo-classes (2)
* 8.1.2.4. Optional tags (2) (3)
* 8.2.3.2. The stack of open elements
* 8.2.5.3. Closing elements that have implied end tags (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9)
* 8.2.8.1. Misnested tags: <b><i></b></i> (2) (3) (4)
* 8.2.8.2. Misnested tags: <b><p></b></p> (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11)
* 8.2.8.6. Unclosed formatting elements (2) (3) (4) (5)
* 8.3. Serializing HTML fragments (2)
* 10.3.10. Margin collapsing quirks (2)
* 11.2. Non-conforming features
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element content categories (2)
* Element Interfaces
* Changes between Working Draft 6 and Working Draft 5
#htmlparagraphelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#elementdef-addressReferenced in:
* 2.2.1. Conformance classes (2)
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 4.3.8. The footer element
* 4.4.1. The p element
* 4.4.2. The address element (2)
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 8.2.5.4.7. The "in body" insertion mode (2)
* Elements
* Element content categories (2)
* Element Interfaces
#elementdef-hrReferenced in:
* 1.10.1. Presentational markup
* 1.10.2. Syntax errors (2)
* 3.2.4.2.2. Flow content
* 4.4.1. The p element
* 4.4.3. The hr element (2) (3) (4) (5)
* 8.1.2. Elements
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 10.3.12. The hr element (2) (3) (4) (5)
* 11.2. Non-conforming features (2) (3) (4) (5)
* 11.3.4. Other elements, attributes and APIs (2)
* Elements
* Element content categories
* Element Interfaces
#htmlhrelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#elementdef-preReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 3.2.5.5. The dir attribute
* 3.2.7.2. User agent conformance criteria
* 4.4.1. The p element
* 4.4.4. The pre element (2) (3) (4) (5) (6) (7) (8)
* 4.5.17. The code element
* 8.1.2.4. Optional tags
* 8.1.2.5. Restrictions on content models (2)
* 8.2.3.2. The stack of open elements
* 8.2.5.4.7. The "in body" insertion mode
* 10.3.10. Margin collapsing quirks
* 11.2. Non-conforming features (2) (3)
* 11.3.4. Other elements, attributes and APIs (2)
* Elements
* Element content categories (2)
* Element Interfaces
#htmlpreelementReferenced in:
* 3.2.2. Elements in the DOM
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#elementdef-blockquoteReferenced in:
* 2.2.1. Conformance classes (2)
* 2.5.3. Dynamic changes to base URLs
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 4.3.9. Headings and sections
* 4.4.1. The p element
* 4.4.5. The blockquote element (2) (3) (4) (5) (6) (7)
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 10.3.10. Margin collapsing quirks
* 10.7.1. Links, forms, and navigation
* Elements
* Element content categories (2) (3)
* Attributes
* Element Interfaces
#htmlquoteelementReferenced in:
* 4.5.7. The q element
* Elements (2)
* Element Interfaces (2)
#element-attrdef-blockquote-citeReferenced in:
* 4.4.5. The blockquote element (2)
* Elements
#dom-htmlquoteelement-citeReferenced in:
* 4.4.5. The blockquote element
#elementdef-olReferenced in:
* 3.2.1. Semantics
* 3.2.2. Elements in the DOM
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 4.4.1. The p element
* 4.4.6. The ol element (2) (3) (4)
* 4.4.7. The ul element
* 4.4.8. The li element (2) (3) (4)
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements (2)
* 10.3.8. Lists
* 10.3.10. Margin collapsing quirks
* 11.2. Non-conforming features
* 11.3.4. Other elements, attributes and APIs
* Elements (2)
* Element content categories (2)
* Attributes (2) (3)
* Element Interfaces
#htmlolistelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#element-attrdef-ol-reversedReferenced in:
* Elements
#element-attrdef-ol-startReferenced in:
* Elements
#element-attrdef-ol-typeReferenced in:
* Elements
#statedef-ol-decimalReferenced in:
* 4.4.6. The ol element
#dom-htmlolistelement-reversedReferenced in:
* 4.4.6. The ol element
#dom-htmlolistelement-startReferenced in:
* 4.4.6. The ol element
#dom-htmlolistelement-typeReferenced in:
* 4.4.6. The ol element
#elementdef-ulReferenced in:
* 1.10.3. Restrictions on content models and on attribute values (2)
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 4.4.1. The p element (2)
* 4.4.6. The ol element
* 4.4.7. The ul element (2)
* 4.4.8. The li element (2) (3)
* 4.6.5. Edits and lists
* 4.13.3. Tag clouds (2)
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements (2)
* 8.3. Serializing HTML fragments (2)
* 10.3.10. Margin collapsing quirks
* 11.2. Non-conforming features (2) (3)
* 11.3.4. Other elements, attributes and APIs
* Elements (2)
* Element content categories (2)
* Element Interfaces
#htmlulistelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#elementdef-liReferenced in:
* 1.10.3. Restrictions on content models and on attribute values (2)
* 3.2.4.2.8. Palpable content (2)
* 4.4.6. The ol element (2) (3)
* 4.4.7. The ul element (2)
* 4.4.8. The li element (2) (3) (4) (5) (6)
* 4.5.8. The dfn element
* 4.6.5. Edits and lists (2)
* 8.1.2.4. Optional tags (2) (3)
* 8.2.3.2. The stack of open elements
* 8.2.5.3. Closing elements that have implied end tags (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10)
* 10.3.8. Lists (2) (3) (4)
* 11.2. Non-conforming features
* 11.3.4. Other elements, attributes and APIs
* Elements (2) (3)
* Element content categories (2)
* Attributes
* Element Interfaces
#htmllielementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#ordinal-valueReferenced in:
* 4.4.6. The ol element (2) (3) (4) (5) (6)
* 4.4.8. The li element
* 10.3.8. Lists
* Attributes (2)
#element-attrdef-li-valueReferenced in:
* Elements
#dom-htmllielement-valueReferenced in:
* 4.4.8. The li element
#elementdef-dlReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 4.4.1. The p element
* 4.4.9. The dl element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14)
* 4.4.10. The dt element (2) (3)
* 4.4.11. The dd element (2)
* 4.4.15. The div element
* 4.13.4. Conversations
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 10.3.10. Margin collapsing quirks
* 11.2. Non-conforming features
* 11.3.4. Other elements, attributes and APIs
* Elements (2) (3)
* Element content categories (2)
* Element Interfaces
#htmldlistelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#term-description-groupsReferenced in:
* 4.4.9. The dl element (2) (3) (4) (5) (6) (7)
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.5.8. The dfn element
#elementdef-dtReferenced in:
* 4.4.9. The dl element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.4.10. The dt element (2) (3) (4) (5) (6) (7) (8)
* 4.4.11. The dd element (2)
* 4.4.15. The div element
* 8.1.2.4. Optional tags (2) (3) (4)
* 8.2.3.2. The stack of open elements
* 8.2.5.3. Closing elements that have implied end tags (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7)
* Elements (2) (3)
* Element Interfaces
#elementdef-ddReferenced in:
* 4.4.9. The dl element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.4.10. The dt element (2) (3)
* 4.4.11. The dd element (2) (3) (4) (5) (6)
* 4.4.15. The div element
* 8.1.2.4. Optional tags (2) (3) (4)
* 8.2.3.2. The stack of open elements
* 8.2.5.3. Closing elements that have implied end tags (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7)
* Elements (2) (3)
* Element Interfaces
#elementdef-figureReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 4.3.9. Headings and sections
* 4.4.1. The p element
* 4.4.5. The blockquote element (2)
* 4.4.8. The li element
* 4.4.12. The figure element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12)
* 4.4.13. The figcaption element (2)
* 4.7.5. The img element (2) (3)
* 4.7.5.1.4. Graphical Representations: Charts, diagrams, graphs, maps,
illustrations
* 4.7.5.1.14. Images of Pictures
* 4.7.5.1.15. Webcam images
* 4.7.5.1.16. When a text alternative is not available at the time of
publication (2)
* 4.7.5.1.22. Guidance for markup generators
* 4.7.5.1.23. Guidance for conformance checkers
* 4.9.1.1. Techniques for describing tables
* 4.9.2. The caption element
* 4.13.5. Footnotes
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* Elements (2) (3)
* Element content categories (2) (3)
* Element Interfaces
#elementdef-figcaptionReferenced in:
* 4.4.1. The p element
* 4.4.5. The blockquote element
* 4.4.8. The li element
* 4.4.12. The figure element (2) (3) (4)
* 4.4.13. The figcaption element (2)
* 4.7.5. The img element (2) (3) (4)
* 4.7.5.1.4. Graphical Representations: Charts, diagrams, graphs, maps,
illustrations
* 4.7.5.1.14. Images of Pictures (2)
* 4.7.5.1.15. Webcam images
* 4.7.5.1.16. When a text alternative is not available at the time of
publication (2) (3) (4) (5)
* 4.7.5.1.22. Guidance for markup generators
* 4.9.2. The caption element (2)
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* Elements (2)
* Element Interfaces
#elementdef-mainReferenced in:
* 3.2.1. Semantics
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 4.3.2. The article element
* 4.3.4. The nav element (2)
* 4.3.5. The aside element
* 4.3.7. The header element (2) (3)
* 4.3.8. The footer element (2) (3)
* 4.4.1. The p element
* 4.4.14. The main element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19)
* 4.8.6.6. Link type "license" (2)
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* Elements
* Element content categories (2)
* Element Interfaces
* Changes between Working Draft 7 and Working Draft 6
#elementdef-divReferenced in:
* 1.10.3. Restrictions on content models and on attribute values (2) (3)
(4)
* 2.2.1. Conformance classes
* 3.2.4. Content models (2)
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 3.2.5. Global attributes
* 4.3.3. The section element
* 4.4.1. The p element (2)
* 4.4.9. The dl element (2) (3) (4)
* 4.4.15. The div element (2) (3) (4) (5)
* 4.10.1.1. Writing a form’s user interface
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 8.2.5.4.7. The "in body" insertion mode (2)
* 8.2.8.4. Scripts that modify the page as it is being parsed (2) (3)
(4) (5)
* 8.3. Serializing HTML fragments (2)
* 10.3.3. Flow content (2) (3) (4)
* 11.2. Non-conforming features (2) (3) (4)
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element content categories (2)
* Element Interfaces
#htmldivelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#elementdef-aReferenced in:
* 1.9. A quick introduction to HTML (2) (3)
* 2.7.2.1. The HTMLAllCollection interface
* 3.1.3. DOM tree accessors (2)
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content
* 3.2.4.3. Transparent content models (2)
* 3.2.4.4. Paragraphs (2) (3)
* 3.2.5.3. The translate attribute
* 4.2.4. The link element (2)
* 4.4.1. The p element
* 4.5.1. The a element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.5.8. The dfn element (2)
* 4.5.31. Usage summary
* 4.7.5. The img element (2) (3)
* 4.7.5.1.3. A link or button containing nothing but an image
* 4.8.1. Introduction (2) (3)
* 4.8.2. Links created by a and area elements (2) (3) (4) (5) (6) (7)
(8)
* 4.8.3. API for a and area elements
* 4.8.4. Following hyperlinks (2)
* 4.8.5. Downloading resources (2)
* 4.8.6. Link types (2)
* 4.8.6.1. Link type "alternate" (2)
* 4.8.6.2. Link type "author" (2) (3)
* 4.8.6.3. Link type "bookmark"
* 4.8.6.4. Link type "help" (2) (3)
* 4.8.6.6. Link type "license"
* 4.8.6.7. Link type "nofollow"
* 4.8.6.8. Link type "noopener"
* 4.8.6.9. Link type "noreferrer" (2)
* 4.8.6.10. Link type "search"
* 4.8.6.12. Link type "tag"
* 4.8.6.13.1. Link type "next"
* 4.8.6.13.2. Link type "prev"
* 4.8.6.14. Other link types (2) (3) (4) (5) (6)
* 4.11.3.2. Using the a element to define a command (2)
* 4.11.3.3. Using the button element to define a command
* 4.13.3. Tag clouds
* 4.13.5. Footnotes
* 4.15.2. Pseudo-classes (2)
* 5.4.3. The tabindex attribute
* 5.7.4. The DragEvent interface
* 5.7.5. Drag-and-drop processing model (2)
* 5.7.7. The draggable attribute
* 6.3.3. Named access on the Window object (2)
* 6.6.4. The Location interface
* 6.7.1. Navigating across documents
* 6.7.9. Navigating to a fragment
* 7.3. Base64 utility methods
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5)
* 8.3. Serializing HTML fragments (2) (3) (4)
* 11.1. Obsolete but conforming features (2)
* 11.1.1. Warnings for obsolete but conforming features
* 11.2. Non-conforming features (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12)
* 11.3.4. Other elements, attributes and APIs
* Elements (2) (3) (4)
* Element content categories (2) (3) (4)
* Attributes (2) (3) (4) (5) (6) (7) (8)
* Element Interfaces
* Changes between Working Draft 8 and Working Draft 7
#htmlanchorelementReferenced in:
* 4.5.1. The a element
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#dom-htmlanchorelement-downloadReferenced in:
* 4.5.1. The a element
#dom-htmlanchorelement-targetReferenced in:
* 4.5.1. The a element
#dom-htmlanchorelement-relReferenced in:
* 4.5.1. The a element
#dom-htmlanchorelement-hreflangReferenced in:
* 4.5.1. The a element
#dom-htmlanchorelement-typeReferenced in:
* 4.5.1. The a element
#dom-htmlanchorelement-rellistReferenced in:
* 4.5.1. The a element
#dom-htmlanchorelement-textReferenced in:
* 4.5.1. The a element
#elementdef-emReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.2. The em element (2) (3) (4)
* 4.5.4. The small element
* 4.5.22. The i element
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.25. The mark element
* 4.5.31. Usage summary
* 8.2.3.2. The stack of open elements
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-strongReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.2. The em element
* 4.5.3. The strong element (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.5.4. The small element
* 4.5.23. The b element (2)
* 4.5.31. Usage summary
* 8.2.3.2. The stack of open elements
* 11.2. Non-conforming features
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-smallReferenced in:
* 1.10.1. Presentational markup
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.4. The small element (2) (3) (4) (5) (6) (7)
* 4.5.31. Usage summary
* 8.2.3.2. The stack of open elements
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-sReferenced in:
* 1.10.1. Presentational markup
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.5. The s element (2)
* 4.5.31. Usage summary
* 8.2.3.2. The stack of open elements
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-citeReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.4.5. The blockquote element (2) (3) (4)
* 4.5.6. The cite element (2) (3) (4) (5) (6) (7) (8) (9)
* 4.5.24. The u element
* 4.5.31. Usage summary
* 10.7.1. Links, forms, and navigation
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-qReferenced in:
* 2.5.3. Dynamic changes to base URLs
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 3.2.5.2. The lang and xml:lang attributes
* 4.4.5. The blockquote element
* 4.5.6. The cite element
* 4.5.7. The q element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.5.31. Usage summary
* 10.7.1. Links, forms, and navigation
* Elements
* Element content categories (2) (3)
* Attributes
* Element Interfaces
#element-attrdef-q-citeReferenced in:
* 4.5.7. The q element
* Elements
#elementdef-dfnReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 3.2.5.1. The title attribute
* 4.4.10. The dt element (2)
* 4.5.8. The dfn element (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.5.22. The i element
* 4.5.31. Usage summary
* Elements
* Element content categories (2) (3)
* Attributes
* Element Interfaces
#defines-the-termReferenced in:
* 4.5.8. The dfn element
* 4.5.9. The abbr element
#element-attrdef-dfn-titleReferenced in:
* 4.5.8. The dfn element (2)
#elementdef-abbrReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 3.2.5.1. The title attribute (2)
* 4.5.8. The dfn element
* 4.5.9. The abbr element (2) (3) (4) (5) (6) (7) (8)
* 4.5.31. Usage summary
* 11.2. Non-conforming features
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element content categories (2) (3)
* Attributes (2)
* Element Interfaces
#element-attrdef-abbr-titleReferenced in:
* 4.5.8. The dfn element
* 4.5.9. The abbr element (2) (3) (4) (5) (6)
* Attributes
#elementdef-rubyReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 3.2.4.3. Transparent content models (2)
* 4.5.10. The ruby element (2) (3) (4) (5) (6) (7) (8)
* 4.5.11. The rb element (2) (3)
* 4.5.12. The rt element (2) (3) (4)
* 4.5.13. The rtc element (2) (3) (4) (5)
* 4.5.14. The rp element (2)
* 4.5.24. The u element
* 4.5.31. Usage summary
* 8.2.5.4.7. The "in body" insertion mode (2)
* 11.2. Non-conforming features (2)
* Elements (2) (3) (4) (5)
* Element content categories (2) (3)
* Element Interfaces
#ruby-segmentReferenced in:
* 4.5.10. The ruby element (2) (3) (4) (5)
#ruby-basesReferenced in:
* 4.5.10. The ruby element (2) (3) (4) (5)
#ruby-base-containerReferenced in:
* 4.5.10. The ruby element (2) (3)
#ruby-text-containerReferenced in:
* 4.5.10. The ruby element (2) (3) (4) (5) (6)
* 4.5.13. The rtc element
#ruby-text-annotationsReferenced in:
* 4.5.10. The ruby element (2) (3) (4) (5) (6)
#ruby-annotation-containerReferenced in:
* 4.5.10. The ruby element (2) (3) (4) (5) (6) (7) (8)
#commit-a-ruby-segmentReferenced in:
* 4.5.10. The ruby element (2)
#commit-the-base-rangeReferenced in:
* 4.5.10. The ruby element (2) (3)
#commit-current-annotationsReferenced in:
* 4.5.10. The ruby element (2)
#commit-an-automatic-baseReferenced in:
* 4.5.10. The ruby element (2) (3) (4)
#elementdef-rbReferenced in:
* 3.2.2. Elements in the DOM
* 4.5.10. The ruby element (2) (3) (4) (5) (6) (7)
* 4.5.11. The rb element (2) (3) (4) (5)
* 4.5.12. The rt element
* 4.5.14. The rp element
* 4.5.31. Usage summary
* 8.2.5.3. Closing elements that have implied end tags (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3)
* 11.2. Non-conforming features
* Elements (2)
* Element Interfaces
#elementdef-rtReferenced in:
* 3.2.4.3. Transparent content models (2)
* 4.5.10. The ruby element (2) (3) (4) (5) (6) (7) (8)
* 4.5.11. The rb element
* 4.5.12. The rt element (2) (3) (4) (5)
* 4.5.13. The rtc element (2)
* 4.5.14. The rp element (2)
* 4.5.31. Usage summary
* 8.1.2.4. Optional tags (2) (3) (4)
* 8.2.5.3. Closing elements that have implied end tags (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3)
* 10.3.4. Phrasing content
* Elements (2)
* Element Interfaces
#elementdef-rtcReferenced in:
* 3.2.2. Elements in the DOM
* 4.5.10. The ruby element (2) (3) (4) (5) (6) (7)
* 4.5.12. The rt element (2) (3)
* 4.5.13. The rtc element (2) (3) (4) (5) (6) (7) (8)
* 4.5.14. The rp element (2)
* 8.2.5.3. Closing elements that have implied end tags (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5)
* 11.2. Non-conforming features
* Elements (2) (3) (4)
* Element Interfaces
#process-an-rtc-elementReferenced in:
* 4.5.10. The ruby element
#commit-an-automatic-annotationReferenced in:
* 4.5.13. The rtc element (2)
#elementdef-rpReferenced in:
* 4.5.10. The ruby element (2) (3) (4) (5)
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element (2) (3) (4) (5) (6) (7) (8)
* 4.5.31. Usage summary
* 8.1.2.4. Optional tags (2) (3) (4)
* 8.2.5.3. Closing elements that have implied end tags (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3)
* 10.3.4. Phrasing content
* Elements (2)
* Element Interfaces
#elementdef-dataReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.15. The data element
* 4.5.31. Usage summary
* 4.13.4. Conversations (2)
* Elements
* Element content categories (2) (3)
* Attributes
* Element Interfaces
#htmldataelementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-data-valueReferenced in:
* Elements
#dom-htmldataelement-valueReferenced in:
* 4.5.15. The data element
#elementdef-timeReferenced in:
* 2.4.5. Dates and times
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.16. The time element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12)
* 4.5.31. Usage summary
* 4.13.4. Conversations (2)
* Elements
* Element content categories (2) (3)
* Attributes
* Element Interfaces
#htmltimeelementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-time-datetimeReferenced in:
* 4.5.16. The time element
* Elements
#datetime-valueReferenced in:
* 4.5.16. The time element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12)
#dom-htmltimeelement-datetimeReferenced in:
* 4.5.16. The time element
#elementdef-codeReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.4.4. The pre element
* 4.5.17. The code element (2) (3)
* 4.5.31. Usage summary
* 8.2.3.2. The stack of open elements
* 11.2. Non-conforming features (2) (3)
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-varReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.18. The var element (2) (3) (4)
* 4.5.21. The sub and sup elements
* 4.5.31. Usage summary
* 11.2. Non-conforming features
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-sampReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.4.4. The pre element
* 4.5.19. The samp element (2)
* 4.5.20. The kbd element (2) (3)
* 4.5.31. Usage summary
* 4.10.12. The output element
* 11.2. Non-conforming features
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-kbdReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.4.4. The pre element (2)
* 4.5.19. The samp element (2)
* 4.5.20. The kbd element (2) (3) (4) (5) (6) (7) (8)
* 4.5.31. Usage summary
* 11.2. Non-conforming features
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-subReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.21. The sub and sup elements (2) (3) (4) (5)
* 4.5.31. Usage summary
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-supReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.21. The sub and sup elements (2) (3)
* 4.5.31. Usage summary
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-iReferenced in:
* 1.10.1. Presentational markup
* 1.10.2. Syntax errors (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 2.2.1. Conformance classes
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.2. The em element
* 4.5.22. The i element (2) (3) (4) (5) (6)
* 4.5.23. The b element
* 4.5.24. The u element
* 4.5.31. Usage summary
* 8.2.3.2. The stack of open elements
* 8.2.8.1. Misnested tags: <b><i></b></i> (2) (3) (4) (5) (6) (7) (8)
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-bReferenced in:
* 1.10.1. Presentational markup
* 2.2.1. Conformance classes
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.23. The b element (2) (3) (4) (5) (6) (7) (8) (9)
* 4.5.24. The u element
* 4.5.26. The bdi element
* 4.5.31. Usage summary
* 4.13.4. Conversations
* 8.2.3.2. The stack of open elements
* 8.2.8.1. Misnested tags: <b><i></b></i> (2) (3) (4) (5)
* 8.2.8.2. Misnested tags: <b><p></b></p> (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15)
* 8.2.8.3. Unexpected markup in tables (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21)
* 8.2.8.6. Unclosed formatting elements (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23)
(24) (25)
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-uReferenced in:
* 1.10.1. Presentational markup
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.24. The u element (2) (3)
* 4.5.25. The mark element
* 4.5.31. Usage summary
* 8.2.3.2. The stack of open elements
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-markReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.24. The u element
* 4.5.25. The mark element (2) (3) (4) (5)
* 4.5.31. Usage summary
* 11.2. Non-conforming features
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-bdiReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 3.2.5.5. The dir attribute (2)
* 3.2.7.1. Authoring conformance criteria for bidirectional-algorithm
formatting characters
* 3.2.7.2. User agent conformance criteria
* 4.5.26. The bdi element (2) (3) (4)
* 4.5.31. Usage summary
* Elements
* Element content categories (2) (3)
* Element Interfaces
#elementdef-bdoReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 3.2.7.1. Authoring conformance criteria for bidirectional-algorithm
formatting characters
* 3.2.7.2. User agent conformance criteria
* 4.5.27. The bdo element
* 4.5.31. Usage summary
* Elements
* Element content categories (2) (3)
* Attributes
* Element Interfaces
#elementdef-spanReferenced in:
* 1.10.3. Restrictions on content models and on attribute values (2) (3)
(4)
* 2.2.1. Conformance classes
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 3.2.5. Global attributes
* 3.2.5.6. The style attribute
* 4.5.19. The samp element
* 4.5.28. The span element (2)
* 4.5.31. Usage summary
* 4.13.1. Subheadings, subtitles, alternative titles and taglines
* 4.13.4. Conversations
* Elements
* Element content categories (2) (3)
* Element Interfaces
#htmlspanelementReferenced in:
* Elements
* Element Interfaces
#elementdef-brReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.6. The innerText IDL attribute (2) (3) (4)
* 3.2.7.2. User agent conformance criteria
* 4.5.29. The br element (2) (3) (4) (5) (6) (7)
* 4.5.31. Usage summary
* 4.13.1. Subheadings, subtitles, alternative titles and taglines
* 8.1.2. Elements
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 10.3.4. Phrasing content
* 11.2. Non-conforming features
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element content categories (2)
* Element Interfaces
#htmlbrelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#elementdef-wbrReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.7.2. User agent conformance criteria
* 4.5.30. The wbr element (2) (3) (4)
* 4.5.31. Usage summary
* 8.1.2. Elements
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* Elements
* Element content categories (2)
* Element Interfaces
#elementdef-insReferenced in:
* 2.5.3. Dynamic changes to base URLs
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 3.2.4.3. Transparent content models (2) (3) (4)
* 3.2.4.4. Paragraphs (2) (3) (4) (5) (6)
* 4.4.1. The p element
* 4.6. Edits
* 4.6.1. The ins element (2) (3)
* 4.6.3. Attributes common to ins and del elements
* 4.6.5. Edits and lists
* 8.1.2.4. Optional tags
* 10.7.1. Links, forms, and navigation
* Elements
* Element content categories (2) (3)
* Attributes (2)
* Element Interfaces
#elementdef-delReferenced in:
* 2.5.3. Dynamic changes to base URLs
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.4. Paragraphs (2) (3) (4) (5) (6)
* 4.4.1. The p element
* 4.5.5. The s element
* 4.6. Edits
* 4.6.2. The del element (2)
* 4.6.3. Attributes common to ins and del elements (2)
* 4.6.4. Edits and paragraphs (2) (3) (4) (5) (6)
* 4.6.5. Edits and lists (2)
* 4.6.6. Edits and tables
* 8.1.2.4. Optional tags
* 10.7.1. Links, forms, and navigation
* Elements
* Element content categories (2)
* Attributes (2)
* Element Interfaces
#element-attrdef-edits-citeReferenced in:
* 4.6.3. Attributes common to ins and del elements (2)
* Elements (2)
#element-attrdef-edits-datetimeReferenced in:
* 4.6.3. Attributes common to ins and del elements
* Elements (2)
#htmlmodelementReferenced in:
* 4.6.1. The ins element
* 4.6.2. The del element
* 4.6.3. Attributes common to ins and del elements
* Elements (2)
* Element Interfaces (2)
#dom-htmlmodelement-citeReferenced in:
* 4.6.3. Attributes common to ins and del elements
#dom-htmlmodelement-datetimeReferenced in:
* 4.6.3. Attributes common to ins and del elements
#device-pixel-ratioReferenced in:
* 4.7.1. Introduction (2) (3)
#viewport-based-selectionReferenced in:
* 4.7.1. Introduction (2)
#image-art-directedReferenced in:
* 4.7.1. Introduction (2) (3) (4)
* 4.7.5. The img element
* 4.7.5.1.21. An image in a picture element
#image-format-based-selectionReferenced in:
* 4.7.1. Introduction
#elementdef-pictureReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.6. Embedded content
* 4.7.1. Introduction
* 4.7.3. The picture element (2) (3) (4)
* 4.7.4. The source element (2) (3)
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8)
* 4.7.5.1.21. An image in a picture element (2) (3)
* Elements (2) (3)
* Element Interfaces
* People who have contributed to previous revisions of HTML 5.x
#htmlpictureelementReferenced in:
* Elements
* Element Interfaces
#elementdef-sourceReferenced in:
* 4.7.1. Introduction (2) (3) (4) (5) (6)
* 4.7.3. The picture element (2) (3)
* 4.7.4. The source element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.7.5.1.21. An image in a picture element
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.13.2. Location of the media resource (2)
* 4.7.13.3. MIME types
* 4.7.13.5. Loading the media resource (2) (3) (4)
* 4.7.13.16. Event summary
* 4.7.13.18. Best practices for authors using media elements
* 8.1.2. Elements
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* Elements (2) (3) (4)
* Attributes (2) (3) (4)
* Element Interfaces
#htmlsourceelementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-source-typeReferenced in:
* 4.7.1. Introduction
* 4.7.4. The source element (2) (3) (4) (5)
* Elements
#element-attrdef-source-srcsetReferenced in:
* 4.7.4. The source element (2)
* Elements
#element-attrdef-source-sizesReferenced in:
* 4.7.4. The source element
* Elements
* People who have contributed to previous revisions of HTML 5.x
#element-attrdef-source-mediaReferenced in:
* 4.7.4. The source element (2)
* Elements
#element-attrdef-source-srcReferenced in:
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.13.5. Loading the media resource (2)
* Elements
#dom-htmlsourceelement-srcReferenced in:
* 4.7.4. The source element
#dom-htmlsourceelement-typeReferenced in:
* 4.7.4. The source element
#dom-htmlsourceelement-srcsetReferenced in:
* 4.7.4. The source element
#dom-htmlsourceelement-sizesReferenced in:
* 4.7.4. The source element
#dom-htmlsourceelement-mediaReferenced in:
* 4.7.4. The source element
#elementdef-imgReferenced in:
* 1.9.1. Writing secure applications with HTML
* 1.9.2. Common pitfalls to avoid when using the scripting APIs (2) (3)
* 2.7.2.1. The HTMLAllCollection interface
* 3.1.3. DOM tree accessors (2) (3) (4) (5) (6)
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.6. Embedded content
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content (2)
* 4.5.1. The a element (2)
* 4.7.1. Introduction (2) (3) (4) (5)
* 4.7.3. The picture element (2) (3)
* 4.7.4. The source element (2) (3)
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26)
(27) (28) (29) (30) (31) (32) (33) (34) (35) (36) (37) (38) (39) (40)
(41) (42) (43) (44) (45) (46) (47) (48) (49) (50) (51) (52) (53) (54)
(55) (56) (57) (58) (59) (60) (61) (62) (63) (64) (65) (66) (67) (68)
(69) (70) (71) (72)
* 4.7.5.1.7. Images that enhance the themes or subject matter of the
page content
* 4.7.5.1.12. Image maps
* 4.7.5.1.14. Images of Pictures (2) (3)
* 4.7.5.1.16. When a text alternative is not available at the time of
publication (2) (3)
* 4.7.5.1.17. An image not intended for the user (2) (3) (4)
* 4.7.5.1.18. Icon Images
* 4.7.5.1.21. An image in a picture element (2)
* 4.7.5.1.22. Guidance for markup generators
* 4.7.5.1.23. Guidance for conformance checkers (2)
* 4.7.13.17. Security and privacy considerations
* 4.7.14. The map element
* 4.7.16.1. Authoring (2)
* 4.7.16.2. Processing model (2) (3) (4) (5) (6)
* 4.7.19. Dimension attributes (2)
* 4.10.2. Categories (2)
* 4.10.3. The form element (2) (3)
* 4.10.5.1.19. Image Button state (type=image)
* 4.12.4.1. Color spaces and color correction
* 5.4.2. Data model (2) (3) (4) (5)
* 5.4.4. Processing model
* 5.7.3. The DataTransfer interface
* 5.7.5. Drag-and-drop processing model (2)
* 5.7.7. The draggable attribute
* 6.3.3. Named access on the Window object (2)
* 6.4. Origin (2)
* 7.8. Images (2) (3) (4) (5) (6)
* 8.1.2. Elements
* 8.2.3.2. The stack of open elements (2)
* 8.3. Serializing HTML fragments
* 10.4.2. Images (2) (3) (4) (5)
* 10.4.3. Attributes for embedded content and images (2) (3) (4) (5)
* 10.4.4. Image maps (2)
* 11.1. Obsolete but conforming features
* 11.1.1. Warnings for obsolete but conforming features
* 11.2. Non-conforming features (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 11.3.4. Other elements, attributes and APIs (2)
* 12.1. text/html
* Elements (2)
* Element content categories (2) (3) (4) (5) (6)
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* Element Interfaces
* Events (2) (3) (4) (5) (6) (7)
* Changes between Working Draft 8 and Working Draft 7
* Changes between Working Draft 6 and Working Draft 5
#htmlimageelementReferenced in:
* 7.8. Images
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#element-attrdef-img-srcReferenced in:
* 4.7.1. Introduction (2)
* 5.7.5. Drag-and-drop processing model
* 11.2. Non-conforming features
* Elements
#element-attrdef-img-srcsetReferenced in:
* 4.7.1. Introduction (2) (3) (4) (5)
* 4.7.5. The img element
* Elements
* People who have contributed to previous revisions of HTML 5.x
#element-attrdef-img-altReferenced in:
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 4.7.1. Introduction
* 4.7.5.1. Requirements for providing text to act as an alternative for
images
* 4.7.5.1.4. Graphical Representations: Charts, diagrams, graphs, maps,
illustrations
* 10.4.2. Images
* Elements
#image-candidate-stringReferenced in:
* 4.7.4. The source element (2) (3) (4)
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14)
* Attributes
#width-descriptorReferenced in:
* 4.7.4. The source element
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10)
#width-descriptor-valueReferenced in:
* 4.7.5. The img element (2)
#valid-source-size-listReferenced in:
* 4.7.4. The source element
* 4.7.5. The img element (2)
* Attributes
#element-attrdef-img-crossoriginReferenced in:
* 4.7.5. The img element
* Elements
#element-attrdef-img-referrerpolicyReferenced in:
* 4.7.5. The img element
* Elements
#current-requestReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26)
(27) (28) (29) (30) (31) (32) (33) (34) (35)
#pending-requestReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26)
(27) (28) (29)
#image-requestReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
#image-stateReferenced in:
* 4.7.5. The img element
* 6.6.2. The History interface (2)
#current-urlReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9)
#image-dataReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6)
#statedef-img-unavailableReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6) (7)
#statedef-img-partially-availableReferenced in:
* 4.7.5. The img element (2) (3) (4) (5)
#statedef-img-completely-availableReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6) (7)
* 7.8. Images
#statedef-img-brokenReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8)
#statedef-img-availableReferenced in:
* 4.7.5. The img element
#relevant-mutationsReferenced in:
* 4.7.5. The img element (2) (3)
#last-selected-sourceReferenced in:
* 4.7.5. The img element (2) (3)
#current-pixel-densityReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8)
#density-corrected-intrinsic-width-and-heightReferenced in:
* 4.7.5. The img element (2) (3) (4) (5)
#list-of-available-imagesReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8)
#ignore-higher-layer-cachingReferenced in:
* 4.7.5. The img element (2) (3) (4) (5)
#update-the-image-dataReferenced in:
* 4.7.5. The img element (2) (3) (4)
#abort-the-image-requestReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
#upgrade-the-pending-request-to-the-current-requestReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6)
#fire-a-progress-event-or-simple-eventReferenced in:
* 4.7.5. The img element (2) (3) (4) (5)
#use-srcset-or-pictureReferenced in:
* 4.7.5. The img element
#fully-decodableReferenced in:
* 7.8. Images
#source-setReferenced in:
* 4.7.4. The source element (2)
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13)
#image-sourceReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14)
#source-sizeReferenced in:
* 4.7.5. The img element (2) (3) (4) (5) (6) (7)
#selecting-an-image-sourceReferenced in:
* 4.7.5. The img element (2)
#update-the-source-setReferenced in:
* 4.7.5. The img element
#parse-a-srcset-attributeReferenced in:
* 4.7.5. The img element (2)
#parse-a-sizes-attributeReferenced in:
* 4.7.5. The img element (2)
#normalize-the-source-densitiesReferenced in:
* 4.7.5. The img element (2)
#element-attrdef-img-usemapReferenced in:
* 3.2.4.2.7. Interactive content
#element-attrdef-img-ismapReferenced in:
* Elements
#dom-htmlimageelement-altReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-srcReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-srcsetReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-sizesReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-crossoriginReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-usemapReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-ismapReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-referrerpolicyReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-longdescReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-widthReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-heightReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-naturalwidthReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-naturalheightReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-completeReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-currentsrcReferenced in:
* 4.7.5. The img element
#dom-htmlimageelement-imageReferenced in:
* 4.7.5. The img element
#the-conditions-described-aboveReferenced in:
* 4.7.5.1.23. Guidance for conformance checkers
#elementdef-iframeReferenced in:
* 1.9.1. Writing secure applications with HTML (2)
* 2.1.5. Plugins
* 2.7.2.1. The HTMLAllCollection interface (2)
* 3.1.2. Resource metadata management
* 3.1.3. DOM tree accessors (2) (3) (4)
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.6. Embedded content
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content
* 3.2.5.3. The translate attribute
* 4.2.5.5. Specifying the document’s character encoding
* 4.7.6. The iframe element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27) (28) (29) (30) (31) (32) (33)
* 4.7.19. Dimension attributes (2) (3)
* 5.4.2. Data model (2) (3)
* 5.4.6. Focus management APIs
* 6.1. Browsing contexts
* 6.1.1. Nested browsing contexts
* 6.4.1. Relaxing the same-origin restriction
* 6.5. Sandboxing
* 6.6.2. The History interface
* 6.6.3. Implementation notes for session history (2)
* 6.7.1. Navigating across documents (2)
* 7.1.3.5. Realms, settings objects, and global objects
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods
* 8.2.2.2. Determining the character encoding
* 8.2.3.2. The stack of open elements
* 8.2.8.4. Scripts that modify the page as it is being parsed
* 8.3. Serializing HTML fragments
* 8.4. Parsing HTML fragments
* 10.3.2. The page (2) (3) (4)
* 10.4.1. Embedded content
* 10.4.3. Attributes for embedded content and images (2) (3) (4)
* 11.2. Non-conforming features (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13)
* 11.3.3. Frames
* 11.3.4. Other elements, attributes and APIs (2) (3) (4) (5)
* Elements
* Element content categories (2) (3) (4) (5)
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
* Element Interfaces
#htmliframeelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#element-attrdef-iframe-srcReferenced in:
* Elements
#element-attrdef-iframe-srcdocReferenced in:
* 3.2.5.3. The translate attribute
* Elements
#an-iframe-srcdoc-documentReferenced in:
* 2.5.1. Terminology (2)
* 2.6.2. Processing model
* 4.2.1. The head element
* 4.2.5.5. Specifying the document’s character encoding (2)
* 4.7.6. The iframe element (2) (3)
* 6.4. Origin
* 6.6.4. The Location interface
* 6.7.1. Navigating across documents
* 8.2.5.4.1. The "initial" insertion mode (2) (3)
* Attributes
#reprocess-the-iframe-attributesReferenced in:
* 4.7.6. The iframe element (2) (3) (4)
* 6.6.4. The Location interface
#otherwise-steps-for-iframe-or-frame-elementsReferenced in:
* 4.7.6. The iframe element
* 11.3.3. Frames
#iframe-load-in-progressReferenced in:
* 4.7.6. The iframe element (2)
* 7.4.1. Opening the input stream
#mute-iframe-loadReferenced in:
* 4.7.6. The iframe element
* 7.4.1. Opening the input stream
#iframe-load-event-stepsReferenced in:
* 4.7.6. The iframe element (2)
#element-attrdef-iframe-nameReferenced in:
* 2.7.2.1. The HTMLAllCollection interface
* 4.7.6. The iframe element
* Elements
#element-attrdef-iframe-sandboxReferenced in:
* 2.1.5. Plugins
* 3.1.2. Resource metadata management
* 4.7.6. The iframe element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13)
* 6.1.5. Browsing context names
* 6.5. Sandboxing
* Elements
* Attributes
#element-attrdef-iframe-allowfullscreenReferenced in:
* Elements
* Attributes
#element-attrdef-iframe-allowpaymentrequestReferenced in:
* 4.7.6. The iframe element
* Attributes
#allowed-to-useReferenced in:
* 4.7.6. The iframe element (2) (3)
#element-attrdef-iframe-referrerpolicyReferenced in:
* Elements
#dom-htmliframeelement-srcReferenced in:
* 4.7.6. The iframe element
#dom-htmliframeelement-srcdocReferenced in:
* 4.7.6. The iframe element
#dom-htmliframeelement-nameReferenced in:
* 4.7.6. The iframe element
#dom-htmliframeelement-sandboxReferenced in:
* 4.7.6. The iframe element
#dom-htmliframeelement-allowfullscreenReferenced in:
* 4.7.6. The iframe element
#dom-htmliframeelement-allowpaymentrequestReferenced in:
* 4.7.6. The iframe element
#dom-htmliframeelement-referrerpolicyReferenced in:
* 4.7.6. The iframe element
#dom-htmliframeelement-contentdocumentReferenced in:
* 4.7.6. The iframe element
#dom-htmliframeelement-contentwindowReferenced in:
* 4.7.6. The iframe element
#elementdef-embedReferenced in:
* 2.7.2.1. The HTMLAllCollection interface
* 3.1.3. DOM tree accessors (2) (3) (4) (5) (6)
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.6. Embedded content
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content
* 4.7.7. The embed element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23)
* 4.7.19. Dimension attributes (2) (3)
* 6.3.3. Named access on the Window object (2)
* 6.5. Sandboxing
* 6.7.7. Page load processing model for content that uses plugins (2)
(3)
* 8.1.2. Elements
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 10.4.1. Embedded content
* 10.4.3. Attributes for embedded content and images (2) (3) (4)
* 11.2. Non-conforming features (2) (3) (4) (5) (6)
* 11.3.1. The applet element
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element content categories (2) (3) (4) (5)
* Attributes (2) (3) (4)
* Element Interfaces
* Events
#htmlembedelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#element-attrdef-embed-srcReferenced in:
* Elements
#element-attrdef-embed-typeReferenced in:
* Elements
#potentially-activeReferenced in:
* 4.7.7. The embed element (2) (3) (4) (5) (6)
#the-embed-element-setup-stepsReferenced in:
* 4.7.7. The embed element (2) (3)
#dom-htmlembedelement-srcReferenced in:
* 4.7.7. The embed element
#dom-htmlembedelement-typeReferenced in:
* 4.7.7. The embed element
#elementdef-objectReferenced in:
* 2.7.2.1. The HTMLAllCollection interface (2)
* 3.1.3. DOM tree accessors (2) (3) (4) (5) (6) (7) (8)
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.6. Embedded content
* 3.2.4.2.8. Palpable content
* 3.2.4.3. Transparent content models (2)
* 3.2.4.4. Paragraphs (2)
* 4.7.7. The embed element (2) (3)
* 4.7.8. The object element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27) (28) (29) (30) (31) (32) (33) (34) (35) (36) (37) (38)
* 4.7.9. The param element (2) (3)
* 4.7.14. The map element
* 4.7.16.2. Processing model (2)
* 4.7.19. Dimension attributes (2) (3)
* 4.10.2. Categories (2) (3) (4) (5)
* 4.10.20.1. Definitions
* 4.10.21.4. Constructing the form data set (2)
* 5.7.7. The draggable attribute
* 6.3.3. Named access on the Window object (2)
* 6.5. Sandboxing
* 6.7.1. Navigating across documents
* 8.2.3.2. The stack of open elements (2)
* 8.2.3.3. The list of active formatting elements (2)
* 9.2. Parsing XML documents
* 10.4.1. Embedded content (2)
* 10.4.3. Attributes for embedded content and images (2) (3) (4) (5)
* 10.4.4. Image maps (2)
* 11.2. Non-conforming features (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16) (17)
* 11.3.1. The applet element
* 11.3.4. Other elements, attributes and APIs (2) (3)
* Elements (2) (3)
* Element content categories (2) (3) (4) (5) (6) (7) (8)
* Attributes (2) (3) (4) (5) (6) (7)
* Element Interfaces
#htmlobjectelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#dom-htmlobjectelement-willvalidateReferenced in:
* 4.7.8. The object element
#dom-htmlobjectelement-validityReferenced in:
* 4.7.8. The object element
#dom-htmlobjectelement-validationmessageReferenced in:
* 4.7.8. The object element
#dom-htmlobjectelement-checkvalidityReferenced in:
* 4.7.8. The object element
#dom-htmlobjectelement-reportvalidityReferenced in:
* 4.7.8. The object element
#dom-htmlobjectelement-setcustomvalidityReferenced in:
* 4.7.8. The object element
#element-attrdef-object-dataReferenced in:
* 11.2. Non-conforming features
* Elements
#element-attrdef-object-typeReferenced in:
* 11.2. Non-conforming features
* Elements
* Attributes
#element-attrdef-object-typemustmatchReferenced in:
* 4.7.8. The object element
* Elements
#element-attrdef-object-nameReferenced in:
* 2.7.2.1. The HTMLAllCollection interface
* 4.7.8. The object element
* Elements
#should-be-usedReferenced in:
* 4.7.8. The object element (2)
#dom-htmlobjectelement-dataReferenced in:
* 4.7.8. The object element
#dom-htmlobjectelement-typeReferenced in:
* 4.7.8. The object element
#dom-htmlobjectelement-nameReferenced in:
* 4.7.8. The object element
#dom-htmlobjectelement-typemustmatchReferenced in:
* 4.7.8. The object element
#dom-htmlobjectelement-contentdocumentReferenced in:
* 4.7.8. The object element
#dom-htmlobjectelement-contentwindowReferenced in:
* 4.7.8. The object element
#elementdef-paramReferenced in:
* 4.7.8. The object element (2) (3)
* 4.7.9. The param element (2) (3)
* 8.1.2. Elements
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 9.2. Parsing XML documents
* 11.2. Non-conforming features (2) (3) (4)
* 11.3.1. The applet element
* 11.3.4. Other elements, attributes and APIs (2)
* Elements (2)
* Attributes (2)
* Element Interfaces
#htmlparamelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#element-attrdef-param-nameReferenced in:
* Elements
#element-attrdef-param-valueReferenced in:
* Elements
#parameterReferenced in:
* 4.7.8. The object element
* 4.7.9. The param element (2)
* 11.3.1. The applet element
#dom-htmlparamelement-nameReferenced in:
* 4.7.9. The param element
#dom-htmlparamelement-valueReferenced in:
* 4.7.9. The param element
#elementdef-videoReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.6. Embedded content
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content (2)
* 3.2.4.4. Paragraphs
* 3.2.6. The innerText IDL attribute
* 4.4.1. The p element
* 4.7.8. The object element (2)
* 4.7.10. The video element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21)
* 4.7.11. The audio element
* 4.7.13. Media elements (2)
* 4.7.13.3. MIME types (2)
* 4.7.13.5. Loading the media resource (2)
* 4.7.13.6. Offsets into the media resource
* 4.7.13.7. Ready states (2) (3)
* 4.7.13.16. Event summary
* 4.7.13.17. Security and privacy considerations
* 4.7.19. Dimension attributes (2) (3)
* 5.4.2. Data model
* 5.4.3. The tabindex attribute
* 6.4. Origin
* 7.8. Images (2) (3) (4) (5)
* 8.1.2.4. Optional tags
* 10.4.1. Embedded content (2) (3) (4) (5) (6) (7) (8) (9)
* 10.4.3. Attributes for embedded content and images
* Elements (2) (3) (4)
* Element content categories (2) (3) (4) (5)
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10)
* Element Interfaces
#htmlvideoelementReferenced in:
* 7.8. Images
* Elements
* Element Interfaces
#element-attrdef-video-posterReferenced in:
* 4.7.10. The video element
* Elements
#poster-frameReferenced in:
* 4.7.10. The video element (2) (3) (4) (5) (6) (7) (8) (9)
#video-intrinsic-widthReferenced in:
* 4.7.10. The video element (2) (3) (4)
#video-intrinsic-heightReferenced in:
* 4.7.10. The video element (2) (3) (4)
#dom-htmlvideoelement-videowidthReferenced in:
* 4.7.10. The video element
#dom-htmlvideoelement-videoheightReferenced in:
* 4.7.10. The video element
#dom-htmlvideoelement-posterReferenced in:
* 4.7.10. The video element
#elementdef-audioReferenced in:
* 3.2.1. Semantics
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.6. Embedded content
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content (2)
* 3.2.4.4. Paragraphs
* 4.4.1. The p element
* 4.7.3. The picture element
* 4.7.4. The source element
* 4.7.11. The audio element (2) (3) (4) (5) (6) (7) (8) (9)
* 4.7.13. Media elements (2)
* 4.7.13.11.5. Text track API
* 5.4.3. The tabindex attribute
* 6.4. Origin
* 8.1.2.4. Optional tags
* 10.4.1. Embedded content (2)
* 11.2. Non-conforming features
* Elements (2) (3) (4)
* Element content categories (2) (3) (4) (5)
* Attributes (2) (3) (4) (5) (6) (7)
* Element Interfaces
#htmlaudioelementReferenced in:
* Elements
* Element Interfaces
#dom-htmlaudioelement-audioReferenced in:
* 4.7.11. The audio element
#elementdef-trackReferenced in:
* 4.7.4. The source element
* 4.7.10. The video element (2) (3) (4)
* 4.7.11. The audio element (2) (3)
* 4.7.12. The track element (2) (3) (4) (5) (6) (7) (8)
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.11.1. Text track model (2) (3) (4) (5)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21)
(22)
* 4.7.13.11.5. Text track API (2) (3) (4)
* 4.7.13.16. Event summary
* 8.1.2. Elements
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* Elements
* Attributes (2) (3) (4) (5)
* Element Interfaces
#htmltrackelementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-track-kindReferenced in:
* Elements
#attr-valuedef-track-kind-subtitlesReferenced in:
* 4.7.12. The track element
* Attributes
#statedef-track-subtitlesReferenced in:
* 4.7.12. The track element
* 4.7.13.11.3. Sourcing out-of-band text tracks
#attr-valuedef-track-kind-captionsReferenced in:
* Attributes
#statedef-track-captionsReferenced in:
* 4.7.12. The track element
* 4.7.13.11.3. Sourcing out-of-band text tracks
#attr-valuedef-track-kind-descriptionsReferenced in:
* Attributes
#statedef-track-descriptionsReferenced in:
* 4.7.12. The track element (2)
* 4.7.13.8. Playing the media resource
* 4.7.13.11.3. Sourcing out-of-band text tracks
#attr-valuedef-track-kind-chaptersReferenced in:
* Attributes
#statedef-track-chaptersReferenced in:
* 4.7.12. The track element
* 4.7.13.11.3. Sourcing out-of-band text tracks
#attr-valuedef-track-kind-metadataReferenced in:
* 4.7.12. The track element
* Attributes
#statedef-track-metadataReferenced in:
* 4.7.12. The track element (2)
* 4.7.13.11.3. Sourcing out-of-band text tracks
#element-attrdef-track-srcReferenced in:
* 4.7.12. The track element
* Elements
#track-urlReferenced in:
* 4.7.12. The track element (2) (3)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5)
#element-attrdef-track-srclangReferenced in:
* Elements
#track-languageReferenced in:
* 4.7.12. The track element
* 4.7.13.11.3. Sourcing out-of-band text tracks
#element-attrdef-track-labelReferenced in:
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* Elements
#track-labelReferenced in:
* 4.7.12. The track element
* 4.7.13.11.3. Sourcing out-of-band text tracks
#element-attrdef-track-defaultReferenced in:
* 4.7.12. The track element (2) (3) (4)
* Elements
#dom-htmltrackelement-readystateReferenced in:
* 4.7.12. The track element
#dom-htmltrackelement-noneReferenced in:
* 4.7.12. The track element
#dom-htmltrackelement-loadingReferenced in:
* 4.7.12. The track element
#dom-htmltrackelement-loadedReferenced in:
* 4.7.12. The track element
#dom-htmltrackelement-errorReferenced in:
* 4.7.12. The track element
#dom-htmltrackelement-trackReferenced in:
* 4.7.12. The track element
#dom-htmltrackelement-srcReferenced in:
* 4.7.12. The track element
#dom-htmltrackelement-srclangReferenced in:
* 4.7.12. The track element
#dom-htmltrackelement-labelReferenced in:
* 4.7.12. The track element
#dom-htmltrackelement-defaultReferenced in:
* 4.7.12. The track element
#dom-htmltrackelement-kindReferenced in:
* 4.7.12. The track element
#media-elementReferenced in:
* 3.2.5. Global attributes
* 4.7.4. The source element (2) (3) (4) (5) (6) (7)
* 4.7.7. The embed element (2)
* 4.7.8. The object element
* 4.7.10. The video element (2) (3) (4)
* 4.7.11. The audio element (2) (3)
* 4.7.12. The track element (2) (3) (4) (5) (6)
* 4.7.13. Media elements (2) (3) (4) (5)
* 4.7.13.1. Error codes
* 4.7.13.2. Location of the media resource (2) (3) (4) (5) (6) (7) (8)
(9) (10)
* 4.7.13.4. Network states
* 4.7.13.5. Loading the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23)
(24) (25) (26) (27) (28) (29) (30) (31) (32) (33) (34) (35) (36) (37)
(38) (39) (40) (41) (42) (43) (44) (45) (46) (47) (48) (49) (50) (51)
(52)
* 4.7.13.6. Offsets into the media resource (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12)
* 4.7.13.7. Ready states (2) (3) (4) (5) (6) (7) (8)
* 4.7.13.8. Playing the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23)
(24) (25) (26) (27) (28) (29) (30) (31) (32) (33) (34) (35) (36) (37)
(38) (39) (40) (41) (42) (43) (44) (45) (46) (47) (48) (49) (50) (51)
(52) (53) (54) (55) (56) (57) (58)
* 4.7.13.9. Seeking (2) (3) (4)
* 4.7.13.10. Media resources with multiple media tracks (2) (3) (4) (5)
* 4.7.13.11.1. Text track model (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16) (17) (18) (19) (20)
* 4.7.13.11.2. Sourcing in-band text tracks (2)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11) (12) (13) (14) (15)
* 4.7.13.11.5. Text track API (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15)
* 4.7.13.13. User interface (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13)
* 4.7.13.14. Time ranges (2)
* 4.7.13.16. Event summary (2) (3)
* 4.7.13.18. Best practices for authors using media elements
* 4.7.13.19. Best practices for implementors of media elements (2) (3)
* 6.4. Origin (2)
* 7.6.1. Simple dialogs
* 11.3.1. The applet element
#enumdef-canplaytyperesultReferenced in:
* 4.7.13. Media elements
#typedefdef-mediaproviderReferenced in:
* 4.7.13. Media elements
#htmlmediaelementReferenced in:
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.13. Media elements
* Element Interfaces (2)
#media-dataReferenced in:
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.13.5. Loading the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16)
* 4.7.13.6. Offsets into the media resource (2) (3) (4) (5) (6)
* 4.7.13.7. Ready states
* 4.7.13.8. Playing the media resource
* 4.7.13.9. Seeking
* 4.7.13.11.1. Text track model (2)
* 4.7.13.16. Event summary (2) (3) (4) (5) (6) (7) (8) (9)
* 6.4. Origin (2) (3)
* 7.6.1. Simple dialogs
#media-resourceReferenced in:
* 4.7.4. The source element (2) (3) (4)
* 4.7.10. The video element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.7.11. The audio element (2) (3) (4)
* 4.7.12. The track element (2) (3)
* 4.7.13. Media elements (2) (3)
* 4.7.13.1. Error codes (2) (3) (4)
* 4.7.13.2. Location of the media resource (2) (3) (4)
* 4.7.13.3. MIME types (2) (3)
* 4.7.13.5. Loading the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22)
* 4.7.13.6. Offsets into the media resource (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22)
(23) (24) (25) (26) (27)
* 4.7.13.7. Ready states (2) (3)
* 4.7.13.8. Playing the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19)
* 4.7.13.9. Seeking (2) (3) (4) (5) (6) (7) (8)
* 4.7.13.10. Media resources with multiple media tracks (2) (3) (4) (5)
(6) (7)
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2) (3) (4) (5)
(6) (7) (8) (9) (10) (11)
* 4.7.13.10.2. Selecting specific audio and video tracks declaratively
(2)
* 4.7.13.11.1. Text track model (2) (3) (4) (5)
* 4.7.13.11.2. Sourcing in-band text tracks (2) (3) (4) (5) (6) (7) (8)
(9)
* 4.7.13.11.5. Text track API (2)
* 4.7.13.11.6. Text tracks exposing in-band metadata
* 4.7.13.11.7. Text tracks describing chapters
* 4.7.13.13. User interface (2)
* 4.7.13.14. Time ranges
* 4.7.13.16. Event summary (2) (3) (4) (5)
* 7.8. Images
* Attributes (2) (3) (4)
#media-element-event-task-sourceReferenced in:
* 4.7.13.5. Loading the media resource (2)
#dom-htmlmediaelement-errorReferenced in:
* 4.7.13. Media elements
#mediaerrorReferenced in:
* 4.7.13. Media elements
#dom-mediaerror-codeReferenced in:
* 4.7.13.1. Error codes
#dom-mediaerror-media_err_abortedReferenced in:
* 4.7.13.1. Error codes
#dom-mediaerror-media_err_networkReferenced in:
* 4.7.13.1. Error codes
#dom-mediaerror-media_err_decodeReferenced in:
* 4.7.13.1. Error codes
#dom-mediaerror-media_err_src_not_supportedReferenced in:
* 4.7.13.1. Error codes
#element-attrdef-media-srcReferenced in:
* 4.7.13.2. Location of the media resource
* 4.7.13.5. Loading the media resource (2)
* Elements (2)
#element-attrdef-media-crossoriginReferenced in:
* Elements (2)
#dom-htmlmediaelement-srcReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-crossoriginReferenced in:
* 4.7.13. Media elements
#media-provider-objectReferenced in:
* 4.7.13.2. Location of the media resource (2) (3)
* 4.7.13.5. Loading the media resource (2) (3) (4)
#assigned-media-provider-objectReferenced in:
* 4.7.13.1. Error codes
* 4.7.13.2. Location of the media resource (2) (3)
* 4.7.13.5. Loading the media resource (2) (3) (4) (5) (6)
#dom-htmlmediaelement-currentsrcReferenced in:
* 4.7.13. Media elements
* 4.7.13.2. Location of the media resource
#dom-htmlmediaelement-srcobjectReferenced in:
* 4.7.13. Media elements
* 4.7.13.2. Location of the media resource (2)
#a-type-that-the-user-agent-knows-it-cannot-renderReferenced in:
* 4.7.13.3. MIME types (2)
* 4.7.13.5. Loading the media resource
#dom-htmlmediaelement-canplaytypeReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-networkstateReferenced in:
* 4.7.13. Media elements
* 4.7.13.4. Network states (2)
* 4.7.13.8. Playing the media resource
#dom-htmlmediaelement-network_emptyReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-network_idleReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-network_loadingReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-network_no_sourceReferenced in:
* 4.7.13. Media elements
#autoplaying-flagReferenced in:
* 4.7.13.5. Loading the media resource
* 4.7.13.7. Ready states (2)
* 4.7.13.8. Playing the media resource (2)
#delaying-the-load-event-flagReferenced in:
* 4.7.13.5. Loading the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13)
#dom-htmlmediaelement-loadReferenced in:
* 4.7.13. Media elements
#media-element-load-algorithmReferenced in:
* 4.7.13.2. Location of the media resource (2)
* 4.7.13.5. Loading the media resource
#resource-selection-algorithmReferenced in:
* 4.7.4. The source element
* 4.7.11. The audio element
* 4.7.13.1. Error codes
* 4.7.13.2. Location of the media resource (2)
* 4.7.13.4. Network states (2) (3)
* 4.7.13.5. Loading the media resource (2) (3) (4) (5) (6) (7)
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.16. Event summary (2)
#dedicated-media-source-failure-stepsReferenced in:
* 4.7.13.5. Loading the media resource (2)
#resource-fetch-algorithmReferenced in:
* 4.7.13.5. Loading the media resource (2) (3)
* 4.7.13.6. Offsets into the media resource
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2)
#stall-timeoutReferenced in:
* 4.7.13.5. Loading the media resource
#the-rules-described-previouslyReferenced in:
* 4.7.13.5. Loading the media resource
#media-data-processing-steps-listReferenced in:
* 4.7.13.5. Loading the media resource (2)
#runsReferenced in:
* 4.7.13.11.2. Sourcing in-band text tracks
#forget-the-media-elements-media-resource-specific-tracksReferenced in:
* 4.7.13.5. Loading the media resource (2) (3)
#element-attrdef-media-preloadReferenced in:
* Elements (2)
#statedef-media-metadataReferenced in:
* 4.7.13.5. Loading the media resource
#statedef-media-automaticReferenced in:
* 4.7.13.5. Loading the media resource
#dom-htmlmediaelement-preloadReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-bufferedReferenced in:
* 4.7.13. Media elements
#media-timelineReferenced in:
* 4.7.13.5. Loading the media resource (2)
* 4.7.13.6. Offsets into the media resource (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15)
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2)
* 4.7.13.14. Time ranges
#establish-the-media-timelineReferenced in:
* 4.7.13.5. Loading the media resource
#current-positionReferenced in:
* 4.7.10. The video element (2) (3) (4) (5) (6) (7) (8) (9)
* 4.7.11. The audio element
* 4.7.13.5. Loading the media resource (2) (3)
* 4.7.13.6. Offsets into the media resource (2) (3) (4) (5) (6)
* 4.7.13.7. Ready states (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13)
* 4.7.13.8. Playing the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21)
* 4.7.13.9. Seeking (2) (3) (4) (5) (6) (7) (8) (9)
* 4.7.13.11.1. Text track model
* 4.7.13.11.5. Text track API
* 4.7.13.16. Event summary (2) (3) (4)
* 7.8. Images
#official-playback-positionReferenced in:
* 4.7.13.5. Loading the media resource (2) (3)
* 4.7.13.6. Offsets into the media resource (2) (3) (4)
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.9. Seeking
#default-playback-start-positionReferenced in:
* 4.7.13.5. Loading the media resource (2)
* 4.7.13.6. Offsets into the media resource (2)
#show-poster-flagReferenced in:
* 4.7.10. The video element (2)
* 4.7.13.5. Loading the media resource (2) (3) (4)
* 4.7.13.7. Ready states
* 4.7.13.8. Playing the media resource (2) (3) (4)
* 4.7.13.9. Seeking
* 4.7.13.11.1. Text track model
* 4.7.13.11.5. Text track API (2)
#dom-htmlmediaelement-currenttimeReferenced in:
* 4.7.13. Media elements
#initial-playback-positionReferenced in:
* 4.7.13.5. Loading the media resource
* 4.7.13.6. Offsets into the media resource (2)
#earliest-possible-positionReferenced in:
* 4.7.13.5. Loading the media resource (2)
* 4.7.13.6. Offsets into the media resource (2) (3) (4) (5) (6) (7) (8)
* 4.7.13.8. Playing the media resource (2) (3) (4)
* 4.7.13.9. Seeking (2)
* 4.7.13.11.5. Text track API
#dom-htmlmediaelement-durationReferenced in:
* 4.7.13. Media elements
#timeline-offsetReferenced in:
* 4.7.13.5. Loading the media resource (2) (3)
* 4.7.13.6. Offsets into the media resource (2) (3)
#dom-htmlmediaelement-getstartdateReferenced in:
* 4.7.13. Media elements
#element-attrdef-media-loopReferenced in:
* Elements (2)
#dom-htmlmediaelement-loopReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-have_nothingReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-have_metadataReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-have_current_dataReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-have_future_dataReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-have_enough_dataReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-readystateReferenced in:
* 4.7.13. Media elements
* 4.7.13.8. Playing the media resource (2) (3) (4)
* 4.7.13.16. Event summary
#element-attrdef-media-autoplayReferenced in:
* 6.5. Sandboxing
* 6.7.6. Page load processing model for media
* Elements (2)
#dom-htmlmediaelement-autoplayReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-pausedReferenced in:
* 4.7.10. The video element (2) (3) (4)
* 4.7.13. Media elements
* 4.7.13.5. Loading the media resource
* 4.7.13.7. Ready states (2) (3) (4)
* 4.7.13.8. Playing the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13)
* 4.7.13.16. Event summary (2) (3) (4) (5) (6)
#blocked-media-elementReferenced in:
* 4.7.13.8. Playing the media resource
#potentially-playingReferenced in:
* 4.7.10. The video element (2)
* 4.7.11. The audio element (2)
* 4.7.13.7. Ready states
* 4.7.13.8. Playing the media resource (2) (3) (4) (5)
* 4.7.13.9. Seeking
* 4.7.13.16. Event summary
#playback-has-endedReferenced in:
* 4.7.13.5. Loading the media resource (2)
* 4.7.13.7. Ready states (2) (3)
* 4.7.13.8. Playing the media resource (2) (3) (4) (5)
* 4.7.13.16. Event summary
#dom-htmlmediaelement-endedReferenced in:
* 4.7.13. Media elements
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.16. Event summary
#stopped-due-to-errorsReferenced in:
* 4.7.13.7. Ready states
* 4.7.13.8. Playing the media resource
* 4.7.13.16. Event summary
#paused-for-user-interactionReferenced in:
* 4.7.13.7. Ready states
* 4.7.13.8. Playing the media resource (2) (3)
* 4.7.13.16. Event summary (2)
#paused-for-in-band-contentReferenced in:
* 4.7.13.7. Ready states
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.16. Event summary (2)
#dom-htmlmediaelement-defaultplaybackrateReferenced in:
* 4.7.13. Media elements
* 4.7.13.8. Playing the media resource (2) (3)
#dom-htmlmediaelement-playbackrateReferenced in:
* 4.7.13. Media elements
* 4.7.13.8. Playing the media resource
#dom-htmlmediaelement-playedReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-playReferenced in:
* 4.7.13. Media elements
* 4.7.13.8. Playing the media resource
#dom-htmlmediaelement-pauseReferenced in:
* 4.7.13. Media elements
#internal-pause-stepsReferenced in:
* 4.7.13.8. Playing the media resource (2)
#effective-playback-rateReferenced in:
* 4.7.13.7. Ready states
* 4.7.13.8. Playing the media resource (2) (3) (4) (5) (6) (7)
#direction-of-playbackReferenced in:
* 4.7.13.7. Ready states (2) (3)
* 4.7.13.8. Playing the media resource (2) (3) (4) (5) (6) (7) (8)
* 4.7.13.13. User interface
#list-of-newly-introduced-cuesReferenced in:
* 4.7.13.8. Playing the media resource (2) (3) (4) (5)
#time-marches-onReferenced in:
* 4.7.13.9. Seeking
#prepare-an-eventReferenced in:
* 4.7.13.8. Playing the media resource (2) (3)
#dom-htmlmediaelement-seekingReferenced in:
* 4.7.13. Media elements
#seekReferenced in:
* 4.7.13.5. Loading the media resource (2)
* 4.7.13.6. Offsets into the media resource (2) (3)
* 4.7.13.8. Playing the media resource (2) (3)
* 4.7.13.9. Seeking (2)
#dom-htmlmediaelement-seekableReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-audiotracksReferenced in:
* 4.7.13. Media elements
#dom-htmlmediaelement-videotracksReferenced in:
* 4.7.13. Media elements
#audiotracklistReferenced in:
* 4.7.13. Media elements
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2)
* 4.7.13.16. Event summary
#audiotrackReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2) (3) (4)
* 4.7.13.15. The TrackEvent interface (2) (3)
#videotracklistReferenced in:
* 4.7.13. Media elements
* 4.7.13.5. Loading the media resource (2)
* 4.7.13.6. Offsets into the media resource (2)
* 4.7.13.10. Media resources with multiple media tracks (2) (3)
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2) (3) (4) (5)
(6) (7) (8) (9) (10) (11)
* 4.7.13.16. Event summary
#videotrackReferenced in:
* 4.7.13.5. Loading the media resource
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2) (3) (4) (5)
* 4.7.13.15. The TrackEvent interface (2) (3)
#dom-audiotracklist-lengthReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-videotracklist-lengthReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-audiotracklist-gettrackbyidReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-videotracklist-gettrackbyidReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-audiotrack-idReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-videotrack-idReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-audiotrack-kindReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-videotrack-kindReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-audiotrack-labelReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-videotrack-labelReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-audiotrack-languageReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-videotrack-languageReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-audiotrack-enabledReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-videotracklist-selectedindexReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-videotrack-selectedReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
#dom-audiotracklist-onchangeReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2)
#dom-audiotracklist-onaddtrackReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2)
#dom-audiotracklist-onremovetrackReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2)
#text-tracksReferenced in:
* 4.7.10. The video element
* 4.7.12. The track element (2) (3) (4)
* 4.7.13.8. Playing the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19)
* 4.7.13.11.1. Text track model (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24)
(25)
* 4.7.13.11.2. Sourcing in-band text tracks (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19)
* 4.7.13.11.4. Guidelines for exposing cues in various formats as text
track cues
* 4.7.13.11.5. Text track API (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27) (28) (29) (30) (31) (32)
* 4.7.13.11.6. Text tracks exposing in-band metadata (2)
* 4.7.13.11.7. Text tracks describing chapters (2)
* 4.7.13.13. User interface
* 10.4.1. Embedded content (2)
* Attributes
#list-of-text-tracksReferenced in:
* 4.7.13.5. Loading the media resource
* 4.7.13.8. Playing the media resource (2) (3) (4) (5)
* 4.7.13.11.1. Text track model (2) (3) (4)
* 4.7.13.11.2. Sourcing in-band text tracks
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5) (6)
* 4.7.13.11.5. Text track API (2) (3) (4) (5) (6) (7) (8)
* 4.7.13.13. User interface
* 10.4.1. Embedded content
#kind-of-trackReferenced in:
* 4.7.13.11.1. Text track model (2) (3) (4)
* 4.7.13.11.2. Sourcing in-band text tracks (2)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5) (6)
* 4.7.13.11.4. Guidelines for exposing cues in various formats as text
track cues
* 4.7.13.11.5. Text track API (2) (3)
* 4.7.13.11.6. Text tracks exposing in-band metadata (2)
* 4.7.13.13. User interface
* 10.4.1. Embedded content
#track-subtitlesReferenced in:
* 4.7.12. The track element (2)
* 4.7.13.11.6. Text tracks exposing in-band metadata
#track-captionsReferenced in:
* 4.7.12. The track element
* 4.7.13.11.6. Text tracks exposing in-band metadata
#track-descriptionsReferenced in:
* 4.7.13.11.6. Text tracks exposing in-band metadata
#track-chaptersReferenced in:
* 4.7.12. The track element
* 4.7.13.11.6. Text tracks exposing in-band metadata
#track-metadataReferenced in:
* 4.7.13.11.6. Text tracks exposing in-band metadata
#label-of-a-trackReferenced in:
* 4.7.13.11.1. Text track model (2)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2)
* 4.7.13.11.5. Text track API (2) (3)
#in-band-metadata-track-dispatch-typeReferenced in:
* 4.7.13.11.1. Text track model
* 4.7.13.11.2. Sourcing in-band text tracks (2) (3) (4) (5) (6) (7) (8)
* 4.7.13.11.5. Text track API (2)
#text-track-languageReferenced in:
* 4.7.13.8. Playing the media resource
* 4.7.13.11.1. Text track model
* 4.7.13.11.3. Sourcing out-of-band text tracks (2)
* 4.7.13.11.5. Text track API (2) (3)
#a-readiness-stateReferenced in:
* 4.7.12. The track element (2)
* 4.7.13.11.1. Text track model (2) (3)
* 4.7.13.11.2. Sourcing in-band text tracks
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5) (6) (7)
* 4.7.13.11.5. Text track API
#statedef-track-not-loadedReferenced in:
* 4.7.12. The track element (2)
* 4.7.13.11.1. Text track model
* 4.7.13.11.3. Sourcing out-of-band text tracks
#statedef-track-loadingReferenced in:
* 4.7.12. The track element (2)
* 4.7.13.11.1. Text track model (2)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2)
#statedef-track-loadedReferenced in:
* 4.7.12. The track element (2)
* 4.7.13.11.1. Text track model
* 4.7.13.11.2. Sourcing in-band text tracks
* 4.7.13.11.3. Sourcing out-of-band text tracks
* 4.7.13.11.5. Text track API
#statedef-track-text-track-failed-to-loadReferenced in:
* 4.7.12. The track element (2)
* 4.7.13.11.1. Text track model
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3)
#a-modeReferenced in:
* 4.7.13.11.1. Text track model (2) (3)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11) (12)
* 4.7.13.11.5. Text track API (2) (3) (4) (5) (6) (7) (8)
#modedef-track-disabledReferenced in:
* 4.7.13.11.5. Text track API (2) (3) (4) (5) (6) (7)
#modedef-track-hiddenReferenced in:
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5)
* 4.7.13.11.5. Text track API (2) (3) (4) (5) (6)
#modedef-track-showingReferenced in:
* 4.7.10. The video element
* 4.7.13.8. Playing the media resource (2) (3)
* 4.7.13.11.1. Text track model
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5) (6) (7)
* 4.7.13.11.5. Text track API (2) (3) (4) (5)
* 4.7.13.11.6. Text tracks exposing in-band metadata
* 4.7.13.13. User interface
* 10.4.1. Embedded content
#list-of-cuesReferenced in:
* 4.7.13.8. Playing the media resource (2) (3) (4)
* 4.7.13.11.1. Text track model (2) (3)
* 4.7.13.11.2. Sourcing in-band text tracks (2)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5)
* 4.7.13.11.5. Text track API (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20)
* 4.7.13.11.7. Text tracks describing chapters
#rules-for-updating-the-text-track-renderingReferenced in:
* 4.7.13.8. Playing the media resource
* 4.7.13.11.1. Text track model (2)
* 4.7.13.11.2. Sourcing in-band text tracks
* 4.7.13.11.3. Sourcing out-of-band text tracks
* 4.7.13.11.5. Text track API (2) (3) (4) (5)
* 4.7.13.11.6. Text tracks exposing in-band metadata
* 10.4.1. Embedded content
#list-of-pending-text-tracksReferenced in:
* 4.7.13.5. Loading the media resource
* 4.7.13.11.1. Text track model (2) (3) (4)
#blocked-on-parserReferenced in:
* 4.7.13.5. Loading the media resource
* 4.7.13.11.1. Text track model (2) (3)
* 4.7.13.11.3. Sourcing out-of-band text tracks
#did-perform-automatic-track-selectionReferenced in:
* 4.7.13.11.3. Sourcing out-of-band text tracks (2)
#populate-the-list-of-pending-text-tracksReferenced in:
* 4.7.13.5. Loading the media resource
* 4.7.13.11.1. Text track model
#the-text-tracks-are-readyReferenced in:
* 4.7.13.7. Ready states
* 4.7.13.16. Event summary
#pending-text-track-change-notification-flagReferenced in:
* 4.7.13.11.1. Text track model (2) (3)
#cueReferenced in:
* 4.7.10. The video element
* 4.7.13.8. Playing the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23)
(24) (25) (26) (27)
* 4.7.13.11.1. Text track model (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13)
* 4.7.13.11.4. Guidelines for exposing cues in various formats as text
track cues (2) (3) (4) (5)
* 4.7.13.11.5. Text track API (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20)
* 4.7.13.11.6. Text tracks exposing in-band metadata (2)
* 4.7.13.11.7. Text tracks describing chapters (2)
#text-track-cue-identifierReferenced in:
* 4.7.13.11.4. Guidelines for exposing cues in various formats as text
track cues
* 4.7.13.11.5. Text track API (2) (3) (4) (5)
#text-track-cue-start-timeReferenced in:
* 4.7.13.8. Playing the media resource (2) (3) (4)
* 4.7.13.11.1. Text track model
* 4.7.13.11.5. Text track API (2) (3)
* 4.7.13.11.6. Text tracks exposing in-band metadata
* 4.7.13.11.7. Text tracks describing chapters (2) (3) (4) (5)
#text-track-cue-end-timeReferenced in:
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.11.1. Text track model
* 4.7.13.11.5. Text track API (2) (3)
* 4.7.13.11.6. Text tracks exposing in-band metadata
* 4.7.13.11.7. Text tracks describing chapters (2) (3) (4)
#pause-on-exit-flagReferenced in:
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.11.4. Guidelines for exposing cues in various formats as text
track cues
* 4.7.13.11.5. Text track API (2) (3)
#text-track-cue-dataReferenced in:
* 4.7.13.11.6. Text tracks exposing in-band metadata (2)
* 4.7.13.11.7. Text tracks describing chapters
#text-track-rules-for-extracting-the-chapter-titleReferenced in:
* 4.7.13.11.7. Text tracks describing chapters
#text-track-cue-active-flagReferenced in:
* 4.7.10. The video element
* 4.7.13.8. Playing the media resource (2) (3) (4) (5) (6) (7)
* 4.7.13.11.1. Text track model
* 4.7.13.11.5. Text track API
#text-track-cue-display-stateReferenced in:
* 4.7.13.11.1. Text track model
#text-track-cue-orderReferenced in:
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.11.5. Text track API (2) (3) (4)
#media-resource-specific-text-trackReferenced in:
* 4.7.13.5. Loading the media resource (2) (3)
* 4.7.13.11.1. Text track model
* 4.7.13.11.2. Sourcing in-band text tracks
* 4.7.13.11.4. Guidelines for exposing cues in various formats as text
track cues (2)
* 4.7.13.11.6. Text tracks exposing in-band metadata (2)
#steps-to-expose-a-media-resource-specific-text-trackReferenced in:
* 4.7.13.5. Loading the media resource
* 4.7.13.11.1. Text track model
#honor-user-preferences-for-automatic-text-track-selectionReferenced in:
* 4.7.13.11.1. Text track model
* 4.7.13.11.3. Sourcing out-of-band text tracks
#perform-automatic-text-track-selectionReferenced in:
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3)
#start-the-track-processing-modelReferenced in:
* 4.7.13.11.3. Sourcing out-of-band text tracks
#guidelines-for-exposing-cuesReferenced in:
* 4.7.13.11.2. Sourcing in-band text tracks
#texttracklistReferenced in:
* 4.7.13. Media elements
* 4.7.13.11.1. Text track model
* 4.7.13.11.2. Sourcing in-band text tracks
* 4.7.13.11.3. Sourcing out-of-band text tracks (2)
* 4.7.13.11.5. Text track API (2) (3) (4) (5) (6) (7) (8) (9)
* 4.7.13.16. Event summary
#dom-htmlmediaelement-texttracksReferenced in:
* 4.7.13. Media elements
#dom-texttracklist-lengthReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttracklist-gettrackbyidReferenced in:
* 4.7.13.11.5. Text track API
#enumdef-texttrackmodeReferenced in:
* 4.7.13.11.5. Text track API
#enumdef-texttrackkindReferenced in:
* 4.7.13. Media elements
* 4.7.13.11.5. Text track API
#texttrackReferenced in:
* 4.7.12. The track element (2) (3)
* 4.7.13. Media elements
* 4.7.13.8. Playing the media resource
* 4.7.13.11.1. Text track model (2)
* 4.7.13.11.2. Sourcing in-band text tracks (2)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3)
* 4.7.13.11.5. Text track API (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27) (28) (29) (30) (31) (32) (33)
* 4.7.13.11.8. Event handlers for objects of the text track APIs
* 4.7.13.15. The TrackEvent interface (2) (3)
* 4.7.13.16. Event summary
#dom-htmlmediaelement-addtexttrackReferenced in:
* 4.7.13. Media elements
#dom-texttrack-kindReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrack-labelReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrack-languageReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrack-idReferenced in:
* 4.7.13.11.5. Text track API (2)
#dom-texttrack-inbandmetadatatrackdispatchtypeReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrack-modeReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrackmode-disabledReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrackmode-hiddenReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrackmode-showingReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrack-cuesReferenced in:
* 4.7.13.11.5. Text track API
#earliest-possible-position-when-the-script-startedReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrack-activecuesReferenced in:
* 4.7.13.11.5. Text track API
#active-flag-was-set-when-the-script-startedReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrack-addcueReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrack-removecueReferenced in:
* 4.7.13.11.5. Text track API
#texttrackcuelistReferenced in:
* 4.7.13.11.5. Text track API (2)
#dom-texttrackcuelist-lengthReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrackcuelist-getcuebyidReferenced in:
* 4.7.13.11.5. Text track API
#texttrackcueReferenced in:
* 4.7.13.11.5. Text track API (2) (3) (4)
* 4.7.13.11.6. Text tracks exposing in-band metadata
* 4.7.13.16. Event summary
#dom-texttrackcue-trackReferenced in:
* 4.7.13.11.5. Text track API (2)
#dom-texttrackcue-idReferenced in:
* 4.7.13.11.5. Text track API (2)
#dom-texttrackcue-starttimeReferenced in:
* 4.7.13.11.5. Text track API (2)
#dom-texttrackcue-endtimeReferenced in:
* 4.7.13.11.5. Text track API (2)
#dom-texttrackcue-pauseonexitReferenced in:
* 4.7.13.11.5. Text track API (2)
#datacueReferenced in:
* 4.7.13.11.6. Text tracks exposing in-band metadata (2) (3) (4) (5)
#dom-datacue-dataReferenced in:
* 4.7.13.11.6. Text tracks exposing in-band metadata (2)
#rules-for-constructing-the-chapter-tree-from-a-text-trackReferenced in:
* 4.7.13.13. User interface
#dom-texttracklist-onchangeReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttracklist-onaddtrackReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttracklist-onremovetrackReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrack-oncuechangeReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrackcue-onenterReferenced in:
* 4.7.13.11.5. Text track API
#dom-texttrackcue-onexitReferenced in:
* 4.7.13.11.5. Text track API
#element-attrdef-mediaelements-controlsReferenced in:
* 3.2.1. Semantics
* 3.2.4.2.7. Interactive content (2)
* 3.2.4.2.8. Palpable content
* 4.7.10. The video element (2) (3) (4)
* 4.7.11. The audio element (2) (3) (4)
* 4.7.13. Media elements
* 4.7.13.13. User interface
* Elements (2)
* Element content categories (2) (3)
#exposing-a-user-interfaceReferenced in:
* 4.7.10. The video element
* 4.7.13.8. Playing the media resource
* 4.7.13.13. User interface (2)
* 5.4.2. Data model
* 10.4.1. Embedded content (2) (3) (4)
#dom-htmlmediaelement-controlsReferenced in:
* 4.7.13. Media elements
#playback-volumeReferenced in:
* 4.7.13.13. User interface (2) (3)
#dom-htmlmediaelement-volumeReferenced in:
* 4.7.13. Media elements
#mutedReferenced in:
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.13. User interface (2)
#dom-htmlmediaelement-mutedReferenced in:
* 4.7.13. Media elements
#effective-media-volumeReferenced in:
* 4.7.10. The video element
* 4.7.11. The audio element
* 4.7.13.13. User interface (2) (3)
#element-attrdef-media-mutedReferenced in:
* 4.7.13.13. User interface
* Elements (2)
#dom-htmlmediaelement-defaultmutedReferenced in:
* 4.7.13. Media elements
#timerangesReferenced in:
* 4.7.13. Media elements (2) (3)
#dom-timeranges-lengthReferenced in:
* 4.7.13.14. Time ranges
#dom-timeranges-startReferenced in:
* 4.7.13.14. Time ranges
#dom-timeranges-endReferenced in:
* 4.7.13.14. Time ranges
#normalized-timeranges-objectReferenced in:
* 4.7.13.5. Loading the media resource
* 4.7.13.8. Playing the media resource
* 4.7.13.9. Seeking
#trackeventReferenced in:
* 4.7.13.5. Loading the media resource (2)
* 4.7.13.6. Offsets into the media resource
* 4.7.13.11.2. Sourcing in-band text tracks
* 4.7.13.11.3. Sourcing out-of-band text tracks (2)
* 4.7.13.11.5. Text track API
* 4.7.13.16. Event summary (2)
#dictdef-trackeventinitReferenced in:
* 4.7.13.15. The TrackEvent interface
#dom-trackevent-trackReferenced in:
* 4.7.13.15. The TrackEvent interface
#eventdef-media-loadstartReferenced in:
* Attributes
#eventdef-media-suspendReferenced in:
* Attributes
#eventdef-media-emptiedReferenced in:
* 4.7.13.5. Loading the media resource (2) (3)
#eventdef-media-stalledReferenced in:
* Attributes
#eventdef-media-loadedmetadataReferenced in:
* Attributes
#eventdef-media-loadeddataReferenced in:
* Attributes
#eventdef-media-canplayReferenced in:
* Attributes
#eventdef-media-canplaythroughReferenced in:
* Attributes
#eventdef-media-playingReferenced in:
* Attributes
#eventdef-media-waitingReferenced in:
* Attributes
#eventdef-media-seekingReferenced in:
* Attributes
#eventdef-media-seekedReferenced in:
* Attributes
#eventdef-media-endedReferenced in:
* Attributes
#eventdef-media-durationchangeReferenced in:
* 4.7.13.6. Offsets into the media resource
* Attributes
#eventdef-media-timeupdateReferenced in:
* Attributes
#eventdef-media-playReferenced in:
* 4.7.13.7. Ready states
* 4.7.13.8. Playing the media resource
* Attributes
#eventdef-media-pauseReferenced in:
* Attributes
#eventdef-media-ratechangeReferenced in:
* Attributes
#eventdef-media-volumechangeReferenced in:
* 3.2.5. Global attributes
* Attributes
#eventdef-track-cuechangeReferenced in:
* Attributes
#elementdef-mapReferenced in:
* 2.7.2.1. The HTMLAllCollection interface (2)
* 3.2.4.2.2. Flow content (2)
* 3.2.4.2.5. Phrasing content (2)
* 3.2.4.2.8. Palpable content
* 3.2.4.3. Transparent content models
* 3.2.4.4. Paragraphs (2) (3)
* 4.4.1. The p element
* 4.7.5.1.12. Image maps
* 4.7.14. The map element (2) (3) (4) (5)
* 4.7.15. The area element (2)
* 4.7.16.1. Authoring
* 4.7.16.2. Processing model (2)
* 8.1.2.4. Optional tags
* Elements
* Element content categories (2) (3) (4) (5)
* Attributes
* Element Interfaces
#htmlmapelementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-map-nameReferenced in:
* 2.7.2.1. The HTMLAllCollection interface
* Elements
#dom-htmlmapelement-areasReferenced in:
* 4.7.14. The map element
#dom-htmlmapelement-imagesReferenced in:
* 4.7.14. The map element
#dom-htmlmapelement-nameReferenced in:
* 4.7.14. The map element
#elementdef-areaReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 3.1.3. DOM tree accessors (2)
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.5.3. The translate attribute
* 4.2.4. The link element
* 4.7.5.1.12. Image maps (2)
* 4.7.14. The map element (2) (3)
* 4.7.15. The area element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15)
* 4.7.16.2. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13)
* 4.8.1. Introduction (2) (3)
* 4.8.2. Links created by a and area elements (2) (3) (4) (5) (6)
* 4.8.3. API for a and area elements
* 4.8.4. Following hyperlinks (2)
* 4.8.5. Downloading resources (2)
* 4.8.6. Link types (2)
* 4.8.6.1. Link type "alternate"
* 4.8.6.2. Link type "author" (2) (3)
* 4.8.6.3. Link type "bookmark"
* 4.8.6.4. Link type "help" (2) (3)
* 4.8.6.6. Link type "license"
* 4.8.6.7. Link type "nofollow"
* 4.8.6.8. Link type "noopener"
* 4.8.6.9. Link type "noreferrer" (2)
* 4.8.6.10. Link type "search"
* 4.8.6.12. Link type "tag"
* 4.8.6.13.1. Link type "next"
* 4.8.6.13.2. Link type "prev"
* 4.8.6.14. Other link types (2) (3) (4) (5) (6)
* 4.15.2. Pseudo-classes (2)
* 5.4.2. Data model (2) (3) (4) (5) (6)
* 5.4.4. Processing model (2)
* 6.3.3. Named access on the Window object (2)
* 6.6.4. The Location interface
* 8.1.2. Elements
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 10.4.4. Image maps (2) (3) (4)
* 11.2. Non-conforming features (2) (3) (4)
* 11.3.4. Other elements, attributes and APIs
* Elements (2)
* Element content categories (2)
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10)
* Element Interfaces
#htmlareaelementReferenced in:
* 4.7.15. The area element
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#element-attrdef-area-altReferenced in:
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* Elements
#element-attrdef-area-shapeReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 4.7.15. The area element
* Elements
#attr-valuedef-area-shape-circleReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
#attr-valuedef-area-shape-circReferenced in:
* 1.10.3. Restrictions on content models and on attribute values (2)
#element-attrdef-area-coordsReferenced in:
* Elements
#statedef-area-circle-stateReferenced in:
* 4.7.15. The area element
* 4.7.16.2. Processing model (2) (3) (4)
#statedef-area-default-stateReferenced in:
* 4.7.15. The area element
* 4.7.16.2. Processing model (2) (3)
#statedef-area-polygon-stateReferenced in:
* 4.7.15. The area element
* 4.7.16.2. Processing model (2) (3)
#statedef-area-rectangle-stateReferenced in:
* 4.7.15. The area element (2)
* 4.7.16.2. Processing model (2) (3) (4) (5)
#dom-htmlareaelement-altReferenced in:
* 4.7.15. The area element
#dom-htmlareaelement-coordsReferenced in:
* 4.7.15. The area element
#dom-htmlareaelement-targetReferenced in:
* 4.7.15. The area element
#dom-htmlareaelement-downloadReferenced in:
* 4.7.15. The area element
#dom-htmlareaelement-relReferenced in:
* 4.7.15. The area element
#dom-htmlareaelement-hreflangReferenced in:
* 4.7.15. The area element
#dom-htmlareaelement-shapeReferenced in:
* 4.7.15. The area element
#dom-htmlareaelement-rellistReferenced in:
* 4.7.15. The area element
#dom-htmlareaelement-referrerpolicyReferenced in:
* 4.7.15. The area element
#image-mapReferenced in:
* 4.7.5. The img element (2)
* 4.7.14. The map element (2) (3)
* 4.7.15. The area element (2) (3) (4)
* 5.4.2. Data model
* 10.4.4. Image maps (2)
* Elements
* Attributes (2) (3) (4)
#element-attrdef-common-usemapReferenced in:
* Elements
* Element content categories
#dimension-attributesReferenced in:
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.10. The video element
* 4.10.5.1.19. Image Button state (type=image)
* 10.4.2. Images
#element-attrdef-media-widthReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 10.4.3. Attributes for embedded content and images
* Elements (2) (3) (4) (5) (6)
#element-attrdef-media-heightReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 10.4.3. Attributes for embedded content and images
* Elements (2) (3) (4) (5) (6)
#dom-htmliframeelement-widthReferenced in:
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.10. The video element
#dom-htmliframeelement-heightReferenced in:
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.10. The video element
#external-resource-linkReferenced in:
* 4.2.4. The link element (2) (3) (4) (5) (6) (7) (8)
* 4.2.4.1. Processing the media attribute
* 4.2.4.2. Processing the type attribute (2)
* 4.8.6. Link types (2)
* 4.8.6.5. Link type "icon"
* 4.8.6.11. Link type "stylesheet" (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.8.6.14. Other link types (2)
#hyperlinkReferenced in:
* 1.9. A quick introduction to HTML
* 2.5.3. Dynamic changes to base URLs
* 4.2.3. The base element (2) (3)
* 4.2.4. The link element (2) (3) (4) (5) (6)
* 4.2.4.1. Processing the media attribute
* 4.2.4.5. Providing users with a means to follow hyperlinks created
using the link element
* 4.5.1. The a element (2) (3) (4)
* 4.7.5.1.3. A link or button containing nothing but an image
* 4.7.15. The area element (2) (3)
* 4.7.16.1. Authoring
* 4.7.16.2. Processing model (2)
* 4.8.1. Introduction (2) (3)
* 4.8.2. Links created by a and area elements
* 4.8.5. Downloading resources (2) (3) (4)
* 4.8.6. Link types (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
(14) (15) (16)
* 4.8.6.1. Link type "alternate" (2)
* 4.8.6.2. Link type "author"
* 4.8.6.3. Link type "bookmark"
* 4.8.6.4. Link type "help"
* 4.8.6.6. Link type "license"
* 4.8.6.7. Link type "nofollow"
* 4.8.6.8. Link type "noopener" (2)
* 4.8.6.9. Link type "noreferrer"
* 4.8.6.10. Link type "search"
* 4.8.6.12. Link type "tag"
* 4.8.6.13.1. Link type "next"
* 4.8.6.13.2. Link type "prev"
* 4.8.6.14. Other link types (2) (3)
* 5.1. The hidden attribute
* 10.7.1. Links, forms, and navigation (2) (3) (4)
* 10.9. Unstyled XML documents
* Elements
* Attributes (2) (3) (4)
#annotatesReferenced in:
* 4.8.6.7. Link type "nofollow"
* 4.8.6.8. Link type "noopener"
* 4.8.6.9. Link type "noreferrer"
* 4.8.6.14. Other link types
#element-attrdef-a-hrefReferenced in:
* 1.9. A quick introduction to HTML (2) (3)
* 2.5.3. Dynamic changes to base URLs
* 3.1.3. DOM tree accessors (2) (3)
* 3.2.4.2.7. Interactive content
* 4.5.1. The a element (2) (3) (4) (5) (6) (7) (8)
* 4.7.5. The img element (2)
* 4.8.2. Links created by a and area elements (2) (3)
* 4.8.4. Following hyperlinks
* 4.8.5. Downloading resources
* 4.11.3.2. Using the a element to define a command
* 4.15.2. Pseudo-classes (2) (3) (4)
* 5.1. The hidden attribute
* 5.4.3. The tabindex attribute
* 5.7.4. The DragEvent interface
* 5.7.5. Drag-and-drop processing model (2) (3)
* 5.7.7. The draggable attribute
* 6.7.1. Navigating across documents
* 11.2. Non-conforming features
* Elements (2)
* Element content categories
#element-attrdef-a-targetReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
* Elements (2)
#element-attrdef-a-downloadReferenced in:
* 3.2.5.3. The translate attribute
* Elements (2)
#element-attrdef-a-relReferenced in:
* 4.2.4. The link element
* 4.5.1. The a element (2) (3) (4)
* 4.7.15. The area element (2) (3) (4)
* 4.8.1. Introduction (2) (3) (4)
* 4.8.2. Links created by a and area elements (2) (3) (4) (5) (6) (7)
(8) (9)
* 4.8.6. Link types
* 4.8.6.14. Other link types
* 4.15.1. Case-sensitivity
* Elements (2)
* Attributes
#element-attrdef-a-revReferenced in:
* 4.2.4. The link element
* 4.5.1. The a element (2) (3)
* 4.8.2. Links created by a and area elements (2) (3) (4) (5) (6)
* 4.8.6.2. Link type "author"
* Attributes
#reverse-linkReferenced in:
* 4.2.4. The link element
* 4.5.1. The a element
* 4.8.2. Links created by a and area elements
* Attributes
#element-attrdef-a-hreflangReferenced in:
* Elements (2)
#element-attrdef-a-typeReferenced in:
* Elements (2)
#htmlhyperlinkelementutilsReferenced in:
* 4.5.1. The a element
* 4.7.15. The area element
#set-the-urlReferenced in:
* 4.8.3. API for a and area elements (2)
#reinitialise-urlReferenced in:
* 4.8.3. API for a and area elements (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20)
#update-hrefReferenced in:
* 4.8.3. API for a and area elements (2) (3) (4) (5) (6) (7) (8) (9)
#dom-htmlhyperlinkelementutils-hrefReferenced in:
* 4.8.3. API for a and area elements
#dom-htmlhyperlinkelementutils-originReferenced in:
* 4.8.3. API for a and area elements
#dom-htmlhyperlinkelementutils-protocolReferenced in:
* 4.8.3. API for a and area elements
#dom-htmlhyperlinkelementutils-usernameReferenced in:
* 4.8.3. API for a and area elements
#dom-htmlhyperlinkelementutils-passwordReferenced in:
* 4.8.3. API for a and area elements
#dom-htmlhyperlinkelementutils-hostReferenced in:
* 4.8.3. API for a and area elements
#dom-htmlhyperlinkelementutils-hostnameReferenced in:
* 4.8.3. API for a and area elements
#dom-htmlhyperlinkelementutils-portReferenced in:
* 4.8.3. API for a and area elements
#dom-htmlhyperlinkelementutils-pathnameReferenced in:
* 4.8.3. API for a and area elements
#dom-htmlhyperlinkelementutils-searchReferenced in:
* 4.8.3. API for a and area elements
#dom-htmlhyperlinkelementutils-hashReferenced in:
* 4.8.3. API for a and area elements
#follow-hyperlinksReferenced in:
* 4.2.3. The base element
* 4.2.4.5. Providing users with a means to follow hyperlinks created
using the link element (2)
* 4.5.1. The a element (2)
* 4.7.15. The area element (2)
* 4.8.2. Links created by a and area elements (2)
* 6.1.5. Browsing context names
* 6.7.1. Navigating across documents
#concept-request-urlReferenced in:
* 7.1.3.2. Fetching scripts
#download-hyperlinksReferenced in:
* 4.5.1. The a element (2)
* 4.7.15. The area element (2)
* 4.8.2. Links created by a and area elements
* 4.8.5. Downloading resources
#as-a-downloadReferenced in:
* 4.8.5. Downloading resources (2)
* 6.7.1. Navigating across documents (2)
#extensionReferenced in:
* 4.8.5. Downloading resources (2) (3) (4) (5) (6)
#allowed-keywords-and-their-meaningsReferenced in:
* 4.2.4. The link element (2) (3)
* 4.2.4.4. Processing Link headers
* 4.8.1. Introduction (2) (3)
* 4.8.2. Links created by a and area elements (2) (3) (4)
* 4.8.4. Following hyperlinks
* 6.1.5. Browsing context names
#body-okReferenced in:
* 4.2.4. The link element
* 4.8.2. Links created by a and area elements
* 4.8.6. Link types (2)
* 4.8.6.11. Link type "stylesheet"
#element-statedef-link-alternateReferenced in:
* 4.2.4. The link element
* 4.8.6. Link types
* 4.8.6.1. Link type "alternate" (2) (3) (4) (5) (6) (7) (8) (9)
* 4.8.6.11. Link type "stylesheet"
#element-statedef-link-authorReferenced in:
* 4.8.6. Link types
* 4.8.6.2. Link type "author" (2) (3) (4)
#element-statedef-link-bookmarkReferenced in:
* 4.8.6. Link types
* 4.8.6.3. Link type "bookmark" (2)
#element-statedef-link-helpReferenced in:
* 4.8.6. Link types
* 4.8.6.4. Link type "help" (2) (3) (4)
#element-statedef-link-iconReferenced in:
* 4.2.4. The link element (2)
* 4.8.6. Link types
* 4.8.6.5. Link type "icon" (2) (3) (4) (5)
#element-statedef-link-licenseReferenced in:
* 4.8.6. Link types
* 4.8.6.6. Link type "license" (2) (3) (4)
#element-statedef-link-nofollowReferenced in:
* 4.8.6. Link types
* 4.8.6.7. Link type "nofollow" (2)
#element-statedef-link-noopenerReferenced in:
* 4.8.2. Links created by a and area elements
* 4.8.4. Following hyperlinks
* 4.8.6. Link types
* 4.8.6.8. Link type "noopener"
* 4.8.6.9. Link type "noreferrer"
#element-statedef-link-noreferrerReferenced in:
* 2.6.7. Referrer policy attributes
* 3.1.2. Resource metadata management
* 4.8.2. Links created by a and area elements
* 4.8.6. Link types
* 4.8.6.9. Link type "noreferrer" (2) (3)
* 6.1.5. Browsing context names (2)
#element-statedef-link-searchReferenced in:
* 4.2.4. The link element
* 4.8.6. Link types
* 4.8.6.10. Link type "search" (2) (3)
#element-statedef-link-stylesheetReferenced in:
* 4.2.4. The link element
* 4.2.4.2. Processing the type attribute
* 4.8.6. Link types (2)
* 4.8.6.1. Link type "alternate" (2)
* 4.8.6.11. Link type "stylesheet" (2)
#an-alternative-stylesheetReferenced in:
* 4.8.6.11. Link type "stylesheet" (2)
#element-statedef-link-tagReferenced in:
* 4.8.6. Link types
* 4.8.6.12. Link type "tag" (2) (3)
#element-statedef-link-nextReferenced in:
* 4.2.4. The link element
* 4.8.6. Link types
* 4.8.6.13.1. Link type "next" (2)
#element-statedef-link-prevReferenced in:
* 4.8.6. Link types
* 4.8.6.13.2. Link type "prev" (2) (3)
#other-link-typesReferenced in:
* 4.8.2. Links created by a and area elements
#link-types-extensions-to-the-predefined-set-of-link-typeReferenced in:
* 1.5.3. Extensibility
* 4.2.4. The link element
#elementdef-tableReferenced in:
* 1.10.2. Syntax errors (2)
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 4.4.1. The p element
* 4.9.1. The table element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27) (28)
* 4.9.1.1. Techniques for describing tables
* 4.9.2. The caption element (2) (3) (4)
* 4.9.3. The colgroup element (2)
* 4.9.4. The col element
* 4.9.5. The tbody element (2) (3) (4)
* 4.9.6. The thead element (2) (3) (4)
* 4.9.7. The tfoot element (2) (3) (4)
* 4.9.8. The tr element (2) (3) (4) (5) (6) (7)
* 4.9.12. Processing model
* 4.9.12.1. Forming a table (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14)
* 8.1.2.4. Optional tags
* 8.1.2.5. Restrictions on content models (2) (3)
* 8.2.3.1. The insertion mode (2)
* 8.2.3.2. The stack of open elements (2) (3)
* 8.2.5.1. Creating and inserting nodes (2) (3)
* 8.2.5.4.9. The "in table" insertion mode (2) (3) (4)
* 8.2.8.3. Unexpected markup in tables (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15)
* 8.3. Serializing HTML fragments (2)
* 10.3.9. Tables (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 11.2. Non-conforming features (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15)
* 11.3.4. Other elements, attributes and APIs (2) (3) (4)
* Elements (2) (3) (4) (5) (6) (7)
* Element content categories (2)
* Attributes (2)
* Element Interfaces
#htmltableelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#dom-htmltableelement-captionReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-createcaptionReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-deletecaptionReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-theadReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-createtheadReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-deletetheadReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-tfootReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-createtfootReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-deletetfootReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-tbodiesReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-createtbodyReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-rowsReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-insertrowReferenced in:
* 4.9.1. The table element
#dom-htmltableelement-deleterowReferenced in:
* 4.9.1. The table element
#provide-such-informationReferenced in:
* 4.9.1. The table element (2)
#elementdef-captionReferenced in:
* 1.10.2. Syntax errors
* 4.9.1. The table element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13)
* 4.9.1.1. Techniques for describing tables (2)
* 4.9.2. The caption element (2) (3)
* 4.9.3. The colgroup element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.12. Processing model
* 4.9.12.1. Forming a table (2) (3)
* 4.13.5. Footnotes
* 8.1.2.4. Optional tags (2)
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements (2)
* 8.2.3.3. The list of active formatting elements (2)
* 8.2.5.3. Closing elements that have implied end tags
* 8.2.5.4.11. The "in caption" insertion mode (2) (3) (4)
* 11.2. Non-conforming features
* 11.3.4. Other elements, attributes and APIs
* Elements (2)
* Element Interfaces
#htmltablecaptionelementReferenced in:
* 4.9.1. The table element (2)
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#elementdef-colgroupReferenced in:
* 4.9.1. The table element (2) (3)
* 4.9.3. The colgroup element (2) (3) (4) (5) (6)
* 4.9.4. The col element (2) (3) (4)
* 4.9.5. The tbody element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.12. Processing model
* 4.9.12.1. Forming a table (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12)
* 4.12.3. The template element
* 8.1.2.4. Optional tags (2) (3) (4) (5)
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements
* 8.2.5.3. Closing elements that have implied end tags
* 8.2.5.4.12. The "in column group" insertion mode (2)
* 10.3.9. Tables
* Elements (2) (3) (4)
* Attributes
* Element Interfaces
#htmltablecolelementReferenced in:
* 4.9.4. The col element
* 11.3.4. Other elements, attributes and APIs
* Elements (2)
* Element Interfaces (2)
#element-attrdef-colgroup-spanReferenced in:
* Elements
#dom-htmltablecolelement-spanReferenced in:
* 4.9.3. The colgroup element
* 4.9.4. The col element (2)
#elementdef-colReferenced in:
* 4.9.3. The colgroup element (2)
* 4.9.4. The col element (2) (3)
* 4.9.12. Processing model (2)
* 4.9.12.1. Forming a table (2) (3) (4) (5) (6) (7) (8) (9)
* 8.1.2. Elements
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 10.3.9. Tables (2) (3) (4)
* 11.2. Non-conforming features (2) (3) (4) (5)
* 11.3.4. Other elements, attributes and APIs (2) (3) (4)
* Elements (2)
* Attributes
* Element Interfaces
#element-attrdef-col-spanReferenced in:
* 10.3.9. Tables (2)
* Elements
#elementdef-tbodyReferenced in:
* 4.9.1. The table element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13)
* 4.9.3. The colgroup element
* 4.9.5. The tbody element (2) (3) (4) (5) (6) (7) (8)
* 4.9.6. The thead element (2)
* 4.9.7. The tfoot element (2) (3)
* 4.9.8. The tr element (2) (3) (4)
* 4.9.10. The th element
* 4.9.12. Processing model
* 4.9.12.1. Forming a table (2) (3) (4) (5) (6) (7)
* 8.1.2.4. Optional tags (2) (3) (4) (5) (6) (7)
* 8.1.2.5. Restrictions on content models
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements
* 8.2.5.1. Creating and inserting nodes (2)
* 8.2.5.3. Closing elements that have implied end tags
* 8.2.5.4.7. The "in body" insertion mode (2) (3)
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.13. The "in table body" insertion mode
* 8.2.8.3. Unexpected markup in tables (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11)
* 10.3.9. Tables (2) (3) (4) (5) (6)
* 11.2. Non-conforming features (2) (3) (4) (5)
* 11.3.4. Other elements, attributes and APIs (2) (3) (4)
* Elements (2) (3)
* Element Interfaces
#htmltablesectionelementReferenced in:
* 4.9.1. The table element (2) (3) (4) (5)
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 11.3.4. Other elements, attributes and APIs
* Elements (2) (3)
* Element Interfaces (2) (3)
#dom-htmltablesectionelement-rowsReferenced in:
* 4.9.5. The tbody element
#dom-htmltablesectionelement-insertrowReferenced in:
* 4.9.5. The tbody element
#dom-htmltablesectionelement-deleterowReferenced in:
* 4.9.5. The tbody element
#elementdef-theadReferenced in:
* 4.9.1. The table element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15)
* 4.9.3. The colgroup element
* 4.9.5. The tbody element (2) (3)
* 4.9.6. The thead element (2) (3) (4) (5) (6) (7)
* 4.9.7. The tfoot element
* 4.9.8. The tr element (2) (3)
* 4.9.12. Processing model
* 4.9.12.1. Forming a table (2) (3) (4) (5) (6) (7) (8) (9)
* 8.1.2.4. Optional tags (2) (3)
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements
* 8.2.5.1. Creating and inserting nodes
* 8.2.5.3. Closing elements that have implied end tags
* 8.2.5.4.7. The "in body" insertion mode (2) (3)
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.13. The "in table body" insertion mode
* 10.3.9. Tables (2) (3) (4) (5) (6)
* 11.2. Non-conforming features (2) (3) (4) (5)
* 11.3.4. Other elements, attributes and APIs (2) (3) (4)
* Elements (2) (3)
* Element Interfaces
#elementdef-tfootReferenced in:
* 4.9.1. The table element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15)
* 4.9.3. The colgroup element
* 4.9.5. The tbody element (2) (3)
* 4.9.6. The thead element (2)
* 4.9.7. The tfoot element (2) (3) (4) (5) (6)
* 4.9.8. The tr element (2) (3)
* 4.9.12. Processing model
* 4.9.12.1. Forming a table (2) (3) (4) (5) (6) (7) (8) (9)
* 8.1.2.4. Optional tags (2) (3) (4)
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements
* 8.2.5.1. Creating and inserting nodes
* 8.2.5.3. Closing elements that have implied end tags
* 8.2.5.4.7. The "in body" insertion mode (2) (3)
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.13. The "in table body" insertion mode
* 10.3.9. Tables (2) (3) (4) (5) (6)
* 11.2. Non-conforming features (2) (3) (4) (5)
* 11.3.4. Other elements, attributes and APIs (2) (3) (4)
* Elements (2) (3)
* Element Interfaces
#elementdef-trReferenced in:
* 3.2.4. Content models
* 4.9.1. The table element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16)
* 4.9.5. The tbody element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.9.9. The td element
* 4.9.10. The th element
* 4.9.11. Attributes common to td and th elements
* 4.9.12. Processing model
* 4.9.12.1. Forming a table (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12)
* 8.1.2.4. Optional tags (2) (3) (4)
* 8.1.2.5. Restrictions on content models (2)
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements
* 8.2.5.1. Creating and inserting nodes
* 8.2.5.3. Closing elements that have implied end tags
* 8.2.5.4.7. The "in body" insertion mode (2) (3)
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.14. The "in row" insertion mode (2) (3) (4)
* 8.2.8.3. Unexpected markup in tables (2) (3) (4) (5) (6) (7) (8)
* 10.3.9. Tables (2) (3) (4) (5) (6) (7) (8)
* 11.2. Non-conforming features (2) (3) (4) (5) (6) (7)
* 11.3.4. Other elements, attributes and APIs (2) (3) (4) (5)
* Elements (2) (3) (4) (5) (6) (7)
* Element Interfaces
#htmltablerowelementReferenced in:
* 4.9.1. The table element
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#dom-htmltablerowelement-rowindexReferenced in:
* 4.9.8. The tr element
#dom-htmltablerowelement-sectionrowindexReferenced in:
* 4.9.8. The tr element
#dom-htmltablerowelement-cellsReferenced in:
* 4.9.8. The tr element
#dom-htmltablerowelement-insertcellReferenced in:
* 4.9.8. The tr element
#dom-htmltablerowelement-deletecellReferenced in:
* 4.9.8. The tr element
#elementdef-tdReferenced in:
* 3.2.4. Content models (2)
* 4.3.9. Headings and sections (2)
* 4.9.8. The tr element (2) (3) (4) (5) (6)
* 4.9.9. The td element (2) (3) (4)
* 4.9.11. Attributes common to td and th elements (2) (3) (4) (5)
* 4.9.12. Processing model
* 8.1.2.4. Optional tags (2) (3) (4)
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements (2)
* 8.2.3.3. The list of active formatting elements (2)
* 8.2.5.3. Closing elements that have implied end tags
* 8.2.5.4.7. The "in body" insertion mode (2) (3)
* 8.2.5.4.15. The "in cell" insertion mode (2) (3)
* 8.2.8.3. Unexpected markup in tables (2) (3) (4) (5) (6)
* 10.3.9. Tables (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 10.3.10. Margin collapsing quirks (2) (3) (4)
* 11.2. Non-conforming features (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12)
* 11.3.4. Other elements, attributes and APIs (2) (3) (4) (5) (6)
* Elements (2)
* Element content categories
* Attributes (2) (3)
* Element Interfaces
#htmltabledatacellelementReferenced in:
* Elements
* Element Interfaces
#elementdef-thReferenced in:
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 4.9.1. The table element
* 4.9.8. The tr element (2) (3) (4) (5)
* 4.9.9. The td element
* 4.9.10. The th element (2) (3) (4) (5) (6) (7) (8) (9)
* 4.9.11. Attributes common to td and th elements (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
* 4.9.12. Processing model
* 4.9.12.1. Forming a table (2) (3) (4)
* 8.1.2.4. Optional tags (2) (3) (4)
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements (2)
* 8.2.3.3. The list of active formatting elements (2)
* 8.2.5.3. Closing elements that have implied end tags
* 8.2.5.4.7. The "in body" insertion mode (2) (3)
* 8.2.5.4.15. The "in cell" insertion mode (2) (3)
* 10.3.9. Tables (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
* 10.3.10. Margin collapsing quirks (2) (3) (4)
* 11.2. Non-conforming features (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13)
* 11.3.4. Other elements, attributes and APIs (2) (3) (4) (5) (6) (7)
* Elements (2) (3)
* Attributes (2) (3) (4) (5)
* Element Interfaces
#htmltableheadercellelementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-th-scopeReferenced in:
* 11.2. Non-conforming features
* Elements
#statedef-scope-rowReferenced in:
* 4.9.12.2. Forming relationships between data cells and header cells
#statedef-scope-columnReferenced in:
* 4.9.12.2. Forming relationships between data cells and header cells
#statedef-scope-autoReferenced in:
* 4.9.12.2. Forming relationships between data cells and header cells
(2)
#element-attrdef-th-abbrReferenced in:
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 10.7.4. Text rendered in native user interfaces
* 11.2. Non-conforming features
* Elements
#dom-htmltableheadercellelement-scopeReferenced in:
* 4.9.10. The th element
#dom-htmltableheadercellelement-abbrReferenced in:
* 4.9.10. The th element
#element-attrdef-tablecells-colspanReferenced in:
* 10.3.9. Tables
* Elements (2)
#element-attrdef-tablecells-rowspanReferenced in:
* 10.3.9. Tables
* Elements (2)
#element-attrdef-tablecells-headersReferenced in:
* Elements (2)
#htmltablecellelementReferenced in:
* 4.9.9. The td element
* 4.9.10. The th element
* 11.3.4. Other elements, attributes and APIs
* Element Interfaces (2)
#dom-htmltablecellelement-colspanReferenced in:
* 4.9.11. Attributes common to td and th elements
#dom-htmltablecellelement-rowspanReferenced in:
* 4.9.11. Attributes common to td and th elements
#dom-htmltablecellelement-headersReferenced in:
* 4.9.11. Attributes common to td and th elements
#dom-htmltablecellelement-cellindexReferenced in:
* 4.9.11. Attributes common to td and th elements
#table-modelReferenced in:
* 4.9.1. The table element (2)
* 4.9.2. The caption element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element (2)
* 4.9.10. The th element
* 4.9.11. Attributes common to td and th elements (2) (3)
#tableReferenced in:
* 4.9.1. The table element
* 4.9.8. The tr element
* 4.9.11. Attributes common to td and th elements (2)
* 4.9.12. Processing model
* 4.9.12.1. Forming a table (2)
* 4.9.12.2. Forming relationships between data cells and header cells
* 10.3.9. Tables
#slotsReferenced in:
* 4.9.12.1. Forming a table
#cellReferenced in:
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.9.12. Processing model (2) (3)
* 4.9.12.1. Forming a table (2) (3) (4)
* 10.3.9. Tables
#rowReferenced in:
* 4.9.5. The tbody element
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.12. Processing model (2) (3)
* 4.9.12.1. Forming a table (2)
#columnReferenced in:
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.12. Processing model (2)
* 4.9.12.1. Forming a table (2) (3) (4)
#row-groupReferenced in:
* 4.9.10. The th element (2)
* 4.9.12. Processing model (2) (3) (4) (5)
* 4.9.12.1. Forming a table
* 4.9.12.2. Forming relationships between data cells and header cells
(2)
#column-groupReferenced in:
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.10. The th element (2)
* 4.9.12. Processing model (2) (3) (4)
* 4.9.12.1. Forming a table (2)
* 4.9.12.2. Forming relationships between data cells and header cells
(2)
* 4.10.5.3.4. The required attribute
* 4.10.20.2. Constraint validation
#table-model-errorReferenced in:
* 4.9.12.1. Forming a table (2) (3)
#advanceReferenced in:
* 4.9.12.1. Forming a table (2) (3) (4) (5) (6) (7) (8)
#algorithm-for-processing-row-groupsReferenced in:
* 4.9.12.1. Forming a table (2) (3)
#algorithm-for-ending-a-row-groupReferenced in:
* 4.9.12.1. Forming a table (2)
#algorithm-for-processing-rowsReferenced in:
* 4.9.12.1. Forming a table (2)
#algorithm-for-growing-downward-growing-cellsReferenced in:
* 4.9.12.1. Forming a table (2)
#algorithm-for-assigning-header-cellsReferenced in:
* 4.9.9. The td element
* 4.9.12.1. Forming a table
#internal-algorithm-for-scanning-and-assigning-header-cellsReferenced in:
* 4.9.12.2. Forming relationships between data cells and header cells
(2)
#column-headerReferenced in:
* 4.9.12.2. Forming relationships between data cells and header cells
(2)
#row-headerReferenced in:
* 4.9.12.2. Forming relationships between data cells and header cells
#column-group-headerReferenced in:
* 4.9.12.2. Forming relationships between data cells and header cells
#row-group-headerReferenced in:
* 4.9.12.2. Forming relationships between data cells and header cells
#empty-cellReferenced in:
* 4.9.12.2. Forming relationships between data cells and header cells
#formsReferenced in:
* 4.2.3. The base element
* 10.7.1. Links, forms, and navigation
* Elements
#form-associated-elementsReferenced in:
* 4.7.5. The img element
* 4.7.8. The object element
* 4.10.2. Categories (2)
* 4.10.3. The form element
* 4.10.4. The label element
* 4.10.5. The input element (2)
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.15. The fieldset element
* 4.10.17.3. Association of controls and forms (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21)
* 8.2.5.1. Creating and inserting nodes
* Elements (2) (3) (4) (5) (6) (7) (8) (9)
* Element content categories
#listed-elementReferenced in:
* 2.7.2.2. The HTMLFormControlsCollection interface
* 4.7.8. The object element
* 4.10.3. The form element (2) (3)
* 4.10.5. The input element (2)
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.15. The fieldset element (2)
* 4.10.18.7.2. Processing model
* 8.2.5.1. Creating and inserting nodes
* Elements (2) (3) (4) (5) (6) (7)
* Element content categories
#submittable-elementReferenced in:
* 4.7.8. The object element
* 4.10.2. Categories
* 4.10.5. The input element (2)
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.10.20.1. Definitions
* 4.10.20.2. Constraint validation
* 4.10.21.4. Constructing the form data set
* Elements (2) (3) (4) (5)
* Element content categories
#buttonsReferenced in:
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button) (2)
* 4.10.5.5. Common event behaviors
* 4.10.6. The button element
* 4.10.21.4. Constructing the form data set
* 10.4.2. Images
#submit-buttonReferenced in:
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.18.6. Form submission (2)
#resettable-elementReferenced in:
* 4.10.5. The input element (2)
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.22. Resetting a form (2)
* 8.2.5.1. Creating and inserting nodes
* Elements (2) (3) (4)
* Element content categories
#reassociateable-elementReferenced in:
* 4.7.8. The object element
* 4.10.5. The input element (2)
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.15. The fieldset element
* 4.10.17.3. Association of controls and forms (2) (3) (4) (5) (6) (7)
(8)
* Elements (2) (3) (4) (5) (6) (7) (8)
* Element content categories
#labelable-elementReferenced in:
* 4.10.4. The label element (2) (3) (4) (5) (6)
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* Elements (2) (3) (4) (5) (6) (7)
* Element content categories
#elementdef-formReferenced in:
* 1.10.3. Restrictions on content models and on attribute values (2)
* 2.7.2.1. The HTMLAllCollection interface (2)
* 2.7.2.2. The HTMLFormControlsCollection interface
* 3.1.3. DOM tree accessors (2) (3) (4)
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 4.4.1. The p element
* 4.7.8. The object element
* 4.10.1.1. Writing a form’s user interface
* 4.10.1.3. Configuring a form to communicate with a server
* 4.10.1.4. Client-side form validation
* 4.10.2. Categories (2)
* 4.10.3. The form element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24)
* 4.10.5. The input element
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* 4.10.17.3. Association of controls and forms (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11) (12) (13)
* 4.10.18.1. Naming form controls: the name attribute
* 4.10.18.6. Form submission (2) (3) (4) (5)
* 4.10.20.2. Constraint validation (2)
* 4.10.21.2. Implicit submission (2) (3) (4) (5) (6)
* 4.10.21.3. Form submission algorithm (2) (3) (4) (5) (6) (7)
* 4.10.21.7. Multipart form data (2) (3)
* 4.10.22. Resetting a form
* 4.15.2. Pseudo-classes (2)
* 5.1. The hidden attribute
* 6.3.3. Named access on the Window object (2)
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 8.2.3.4. The element pointers (2)
* 8.2.5.1. Creating and inserting nodes
* 8.2.5.4.7. The "in body" insertion mode (2)
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.7. Coercing an HTML DOM into an infoset
* 8.3. Serializing HTML fragments (2) (3)
* 8.4. Parsing HTML fragments (2) (3)
* 11.2. Non-conforming features (2)
* Elements
* Element content categories (2)
* Attributes (2) (3) (4) (5) (6) (7) (8)
* Element Interfaces
* Events (2) (3) (4)
#htmlformelementReferenced in:
* 4.7.8. The object element
* 4.10.4. The label element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.10. The option element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.15. The fieldset element
* 4.10.16. The legend element
* Elements
* Element Interfaces
#element-attrdef-form-accept-charsetReferenced in:
* 4.10.3. The form element (2)
* 4.10.21.7. Multipart form data (2)
* Elements
* Attributes
#element-attrdef-form-nameReferenced in:
* 2.7.2.1. The HTMLAllCollection interface
* 4.10.3. The form element
* Elements
#attr-valuedef-form-autocomplete-onReferenced in:
* Attributes
#statedef-form-autocomplete-onReferenced in:
* 4.10.3. The form element (2)
#attr-valuedef-form-autocomplete-offReferenced in:
* Attributes
#statedef-form-autocomplete-offReferenced in:
* 4.10.3. The form element
* 4.10.18.7.2. Processing model
#dom-htmlformelement-autocompleteReferenced in:
* 4.10.3. The form element
#dom-htmlformelement-nameReferenced in:
* 4.10.3. The form element
#dom-htmlformelement-acceptcharsetReferenced in:
* 4.10.3. The form element
#dom-htmlformelement-elementsReferenced in:
* 4.10.2. Categories
* 4.10.3. The form element (2)
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.15. The fieldset element
* Attributes
#dom-htmlformelement-lengthReferenced in:
* 4.10.3. The form element (2)
#past-names-mapReferenced in:
* 4.10.3. The form element (2) (3) (4) (5)
#dom-htmlformelement-submitReferenced in:
* 4.10.3. The form element (2) (3)
* 4.10.21.3. Form submission algorithm (2) (3) (4)
#dom-htmlformelement-resetReferenced in:
* 4.10.3. The form element (2)
#dom-htmlformelement-checkvalidityReferenced in:
* 4.10.3. The form element (2)
#dom-htmlformelement-reportvalidityReferenced in:
* 4.10.3. The form element (2)
#elementdef-labelReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content
* 4.10.1.1. Writing a form’s user interface (2)
* 4.10.2. Categories (2) (3) (4)
* 4.10.4. The label element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21)
* 4.10.5. The input element
* 4.10.5.3.10. The placeholder attribute (2) (3) (4)
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.11. The textarea element (2) (3) (4) (5)
* 4.10.12. The output element
* 4.10.13. The progress element
* 4.10.14. The meter element
* 4.11.3.4. Using the input element to define a command
* 4.11.3.6. Using the accesskey attribute on a label element to define a
command (2)
* 4.11.3.7. Using the accesskey attribute on a legend element to define
a command
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements
* 4.15.2. Pseudo-classes (2) (3) (4) (5)
* 5.1. The hidden attribute
* 11.2. Non-conforming features (2) (3)
* Elements
* Element content categories (2) (3) (4) (5) (6)
* Attributes (2)
* Element Interfaces
#htmllabelelementReferenced in:
* Elements
* Element Interfaces
#labeled-controlReferenced in:
* 4.10.4. The label element (2) (3) (4) (5) (6) (7)
* 4.11.3.4. Using the input element to define a command (2)
* 4.11.3.6. Using the accesskey attribute on a label element to define a
command (2) (3)
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements (2)
* 4.15.2. Pseudo-classes (2)
#element-attrdef-label-forReferenced in:
* 4.10.4. The label element (2) (3) (4) (5) (6) (7)
* Elements
#dom-htmllabelelement-htmlforReferenced in:
* 4.10.4. The label element
#dom-htmllabelelement-controlReferenced in:
* 4.10.4. The label element
#dom-htmllabelelement-labelsReferenced in:
* 4.10.5. The input element (2)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.12. The output element (2)
* 4.10.13. The progress element (2)
* 4.10.14. The meter element (2)
#elementdef-inputReferenced in:
* 2.7.2.1. The HTMLAllCollection interface (2)
* 2.7.2.2. The HTMLFormControlsCollection interface (2) (3)
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content
* 3.2.5.1. The title attribute
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute (2)
* 3.2.6. The innerText IDL attribute
* 4.7.19. Dimension attributes (2)
* 4.10.1.1. Writing a form’s user interface (2) (3) (4) (5) (6)
* 4.10.1.4. Client-side form validation
* 4.10.1.6. The difference between the field type, the autofill field
name, and the input modality (2)
* 4.10.1.7. Date, time, and number formats
* 4.10.2. Categories (2) (3) (4) (5) (6) (7)
* 4.10.3. The form element (2) (3)
* 4.10.5. The input element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19)
* 4.10.5.1.1. Hidden state (type=hidden) (2) (3)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search) (2)
(3) (4)
* 4.10.5.1.3. Telephone state (type=tel) (2) (3)
* 4.10.5.1.4. URL state (type=url) (2) (3)
* 4.10.5.1.5. E-mail state (type=email) (2) (3) (4)
* 4.10.5.1.6. Password state (type=password) (2) (3)
* 4.10.5.1.7. Date state (type=date) (2) (3)
* 4.10.5.1.8. Month state (type=month) (2) (3)
* 4.10.5.1.9. Week state (type=week) (2) (3)
* 4.10.5.1.10. Time state (type=time) (2) (3)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2) (3)
(4) (5)
* 4.10.5.1.12. Number state (type=number) (2) (3)
* 4.10.5.1.13. Range state (type=range) (2) (3)
* 4.10.5.1.14. Color state (type=color) (2) (3)
* 4.10.5.1.15. Checkbox state (type=checkbox) (2) (3)
* 4.10.5.1.16. Radio Button state (type=radio) (2) (3) (4) (5) (6) (7)
(8) (9)
* 4.10.5.1.17. File Upload state (type=file) (2) (3) (4) (5) (6) (7)
* 4.10.5.1.18. Submit Button state (type=submit) (2) (3) (4)
* 4.10.5.1.19. Image Button state (type=image) (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11) (12) (13) (14)
* 4.10.5.1.20. Reset Button state (type=reset) (2)
* 4.10.5.1.21. Button state (type=button) (2)
* 4.10.5.2. Implementation notes regarding localization of form controls
* 4.10.5.3. Common input element attributes (2) (3)
* 4.10.5.3.1. The maxlength and minlength attributes (2) (3)
* 4.10.5.3.3. The readonly attribute
* 4.10.5.3.6. The pattern attribute (2) (3) (4)
* 4.10.5.3.9. The list attribute (2) (3) (4) (5)
* 4.10.5.4. Common input element APIs (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13)
* 4.10.5.5. Common event behaviors (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14)
* 4.10.8. The datalist element (2)
* 4.10.17.1. A form control value (2) (3)
* 4.10.18.5. Enabling and disabling form controls: the disabled
attribute
* 4.10.18.6. Form submission
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15) (16) (17)
(18) (19) (20) (21) (22) (23) (24) (25) (26) (27) (28) (29) (30) (31)
(32) (33)
* 4.10.18.7.2. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12)
* 4.10.19. APIs for text field selections (2) (3) (4) (5) (6) (7) (8)
(9)
* 4.10.20.1. Definitions (2) (3)
* 4.10.21.2. Implicit submission
* 4.10.21.3. Form submission algorithm
* 4.10.21.4. Constructing the form data set (2) (3) (4) (5) (6) (7) (8)
(9)
* 4.11.3.4. Using the input element to define a command (2)
* 4.14. Disabled elements
* 4.15.2. Pseudo-classes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13)
* 5.4.2. Data model
* 5.4.3. The tabindex attribute
* 5.4.4. Processing model
* 5.6.5. Spelling and grammar checking (2) (3)
* 5.7.5. Drag-and-drop processing model (2) (3) (4)
* 6.7.10.1. Persisted user state restoration
* 8.1.2. Elements
* 8.2.3.2. The stack of open elements
* 8.2.5.4.9. The "in table" insertion mode
* 8.3. Serializing HTML fragments (2) (3)
* 10.3.5. Bidirectional text (2)
* 10.4.2. Images (2) (3)
* 10.4.3. Attributes for embedded content and images (2) (3) (4) (5)
* 10.5.4. The input element as a text entry widget. (2) (3) (4) (5)
* 10.5.5. The input element as domain-specific widgets (2) (3) (4) (5)
(6) (7)
* 10.5.6. The input element as a range control (2)
* 10.5.7. The input element as a color well (2)
* 10.5.8. The input element as a checkbox and radio button widgets (2)
(3)
* 10.5.9. The input element as a file upload control (2)
* 10.5.10. The input element as a button (2)
* 11.1. Obsolete but conforming features (2)
* 11.1.1. Warnings for obsolete but conforming features (2)
* 11.2. Non-conforming features (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12)
* 11.3.4. Other elements, attributes and APIs (2)
* Elements
* Element content categories (2) (3) (4) (5) (6) (7) (8) (9) (10)
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14)
(15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26) (27) (28)
(29) (30) (31) (32)
* Element Interfaces
#htmlinputelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#element-attrdef-input-typeReferenced in:
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute (2)
* 4.10.1.1. Writing a form’s user interface (2) (3) (4) (5)
* 4.10.1.6. The difference between the field type, the autofill field
name, and the input modality (2)
* 4.10.1.7. Date, time, and number formats
* 4.10.2. Categories
* 4.10.3. The form element (2) (3)
* 4.10.5. The input element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19)
* 4.10.5.1.1. Hidden state (type=hidden) (2)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio) (2)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image) (2) (3) (4) (5)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.3. Common input element attributes
* 4.10.5.3.6. The pattern attribute
* 4.10.5.3.7. The min and max attributes (2) (3)
* 4.10.5.3.8. The step attribute (2) (3)
* 4.10.5.3.9. The list attribute (2)
* 4.10.5.4. Common input element APIs (2) (3) (4) (5) (6) (7)
* 4.10.5.5. Common event behaviors (2) (3)
* 4.10.6. The button element (2) (3) (4)
* 4.10.18.6. Form submission
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15) (16) (17)
(18) (19) (20) (21) (22) (23) (24) (25) (26) (27) (28) (29) (30) (31)
(32) (33)
* 4.10.18.7.2. Processing model (2) (3) (4) (5) (6)
* 4.10.21.2. Implicit submission
* 4.10.21.3. Form submission algorithm
* 4.10.21.4. Constructing the form data set (2) (3) (4) (5) (6) (7) (8)
* 4.15.2. Pseudo-classes (2) (3) (4) (5)
* 5.4.3. The tabindex attribute
* 5.6.5. Spelling and grammar checking
* 5.7.5. Drag-and-drop processing model (2) (3) (4)
* 8.1.2.3. Attributes
* 10.3.5. Bidirectional text (2)
* 10.4.2. Images
* 10.4.3. Attributes for embedded content and images (2) (3) (4) (5)
* 10.5.4. The input element as a text entry widget. (2) (3) (4)
* 10.5.5. The input element as domain-specific widgets (2) (3) (4) (5)
(6)
* 10.5.6. The input element as a range control
* 10.5.7. The input element as a color well
* 10.5.8. The input element as a checkbox and radio button widgets (2)
* 10.5.9. The input element as a file upload control
* 10.5.10. The input element as a button (2)
* 11.1. Obsolete but conforming features
* 11.1.1. Warnings for obsolete but conforming features (2)
* 11.2. Non-conforming features
* Elements
* Element content categories (2)
* Changes between Working Draft 7 and Working Draft 6
* Changes since HTML 5.1 - Note that these may change if the HTML 5.1
specification is updated.
#applyReferenced in:
* 4.10.5. The input element
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search) (2)
* 4.10.5.1.3. Telephone state (type=tel) (2)
* 4.10.5.1.4. URL state (type=url) (2)
* 4.10.5.1.5. E-mail state (type=email) (2)
* 4.10.5.1.6. Password state (type=password) (2)
* 4.10.5.1.7. Date state (type=date) (2)
* 4.10.5.1.8. Month state (type=month) (2)
* 4.10.5.1.9. Week state (type=week) (2)
* 4.10.5.1.10. Time state (type=time) (2)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2)
* 4.10.5.1.12. Number state (type=number) (2)
* 4.10.5.1.13. Range state (type=range) (2)
* 4.10.5.1.14. Color state (type=color) (2)
* 4.10.5.1.15. Checkbox state (type=checkbox) (2)
* 4.10.5.1.16. Radio Button state (type=radio) (2)
* 4.10.5.1.17. File Upload state (type=file) (2)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.3. Common input element attributes (2)
* 4.10.5.3.1. The maxlength and minlength attributes (2)
* 4.10.5.3.4. The required attribute
* 4.10.5.3.6. The pattern attribute (2)
* 4.10.5.3.7. The min and max attributes
* 4.10.5.3.8. The step attribute
* 4.10.5.4. Common input element APIs (2) (3)
* 4.10.5.5. Common event behaviors (2) (3) (4) (5)
* 4.10.18.7.2. Processing model
* 4.10.19. APIs for text field selections
* 5.4.4. Processing model
#does-not-applyReferenced in:
* 4.10.5.1.1. Hidden state (type=hidden) (2) (3)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search) (2)
* 4.10.5.1.3. Telephone state (type=tel) (2)
* 4.10.5.1.4. URL state (type=url) (2)
* 4.10.5.1.5. E-mail state (type=email) (2)
* 4.10.5.1.6. Password state (type=password) (2)
* 4.10.5.1.7. Date state (type=date) (2)
* 4.10.5.1.8. Month state (type=month) (2)
* 4.10.5.1.9. Week state (type=week) (2)
* 4.10.5.1.10. Time state (type=time) (2)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2)
* 4.10.5.1.12. Number state (type=number) (2)
* 4.10.5.1.13. Range state (type=range) (2)
* 4.10.5.1.14. Color state (type=color) (2)
* 4.10.5.1.15. Checkbox state (type=checkbox) (2)
* 4.10.5.1.16. Radio Button state (type=radio) (2)
* 4.10.5.1.17. File Upload state (type=file) (2)
* 4.10.5.1.18. Submit Button state (type=submit) (2) (3)
* 4.10.5.1.19. Image Button state (type=image) (2) (3)
* 4.10.5.1.20. Reset Button state (type=reset) (2) (3)
* 4.10.5.1.21. Button state (type=button) (2) (3)
* 4.10.5.3. Common input element attributes
* 4.10.5.3.6. The pattern attribute
* 4.10.5.3.7. The min and max attributes
* 4.10.5.3.8. The step attribute
* 4.10.5.3.9. The list attribute (2)
* 4.10.5.4. Common input element APIs (2) (3) (4) (5) (6)
* 4.10.19. APIs for text field selections (2)
#value-sanitization-algorithmReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email) (2) (3)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.4. Common input element APIs
#algorithm-to-convert-a-string-to-a-numberReferenced in:
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.3.7. The min and max attributes (2) (3) (4) (5) (6) (7)
* 4.10.5.3.8. The step attribute (2) (3) (4)
* 4.10.5.4. Common input element APIs (2)
#algorithm-to-convert-a-number-to-a-stringReferenced in:
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.4. Common input element APIs (2)
#algorithm-to-convert-a-string-to-a-date-objectReferenced in:
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.4. Common input element APIs (2)
#algorithm-to-convert-a-date-object-to-a-stringReferenced in:
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.4. Common input element APIs (2)
#input-dirty-value-flagReferenced in:
* 4.10.5. The input element (2) (3) (4) (5)
* 4.10.5.3.1. The maxlength and minlength attributes (2)
* 4.10.5.4. Common input element APIs
#element-attrdef-input-valueReferenced in:
* 3.2.5.3. The translate attribute
* 4.10.5. The input element (2) (3) (4) (5) (6) (7)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button) (2)
* 4.10.5.3.8. The step attribute
* 4.10.5.4. Common input element APIs (2) (3) (4) (5) (6) (7) (8)
* 8.1.2.3. Attributes
* 10.5.10. The input element as a button
* Elements
#dirty-checkedness-flagReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.4. Common input element APIs
#element-attrdef-input-checkedReferenced in:
* 4.10.5. The input element (2) (3) (4) (5) (6) (7)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.15.2. Pseudo-classes (2)
* Elements
#a-type-change-is-signalledReferenced in:
* 4.10.5.1.16. Radio Button state (type=radio)
#dom-htmlinputelement-indeterminateReferenced in:
* 4.10.5. The input element
* 4.15.2. Pseudo-classes
#dom-htmlinputelement-acceptReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-altReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-maxReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-minReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-multipleReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-patternReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-placeholderReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-_requiredReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-sizeReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-srcReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-stepReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-dirnameReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-readonlyReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-defaultcheckedReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-defaultvalueReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-typeReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-maxlengthReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-minlengthReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-widthReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-heightReferenced in:
* 4.10.5. The input element
#state-of-the-type-attributeReferenced in:
* 4.10.5. The input element
#element-statedef-input-hiddenReferenced in:
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content
* 4.10.2. Categories
* 4.10.5. The input element (2) (3) (4) (5) (6)
* 4.10.5.1.1. Hidden state (type=hidden) (2)
* 4.10.5.5. Common event behaviors
* 4.10.18.1. Naming form controls: the name attribute
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5) (6) (7) (8) (9) (10)
* 5.4.3. The tabindex attribute
* Element content categories (2)
#element-statedef-input-textReferenced in:
* 3.2.5.5. The dir attribute
* 4.10.5. The input element (2)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search) (2)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15) (16) (17)
(18) (19) (20) (21) (22) (23) (24) (25) (26) (27) (28) (29) (30) (31)
(32) (33) (34) (35) (36) (37) (38) (39) (40) (41) (42) (43) (44) (45)
* 4.10.18.7.2. Processing model
* 4.10.21.2. Implicit submission
* 4.10.21.4. Constructing the form data set
* 5.6.5. Spelling and grammar checking
* 5.7.5. Drag-and-drop processing model
* 6.7.10.1. Persisted user state restoration
* 10.3.5. Bidirectional text
* 10.5.4. The input element as a text entry widget.
* 11.2. Non-conforming features
#element-statedef-input-searchReferenced in:
* 3.2.5.5. The dir attribute
* 4.10.5. The input element (2)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search) (2)
(3)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5) (6) (7) (8)
* 4.10.21.2. Implicit submission
* 4.10.21.4. Constructing the form data set
* 5.6.5. Spelling and grammar checking
* 5.7.5. Drag-and-drop processing model
* 6.7.10.1. Persisted user state restoration
* 10.3.5. Bidirectional text
* 10.5.4. The input element as a text entry widget.
#element-statedef-input-telephoneReferenced in:
* 3.2.5.5. The dir attribute (2)
* 4.10.5. The input element (2)
* 4.10.5.1.3. Telephone state (type=tel) (2)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
* 4.10.21.2. Implicit submission
* 5.7.5. Drag-and-drop processing model
* 10.3.5. Bidirectional text
* 10.5.4. The input element as a text entry widget.
#element-statedef-input-urlReferenced in:
* 3.2.5.5. The dir attribute
* 4.10.5. The input element (2)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4)
* 4.10.20.1. Definitions
* 4.10.21.2. Implicit submission
* 5.6.5. Spelling and grammar checking
* 5.7.5. Drag-and-drop processing model
* 10.3.5. Bidirectional text
* 10.5.4. The input element as a text entry widget.
#element-statedef-input-e-mailReferenced in:
* 3.2.5.5. The dir attribute
* 4.10.5. The input element (2)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.5. E-mail state (type=email) (2)
* 4.10.5.3.9. The list attribute
* 4.10.17.1. A form control value
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
* 4.10.18.7.2. Processing model
* 4.10.20.1. Definitions
* 4.10.21.2. Implicit submission
* 5.6.5. Spelling and grammar checking
* 5.7.5. Drag-and-drop processing model
* 10.3.5. Bidirectional text
* 10.5.4. The input element as a text entry widget.
#valid-e-mail-addressReferenced in:
* 4.10.5.1.5. E-mail state (type=email) (2) (3) (4) (5)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute
#valid-e-mail-address-listReferenced in:
* 4.10.5.1.5. E-mail state (type=email) (2) (3) (4)
#element-statedef-input-passwordReferenced in:
* 4.10.5. The input element (2)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3)
* 4.10.18.7.2. Processing model (2) (3)
* 4.10.21.2. Implicit submission
* 5.7.5. Drag-and-drop processing model
* 10.5.4. The input element as a text entry widget.
#element-statedef-input-dateReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.3.8. The step attribute
* 4.10.5.5. Common event behaviors
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
* 4.10.21.2. Implicit submission
* 10.5.5. The input element as domain-specific widgets
#element-statedef-input-monthReferenced in:
* 4.10.5. The input element (2)
* 4.10.5.3.8. The step attribute
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
* 4.10.21.2. Implicit submission
* 10.5.5. The input element as domain-specific widgets
#element-statedef-input-weekReferenced in:
* 4.10.5. The input element (2)
* 4.10.5.3.8. The step attribute
* 4.10.5.4. Common input element APIs
* 4.10.21.2. Implicit submission
* 10.5.5. The input element as domain-specific widgets
#element-statedef-input-timeReferenced in:
* 4.10.5. The input element (2)
* 4.10.5.3.8. The step attribute
* 4.10.21.2. Implicit submission
* 10.5.5. The input element as domain-specific widgets
#element-statedef-input-localdatetimeReferenced in:
* 4.10.5. The input element (2)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2) (3)
(4) (5)
* 4.10.5.3.8. The step attribute
* 4.10.21.2. Implicit submission
* 10.5.5. The input element as domain-specific widgets
#element-statedef-input-numberReferenced in:
* 4.10.5. The input element (2)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5) (6) (7)
* 4.10.21.2. Implicit submission
* 5.7.5. Drag-and-drop processing model
* 10.5.5. The input element as domain-specific widgets
* 11.1. Obsolete but conforming features
* 11.1.1. Warnings for obsolete but conforming features (2)
#element-statedef-input-rangeReferenced in:
* 4.10.5. The input element (2)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.3.9. The list attribute
* 4.10.5.5. Common event behaviors (2) (3)
* 10.5.6. The input element as a range control
#range-default-valueReferenced in:
* 4.10.5.1.13. Range state (type=range) (2)
#element-statedef-input-colorReferenced in:
* 4.10.5. The input element (2)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.5. Common event behaviors
* 10.5.7. The input element as a color well
#element-statedef-input-checkboxReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.15. Checkbox state (type=checkbox) (2)
* 4.10.5.5. Common event behaviors
* 4.10.21.4. Constructing the form data set (2)
* 4.11.3.4. Using the input element to define a command
* 4.15.2. Pseudo-classes (2)
* 10.5.8. The input element as a checkbox and radio button widgets
#element-statedef-input-radioReferenced in:
* 2.7.2.2. The HTMLFormControlsCollection interface (2) (3)
* 4.10.5. The input element (2) (3)
* 4.10.5.1.16. Radio Button state (type=radio) (2)
* 4.10.5.5. Common event behaviors
* 4.10.21.4. Constructing the form data set (2)
* 4.11.3.4. Using the input element to define a command
* 4.15.2. Pseudo-classes (2)
* 10.5.8. The input element as a checkbox and radio button widgets
#radio-button-groupReferenced in:
* 4.10.5.1.16. Radio Button state (type=radio) (2) (3) (4) (5)
* 4.10.5.3.4. The required attribute
* 4.15.2. Pseudo-classes
#element-statedef-input-fileReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.17. File Upload state (type=file) (2)
* 4.10.5.4. Common input element APIs (2)
* 4.10.5.5. Common event behaviors
* 4.10.21.4. Constructing the form data set (2)
* 10.5.9. The input element as a file upload control
* Attributes
#selected-filesReferenced in:
* 4.10.5. The input element
* 4.10.5.1.17. File Upload state (type=file) (2) (3) (4)
* 4.10.5.4. Common input element APIs (2) (3) (4) (5) (6) (7)
* 4.10.21.4. Constructing the form data set
* 5.4.4. Processing model
* 10.5.9. The input element as a file upload control
#path-componentsReferenced in:
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.4. Common input element APIs
#element-attrdef-input-acceptReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file) (2)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 11.2. Non-conforming features
* Elements
* Attributes
#element-statedef-input-submitReferenced in:
* 4.10.5. The input element (2)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.18.6. Form submission (2) (3) (4) (5) (6)
* 4.10.21.2. Implicit submission (2)
* 4.11.3.4. Using the input element to define a command (2)
* 4.15.2. Pseudo-classes (2)
* 10.5.10. The input element as a button
#element-statedef-input-imageReferenced in:
* 4.7.19. Dimension attributes
* 4.10.3. The form element (2) (3)
* 4.10.5. The input element (2) (3)
* 4.10.5.1.19. Image Button state (type=image) (2) (3) (4) (5)
* 4.10.21.3. Form submission algorithm
* 4.10.21.4. Constructing the form data set (2)
* 4.11.3.4. Using the input element to define a command (2)
* 4.15.2. Pseudo-classes (2)
* 10.4.2. Images
* 10.4.3. Attributes for embedded content and images (2) (3) (4) (5)
* 11.2. Non-conforming features
#element-attrdef-input-srcReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image) (2) (3) (4) (5) (6) (7)
(8) (9)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* Elements
#availableReferenced in:
* 4.7.5. The img element (2) (3)
#element-attrdef-input-altReferenced in:
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image) (2) (3)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* Elements
#coordinateReferenced in:
* 4.10.5.1.19. Image Button state (type=image) (2) (3) (4)
* 4.10.21.3. Form submission algorithm (2)
* 4.10.21.4. Constructing the form data set
#element-statedef-input-resetReferenced in:
* 3.2.5.3. The translate attribute
* 4.10.5. The input element (2)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.11.3.4. Using the input element to define a command (2)
* 4.15.2. Pseudo-classes
* 10.5.10. The input element as a button
#element-statedef-input-buttonReferenced in:
* 3.2.5.3. The translate attribute
* 4.10.5. The input element (2)
* 4.11.3.4. Using the input element to define a command (2)
* 4.15.2. Pseudo-classes
* 10.5.10. The input element as a button
#implementation-notesReferenced in:
* 4.10.1.7. Date, time, and number formats
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
#element-attrdef-input-maxlengthReferenced in:
* 4.10.1.4. Client-side form validation
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.20.1. Definitions
* 11.1. Obsolete but conforming features
* 11.1.1. Warnings for obsolete but conforming features
* Elements
#element-attrdef-input-minlengthReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.20.1. Definitions
* Elements
#element-attrdef-input-sizeReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 10.5.4. The input element as a text entry widget. (2)
* 11.1. Obsolete but conforming features
* 11.1.1. Warnings for obsolete but conforming features
* Elements
#element-attrdef-input-readonlyReferenced in:
* 4.10.5. The input element (2) (3) (4) (5)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.15.2. Pseudo-classes (2)
* Elements
#element-attrdef-input-requiredReferenced in:
* 4.10.1.4. Client-side form validation
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.20.1. Definitions
* 4.15.2. Pseudo-classes
* Elements
#requiredReferenced in:
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.3.4. The required attribute
* 4.15.2. Pseudo-classes (2)
#element-attrdef-input-multipleReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file) (2)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.17.1. A form control value
* Elements
#element-attrdef-input-patternReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.3.6. The pattern attribute
* 4.10.20.1. Definitions
* Elements
#compiled-pattern-regular-expressionReferenced in:
* 4.10.5.3.6. The pattern attribute (2) (3) (4)
#element-attrdef-input-titleReferenced in:
* 4.10.5. The input element
* 4.10.5.3.6. The pattern attribute (2) (3) (4)
* Attributes
#has-a-periodic-domainReferenced in:
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.3.7. The min and max attributes (2) (3)
#element-attrdef-input-minReferenced in:
* 4.10.1.1. Writing a form’s user interface
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date) (2)
* 4.10.5.1.8. Month state (type=month) (2)
* 4.10.5.1.9. Week state (type=week) (2)
* 4.10.5.1.10. Time state (type=time) (2)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2)
* 4.10.5.1.12. Number state (type=number) (2)
* 4.10.5.1.13. Range state (type=range) (2) (3)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.3.7. The min and max attributes (2) (3) (4)
* 4.10.5.3.8. The step attribute (2)
* 4.10.5.4. Common input element APIs
* 4.10.20.1. Definitions
* Elements
#element-attrdef-input-maxReferenced in:
* 4.10.1.1. Writing a form’s user interface
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date) (2)
* 4.10.5.1.8. Month state (type=month) (2)
* 4.10.5.1.9. Week state (type=week) (2)
* 4.10.5.1.10. Time state (type=time) (2)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2)
* 4.10.5.1.12. Number state (type=number) (2)
* 4.10.5.1.13. Range state (type=range) (2)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.3.7. The min and max attributes (2) (3)
* 4.10.20.1. Definitions
* Elements
* Attributes
#min-minimumReferenced in:
* 4.10.5.1.13. Range state (type=range) (2) (3) (4) (5) (6) (7) (8)
* 4.10.5.3.7. The min and max attributes (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11)
* 4.10.5.4. Common input element APIs (2) (3) (4) (5) (6) (7)
#default-minimumReferenced in:
* 4.10.5.1.13. Range state (type=range)
#max-maximumReferenced in:
* 4.10.5.1.13. Range state (type=range) (2) (3) (4) (5) (6)
* 4.10.5.3.7. The min and max attributes (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11)
* 4.10.5.4. Common input element APIs (2) (3) (4) (5) (6) (7)
#default-maximumReferenced in:
* 4.10.5.1.13. Range state (type=range)
#have-a-reversed-rangeReferenced in:
* 4.10.5.3.7. The min and max attributes (2) (3)
#have-range-limitationsReferenced in:
* 4.15.2. Pseudo-classes (2)
#element-attrdef-input-stepReferenced in:
* 4.10.1.1. Writing a form’s user interface
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date) (2)
* 4.10.5.1.8. Month state (type=month) (2)
* 4.10.5.1.9. Week state (type=week) (2)
* 4.10.5.1.10. Time state (type=time) (2)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range) (2)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.3.8. The step attribute (2) (3)
* 4.10.5.4. Common input element APIs (2) (3) (4) (5)
* 4.10.20.1. Definitions
* 4.10.20.3. The constraint validation API
* Elements
* Attributes
#default-stepReferenced in:
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.3.8. The step attribute (2)
#step-scale-factorReferenced in:
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.3.8. The step attribute (2) (3)
#default-step-baseReferenced in:
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.3.8. The step attribute
#allowed-value-stepReferenced in:
* 4.10.5.3.8. The step attribute (2) (3) (4) (5) (6)
* 4.10.5.4. Common input element APIs (2) (3) (4) (5) (6) (7) (8)
#step-baseReferenced in:
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.3.7. The min and max attributes
* 4.10.5.4. Common input element APIs (2) (3) (4)
#element-attrdef-input-listReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search) (2)
(3)
* 4.10.5.1.3. Telephone state (type=tel) (2) (3)
* 4.10.5.1.4. URL state (type=url) (2) (3)
* 4.10.5.1.5. E-mail state (type=email) (2) (3)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range) (2)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.3.9. The list attribute (2) (3) (4)
* 4.10.5.4. Common input element APIs
* 4.10.8. The datalist element
* 10.5.6. The input element as a range control
* 10.5.7. The input element as a color well
* Elements
* Attributes
#suggestions-source-elementReferenced in:
* 4.10.5.3.9. The list attribute (2) (3) (4) (5)
* 4.10.5.4. Common input element APIs
#element-attrdef-input-placeholderReferenced in:
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* Elements
#apisReferenced in:
* 4.10.5. The input element
#dom-htmlinputelement-valueReferenced in:
* 4.10.5. The input element (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search) (2)
* 4.10.5.1.3. Telephone state (type=tel) (2)
* 4.10.5.1.4. URL state (type=url) (2)
* 4.10.5.1.5. E-mail state (type=email) (2)
* 4.10.5.1.6. Password state (type=password) (2)
* 4.10.5.1.7. Date state (type=date) (2)
* 4.10.5.1.8. Month state (type=month) (2)
* 4.10.5.1.9. Week state (type=week) (2)
* 4.10.5.1.10. Time state (type=time) (2)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2)
* 4.10.5.1.12. Number state (type=number) (2)
* 4.10.5.1.13. Range state (type=range) (2)
* 4.10.5.1.14. Color state (type=color) (2)
* 4.10.5.1.15. Checkbox state (type=checkbox) (2)
* 4.10.5.1.16. Radio Button state (type=radio) (2)
* 4.10.5.1.17. File Upload state (type=file) (2) (3) (4)
* 4.10.5.1.18. Submit Button state (type=submit) (2)
* 4.10.5.1.19. Image Button state (type=image) (2)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.4. Common input element APIs
#modedef-input-valueReferenced in:
* 4.10.5. The input element (2) (3) (4) (5) (6) (7) (8)
#modedef-input-defaultReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
#modedef-input-default-onReferenced in:
* 4.10.5. The input element
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
#modedef-input-filenameReferenced in:
* 4.10.5. The input element
* 4.10.5.1.17. File Upload state (type=file)
#dom-htmlinputelement-checkedReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.4. Common input element APIs
#dom-htmlinputelement-filesReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.4. Common input element APIs
#dom-htmlinputelement-valueasdateReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.4. Common input element APIs
#dom-htmlinputelement-valueasnumberReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.4. Common input element APIs
#dom-htmlinputelement-stepdownReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.4. Common input element APIs (2) (3)
#dom-htmlinputelement-stepupReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.4. Common input element APIs (2) (3) (4) (5) (6)
#is-step-alignedReferenced in:
* 4.10.5.4. Common input element APIs (2)
#is-not-step-alignedReferenced in:
* 4.10.5.3.8. The step attribute (2)
* 4.10.5.4. Common input element APIs
#step-alignReferenced in:
* 4.10.5.4. Common input element APIs (2) (3) (4) (5) (6) (7) (8) (9)
(10)
#dom-htmlinputelement-listReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.4. Common input element APIs
#elementdef-buttonReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 2.1.2. XML compatibility (2) (3)
* 2.7.2.1. The HTMLAllCollection interface (2)
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content
* 3.2.6. The innerText IDL attribute
* 4.7.5.1.3. A link or button containing nothing but an image
* 4.10.1.1. Writing a form’s user interface
* 4.10.2. Categories (2) (3) (4) (5) (6)
* 4.10.6. The button element (2) (3) (4)
* 4.10.18.5. Enabling and disabling form controls: the disabled
attribute
* 4.11.3.3. Using the button element to define a command (2)
* 4.14. Disabled elements
* 4.15.2. Pseudo-classes (2) (3) (4)
* 5.4.3. The tabindex attribute
* 8.2.3.2. The stack of open elements (2)
* 8.2.5.4.7. The "in body" insertion mode
* 10.5.2. The button element (2)
* 11.2. Non-conforming features (2) (3)
* Elements
* Element content categories (2) (3) (4) (5) (6) (7) (8) (9)
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* Element Interfaces
* Changes between Working Draft 6 and Working Draft 5
#htmlbuttonelementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-button-typeReferenced in:
* 4.10.6. The button element
* Elements
* Attributes
#attr-valuedef-button-type-submitReferenced in:
* Attributes
#element-statedef-button-type-submit-buttonReferenced in:
* 4.10.6. The button element (2) (3) (4) (5)
#element-statedef-button-type-reset-buttonReferenced in:
* 4.10.6. The button element (2)
#element-statedef-button-type-buttonReferenced in:
* 4.10.6. The button element (2)
#element-attrdef-button-valueReferenced in:
* 4.10.6. The button element (2)
* Elements
#dom-htmlbuttonelement-valueReferenced in:
* 4.10.6. The button element
#dom-htmlbuttonelement-typeReferenced in:
* 4.10.6. The button element
#elementdef-selectReferenced in:
* 2.7.2.1. The HTMLAllCollection interface (2)
* 2.7.2.3. The HTMLOptionsCollection interface (2) (3) (4) (5) (6) (7)
(8)
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content
* 3.2.6. The innerText IDL attribute
* 4.10.1.6. The difference between the field type, the autofill field
name, and the input modality
* 4.10.2. Categories (2) (3) (4) (5) (6) (7)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.3.9. The list attribute
* 4.10.7. The select element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27) (28) (29) (30) (31) (32) (33)
* 4.10.8. The datalist element
* 4.10.9. The optgroup element (2) (3) (4)
* 4.10.10. The option element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.10.17.1. A form control value
* 4.10.18.5. Enabling and disabling form controls: the disabled
attribute
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5) (6) (7) (8) (9)
* 4.10.18.7.2. Processing model (2) (3) (4) (5) (6) (7)
* 4.10.20.1. Definitions (2)
* 4.10.21.4. Constructing the form data set (2)
* 4.11.3.5. Using the option element to define a command (2) (3)
* 4.14. Disabled elements
* 4.15.2. Pseudo-classes (2) (3)
* 5.4.3. The tabindex attribute
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements
* 8.2.5.4.16. The "in select" insertion mode (2) (3)
* 8.2.5.4.17. The "in select in table" insertion mode (2)
* 10.5.14. The select element (2) (3) (4) (5) (6)
* 10.7.4. Text rendered in native user interfaces
* 11.2. Non-conforming features (2) (3)
* Elements (2) (3)
* Element content categories (2) (3) (4) (5) (6) (7) (8) (9) (10)
* Attributes (2) (3) (4) (5) (6) (7) (8)
* Element Interfaces
#htmlselectelementReferenced in:
* 4.10.7. The select element
* Elements
* Element Interfaces
#dom-htmlselectelement-removeReferenced in:
* 4.10.7. The select element
#element-attrdef-select-multipleReferenced in:
* 4.10.7. The select element
* 4.10.10. The option element
* 10.5.14. The select element (2) (3)
* Elements
#element-attrdef-select-sizeReferenced in:
* 4.10.7. The select element
* Elements
#display-sizeReferenced in:
* 4.10.7. The select element (2) (3) (4) (5) (6) (7)
* 10.5.14. The select element (2) (3)
#list-of-optionsReferenced in:
* 4.10.7. The select element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27) (28) (29) (30) (31)
* 4.10.10. The option element (2)
* 4.10.18.7.2. Processing model (2)
* 4.10.21.4. Constructing the form data set
* 10.5.14. The select element (2)
#element-attrdef-select-requiredReferenced in:
* 4.10.7. The select element
* 4.10.20.1. Definitions
* 4.15.2. Pseudo-classes (2)
* Elements
#placeholder-label-optionReferenced in:
* 4.10.7. The select element (2)
* 4.10.10. The option element (2)
* 10.5.14. The select element (2) (3)
#pickedReferenced in:
* 4.11.3.5. Using the option element to define a command
#ask-for-a-resetReferenced in:
* 4.10.7. The select element
* 4.10.10. The option element
#toggleReferenced in:
* 4.10.7. The select element
* 4.11.3.5. Using the option element to define a command
#send-select-update-notificationsReferenced in:
* 4.10.7. The select element (2) (3) (4)
#dom-htmlselectelement-typeReferenced in:
* 4.10.7. The select element
#dom-htmlselectelement-optionsReferenced in:
* 4.10.7. The select element
* 4.10.10. The option element
#dom-htmlselectelement-lengthReferenced in:
* 4.10.7. The select element
#dom-htmlselectelement-itemReferenced in:
* 4.10.7. The select element
#dom-htmlselectelement-nameditemReferenced in:
* 4.10.7. The select element
#set-the-value-of-a-new-indexed-propertyReferenced in:
* 4.10.7. The select element
#dom-htmlselectelement-selectedoptionsReferenced in:
* 4.10.7. The select element
#dom-htmlselectelement-selectedindexReferenced in:
* 4.10.7. The select element
#dom-htmlselectelement-valueReferenced in:
* 4.10.7. The select element
#dom-htmlselectelement-multipleReferenced in:
* 4.10.7. The select element
#dom-htmlselectelement-_requiredReferenced in:
* 4.10.7. The select element
#dom-htmlselectelement-sizeReferenced in:
* 4.10.7. The select element
#elementdef-datalistReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 4.10.5.3.5. The multiple attribute
* 4.10.5.3.9. The list attribute (2) (3) (4) (5) (6) (7) (8) (9)
* 4.10.5.4. Common input element APIs
* 4.10.8. The datalist element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12)
* 4.10.10. The option element (2) (3) (4)
* 4.10.21.4. Constructing the form data set
* Elements (2)
* Element content categories (2)
* Element Interfaces
* Changes between Working Draft 2 and the First Public Working Draft
#htmldatalistelementReferenced in:
* Elements
* Element Interfaces
#dom-htmldatalistelement-optionsReferenced in:
* 4.10.8. The datalist element
#elementdef-optgroupReferenced in:
* 2.7.2.3. The HTMLOptionsCollection interface (2)
* 3.2.6. The innerText IDL attribute (2)
* 4.10.7. The select element (2) (3)
* 4.10.9. The optgroup element (2) (3) (4) (5) (6) (7)
* 4.10.10. The option element (2) (3) (4) (5)
* 4.14. Disabled elements
* 4.15.2. Pseudo-classes
* 8.1.2.4. Optional tags (2) (3) (4)
* 8.2.3.2. The stack of open elements
* 8.2.5.3. Closing elements that have implied end tags (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3)
* 8.2.5.4.16. The "in select" insertion mode (2) (3)
* 10.5.14. The select element (2) (3) (4)
* Elements (2) (3)
* Attributes (2)
* Element Interfaces
#htmloptgroupelementReferenced in:
* 2.7.2.3. The HTMLOptionsCollection interface
* 4.10.7. The select element
* Elements
* Element Interfaces
#element-attrdef-optgroup-disabledReferenced in:
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.15.2. Pseudo-classes
* Elements
#element-attrdef-optgroup-labelReferenced in:
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 4.10.9. The optgroup element
* 10.5.14. The select element
* Elements
#dom-htmloptgroupelement-disabledReferenced in:
* 4.10.9. The optgroup element
#dom-htmloptgroupelement-labelReferenced in:
* 4.10.9. The optgroup element
#elementdef-optionReferenced in:
* 2.7.2.3. The HTMLOptionsCollection interface (2) (3) (4) (5) (6) (7)
* 3.2.6. The innerText IDL attribute (2) (3)
* 4.10.5.3.9. The list attribute (2)
* 4.10.7. The select element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27) (28) (29) (30) (31) (32) (33) (34) (35)
* 4.10.8. The datalist element (2) (3) (4) (5) (6) (7)
* 4.10.9. The optgroup element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.10.10. The option element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24)
* 4.10.17.1. A form control value
* 4.10.18.7.2. Processing model (2) (3)
* 4.10.20.1. Definitions
* 4.10.21.4. Constructing the form data set (2)
* 4.11.3.5. Using the option element to define a command (2) (3) (4) (5)
(6)
* 4.14. Disabled elements
* 4.15.2. Pseudo-classes (2) (3)
* 8.1.2.4. Optional tags (2) (3)
* 8.2.3.2. The stack of open elements (2)
* 8.2.5.3. Closing elements that have implied end tags (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4)
* 8.2.5.4.16. The "in select" insertion mode (2) (3) (4)
* 10.5.14. The select element (2) (3)
* 11.2. Non-conforming features (2) (3)
* Elements (2) (3) (4)
* Attributes (2) (3) (4)
* Element Interfaces
* Changes between Working Draft 6 and Working Draft 5
* Changes between Working Draft 2 and the First Public Working Draft
#htmloptionelementReferenced in:
* 2.7.2.3. The HTMLOptionsCollection interface (2)
* 4.10.7. The select element (2) (3)
* 4.10.10. The option element (2)
* Elements
* Element Interfaces
#element-attrdef-option-disabledReferenced in:
* 4.10.10. The option element (2)
* Elements
#element-attrdef-option-labelReferenced in:
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 4.10.5.3.9. The list attribute (2)
* 4.10.10. The option element (2) (3) (4) (5) (6) (7) (8) (9)
* Elements
* Changes between Working Draft 6 and Working Draft 5
* Changes between Working Draft 2 and the First Public Working Draft
#labelReferenced in:
* 4.7.13.11.2. Sourcing in-band text tracks (2)
* 4.10.5.3.9. The list attribute
* 4.10.8. The datalist element
* 4.10.10. The option element
* 4.11.3.4. Using the input element to define a command (2) (3)
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements
* 10.5.14. The select element
* Attributes
#element-attrdef-option-valueReferenced in:
* 4.10.5.3.9. The list attribute
* 4.10.10. The option element (2) (3) (4) (5)
* Elements
#element-attrdef-option-selectedReferenced in:
* 4.10.10. The option element (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.15.2. Pseudo-classes
* Elements
#statedef-option-dirtinessReferenced in:
* 4.10.7. The select element (2) (3) (4) (5) (6)
* 4.10.10. The option element (2) (3)
#statedef-option-selectednessReferenced in:
* 4.10.7. The select element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
* 4.10.10. The option element (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.10.17.1. A form control value
* 4.10.18.7.2. Processing model (2)
* 4.10.20.1. Definitions
* 4.10.21.4. Constructing the form data set
* 4.15.2. Pseudo-classes
* 10.5.14. The select element
#option-indexReferenced in:
* 4.10.7. The select element (2)
* 4.10.10. The option element
#dom-htmloptionelement-disabledReferenced in:
* 4.10.10. The option element
#dom-htmloptionelement-defaultselectedReferenced in:
* 4.10.10. The option element
#dom-htmloptionelement-labelReferenced in:
* 4.10.10. The option element
#dom-htmloptionelement-valueReferenced in:
* 4.10.10. The option element
#dom-htmloptionelement-selectedReferenced in:
* 4.10.10. The option element (2)
#dom-htmloptionelement-indexReferenced in:
* 4.10.10. The option element (2) (3)
#dom-htmloptionelement-textReferenced in:
* 4.10.10. The option element (2) (3) (4) (5)
#dom-htmloptionelement-optionReferenced in:
* 4.10.10. The option element (2) (3)
#elementdef-textareaReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 2.7.2.1. The HTMLAllCollection interface (2)
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content (2) (3)
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content
* 3.2.5.5. The dir attribute (2) (3)
* 3.2.6. The innerText IDL attribute
* 3.2.7.2. User agent conformance criteria
* 4.10.1.1. Writing a form’s user interface
* 4.10.1.4. Client-side form validation
* 4.10.1.6. The difference between the field type, the autofill field
name, and the input modality
* 4.10.2. Categories (2) (3) (4) (5) (6) (7)
* 4.10.11. The textarea element (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16) (17) (18) (19)
* 4.10.18.3. Limiting user input length: the maxlength attribute
* 4.10.18.5. Enabling and disabling form controls: the disabled
attribute
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5) (6) (7) (8) (9) (10)
* 4.10.18.7.2. Processing model (2)
* 4.10.19. APIs for text field selections (2) (3) (4) (5) (6) (7)
* 4.10.20.1. Definitions (2) (3)
* 4.10.21.4. Constructing the form data set (2)
* 4.14. Disabled elements
* 4.15.2. Pseudo-classes (2) (3) (4) (5)
* 5.4.3. The tabindex attribute
* 5.6.5. Spelling and grammar checking (2) (3)
* 5.7.5. Drag-and-drop processing model (2) (3) (4)
* 6.7.10.1. Persisted user state restoration
* 8.1.2. Elements
* 8.1.2.5. Restrictions on content models
* 8.2.3.2. The stack of open elements
* 8.2.5.4.7. The "in body" insertion mode
* 8.3. Serializing HTML fragments
* 8.4. Parsing HTML fragments
* 10.3.5. Bidirectional text
* 10.5.15. The textarea element (2) (3) (4) (5)
* 11.2. Non-conforming features (2)
* Elements
* Element content categories (2) (3) (4) (5) (6) (7) (8) (9) (10)
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14)
* Element Interfaces
* Changes between Working Draft 2 and the First Public Working Draft
#htmltextareaelementReferenced in:
* Elements
* Element Interfaces
#raw-valueReferenced in:
* 4.10.11. The textarea element (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12)
* 4.10.18.3. Limiting user input length: the maxlength attribute
* 4.10.19. APIs for text field selections
* 4.10.21.4. Constructing the form data set
#element-attrdef-textarea-readonlyReferenced in:
* 4.10.11. The textarea element (2) (3) (4)
* 4.15.2. Pseudo-classes
* Elements
#textarea-dirty-value-flagReferenced in:
* 4.10.11. The textarea element (2) (3) (4) (5)
#element-attrdef-textarea-colsReferenced in:
* 4.10.11. The textarea element
* Elements
#character-widthReferenced in:
* 4.10.11. The textarea element (2)
* 10.5.15. The textarea element
#element-attrdef-textarea-rowsReferenced in:
* 4.10.11. The textarea element (2)
* Elements
#character-heightReferenced in:
* 4.10.11. The textarea element
* 10.5.15. The textarea element
#element-attrdef-textarea-wrapReferenced in:
* 4.10.11. The textarea element
* 10.5.15. The textarea element
* Elements
#attr-valuedef-textarea-wrap-softReferenced in:
* Attributes
#attr-valuedef-textarea-wrap-hardReferenced in:
* Attributes
#statedef-textarea-softReferenced in:
* 4.10.11. The textarea element (2)
#statedef-textarea-hardReferenced in:
* 4.10.11. The textarea element (2) (3)
#api-valueReferenced in:
* 4.10.11. The textarea element (2) (3)
#textarea-wrapping-transformationReferenced in:
* 4.10.11. The textarea element (2)
* 4.10.18.3. Limiting user input length: the maxlength attribute
#element-attrdef-textarea-maxlengthReferenced in:
* 4.10.11. The textarea element (2)
* 4.10.20.1. Definitions
* Elements
#element-attrdef-textarea-minlengthReferenced in:
* 4.10.11. The textarea element (2)
* 4.10.20.1. Definitions
* Elements
#element-attrdef-textarea-requiredReferenced in:
* 4.10.11. The textarea element
* 4.10.20.1. Definitions
* 4.15.2. Pseudo-classes (2)
* Elements
#element-attrdef-textarea-placeholderReferenced in:
* 3.2.5.3. The translate attribute
* 3.2.5.5. The dir attribute
* 4.10.11. The textarea element
* Elements
#dom-htmltextareaelement-colsReferenced in:
* 4.10.11. The textarea element
* 10.5.15. The textarea element
#dom-htmltextareaelement-placeholderReferenced in:
* 4.10.11. The textarea element
#dom-htmltextareaelement-_requiredReferenced in:
* 4.10.11. The textarea element
#dom-htmltextareaelement-rowsReferenced in:
* 4.10.11. The textarea element
* 10.5.15. The textarea element
#dom-htmltextareaelement-wrapReferenced in:
* 4.10.11. The textarea element
#dom-htmltextareaelement-dirnameReferenced in:
* 4.10.11. The textarea element
#dom-htmltextareaelement-maxlengthReferenced in:
* 4.10.11. The textarea element
#dom-htmltextareaelement-minlengthReferenced in:
* 4.10.11. The textarea element
#dom-htmltextareaelement-readonlyReferenced in:
* 4.10.11. The textarea element
#dom-htmltextareaelement-typeReferenced in:
* 4.10.11. The textarea element
#dom-htmltextareaelement-defaultvalueReferenced in:
* 4.10.11. The textarea element
#dom-htmltextareaelement-valueReferenced in:
* 4.10.11. The textarea element
#dom-htmltextareaelement-textlengthReferenced in:
* 4.10.11. The textarea element
#elementdef-outputReferenced in:
* 1.9. A quick introduction to HTML
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.5.19. The samp element
* 4.10.2. Categories (2) (3) (4) (5) (6)
* 4.10.12. The output element (2) (3) (4) (5) (6)
* 5.1. The hidden attribute
* Elements
* Element content categories (2) (3) (4) (5) (6) (7) (8)
* Attributes (2) (3)
* Element Interfaces
#htmloutputelementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-output-forReferenced in:
* 4.10.12. The output element (2) (3)
* Elements
#value-mode-flagReferenced in:
* 4.10.12. The output element (2) (3) (4) (5) (6) (7)
#output-default-valueReferenced in:
* 4.10.12. The output element (2) (3) (4) (5) (6) (7)
#dom-htmloutputelement-valueReferenced in:
* 4.10.12. The output element
#dom-htmloutputelement-defaultvalueReferenced in:
* 4.10.12. The output element
#dom-htmloutputelement-typeReferenced in:
* 4.10.12. The output element
#dom-htmloutputelement-htmlforReferenced in:
* 4.10.12. The output element
#elementdef-progressReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.10.2. Categories (2)
* 4.10.13. The progress element (2) (3) (4) (5)
* 4.10.14. The meter element
* 4.15.2. Pseudo-classes
* 10.5.13. The progress element (2) (3)
* Elements
* Element content categories (2) (3) (4)
* Attributes (2)
* Element Interfaces
#htmlprogresselementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-progress-valueReferenced in:
* 4.10.13. The progress element (2) (3) (4) (5) (6) (7) (8) (9)
* 4.15.2. Pseudo-classes
* Elements
#element-attrdef-progress-maxReferenced in:
* 4.10.13. The progress element (2) (3) (4) (5) (6) (7) (8) (9) (10)
* Elements
#progress-maximum-valueReferenced in:
* 4.10.13. The progress element (2) (3) (4) (5) (6) (7)
#progress-current-valueReferenced in:
* 4.10.13. The progress element (2) (3) (4) (5) (6)
#dom-htmlprogresselement-positionReferenced in:
* 4.10.13. The progress element
#dom-htmlprogresselement-valueReferenced in:
* 4.10.13. The progress element (2)
#dom-htmlprogresselement-maxReferenced in:
* 4.10.13. The progress element
#elementdef-meterReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.8. Palpable content
* 4.10.2. Categories (2)
* 4.10.13. The progress element
* 4.10.14. The meter element (2) (3) (4) (5) (6) (7) (8)
* 10.5.12. The meter element (2) (3)
* Elements
* Element content categories (2) (3) (4)
* Attributes (2) (3) (4) (5) (6)
* Element Interfaces
#htmlmeterelementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-meter-minReferenced in:
* 4.10.14. The meter element (2) (3) (4) (5) (6)
* Elements
#element-attrdef-meter-maxReferenced in:
* 4.10.14. The meter element (2) (3) (4) (5) (6)
* Elements
* Attributes
#element-attrdef-meter-valueReferenced in:
* 4.10.14. The meter element (2) (3) (4) (5) (6) (7) (8)
* Elements
#element-attrdef-meter-lowReferenced in:
* 4.10.14. The meter element (2) (3) (4) (5)
* Elements
#element-attrdef-meter-highReferenced in:
* 4.10.14. The meter element (2) (3) (4) (5)
* Elements
#element-attrdef-meter-optimumReferenced in:
* 4.10.14. The meter element (2) (3) (4) (5)
* Elements
#meter-minimum-valueReferenced in:
* 4.10.14. The meter element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14)
#meter-maximum-valueReferenced in:
* 4.10.14. The meter element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19)
#meter-actual-valueReferenced in:
* 4.10.14. The meter element
#meter-low-boundaryReferenced in:
* 4.10.14. The meter element
#meter-high-boundaryReferenced in:
* 4.10.14. The meter element
#meter-optimum-valueReferenced in:
* 4.10.14. The meter element
#dom-htmlmeterelement-valueReferenced in:
* 4.10.14. The meter element
#dom-htmlmeterelement-minReferenced in:
* 4.10.14. The meter element
#dom-htmlmeterelement-maxReferenced in:
* 4.10.14. The meter element
#dom-htmlmeterelement-lowReferenced in:
* 4.10.14. The meter element
#dom-htmlmeterelement-highReferenced in:
* 4.10.14. The meter element
#dom-htmlmeterelement-optimumReferenced in:
* 4.10.14. The meter element
#elementdef-fieldsetReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.8. Palpable content
* 4.3.9. Headings and sections
* 4.4.1. The p element
* 4.4.15. The div element
* 4.10.1.1. Writing a form’s user interface (2)
* 4.10.2. Categories (2) (3) (4)
* 4.10.15. The fieldset element (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14)
* 4.10.16. The legend element (2) (3) (4) (5)
* 4.10.18.5. Enabling and disabling form controls: the disabled
attribute (2)
* 4.11.3.7. Using the accesskey attribute on a legend element to define
a command
* 4.14. Disabled elements
* 4.15.2. Pseudo-classes (2) (3)
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 10.3.13. The fieldset and legend elements (2) (3) (4) (5) (6)
* 11.2. Non-conforming features
* Elements (2) (3)
* Element content categories (2) (3) (4) (5) (6)
* Attributes (2) (3)
* Element Interfaces
#htmlfieldsetelementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-fieldset-disabledReferenced in:
* 4.10.15. The fieldset element (2) (3)
* Elements
#disabled-fieldsetReferenced in:
* 4.14. Disabled elements
* 4.15.2. Pseudo-classes
#dom-htmlfieldsetelement-disabledReferenced in:
* 4.10.15. The fieldset element
#dom-htmlfieldsetelement-typeReferenced in:
* 4.10.15. The fieldset element
#dom-htmlfieldsetelement-elementsReferenced in:
* 4.10.2. Categories
* 4.10.15. The fieldset element
#elementdef-legendReferenced in:
* 4.10.1.1. Writing a form’s user interface
* 4.10.15. The fieldset element (2) (3) (4)
* 4.10.16. The legend element (2) (3) (4)
* 4.10.18.5. Enabling and disabling form controls: the disabled
attribute
* 4.11.3.7. Using the accesskey attribute on a legend element to define
a command (2) (3) (4) (5) (6)
* 10.3.13. The fieldset and legend elements (2) (3) (4)
* 11.2. Non-conforming features (2) (3) (4)
* 11.3.4. Other elements, attributes and APIs
* Elements (2)
* Element Interfaces
* Changes between Working Draft 3 and Working Draft 2
#htmllegendelementReferenced in:
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#forms-valueReferenced in:
* 4.10.5. The input element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search) (2)
(3) (4) (5)
* 4.10.5.1.3. Telephone state (type=tel) (2) (3) (4) (5) (6)
* 4.10.5.1.4. URL state (type=url) (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.10.5.1.5. E-mail state (type=email) (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23)
* 4.10.5.1.6. Password state (type=password) (2) (3) (4) (5)
* 4.10.5.1.7. Date state (type=date) (2) (3) (4) (5) (6) (7) (8)
* 4.10.5.1.8. Month state (type=month) (2) (3) (4) (5) (6) (7) (8)
* 4.10.5.1.9. Week state (type=week) (2) (3) (4) (5) (6) (7) (8)
* 4.10.5.1.10. Time state (type=time) (2) (3) (4) (5) (6) (7) (8)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2) (3)
(4) (5) (6) (7) (8)
* 4.10.5.1.12. Number state (type=number) (2) (3) (4) (5) (6) (7) (8)
* 4.10.5.1.13. Range state (type=range) (2) (3) (4) (5) (6) (7) (8) (9)
(10)
* 4.10.5.1.14. Color state (type=color) (2) (3) (4) (5) (6) (7) (8)
* 4.10.5.3.2. The size attribute
* 4.10.5.3.4. The required attribute (2)
* 4.10.5.3.6. The pattern attribute (2) (3) (4) (5) (6)
* 4.10.5.3.7. The min and max attributes (2) (3) (4) (5) (6)
* 4.10.5.3.8. The step attribute (2) (3) (4)
* 4.10.5.3.9. The list attribute (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.10.5.3.10. The placeholder attribute
* 4.10.5.4. Common input element APIs (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21)
* 4.10.5.5. Common event behaviors (2) (3) (4) (5) (6) (7) (8)
* 4.10.6. The button element
* 4.10.7. The select element (2) (3) (4)
* 4.10.8. The datalist element (2)
* 4.10.10. The option element
* 4.10.11. The textarea element (2) (3) (4)
* 4.10.17.1. A form control value (2) (3) (4) (5)
* 4.10.17.2. Mutability
* 4.10.18.3. Limiting user input length: the maxlength attribute (2) (3)
(4)
* 4.10.18.4. Setting minimum input length requirements: the minlength
attribute (2) (3)
* 4.10.18.7.2. Processing model (2) (3)
* 4.10.19. APIs for text field selections
* 4.10.20.1. Definitions (2) (3) (4) (5) (6) (7) (8)
* 4.10.21.3. Form submission algorithm (2)
* 4.10.21.4. Constructing the form data set (2) (3) (4)
* 5.4.4. Processing model
* 5.6.5. Spelling and grammar checking (2)
* 8.2.5.1. Creating and inserting nodes
#forms-checkednessReferenced in:
* 2.7.2.2. The HTMLFormControlsCollection interface (2)
* 4.10.5. The input element (2) (3) (4) (5) (6) (7) (8)
* 4.10.5.1.15. Checkbox state (type=checkbox) (2) (3) (4) (5)
* 4.10.5.1.16. Radio Button state (type=radio) (2) (3) (4) (5) (6) (7)
(8) (9) (10)
* 4.10.5.4. Common input element APIs (2) (3) (4) (5)
* 4.10.17.2. Mutability
* 4.10.21.4. Constructing the form data set (2)
* 4.15.2. Pseudo-classes (2) (3)
* 8.2.5.1. Creating and inserting nodes
#mutableReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search) (2)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email) (2)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox) (2)
* 4.10.5.1.16. Radio Button state (type=radio) (2)
* 4.10.5.1.17. File Upload state (type=file) (2) (3)
* 4.10.5.1.18. Submit Button state (type=submit) (2)
* 4.10.5.1.19. Image Button state (type=image) (2) (3) (4)
* 4.10.5.1.20. Reset Button state (type=reset) (2)
* 4.10.5.1.21. Button state (type=button) (2)
* 4.10.5.3.3. The readonly attribute
* 4.10.5.3.4. The required attribute
* 4.10.7. The select element
* 4.10.11. The textarea element (2) (3) (4)
* 4.10.18.7.2. Processing model
* 4.15.2. Pseudo-classes
* 5.6.5. Spelling and grammar checking
#form-ownerReferenced in:
* 4.7.8. The object element
* 4.10.2. Categories (2)
* 4.10.3. The form element (2) (3) (4) (5)
* 4.10.5. The input element
* 4.10.5.1.16. Radio Button state (type=radio) (2) (3)
* 4.10.5.1.18. Submit Button state (type=submit) (2)
* 4.10.5.1.19. Image Button state (type=image) (2) (3) (4) (5)
* 4.10.5.1.20. Reset Button state (type=reset) (2)
* 4.10.6. The button element (2) (3) (4) (5)
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.15. The fieldset element
* 4.10.17.3. Association of controls and forms (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11)
* 4.10.18.6. Form submission (2) (3) (4) (5)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
* 4.10.18.7.2. Processing model (2) (3) (4) (5)
* 4.10.20.2. Constraint validation
* 4.10.21.2. Implicit submission (2)
* 4.10.21.4. Constructing the form data set
* 4.10.22. Resetting a form
* 4.15.2. Pseudo-classes (2)
* 7.1.5.1. Event handlers (2)
#element-attrdef-formelements-formReferenced in:
* 4.7.8. The object element
* 4.10.2. Categories (2)
* 4.10.5. The input element (2)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.12. The output element (2)
* 4.10.15. The fieldset element (2)
* 4.10.17.3. Association of controls and forms (2) (3) (4) (5) (6) (7)
* 8.2.5.1. Creating and inserting nodes
* Elements (2) (3) (4) (5) (6) (7)
#associatedReferenced in:
* 8.2.5.1. Creating and inserting nodes
#reset-the-form-ownerReferenced in:
* 4.10.17.3. Association of controls and forms (2) (3) (4) (5)
* 8.2.5.1. Creating and inserting nodes
#dom-formidlattribute-formReferenced in:
* 4.7.8. The object element (2)
* 4.10.2. Categories
* 4.10.4. The label element
* 4.10.5. The input element (2)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.10. The option element (2) (3) (4) (5)
* 4.10.11. The textarea element (2)
* 4.10.12. The output element (2)
* 4.10.15. The fieldset element (2)
* 4.10.16. The legend element (2) (3) (4) (5)
* 4.10.17.3. Association of controls and forms
#element-attrdef-formelements-nameReferenced in:
* 2.7.2.1. The HTMLAllCollection interface
* 4.10.1.1. Writing a form’s user interface
* 4.10.1.3. Configuring a form to communicate with a server
* 4.10.3. The form element (2) (3) (4) (5) (6)
* 4.10.4. The label element
* 4.10.5. The input element (2)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.16. Radio Button state (type=radio) (2) (3) (4) (5)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2) (3)
* 4.10.11. The textarea element (2)
* 4.10.12. The output element (2)
* 4.10.15. The fieldset element (2)
* 4.10.18.1. Naming form controls: the name attribute (2)
* 4.10.18.7.2. Processing model
* 4.10.21.4. Constructing the form data set (2) (3) (4)
* 8.1.2.3. Attributes
* Elements (2) (3) (4) (5) (6)
#dom-htmlinputelement-nameReferenced in:
* 4.10.5. The input element (2)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.12. The output element (2)
* 4.10.15. The fieldset element (2)
#element-attrdef-input-dirnameReferenced in:
* 4.10.5. The input element (2) (3) (4) (5)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.11. The textarea element (2) (3)
* Elements (2)
#form-control-maxlength-attributeReferenced in:
* 4.10.5.3.1. The maxlength and minlength attributes
* 4.10.11. The textarea element
* 4.10.18.3. Limiting user input length: the maxlength attribute
* 4.10.20.1. Definitions
#maximum-allowed-value-lengthReferenced in:
* 4.10.5.3.1. The maxlength and minlength attributes (2)
* 4.10.11. The textarea element (2)
* 4.10.18.3. Limiting user input length: the maxlength attribute (2) (3)
(4) (5)
* 4.10.18.4. Setting minimum input length requirements: the minlength
attribute (2)
#form-control-minlength-attributeReferenced in:
* 4.10.5.3.1. The maxlength and minlength attributes
* 4.10.11. The textarea element
* 4.10.18.4. Setting minimum input length requirements: the minlength
attribute
* 4.10.20.1. Definitions
#minimum-allowed-value-lengthReferenced in:
* 4.10.18.4. Setting minimum input length requirements: the minlength
attribute (2) (3) (4) (5)
#element-attrdef-disabledformelements-disabledReferenced in:
* 1.10.3. Restrictions on content models and on attribute values
* 4.10.5. The input element (2)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.18.5. Enabling and disabling form controls: the disabled
attribute
* 8.1.2.3. Attributes
* Elements (2) (3) (4)
#dom-htmlinputelement-disabledReferenced in:
* 4.10.5. The input element (2)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
#forms-attributes-for-form-submissionReferenced in:
* 4.10.3. The form element
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.6. The button element
* 4.10.18.6. Form submission (2)
#element-attrdef-form-actionReferenced in:
* 4.10.1.3. Configuring a form to communicate with a server
* 4.10.3. The form element (2)
* 4.10.18.6. Form submission (2)
* 4.10.21.1. Introduction
* Elements
* Attributes
#element-attrdef-submitbuttonelements-formactionReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit) (2)
* 4.10.5.1.19. Image Button state (type=image) (2)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.6. The button element (2) (3)
* 4.10.18.6. Form submission (2) (3)
* Elements (2)
#actionReferenced in:
* 4.10.21.3. Form submission algorithm
* 4.11.3.5. Using the option element to define a command
* 5.5.3. Processing model
#element-attrdef-form-methodReferenced in:
* 4.10.1.3. Configuring a form to communicate with a server
* 4.10.3. The form element (2)
* 4.10.18.6. Form submission (2) (3) (4) (5) (6)
* Elements
* Attributes
#element-attrdef-submitbuttonelements-formmethodReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit) (2)
* 4.10.5.1.19. Image Button state (type=image) (2)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.6. The button element (2) (3)
* 4.10.18.6. Form submission (2) (3) (4)
* Elements (2)
#attr-valuedef-form-method-getReferenced in:
* 4.10.18.6. Form submission
* Attributes
#http-getReferenced in:
* 4.10.18.6. Form submission (2)
* 4.10.21.3. Form submission algorithm
#attr-valuedef-form-method-postReferenced in:
* 4.10.18.6. Form submission
* Attributes
#http-postReferenced in:
* 4.10.21.3. Form submission algorithm
#attr-valuedef-form-method-dialogReferenced in:
* 4.10.18.6. Form submission
* Attributes
#state-dialogReferenced in:
* 4.10.21.3. Form submission algorithm
* Events
#forms-methodReferenced in:
* 4.10.18.6. Form submission
* 4.10.21.1. Introduction
* 4.10.21.3. Form submission algorithm
#element-attrdef-form-enctypeReferenced in:
* 4.10.1.3. Configuring a form to communicate with a server
* 4.10.3. The form element (2) (3)
* 4.10.18.6. Form submission (2) (3) (4)
* Elements
* Attributes
#element-attrdef-submitbuttonelements-formenctypeReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit) (2)
* 4.10.5.1.19. Image Button state (type=image) (2)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.6. The button element (2) (3)
* 4.10.18.6. Form submission (2) (3) (4)
* Elements (2)
#enctypeReferenced in:
* 4.10.18.6. Form submission
* 4.10.21.1. Introduction
* 4.10.21.3. Form submission algorithm
#element-attrdef-form-targetReferenced in:
* 4.10.3. The form element (2)
* 4.10.18.6. Form submission (2) (3) (4) (5)
* Elements
* Attributes
#element-attrdef-submitbuttonelements-formtargetReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit) (2)
* 4.10.5.1.19. Image Button state (type=image) (2)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.6. The button element (2) (3)
* 4.10.18.6. Form submission (2) (3)
* Elements (2)
#element-attrdef-form-novalidateReferenced in:
* 4.10.3. The form element (2)
* 4.10.18.6. Form submission (2) (3)
* Elements
* Attributes
#element-attrdef-submitbuttonelements-formnovalidateReferenced in:
* 4.10.5. The input element (2) (3)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit) (2) (3)
* 4.10.5.1.19. Image Button state (type=image) (2)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.6. The button element (2) (3) (4)
* 4.10.18.6. Form submission (2) (3)
* Elements (2)
#no-validate-stateReferenced in:
* 4.10.21.3. Form submission algorithm
#dom-htmlformelement-actionReferenced in:
* 4.10.3. The form element
#dom-htmlformelement-targetReferenced in:
* 4.10.3. The form element
#dom-htmlformelement-methodReferenced in:
* 4.10.3. The form element
#dom-htmlformelement-enctypeReferenced in:
* 4.10.3. The form element
#dom-htmlformelement-encodingReferenced in:
* 4.10.3. The form element
#dom-htmlformelement-novalidateReferenced in:
* 4.10.3. The form element
#dom-htmlinputelement-formactionReferenced in:
* 4.10.5. The input element
* 4.10.6. The button element
#dom-htmlinputelement-formenctypeReferenced in:
* 4.10.5. The input element
* 4.10.6. The button element
#dom-htmlinputelement-formmethodReferenced in:
* 4.10.5. The input element
* 4.10.6. The button element
#dom-htmlinputelement-formnovalidateReferenced in:
* 4.10.5. The input element
* 4.10.6. The button element
#dom-htmlinputelement-formtargetReferenced in:
* 4.10.5. The input element
* 4.10.6. The button element
#element-attrdef-formelements-autofocusReferenced in:
* 4.10.5. The input element (2)
* 4.10.5.3.10. The placeholder attribute
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute (2)
(3) (4) (5) (6)
* 4.11.4. The dialog element (2)
* 6.5. Sandboxing
* Elements (2) (3) (4)
* Attributes
#nearest-ancestor-autofocus-scoping-document-elementReferenced in:
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute
#dom-htmlinputelement-autofocusReferenced in:
* 4.10.5. The input element (2)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
#element-attrdef-autocompleteelements-autocompleteReferenced in:
* 4.10.1.5. Enabling client-side automatic filling of form controls
* 4.10.1.6. The difference between the field type, the autofill field
name, and the input modality (2) (3) (4)
* 4.10.3. The form element (2)
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5) (6) (7)
* 4.10.18.7.2. Processing model (2) (3) (4) (5) (6)
* Elements (2) (3)
* Attributes (2)
#autofill-expectation-mantleReferenced in:
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3)
* 4.10.18.7.2. Processing model
#autofill-anchor-mantleReferenced in:
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3)
* 4.10.18.7.2. Processing model (2) (3) (4)
#autofill-detail-tokensReferenced in:
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
#attr-valuedef-forms-autocomplete-offReferenced in:
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute
* 4.10.18.7.2. Processing model (2) (3) (4)
#attr-valuedef-forms-autocomplete-onReferenced in:
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute
* 4.10.18.7.2. Processing model
#autofill-fieldReferenced in:
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4) (5) (6) (7)
* 4.10.18.7.2. Processing model
* Attributes
#inappropriate-for-the-controlReferenced in:
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
#administrative-levelReferenced in:
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute (2)
(3) (4)
#autofill-hint-setReferenced in:
* 4.10.18.7.2. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11)
#autofill-scopeReferenced in:
* 4.10.18.7.2. Processing model (2) (3) (4) (5) (6) (7) (8) (9)
#autofill-field-nameReferenced in:
* 4.10.3. The form element (2)
* 4.10.18.7.2. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24)
(25)
* 6.7.10. History traversal
#idl-exposed-autofill-valueReferenced in:
* 4.10.18.7.2. Processing model (2) (3) (4) (5)
#controls-dataReferenced in:
* 4.10.18.7.2. Processing model (2) (3) (4)
#derived-from-country-in-some-casesReferenced in:
* 4.10.18.7.1. Autofilling form controls: the autocomplete attribute
#dom-htmlinputelement-autocompleteReferenced in:
* 4.10.5. The input element
* 4.10.7. The select element
* 4.10.11. The textarea element
#enumdef-selectionmodeReferenced in:
* 4.10.5. The input element
* 4.10.11. The textarea element
#dom-selectionapielements-selectReferenced in:
* 4.10.5. The input element (2) (3) (4) (5)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email) (2)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.11. The textarea element (2)
* 4.10.19. APIs for text field selections (2)
#dom-selectionapielements-selectionstartReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.11. The textarea element (2)
* 4.10.19. APIs for text field selections (2) (3) (4) (5) (6)
#dom-selectionapielements-selectionendReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.11. The textarea element (2)
* 4.10.19. APIs for text field selections (2) (3) (4) (5) (6) (7)
#dom-selectionapielements-selectiondirectionReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.11. The textarea element (2)
* 4.10.19. APIs for text field selections (2) (3) (4)
#dom-selectionapielements-setselectionrangeReferenced in:
* 4.10.5. The input element (2) (3) (4)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.11. The textarea element (2)
* 4.10.19. APIs for text field selections (2) (3) (4)
#dom-selectionapielements-setrangetextReferenced in:
* 4.10.5. The input element (2) (3) (4) (5)
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email)
* 4.10.5.1.6. Password state (type=password)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.11. The textarea element (2) (3)
* 4.10.19. APIs for text field selections (2)
#dom-selectionmode-selectReferenced in:
* 4.10.19. APIs for text field selections
#dom-selectionmode-startReferenced in:
* 4.10.19. APIs for text field selections
#dom-selectionmode-endReferenced in:
* 4.10.19. APIs for text field selections
#dom-selectionmode-preserveReferenced in:
* 4.10.19. APIs for text field selections
#candidates-for-constraint-validationReferenced in:
* 4.10.20.2. Constraint validation
* 4.10.20.3. The constraint validation API (2) (3) (4) (5)
* 4.15.2. Pseudo-classes (2) (3) (4) (5) (6) (7) (8)
#barred-from-constraint-validationReferenced in:
* 4.7.8. The object element
* 4.10.5.1.1. Hidden state (type=hidden)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.5.1.21. Button state (type=button)
* 4.10.5.3.3. The readonly attribute
* 4.10.8. The datalist element
* 4.10.11. The textarea element
* 4.10.18.5. Enabling and disabling form controls: the disabled
attribute
* 4.10.20.1. Definitions
* 4.10.20.3. The constraint validation API
#custom-validity-error-messageReferenced in:
* 4.10.20.1. Definitions (2) (3)
* 4.10.20.3. The constraint validation API (2)
#validity-statesReferenced in:
* 4.10.20.1. Definitions
* 4.10.20.3. The constraint validation API
#suffer-from-being-missingReferenced in:
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
* 4.10.5.1.17. File Upload state (type=file)
* 4.10.5.3.4. The required attribute
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.10.20.3. The constraint validation API
#suffer-from-a-type-mismatchReferenced in:
* 4.10.5.1.4. URL state (type=url)
* 4.10.5.1.5. E-mail state (type=email) (2)
* 4.10.18.7.2. Processing model
* 4.10.20.3. The constraint validation API
#suffer-from-a-pattern-mismatchReferenced in:
* 4.10.5.3.6. The pattern attribute (2)
* 4.10.18.7.2. Processing model
* 4.10.20.3. The constraint validation API
#suffer-from-being-too-longReferenced in:
* 4.10.18.3. Limiting user input length: the maxlength attribute
* 4.10.18.7.2. Processing model
* 4.10.20.3. The constraint validation API
#suffer-from-being-too-shortReferenced in:
* 4.10.18.4. Setting minimum input length requirements: the minlength
attribute
* 4.10.18.7.2. Processing model
* 4.10.20.3. The constraint validation API
#suffer-from-an-underflowReferenced in:
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.3.7. The min and max attributes (2) (3) (4)
* 4.10.18.7.2. Processing model
* 4.10.20.3. The constraint validation API
* 4.15.2. Pseudo-classes (2)
#suffer-from-an-overflowReferenced in:
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.3.7. The min and max attributes (2) (3) (4)
* 4.10.18.7.2. Processing model
* 4.10.20.3. The constraint validation API
* 4.15.2. Pseudo-classes (2)
#suffer-from-a-step-mismatchReferenced in:
* 4.10.5.1.7. Date state (type=date) (2)
* 4.10.5.1.8. Month state (type=month) (2)
* 4.10.5.1.9. Week state (type=week) (2)
* 4.10.5.1.10. Time state (type=time) (2)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local) (2)
* 4.10.5.1.12. Number state (type=number) (2)
* 4.10.5.1.13. Range state (type=range) (2)
* 4.10.5.3.8. The step attribute (2)
* 4.10.5.4. Common input element APIs
* 4.10.18.7.2. Processing model
* 4.10.20.3. The constraint validation API
#suffer-from-bad-inputReferenced in:
* 4.10.5.1.5. E-mail state (type=email) (2)
* 4.10.5.1.7. Date state (type=date)
* 4.10.5.1.8. Month state (type=month)
* 4.10.5.1.9. Week state (type=week)
* 4.10.5.1.10. Time state (type=time)
* 4.10.5.1.11. Local Date and Time state (type=datetime-local)
* 4.10.5.1.12. Number state (type=number)
* 4.10.5.1.13. Range state (type=range)
* 4.10.5.1.14. Color state (type=color)
* 4.10.20.3. The constraint validation API
#suffer-from-a-custom-errorReferenced in:
* 4.10.20.1. Definitions
* 4.10.20.3. The constraint validation API (2)
#satisfy-its-constraintsReferenced in:
* 4.10.20.2. Constraint validation
* 4.10.20.3. The constraint validation API (2) (3)
* 4.15.2. Pseudo-classes (2) (3) (4) (5) (6)
#statically-validating-the-constraintsReferenced in:
* 4.10.3. The form element
* 4.10.20.2. Constraint validation
#interactively-validate-the-constraintsReferenced in:
* 4.10.3. The form element
* 4.10.21.3. Form submission algorithm
#constraint-validation-apiReferenced in:
* 4.7.8. The object element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.15. The fieldset element
#dom-htmlinputelement-willvalidateReferenced in:
* 4.10.5. The input element (2)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.12. The output element (2)
* 4.10.15. The fieldset element (2)
#dom-htmlinputelement-setcustomvalidityReferenced in:
* 4.10.5. The input element (2)
* 4.10.5.1.3. Telephone state (type=tel)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.12. The output element (2)
* 4.10.15. The fieldset element (2)
* 4.10.20.1. Definitions (2)
* 4.10.20.3. The constraint validation API (2)
#dom-htmlinputelement-validityReferenced in:
* 4.10.5. The input element (2)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.12. The output element (2)
* 4.10.15. The fieldset element (2)
#validitystateReferenced in:
* 4.7.8. The object element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.7. The select element
* 4.10.11. The textarea element
* 4.10.12. The output element
* 4.10.15. The fieldset element
* 4.10.20.3. The constraint validation API (2)
#dom-validitystate-valuemissingReferenced in:
* 4.10.20.3. The constraint validation API
#dom-validitystate-typemismatchReferenced in:
* 4.10.20.3. The constraint validation API
#dom-validitystate-patternmismatchReferenced in:
* 4.10.20.3. The constraint validation API
#dom-validitystate-toolongReferenced in:
* 4.10.20.3. The constraint validation API
#dom-validitystate-tooshortReferenced in:
* 4.10.20.3. The constraint validation API
#dom-validitystate-rangeunderflowReferenced in:
* 4.10.20.3. The constraint validation API
#dom-validitystate-rangeoverflowReferenced in:
* 4.10.20.3. The constraint validation API
#dom-validitystate-stepmismatchReferenced in:
* 4.10.20.3. The constraint validation API
#dom-validitystate-badinputReferenced in:
* 4.10.20.3. The constraint validation API
#dom-validitystate-customerrorReferenced in:
* 4.10.20.3. The constraint validation API
#dom-validitystate-validReferenced in:
* 4.10.20.3. The constraint validation API
#dom-htmlinputelement-checkvalidityReferenced in:
* 4.10.5. The input element (2)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.12. The output element (2)
* 4.10.15. The fieldset element (2)
#dom-htmlinputelement-reportvalidityReferenced in:
* 4.10.5. The input element (2)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.12. The output element (2)
* 4.10.15. The fieldset element (2)
#dom-htmlinputelement-validationmessageReferenced in:
* 4.10.5. The input element (2)
* 4.10.6. The button element (2)
* 4.10.7. The select element (2)
* 4.10.11. The textarea element (2)
* 4.10.12. The output element (2)
* 4.10.15. The fieldset element (2)
#form-submissionReferenced in:
* 4.10.1.3. Configuring a form to communicate with a server
* 4.10.5. The input element (2)
* 4.10.5.2. Implementation notes regarding localization of form controls
* 4.10.6. The button element (2) (3)
* 4.10.11. The textarea element
* 4.10.21.4. Constructing the form data set (2)
* 4.10.21.5. Selecting a form submission encoding
* 4.10.21.7. Multipart form data
* 6.1.5. Browsing context names
* 6.7.1. Navigating across documents
* 6.7.10. History traversal
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14)
(15) (16) (17)
#default-buttonReferenced in:
* 4.10.21.2. Implicit submission (2) (3)
* 4.15.2. Pseudo-classes (2)
#submitReferenced in:
* 4.10.2. Categories
* 4.10.3. The form element
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image) (2)
* 4.10.6. The button element
* 4.10.21.2. Implicit submission
* 4.10.21.3. Form submission algorithm
* 6.5. Sandboxing
* 6.7.1. Navigating across documents
* Events
#planned-navigationReferenced in:
* 4.10.21.3. Form submission algorithm (2) (3) (4) (5) (6)
#plan-to-navigateReferenced in:
* 4.10.21.3. Form submission algorithm (2) (3) (4) (5) (6)
#mutate-action-urlReferenced in:
* 4.10.21.3. Form submission algorithm (2)
#submit-as-entity-bodyReferenced in:
* 4.10.21.3. Form submission algorithm (2)
#get-action-urlReferenced in:
* 4.10.21.3. Form submission algorithm (2) (3) (4) (5)
#post-to-dataReferenced in:
* 4.10.21.3. Form submission algorithm
#mail-with-headersReferenced in:
* 4.10.21.3. Form submission algorithm
#mail-as-bodyReferenced in:
* 4.10.21.3. Form submission algorithm
#submit-dialogReferenced in:
* 4.10.21.3. Form submission algorithm
#appropriate-form-encoding-algorithmReferenced in:
* 4.10.21.3. Form submission algorithm (2) (3)
#constructing-the-form-data-setReferenced in:
* 4.10.2. Categories
* 4.10.21.3. Form submission algorithm
#during-form-submissionReferenced in:
* 4.10.5.1.19. Image Button state (type=image)
#picking-an-encoding-for-the-formReferenced in:
* 4.10.21.6. URL-encoded form data
* 4.10.21.7. Multipart form data
* 4.10.21.8. Plain text form data
#application-x-www-form-urlencoded-encoding-algorithmReferenced in:
* 4.10.21.3. Form submission algorithm (2) (3)
#multipart-form-data-encoding-algorithmReferenced in:
* 4.10.21.3. Form submission algorithm (2)
#multipart-form-data-boundary-stringReferenced in:
* 4.10.21.3. Form submission algorithm
#text-plain-encoding-algorithmReferenced in:
* 4.10.21.3. Form submission algorithm
#resetReferenced in:
* 4.10.2. Categories
* 4.10.3. The form element
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.6. The button element
* 4.10.22. Resetting a form (2)
* Events
#reset-algorithmReferenced in:
* 4.10.5. The input element
* 4.10.7. The select element
* 4.10.11. The textarea element (2)
* 4.10.12. The output element
* 4.10.22. Resetting a form
* 6.7.10. History traversal
* 8.2.5.1. Creating and inserting nodes
#elementdef-detailsReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.7. Interactive content
* 3.2.4.2.8. Palpable content
* 4.3.9. Headings and sections
* 4.4.1. The p element
* 4.7.5.1.4. Graphical Representations: Charts, diagrams, graphs, maps,
illustrations
* 4.11.1. The details element (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.11.2. The summary element (2) (3)
* 4.12. Scripting
* 5.4.2. Data model
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 10.5.3. The details and summary elements (2) (3) (4)
* Elements (2) (3)
* Element content categories (2) (3) (4)
* Attributes
* Element Interfaces
* Events (2)
* Changes between Working Draft 6 and Working Draft 5 (2) (3)
#htmldetailselementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-details-openReferenced in:
* 4.11.1. The details element
* 10.5.3. The details and summary elements
* Elements
#details-notification-task-stepsReferenced in:
* 4.11.1. The details element
* 4.11.2. The summary element
#dom-htmldetailselement-openReferenced in:
* 4.11.1. The details element
#elementdef-summaryReferenced in:
* 4.7.5.1.4. Graphical Representations: Charts, diagrams, graphs, maps,
illustrations
* 4.11.1. The details element (2)
* 4.11.2. The summary element
* 8.2.3.2. The stack of open elements
* 10.5.3. The details and summary elements (2) (3)
* Elements (2)
* Element Interfaces
* Changes between Working Draft 6 and Working Draft 5 (2) (3) (4)
#defines-a-commandReferenced in:
* 4.11.3.1. Facets
* 5.2. Inert subtrees
#facet-labelReferenced in:
* 4.11.3.2. Using the a element to define a command
* 4.11.3.3. Using the button element to define a command
* 4.11.3.4. Using the input element to define a command (2)
* 4.11.3.5. Using the option element to define a command
* 4.11.3.6. Using the accesskey attribute on a label element to define a
command
* 4.11.3.7. Using the accesskey attribute on a legend element to define
a command
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements (2)
#facet-access-keyReferenced in:
* 4.11.3.1. Facets
* 4.11.3.2. Using the a element to define a command
* 4.11.3.3. Using the button element to define a command
* 4.11.3.4. Using the input element to define a command
* 4.11.3.5. Using the option element to define a command
* 4.11.3.6. Using the accesskey attribute on a label element to define a
command
* 4.11.3.7. Using the accesskey attribute on a legend element to define
a command
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements
#facet-hidden-stateReferenced in:
* 4.11.3.1. Facets
* 4.11.3.2. Using the a element to define a command
* 4.11.3.3. Using the button element to define a command
* 4.11.3.4. Using the input element to define a command
* 4.11.3.5. Using the option element to define a command
* 4.11.3.6. Using the accesskey attribute on a label element to define a
command
* 4.11.3.7. Using the accesskey attribute on a legend element to define
a command
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements
* 5.5.3. Processing model
#facet-disabled-stateReferenced in:
* 4.11.3.2. Using the a element to define a command
* 4.11.3.3. Using the button element to define a command
* 4.11.3.4. Using the input element to define a command
* 4.11.3.5. Using the option element to define a command
* 4.11.3.6. Using the accesskey attribute on a label element to define a
command
* 4.11.3.7. Using the accesskey attribute on a legend element to define
a command
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements
* 5.5.3. Processing model
#facet-actionReferenced in:
* 4.11.3.2. Using the a element to define a command
* 4.11.3.3. Using the button element to define a command
* 4.11.3.4. Using the input element to define a command
* 4.11.3.5. Using the option element to define a command
* 4.11.3.6. Using the accesskey attribute on a label element to define a
command
* 4.11.3.7. Using the accesskey attribute on a legend element to define
a command
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements
#elementdef-dialogReferenced in:
* 2.2.2. Dependencies
* 3.2.4.2.2. Flow content
* 4.3.9. Headings and sections
* 4.10.18.6. Form submission
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute (2)
(3)
* 4.10.21.3. Form submission algorithm
* 4.11.4. The dialog element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24)
* 5.2. Inert subtrees (2)
* 5.4.2. Data model (2) (3) (4) (5)
* 5.4.4. Processing model (2) (3) (4)
* Elements
* Element content categories (2)
* Attributes
* Element Interfaces
* Events (2) (3)
* Changes since HTML 5.1 - Note that these may change if the HTML 5.1
specification is updated.
#htmldialogelementReferenced in:
* Elements
* Element Interfaces
#element-attrdef-dialog-openReferenced in:
* Elements
#dom-htmldialogelement-showReferenced in:
* 4.11.4. The dialog element
#pending-dialog-stackReferenced in:
* 4.11.4. The dialog element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14)
#modal-dialog-is-shownReferenced in:
* 5.4.4. Processing model
#dom-htmldialogelement-showmodalReferenced in:
* 4.11.4. The dialog element
#dialog-focusing-stepsReferenced in:
* 4.11.4. The dialog element (2)
#dom-htmldialogelement-closeReferenced in:
* 4.11.4. The dialog element
#close-the-dialogReferenced in:
* 4.10.21.3. Form submission algorithm
* 4.11.4. The dialog element (2)
#dom-htmldialogelement-returnvalueReferenced in:
* 4.11.4. The dialog element (2) (3)
#normal-alignmentReferenced in:
* 4.11.4. The dialog element (2) (3)
#centered-alignmentReferenced in:
* 4.11.4. The dialog element (2) (3) (4) (5) (6) (7)
#magically-alignedReferenced in:
* 4.11.4. The dialog element (2) (3)
#set-up-the-positionReferenced in:
* 4.11.4. The dialog element (2) (3)
#absolute-anchoredReferenced in:
* 4.11.4. The dialog element (2) (3) (4)
#dom-htmldialogelement-openReferenced in:
* 4.11.4. The dialog element
#propdef-anchor-pointReferenced in:
* 4.11.4. The dialog element (2) (3) (4) (5) (6) (7)
* 4.11.4.1. Anchor points
#valdef-anchor-point-noneReferenced in:
* 4.11.4. The dialog element (2) (3) (4) (5)
#elementdef-scriptReferenced in:
* 1.5.3. Extensibility
* 1.9. A quick introduction to HTML
* 1.9.1. Writing secure applications with HTML
* 1.10.3. Restrictions on content models and on attribute values (2)
* 2.2.1. Conformance classes (2) (3)
* 3.1.3. DOM tree accessors (2) (3) (4) (5) (6)
* 3.2.4.2.1. Metadata content
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.9. Script-supporting elements
* 3.2.5.5. The dir attribute
* 4.2.5. The meta element
* 4.3.1. The body element
* 4.10.10. The option element (2) (3)
* 4.12.1. The script element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13)
* 4.12.1.1. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27) (28) (29) (30) (31) (32) (33) (34) (35) (36) (37) (38) (39)
(40) (41) (42) (43) (44) (45) (46) (47) (48) (49) (50) (51) (52) (53)
(54) (55)
* 4.12.1.3. Restrictions for contents of script elements (2) (3) (4) (5)
(6) (7)
* 4.12.1.4. Inline documentation for external scripts (2) (3)
* 4.12.1.5. Interaction of script elements and XSLT (2) (3) (4) (5) (6)
* 4.12.2. The noscript element (2)
* 7.1.1. Introduction
* 7.1.3.1. Definitions
* 7.1.3.2. Fetching scripts
* 7.1.3.5.2. Incumbent
* 7.1.3.8. Integration with the JavaScript module system (2)
* 7.1.3.9. Runtime script errors (2)
* 7.4.3. document.write()
* 8.1.2. Elements
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 8.2.3.5. Other parsing state flags
* 8.2.4. Tokenization
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.8. The "text" insertion mode (2) (3)
* 8.2.6. The end (2) (3)
* 8.2.8.4. Scripts that modify the page as it is being parsed (2) (3)
(4) (5)
* 8.2.8.5. The execution of scripts that are moving across multiple
documents (2) (3)
* 8.3. Serializing HTML fragments (2) (3) (4)
* 8.4. Parsing HTML fragments
* 9.2. Parsing XML documents (2)
* 11.1. Obsolete but conforming features
* 11.1.1. Warnings for obsolete but conforming features
* 11.2. Non-conforming features (2) (3)
* 11.3.4. Other elements, attributes and APIs (2)
* Elements
* Element content categories (2) (3) (4)
* Attributes (2) (3) (4) (5) (6) (7)
* Element Interfaces
* Events (2) (3) (4)
#htmlscriptelementReferenced in:
* 2.2.1. Conformance classes
* 3.1.1. The Document object
* 11.3.4. Other elements, attributes and APIs
* Elements
* Element Interfaces
#element-attrdef-script-typeReferenced in:
* 4.12.1. The script element (2) (3) (4) (5) (6)
* 4.12.1.1. Processing model (2) (3) (4) (5) (6)
* 7.1.3.8. Integration with the JavaScript module system
* 11.1. Obsolete but conforming features (2)
* 11.1.1. Warnings for obsolete but conforming features
* Elements
#data-blockReferenced in:
* 4.12.1. The script element (2) (3) (4) (5)
#element-attrdef-script-srcReferenced in:
* 1.10.3. Restrictions on content models and on attribute values (2)
* 4.12.1. The script element (2) (3) (4) (5)
* 4.12.1.1. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13)
* 4.12.1.4. Inline documentation for external scripts (2)
* 8.2.8.5. The execution of scripts that are moving across multiple
documents (2)
* Elements
#element-attrdef-script-charsetReferenced in:
* 4.12.1. The script element (2) (3) (4) (5)
* 4.12.1.1. Processing model (2) (3)
* Elements
#element-attrdef-script-asyncReferenced in:
* 4.12.1. The script element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12)
* 4.12.1.1. Processing model (2) (3) (4) (5) (6) (7) (8)
* 4.12.1.5. Interaction of script elements and XSLT (2)
* Elements
* Attributes
#element-attrdef-script-deferReferenced in:
* 4.12.1. The script element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.12.1.1. Processing model (2) (3) (4) (5)
* 4.12.1.5. Interaction of script elements and XSLT
* Elements
#element-attrdef-script-crossoriginReferenced in:
* 4.12.1. The script element (2) (3) (4)
* 4.12.1.1. Processing model (2) (3)
* Elements
#element-attrdef-script-nonceReferenced in:
* 4.12.1. The script element (2) (3)
* 4.12.1.1. Processing model
* Elements
#dom-htmlscriptelement-srcReferenced in:
* 4.12.1. The script element
#dom-htmlscriptelement-typeReferenced in:
* 4.12.1. The script element
#dom-htmlscriptelement-charsetReferenced in:
* 4.12.1. The script element
#dom-htmlscriptelement-deferReferenced in:
* 4.12.1. The script element
#dom-htmlscriptelement-nonceReferenced in:
* 4.12.1. The script element
#dom-htmlscriptelement-crossoriginReferenced in:
* 4.12.1. The script element
#dom-htmlscriptelement-asyncReferenced in:
* 4.12.1. The script element (2)
* 4.12.1.5. Interaction of script elements and XSLT
#dom-htmlscriptelement-textReferenced in:
* 4.12.1. The script element (2)
* 4.12.1.1. Processing model
* 4.12.1.4. Inline documentation for external scripts
#already-startedReferenced in:
* 4.12.1.1. Processing model (2)
* 4.12.1.5. Interaction of script elements and XSLT (2)
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.8. The "text" insertion mode
* 9.2. Parsing XML documents
#parser-insertedReferenced in:
* 4.12.1.1. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12)
* 4.12.1.5. Interaction of script elements and XSLT (2) (3)
* 8.2.5.4.4. The "in head" insertion mode
* 9.2. Parsing XML documents
#non-blockingReferenced in:
* 4.12.1. The script element (2) (3)
* 4.12.1.1. Processing model (2) (3) (4) (5) (6)
* 8.2.5.4.4. The "in head" insertion mode
* 9.2. Parsing XML documents
#ready-to-be-parser-executedReferenced in:
* 4.12.1.1. Processing model (2) (3)
* 8.2.5.4.8. The "text" insertion mode (2)
* 8.2.6. The end
* 9.2. Parsing XML documents
#the-scripts-typeReferenced in:
* 4.12.1.1. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15)
#from-an-external-fileReferenced in:
* 4.12.1.1. Processing model (2) (3)
#the-scripts-scriptReferenced in:
* 4.12.1.1. Processing model (2) (3) (4) (5) (6) (7)
#the-script-is-readyReferenced in:
* 4.12.1.1. Processing model (2) (3) (4) (5) (6) (7) (8) (9)
#prepare-a-scriptReferenced in:
* 4.12.1.1. Processing model (2) (3) (4) (5) (6)
* 4.12.1.5. Interaction of script elements and XSLT
#list-of-scripts-that-will-execute-when-the-document-has-finished-parsingReferenced
in:
* 8.2.6. The end (2) (3) (4) (5)
#list-of-scripts-that-will-execute-in-order-as-soon-as-possibleReferenced
in:
* 4.12.1.1. Processing model (2) (3) (4)
* 8.2.6. The end
#set-of-scripts-that-will-execute-as-soon-as-possibleReferenced in:
* 4.12.1.1. Processing model
* 8.2.6. The end
#pending-parsing-blocking-scriptReferenced in:
* 4.12.1.1. Processing model (2) (3)
* 7.4.2. Closing the input stream
* 7.4.3. document.write()
* 8.2.5.4.8. The "text" insertion mode (2) (3) (4)
* 9.2. Parsing XML documents (2) (3) (4)
#execute-a-script-blockReferenced in:
* 4.12.1.1. Processing model (2) (3)
* 8.2.5.4.8. The "text" insertion mode
* 8.2.6. The end
* 9.2. Parsing XML documents
#javascript-mime-typeReferenced in:
* 4.12.1. The script element (2) (3)
* 4.12.1.1. Processing model
* 4.12.1.2. Scripting languages
* 6.7.1. Navigating across documents
* 7.1.3.2. Fetching scripts
#script-content-restrictionsReferenced in:
* 4.12.1. The script element (2)
#script-documentationReferenced in:
* 4.12.1. The script element
* 4.12.1.3. Restrictions for contents of script elements
#elementdef-noscriptReferenced in:
* 1.6. HTML vs XML Syntax
* 3.2.4.2.1. Metadata content
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.2.6. The style element
* 4.4.1. The p element
* 4.12.2. The noscript element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27) (28) (29) (30) (31) (32)
* 8.1.2.4. Optional tags
* 8.2.3.2. The stack of open elements
* 8.2.5.4.5. The "in head noscript" insertion mode (2)
* 8.3. Serializing HTML fragments
* 8.4. Parsing HTML fragments
* Elements (2) (3) (4)
* Element content categories (2) (3)
* Element Interfaces
#elementdef-templateReferenced in:
* 3.2.4. Content models
* 3.2.4.2.1. Metadata content
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.9. Script-supporting elements
* 4.3.1. The body element
* 4.7.15. The area element (2)
* 4.9.3. The colgroup element
* 4.12.3. The template element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20)
* 4.12.3.1. Interaction of template elements with XSLT and XPath (2) (3)
* 8.1.2. Elements (2) (3) (4) (5) (6) (7) (8) (9)
* 8.1.2.4. Optional tags
* 8.2.3.1. The insertion mode (2) (3)
* 8.2.3.2. The stack of open elements (2) (3)
* 8.2.3.3. The list of active formatting elements (2)
* 8.2.3.4. The element pointers
* 8.2.5.1. Creating and inserting nodes (2) (3) (4)
* 8.2.5.4.4. The "in head" insertion mode (2) (3)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6)
* 8.2.5.4.9. The "in table" insertion mode (2)
* 8.2.5.4.13. The "in table body" insertion mode
* 8.2.5.4.14. The "in row" insertion mode
* 8.2.5.4.18. The "in template" insertion mode (2)
* 8.2.7. Coercing an HTML DOM into an infoset
* 8.3. Serializing HTML fragments (2)
* 8.4. Parsing HTML fragments
* 9.2. Parsing XML documents (2)
* 9.3. Serializing XML fragments
* Elements (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15)
(16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26) (27) (28) (29)
(30)
* Element content categories (2) (3) (4)
* Element Interfaces
#template-nothingReferenced in:
* 4.12.3. The template element
#htmltemplateelementReferenced in:
* Elements
* Element Interfaces
#template-contentsReferenced in:
* 3.2.4. Content models
* 4.12.3. The template element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.12.3.1. Interaction of template elements with XSLT and XPath (2) (3)
* 8.1.2. Elements (2) (3)
* 8.2.5.1. Creating and inserting nodes (2)
* 8.2.7. Coercing an HTML DOM into an infoset
* 8.3. Serializing HTML fragments
* 9.2. Parsing XML documents
* 9.3. Serializing XML fragments
#appropriate-template-contents-owner-documentReferenced in:
* 4.12.3. The template element (2)
#associated-inert-template-documentReferenced in:
* 4.12.3. The template element (2)
#dom-htmltemplateelement-contentReferenced in:
* 4.12.3. The template element
#elementdef-canvasReferenced in:
* 3.2.4.2.2. Flow content
* 3.2.4.2.5. Phrasing content
* 3.2.4.2.6. Embedded content
* 3.2.4.2.8. Palpable content (2)
* 3.2.4.4. Paragraphs
* 4.7.5. The img element
* 4.7.13.7. Ready states
* 4.12.4. The canvas element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27) (28) (29) (30) (31) (32) (33) (34) (35)
* 4.12.4.1. Color spaces and color correction (2)
* 4.12.4.3. Security with canvas elements (2) (3) (4) (5)
* 5.1. The hidden attribute
* 5.3. Activation
* 7.8. Images (2) (3) (4) (5)
* 10.4.1. Embedded content (2) (3)
* Elements
* Element content categories (2) (3) (4)
* Attributes (2)
* Element Interfaces
#typedefdef-renderingcontextReferenced in:
* 4.12.4. The canvas element
#htmlcanvaselementReferenced in:
* 7.8. Images
* Elements
* Element Interfaces
#callbackdef-blobcallbackReferenced in:
* 4.12.4. The canvas element
#being-used-as-relevant-canvas-fallback-contentReferenced in:
* 5.4.2. Data model
#element-attrdef-canvas-widthReferenced in:
* Elements
#element-attrdef-canvas-heightReferenced in:
* Elements
#canvas-origin-cleanReferenced in:
* 4.12.4. The canvas element (2) (3)
* 4.12.4.3. Security with canvas elements (2) (3) (4) (5)
* 7.8. Images (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
#modedef-canvas-context-modeReferenced in:
* 4.12.4. The canvas element (2) (3) (4) (5) (6) (7)
#contextdef-canvas-noneReferenced in:
* 4.12.4. The canvas element (2)
#contextdef-canvas-2dReferenced in:
* 4.12.4. The canvas element (2) (3) (4)
#contextdef-canvas-webglReferenced in:
* 4.12.4. The canvas element (2) (3)
#dom-htmlcanvaselement-widthReferenced in:
* 4.12.4. The canvas element
#dom-htmlcanvaselement-heightReferenced in:
* 4.12.4. The canvas element
#dom-htmlcanvaselement-todataurlReferenced in:
* 4.12.4. The canvas element
#a-serialization-of-the-canvas-elements-bitmap-as-a-fileReferenced in:
* 4.12.4. The canvas element (2)
#tag-cloudsReferenced in:
* 4.8.6.12. Link type "tag"
#disablingReferenced in:
* 4.10.9. The optgroup element
* 4.15.2. Pseudo-classes
* 5.4.2. Data model (2)
* 5.4.3. The tabindex attribute
#selector-linkReferenced in:
* 2.5.3. Dynamic changes to base URLs
* 4.15.2. Pseudo-classes
* 10.3.2. The page
* 10.7.1. Links, forms, and navigation
#selector-visitedReferenced in:
* 2.5.3. Dynamic changes to base URLs
* 4.15.2. Pseudo-classes
* 10.3.2. The page (2)
* 10.7.1. Links, forms, and navigation
#selector-activeReferenced in:
* 4.15.2. Pseudo-classes (2) (3) (4)
* 10.3.2. The page
#being-activatedReferenced in:
* 4.15.2. Pseudo-classes (2) (3) (4) (5) (6)
#in-a-formal-activation-stateReferenced in:
* 4.15.2. Pseudo-classes (2)
#being-actively-pointed-atReferenced in:
* 4.15.2. Pseudo-classes
#selector-hoverReferenced in:
* 4.15.2. Pseudo-classes (2) (3) (4) (5) (6) (7)
#designatesReferenced in:
* 4.15.2. Pseudo-classes (2)
#selector-focusReferenced in:
* 4.15.2. Pseudo-classes
#selector-enabledReferenced in:
* 4.15.2. Pseudo-classes
#selector-disabledReferenced in:
* 4.14. Disabled elements
* 4.15.2. Pseudo-classes
#selector-checkedReferenced in:
* 4.15.2. Pseudo-classes
#selector-indeterminateReferenced in:
* 4.15.2. Pseudo-classes
#selector-defaultReferenced in:
* 4.15.2. Pseudo-classes
#selector-validReferenced in:
* 4.15.2. Pseudo-classes
#selector-invalidReferenced in:
* 4.15.2. Pseudo-classes
#selector-in-rangeReferenced in:
* 4.15.2. Pseudo-classes
#selector-out-of-rangeReferenced in:
* 4.15.2. Pseudo-classes
#selector-requiredReferenced in:
* 4.15.2. Pseudo-classes
#selector-optionalReferenced in:
* 4.15.2. Pseudo-classes
#selector-read-onlyReferenced in:
* 4.15.2. Pseudo-classes
#selector-read-writeReferenced in:
* 4.15.2. Pseudo-classes
#selector-dir-ltrReferenced in:
* 4.15.2. Pseudo-classes
#selector-dir-rtlReferenced in:
* 4.15.2. Pseudo-classes
#element-attrdef-global-hiddenReferenced in:
* 3.2.4.2.8. Palpable content
* 3.2.5. Global attributes
* 3.2.5.6. The style attribute
* 4.3.9.1. Creating an outline (2) (3)
* 4.10.20.2. Constraint validation
* 4.11.3.1. Facets
* 4.11.3.2. Using the a element to define a command
* 4.11.3.4. Using the input element to define a command
* 4.11.3.5. Using the option element to define a command
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements
* 5.1. The hidden attribute (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19)
* 5.4.4. Processing model
* 5.5.3. Processing model
* 10.1. Introduction
* Attributes
#dom-htmlelement-hiddenReferenced in:
* 3.2.2. Elements in the DOM
#inertnessReferenced in:
* 4.11.3.2. Using the a element to define a command
* 4.11.3.3. Using the button element to define a command
* 4.11.3.4. Using the input element to define a command
* 4.11.3.5. Using the option element to define a command
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements
* 4.11.4. The dialog element (2) (3)
* 5.2. Inert subtrees (2) (3) (4) (5) (6) (7) (8) (9)
* 5.4.2. Data model (2) (3) (4)
* 5.4.3. The tabindex attribute
* 5.4.4. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16)
* 5.4.5. Sequential focus navigation
#blocked-by-the-modal-dialogReferenced in:
* 4.11.4. The dialog element (2) (3) (4) (5)
* 5.2. Inert subtrees
#running-synthetic-click-activation-stepsReferenced in:
* 4.10.4. The label element
* 4.10.21.2. Implicit submission
* 4.11.3.2. Using the a element to define a command
* 4.11.3.4. Using the input element to define a command
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements
* 5.3. Activation (2) (3) (4)
* 5.4.4. Processing model
#run-authentic-click-activation-stepsReferenced in:
* 5.3. Activation
#nearest-activatable-elementReferenced in:
* 5.3. Activation (2)
#run-pre-click-activation-stepsReferenced in:
* 5.3. Activation (2)
#pre-click-activation-stepsReferenced in:
* 4.10.5.1.15. Checkbox state (type=checkbox) (2)
* 4.10.5.1.16. Radio Button state (type=radio) (2)
#run-canceled-activation-stepsReferenced in:
* 5.3. Activation (2)
#canceled-activation-stepsReferenced in:
* 4.10.5.1.15. Checkbox state (type=checkbox)
* 4.10.5.1.16. Radio Button state (type=radio)
#run-post-click-activation-stepsReferenced in:
* 5.3. Activation (2)
#activation-behaviorReferenced in:
* 4.2.4.5. Providing users with a means to follow hyperlinks created
using the link element
* 4.5.1. The a element
* 4.7.15. The area element
* 4.8.2. Links created by a and area elements
* 4.10.4. The label element (2) (3)
* 4.10.5.1.15. Checkbox state (type=checkbox) (2)
* 4.10.5.1.16. Radio Button state (type=radio) (2)
* 4.10.5.1.17. File Upload state (type=file) (2)
* 4.10.5.1.18. Submit Button state (type=submit) (2)
* 4.10.5.1.19. Image Button state (type=image) (2) (3) (4)
* 4.10.5.1.20. Reset Button state (type=reset) (2)
* 4.10.5.1.21. Button state (type=button) (2)
* 4.10.5.5. Common event behaviors (2) (3) (4)
* 4.10.6. The button element
* 4.10.21.2. Implicit submission (2)
* 4.11.3.2. Using the a element to define a command
* 4.11.3.4. Using the input element to define a command
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements (2)
* 4.15.2. Pseudo-classes (2) (3)
* 5.3. Activation (2) (3) (4) (5)
* 5.4.4. Processing model
* 6.1.5. Browsing context names
* 6.6.4. The Location interface
* Events
#dom-htmlelement-clickReferenced in:
* 3.2.2. Elements in the DOM
* 7.1.5.3. Event firing
#focusableReferenced in:
* 4.7.16.2. Processing model (2)
* 4.11.4. The dialog element (2)
* 5.4.2. Data model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
(14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
* 5.4.3. The tabindex attribute (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16)
* 5.4.4. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16) (17) (18) (19) (20) (21) (22)
* 5.4.5. Sequential focus navigation (2) (3) (4) (5) (6)
* 5.4.6. Focus management APIs
* 10.7.2. The title attribute
#dom-anchorReferenced in:
* 4.11.4. The dialog element
* 5.4.2. Data model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
(14)
* 5.4.3. The tabindex attribute (2) (3) (4) (5) (6) (7) (8) (9)
* 5.4.4. Processing model (2)
* 5.4.5. Sequential focus navigation
* 5.4.6. Focus management APIs
#control-groupReferenced in:
* 4.11.4. The dialog element (2)
* 5.4.2. Data model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
* 5.4.4. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16)
* 5.4.5. Sequential focus navigation (2) (3) (4) (5) (6) (7) (8) (9)
* 5.4.6. Focus management APIs
#ownerReferenced in:
* 5.4.2. Data model
* 5.4.4. Processing model
#control-group-ownerReferenced in:
* 4.11.4. The dialog element
* 5.4.2. Data model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
(14) (15) (16)
* 5.4.4. Processing model (2) (3) (4) (5) (6)
* 5.4.5. Sequential focus navigation
#expressly-inertReferenced in:
* 5.4.2. Data model (2) (3) (4)
* 5.4.4. Processing model (2)
#focused-areaReferenced in:
* 5.4.2. Data model (2) (3)
* 5.4.4. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16)
* 5.4.6. Focus management APIs
#dialog-group-managerReferenced in:
* 5.4.2. Data model (2)
* 5.4.4. Processing model (2) (3) (4) (5)
#dialog-groupReferenced in:
* 5.4.2. Data model (2) (3) (4) (5) (6) (7)
* 5.4.4. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16) (17) (18) (19)
* 5.4.5. Sequential focus navigation (2) (3)
* 5.4.6. Focus management APIs
#dialog-expressly-inertReferenced in:
* 5.4.2. Data model
#focused-dialog-of-the-dialog-groupReferenced in:
* 5.4.2. Data model (2)
* 5.4.4. Processing model (2) (3) (4) (5) (6) (7) (8) (9)
* 5.4.5. Sequential focus navigation (2)
* 5.4.6. Focus management APIs (2)
#currently-focused-area-of-the-top-level-browsing-contextReferenced in:
* 4.15.2. Pseudo-classes
* 5.4.2. Data model (2) (3)
* 5.4.4. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15)
* 5.4.5. Sequential focus navigation (2)
#focusedReferenced in:
* 4.10.5.3.10. The placeholder attribute (2)
* 4.10.5.5. Common event behaviors
* 4.10.11. The textarea element
* 4.10.21.2. Implicit submission
* 4.12.4. The canvas element
* 5.4.1. Introduction (2) (3)
* 5.4.3. The tabindex attribute
* 5.4.6. Focus management APIs
* 5.5.3. Processing model
* 10.7.2. The title attribute (2)
#focus-chainReferenced in:
* 4.15.2. Pseudo-classes
* 5.4.4. Processing model (2) (3) (4) (5)
#element-attrdef-global-tabindexReferenced in:
* 2.2.2. Dependencies
* 3.2.4.2.7. Interactive content
* 3.2.5. Global attributes
* 4.11.4. The dialog element
* 5.4.3. The tabindex attribute (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16) (17) (18)
* 5.4.4. Processing model
* Element content categories
* Attributes
* Changes between Working Draft 3 and Working Draft 2
#can-be-focusedReferenced in:
* 4.14. Disabled elements
* 4.15.2. Pseudo-classes
* 5.4.2. Data model
* 5.4.3. The tabindex attribute (2) (3) (4) (5)
#dom-htmlelement-tabindexReferenced in:
* 3.2.2. Elements in the DOM
* 5.4.3. The tabindex attribute
#focusing-stepsReferenced in:
* 4.10.4. The label element
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute
* 4.10.20.2. Constraint validation
* 4.10.20.3. The constraint validation API
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements
* 4.11.4. The dialog element
* 5.4.4. Processing model (2) (3) (4)
* 5.4.5. Sequential focus navigation
* 5.4.6. Focus management APIs (2)
* 5.6.2. Making entire documents editable: The designMode IDL attribute
* 6.7.9. Navigating to a fragment
#unfocusing-stepsReferenced in:
* 5.4.4. Processing model (2)
* 5.4.6. Focus management APIs
#loses-focusReferenced in:
* 4.10.5.5. Common event behaviors (2)
* 5.4.4. Processing model (2)
#fire-a-focus-eventReferenced in:
* 5.4.4. Processing model (2)
#has-focus-stepsReferenced in:
* 5.4.6. Focus management APIs
#sequential-focus-navigationReferenced in:
* 5.4.3. The tabindex attribute (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14)
* 5.4.5. Sequential focus navigation (2) (3) (4) (5) (6) (7) (8) (9)
#sequential-focus-navigation-starting-pointReferenced in:
* 5.4.5. Sequential focus navigation (2) (3)
* 6.7.9. Navigating to a fragment
#sequential-navigation-search-algorithmReferenced in:
* 5.4.5. Sequential focus navigation (2)
#suitable-sequentially-focusable-areaReferenced in:
* 5.4.5. Sequential focus navigation (2) (3) (4) (5) (6)
#primary-control-groupReferenced in:
* 5.4.5. Sequential focus navigation (2) (3)
#home-control-groupReferenced in:
* 5.4.5. Sequential focus navigation (2) (3)
#home-sequential-focus-navigation-orderReferenced in:
* 5.4.5. Sequential focus navigation (2) (3)
#dom-document-activeelementReferenced in:
* 3.1.1. The Document object
#dom-document-hasfocusReferenced in:
* 3.1.1. The Document object
#dom-window-focusReferenced in:
* 6.3. The Window object
#dom-window-blurReferenced in:
* 6.3. The Window object
#dom-htmlelement-focusReferenced in:
* 3.2.2. Elements in the DOM
#dom-htmlelement-blurReferenced in:
* 3.2.2. Elements in the DOM
#element-attrdef-global-accesskeyReferenced in:
* 3.2.5. Global attributes
* 5.5.1. Introduction (2) (3)
* 5.5.2. The accesskey attribute (2) (3)
* 5.5.3. Processing model (2) (3) (4) (5) (6) (7)
* Attributes
#assigned-access-keyReferenced in:
* 4.11.3.2. Using the a element to define a command
* 4.11.3.4. Using the input element to define a command
* 4.11.3.5. Using the option element to define a command
* 4.11.3.6. Using the accesskey attribute on a label element to define a
command (2)
* 4.11.3.7. Using the accesskey attribute on a legend element to define
a command (2)
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements (2)
* 5.5.3. Processing model (2) (3) (4) (5) (6) (7) (8)
#dom-htmlelement-accesskeyReferenced in:
* 3.2.2. Elements in the DOM
#elementcontenteditableReferenced in:
* 3.2.2. Elements in the DOM
#element-attrdef-global-contenteditableReferenced in:
* 3.2.5. Global attributes
* 5.6.1. Making document regions editable: The contenteditable content
attribute
* 5.6.5. Spelling and grammar checking
* 5.7.8. Security risks in the drag-and-drop model
#dom-elementcontenteditable-contenteditableReferenced in:
* 5.6.1. Making document regions editable: The contenteditable content
attribute (2)
#dom-elementcontenteditable-iscontenteditableReferenced in:
* 5.6.1. Making document regions editable: The contenteditable content
attribute
#dom-document-designmodeReferenced in:
* 3.1.1. The Document object
* 5.6.2. Making entire documents editable: The designMode IDL attribute
#active-rangeReferenced in:
* 5.6.2. Making entire documents editable: The designMode IDL attribute
* 10.7.3. Editing hosts
#editing-hostReferenced in:
* 4.15.2. Pseudo-classes
* 5.4.3. The tabindex attribute
* 5.6.1. Making document regions editable: The contenteditable content
attribute
* 5.6.3. Best practices for in-page editors
* 5.6.4. Editing APIs
* 5.6.5. Spelling and grammar checking (2)
* 5.7.5. Drag-and-drop processing model (2) (3) (4) (5)
* 10.7.3. Editing hosts
#editableReferenced in:
* 4.15.2. Pseudo-classes
* 5.6.1. Making document regions editable: The contenteditable content
attribute
* 5.6.4. Editing APIs
* 5.6.5. Spelling and grammar checking (2)
* 5.7.5. Drag-and-drop processing model (2) (3) (4)
#dom-document-execcommandReferenced in:
* 3.1.1. The Document object
#dom-document-querycommandenabledReferenced in:
* 3.1.1. The Document object
#dom-document-querycommandindetermReferenced in:
* 3.1.1. The Document object
#dom-document-querycommandstateReferenced in:
* 3.1.1. The Document object
#dom-document-querycommandsupportedReferenced in:
* 3.1.1. The Document object
#dom-document-querycommandvalueReferenced in:
* 3.1.1. The Document object
#delete-the-selectionReferenced in:
* 5.7.5. Drag-and-drop processing model
#default-behaviorReferenced in:
* 5.6.5. Spelling and grammar checking (2) (3) (4)
#true-by-defaultReferenced in:
* 5.6.5. Spelling and grammar checking (2)
#false-by-defaultReferenced in:
* 5.6.5. Spelling and grammar checking
#inherit-by-defaultReferenced in:
* 5.6.5. Spelling and grammar checking
#element-attrdef-global-spellcheckReferenced in:
* 3.2.5. Global attributes
* 5.6.5. Spelling and grammar checking (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12)
* Attributes
#dom-htmlelement-spellcheckReferenced in:
* 3.2.2. Elements in the DOM
* 5.6.5. Spelling and grammar checking (2) (3)
#dom-htmlelement-forcespellcheckReferenced in:
* 3.2.2. Elements in the DOM
#drag-data-storeReferenced in:
* 5.7.2. The drag data store (2) (3)
* 5.7.3. The DataTransfer interface (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14)
* 5.7.3.1. The DataTransferItemList interface (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11) (12)
* 5.7.3.2. The DataTransferItem interface (2) (3) (4) (5)
* 5.7.4. The DragEvent interface (2) (3) (4)
* 5.7.5. Drag-and-drop processing model
#drag-data-store-item-listReferenced in:
* 5.7.2. The drag data store (2)
* 5.7.3. The DataTransfer interface (2) (3) (4) (5) (6) (7) (8) (9)
* 5.7.3.1. The DataTransferItemList interface (2) (3) (4) (5)
* 5.7.3.2. The DataTransferItem interface (2)
* 5.7.5. Drag-and-drop processing model (2) (3) (4) (5) (6) (7) (8) (9)
#a-drag-data-item-kindReferenced in:
* 5.7.2. The drag data store
* 5.7.3.2. The DataTransferItem interface (2) (3) (4) (5) (6)
* 5.7.5. Drag-and-drop processing model (2) (3) (4) (5) (6) (7) (8)
#item-type-stringReferenced in:
* 5.7.2. The drag data store
* 5.7.3. The DataTransfer interface (2) (3) (4) (5) (6)
* 5.7.3.1. The DataTransferItemList interface (2) (3)
* 5.7.3.2. The DataTransferItem interface (2)
* 5.7.5. Drag-and-drop processing model (2) (3) (4) (5) (6) (7) (8) (9)
#drag-data-store-default-feedbackReferenced in:
* 5.7.2. The drag data store
* 5.7.5. Drag-and-drop processing model (2)
#drag-data-store-bitmapReferenced in:
* 5.7.2. The drag data store
* 5.7.3. The DataTransfer interface (2)
* 5.7.5. Drag-and-drop processing model
#drag-data-store-hot-spot-coordinateReferenced in:
* 5.7.2. The drag data store
* 5.7.3. The DataTransfer interface
* 5.7.5. Drag-and-drop processing model
#drag-data-store-modeReferenced in:
* 5.7.2. The drag data store
* 5.7.3.1. The DataTransferItemList interface
* 5.7.3.2. The DataTransferItem interface
* 5.7.4. The DragEvent interface (2)
* 5.7.6. Events summary
#read-write-modeReferenced in:
* 5.7.3. The DataTransfer interface (2) (3) (4)
* 5.7.4. The DragEvent interface
* 5.7.6. Events summary
#read-only-modeReferenced in:
* 5.7.4. The DragEvent interface
* 5.7.6. Events summary
#protected-modeReferenced in:
* 5.7.2. The drag data store
* 5.7.3. The DataTransfer interface (2)
* 5.7.4. The DragEvent interface
* 5.7.6. Events summary (2) (3) (4) (5) (6)
#drag-data-store-allowed-effects-stateReferenced in:
* 5.7.2. The drag data store
* 5.7.4. The DragEvent interface (2)
#create-a-drag-data-storeReferenced in:
* 5.7.5. Drag-and-drop processing model
#datatransferReferenced in:
* 5.7.1. Introduction
* 5.7.3. The DataTransfer interface (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12)
* 5.7.3.1. The DataTransferItemList interface (2) (3) (4) (5)
* 5.7.3.2. The DataTransferItem interface (2) (3) (4)
* 5.7.4. The DragEvent interface (2) (3) (4) (5) (6) (7)
* 5.7.8. Security risks in the drag-and-drop model
#dom-datatransfer-setdragimageReferenced in:
* 5.7.3. The DataTransfer interface
#dom-datatransfer-dropeffectReferenced in:
* 5.7.1. Introduction
* 5.7.3. The DataTransfer interface (2) (3) (4)
* 5.7.4. The DragEvent interface (2)
* 5.7.5. Drag-and-drop processing model (2) (3)
* 5.7.6. Events summary
#dom-datatransfer-effectallowedReferenced in:
* 5.7.3. The DataTransfer interface (2) (3) (4)
* 5.7.4. The DragEvent interface (2) (3) (4)
* 5.7.5. Drag-and-drop processing model (2)
* 5.7.6. Events summary (2) (3)
#dom-datatransfer-itemsReferenced in:
* 5.7.3. The DataTransfer interface (2)
#dom-datatransfer-typesReferenced in:
* 5.7.3. The DataTransfer interface (2) (3)
#dom-datatransfer-getdataReferenced in:
* 5.7.3. The DataTransfer interface (2)
#dom-datatransfer-setdataReferenced in:
* 5.7.3. The DataTransfer interface (2)
#dom-datatransfer-cleardataReferenced in:
* 5.7.3. The DataTransfer interface (2) (3) (4)
#dom-datatransfer-filesReferenced in:
* 5.7.3. The DataTransfer interface (2)
#datatransferitemlistReferenced in:
* 5.7.3. The DataTransfer interface (2) (3)
* 5.7.3.1. The DataTransferItemList interface (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11) (12) (13) (14)
#dom-datatransferitemlist-removeReferenced in:
* 5.7.3.1. The DataTransferItemList interface
#dom-datatransferitemlist-lengthReferenced in:
* 5.7.3.1. The DataTransferItemList interface (2)
#dom-datatransferitemlist-addReferenced in:
* 5.7.3.1. The DataTransferItemList interface (2) (3) (4)
#dom-datatransferitemlist-clearReferenced in:
* 5.7.3.1. The DataTransferItemList interface (2)
#datatransferitemReferenced in:
* 5.7.3.1. The DataTransferItemList interface (2) (3) (4) (5) (6) (7)
* 5.7.3.2. The DataTransferItem interface (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15) (16) (17)
#callbackdef-functionstringcallbackReferenced in:
* 5.7.3.2. The DataTransferItem interface
#dom-datatransferitem-kindReferenced in:
* 5.7.3. The DataTransfer interface (2) (3) (4) (5) (6) (7) (8) (9)
* 5.7.3.1. The DataTransferItemList interface (2) (3)
* 5.7.3.2. The DataTransferItem interface (2)
#dom-datatransferitem-typeReferenced in:
* 5.7.3.1. The DataTransferItemList interface
* 5.7.3.2. The DataTransferItem interface (2)
#dom-datatransferitem-getasstringReferenced in:
* 5.7.3.2. The DataTransferItem interface (2)
#dom-datatransferitem-getasfileReferenced in:
* 5.7.3.2. The DataTransferItem interface (2)
#drageventReferenced in:
* 5.7.4. The DragEvent interface (2) (3) (4) (5)
* 5.7.5. Drag-and-drop processing model (2)
#dictdef-drageventinitReferenced in:
* 5.7.4. The DragEvent interface
#dom-dragevent-datatransferReferenced in:
* 5.7.4. The DragEvent interface (2) (3)
* 5.7.5. Drag-and-drop processing model (2)
#fire-a-dnd-eventReferenced in:
* 5.7.5. Drag-and-drop processing model (2) (3) (4) (5) (6) (7) (8) (9)
(10)
#if-appropriateReferenced in:
* 5.7.4. The DragEvent interface (2) (3) (4) (5) (6) (7) (8)
#source-nodeReferenced in:
* 5.7.5. Drag-and-drop processing model (2) (3) (4) (5) (6) (7) (8) (9)
(10)
* 5.7.6. Events summary (2) (3)
#list-of-dragged-nodesReferenced in:
* 5.7.5. Drag-and-drop processing model (2) (3) (4)
#initiatedReferenced in:
* 5.7.5. Drag-and-drop processing model (2)
#immediate-user-selectionReferenced in:
* 5.7.5. Drag-and-drop processing model (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14)
* 5.7.6. Events summary (2)
#previous-target-elementReferenced in:
* 5.7.5. Drag-and-drop processing model (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23)
(24)
* 5.7.6. Events summary (2) (3) (4)
#current-drag-operationReferenced in:
* 5.7.4. The DragEvent interface
* 5.7.5. Drag-and-drop processing model (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13)
* 5.7.6. Events summary (2) (3)
#drag-and-drop-eventsReferenced in:
* 5.7.3. The DataTransfer interface
* Events
#eventdef-global-dragstartReferenced in:
* Attributes
#eventdef-global-dragReferenced in:
* Attributes
#eventdef-global-dragenterReferenced in:
* Attributes
#eventdef-global-dragexitReferenced in:
* Attributes
#eventdef-global-dragleaveReferenced in:
* Attributes
#eventdef-global-dragoverReferenced in:
* Attributes
#eventdef-global-dropReferenced in:
* Attributes
#eventdef-global-dragendReferenced in:
* Attributes
#element-attrdef-global-draggableReferenced in:
* 3.2.5. Global attributes
* 5.4.3. The tabindex attribute
* 5.7.1. Introduction
* 5.7.5. Drag-and-drop processing model
* 5.7.7. The draggable attribute (2) (3) (4) (5) (6) (7) (8)
* Attributes
#dom-htmlelement-draggableReferenced in:
* 3.2.2. Elements in the DOM
* 5.7.5. Drag-and-drop processing model
* 5.7.7. The draggable attribute (2) (3) (4) (5) (6) (7) (8)
#browsing-contextReferenced in:
* 1.5.1. Serializability of script execution
* 2.1.5. Plugins
* 2.2.1. Conformance classes (2)
* 2.5.1. Terminology (2)
* 2.6.2. Processing model (2)
* 3.1. Documents (2) (3) (4) (5) (6)
* 3.1.2. Resource metadata management
* 3.2.1. Semantics
* 4.2.3. The base element (2) (3)
* 4.2.5.3. Pragma directives (2) (3) (4)
* 4.2.7. Interactions of styling and scripting
* 4.5.1. The a element
* 4.7.5. The img element (2) (3)
* 4.7.6. The iframe element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13)
* 4.7.7. The embed element (2) (3)
* 4.7.8. The object element (2) (3) (4) (5) (6) (7)
* 4.7.11. The audio element
* 4.7.15. The area element (2)
* 4.8.2. Links created by a and area elements
* 4.8.4. Following hyperlinks (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.8.6. Link types
* 4.8.6.8. Link type "noopener"
* 4.8.6.9. Link type "noreferrer"
* 4.10.3. The form element
* 4.10.5. The input element
* 4.10.6. The button element
* 4.10.10. The option element
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute (2)
* 4.10.21.3. Form submission algorithm (2) (3) (4) (5)
* 4.11.3.1. Facets
* 4.11.4. The dialog element
* 4.12.1.5. Interaction of script elements and XSLT
* 4.12.3. The template element (2)
* 5.4.2. Data model (2)
* 5.4.4. Processing model (2) (3) (4)
* 5.4.5. Sequential focus navigation (2)
* 5.4.6. Focus management APIs (2) (3) (4) (5)
* 5.5.3. Processing model
* 5.7.5. Drag-and-drop processing model
* 6.1. Browsing contexts (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23)
* 6.1.1. Nested browsing contexts (2) (3) (4) (5) (6) (7)
* 6.1.1.1. Navigating nested browsing contexts in the DOM (2) (3) (4)
* 6.1.2. Auxiliary browsing contexts
* 6.1.2.1. Navigating auxiliary browsing contexts in the DOM (2) (3) (4)
* 6.1.3. Security (2) (3) (4) (5) (6)
* 6.1.4. Groupings of browsing contexts (2) (3) (4) (5) (6) (7) (8)
* 6.1.5. Browsing context names (2) (3)
* 6.1.6. Script settings for browsing contexts (2)
* 6.3. The Window object (2) (3)
* 6.3.1. APIs for creating and navigating browsing contexts by name (2)
(3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14)
* 6.3.2. Accessing other browsing contexts
* 6.3.3. Named access on the Window object
* 6.3.4. Garbage collection and browsing contexts (2) (3) (4) (5) (6)
* 6.3.5. Closing browsing contexts
* 6.3.6. Browser interface elements
* 6.3.7. The WindowProxy object (2) (3)
* 6.3.7.1.5. [[GetOwnProperty]] ( P )
* 6.4. Origin (2)
* 6.4.1. Relaxing the same-origin restriction (2)
* 6.5. Sandboxing (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 6.6.1. The session history of browsing contexts (2) (3) (4) (5) (6)
(7)
* 6.6.2. The History interface (2) (3) (4) (5) (6) (7) (8)
* 6.6.4. The Location interface (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21)
* 6.7.1. Navigating across documents (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23)
(24) (25) (26) (27)
* 6.7.2. Page load processing model for HTML files
* 6.7.4. Page load processing model for text files
* 6.7.5. Page load processing model for multipart/x-mixed-replace
resources
* 6.7.6. Page load processing model for media
* 6.7.7. Page load processing model for content that uses plugins
* 6.7.8. Page load processing model for inline content that doesn’t have
a DOM
* 6.7.9. Navigating to a fragment
* 6.7.10. History traversal (2) (3) (4)
* 6.7.11. Unloading documents (2) (3) (4) (5) (6) (7)
* 7.1.2. Enabling and disabling scripting (2) (3) (4) (5) (6) (7) (8)
* 7.1.3.1. Definitions (2) (3)
* 7.1.3.5. Realms, settings objects, and global objects
* 7.1.3.6. Killing scripts
* 7.1.4.1. Definitions (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 7.1.4.2. Processing model (2) (3) (4) (5) (6) (7)
* 7.1.5.1. Event handlers (2)
* 7.1.5.4. Events and the Window object
* 7.4.1. Opening the input stream (2) (3) (4)
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods (2)
* 8.1.2. Elements
* 8.2.5.4.8. The "text" insertion mode
* 8.2.6. The end (2)
* 8.2.8.4. Scripts that modify the page as it is being parsed
* 10.3.2. The page (2) (3)
* 10.7.1. Links, forms, and navigation (2)
* 11.3.3. Frames (2) (3) (4)
* Elements
* Attributes (2) (3) (4) (5)
#active-documentReferenced in:
* 2.6.2. Processing model
* 3.1. Documents (2) (3) (4) (5)
* 4.2.7. Interactions of styling and scripting
* 4.7.5. The img element (2) (3) (4)
* 4.7.6. The iframe element (2) (3) (4) (5) (6)
* 4.7.7. The embed element (2)
* 4.7.8. The object element (2) (3)
* 4.7.11. The audio element
* 4.10.10. The option element
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute (2)
(3)
* 5.2. Inert subtrees
* 5.4.2. Data model (2) (3)
* 5.4.4. Processing model (2) (3) (4) (5)
* 5.4.5. Sequential focus navigation (2)
* 6.1. Browsing contexts
* 6.1.1. Nested browsing contexts (2) (3)
* 6.1.3. Security (2) (3) (4) (5) (6) (7)
* 6.1.4. Groupings of browsing contexts
* 6.1.5. Browsing context names (2)
* 6.3. The Window object
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.3.2. Accessing other browsing contexts
* 6.3.3. Named access on the Window object (2) (3) (4) (5)
* 6.3.5. Closing browsing contexts (2)
* 6.3.6. Browser interface elements
* 6.4. Origin
* 6.5. Sandboxing
* 6.6.1. The session history of browsing contexts
* 6.6.2. The History interface (2) (3) (4) (5) (6)
* 6.6.4. The Location interface (2) (3) (4) (5) (6) (7)
* 6.7.1. Navigating across documents (2) (3) (4) (5) (6) (7) (8) (9)
(10)
* 6.7.10. History traversal (2) (3)
* 6.7.11. Unloading documents (2) (3) (4)
* 6.7.12. Aborting a document load (2)
* 7.1.2. Enabling and disabling scripting
* 7.1.4.1. Definitions
* 7.4.1. Opening the input stream
* 7.4.3. document.write()
* 7.6.1. Simple dialogs (2) (3)
* 7.6.2. Printing
* 8.2.2.2. Determining the character encoding
* 11.3.3. Frames (2) (3)
#document-associated-with-a-windowReferenced in:
* 6.1.1.1. Navigating nested browsing contexts in the DOM
* 6.3. The Window object
* 6.3.2. Accessing other browsing contexts
* 6.7.1. Navigating across documents
* 7.4.1. Opening the input stream
#creator-browsing-contextReferenced in:
* 2.5.1. Terminology
* 6.1. Browsing contexts (2) (3) (4) (5) (6)
#creator-originReferenced in:
* 6.1. Browsing contexts
#creator-urlReferenced in:
* 6.1. Browsing contexts
#creator-base-urlReferenced in:
* 2.5.1. Terminology
#creating-a-new-browsing-contextReferenced in:
* 4.8.6.9. Link type "noreferrer"
* 6.4. Origin
* 6.7.1. Navigating across documents
* 7.4.1. Opening the input stream
* 11.3.3. Frames
#nested-browsing-contextsReferenced in:
* 3.1.3. DOM tree accessors (2)
* 4.7.6. The iframe element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20)
* 4.7.7. The embed element (2) (3) (4) (5) (6) (7)
* 4.7.8. The object element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute
* 5.2. Inert subtrees
* 5.4.2. Data model (2) (3) (4)
* 5.4.4. Processing model (2) (3) (4)
* 5.4.5. Sequential focus navigation (2) (3)
* 5.4.6. Focus management APIs
* 6.1.1. Nested browsing contexts (2) (3) (4) (5) (6)
* 6.1.1.1. Navigating nested browsing contexts in the DOM (2) (3)
* 6.1.3. Security
* 6.3.3. Named access on the Window object (2)
* 6.3.7.1.5. [[GetOwnProperty]] ( P )
* 6.5. Sandboxing (2) (3) (4) (5)
* 6.6.1. The session history of browsing contexts
* 6.7.1. Navigating across documents (2) (3)
* 7.1.4.2. Processing model (2) (3)
* 7.6.2. Printing (2)
* 8.2.2.2. Determining the character encoding
* 10.3.2. The page (2) (3) (4) (5) (6)
* 10.4.1. Embedded content
* 10.6. Frames and framesets (2) (3)
* 11.3.3. Frames (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
(14)
* Elements (2)
* Attributes
#through-which-new-document-is-nestedReferenced in:
* 6.1.1. Nested browsing contexts (2)
* 6.3.2. Accessing other browsing contexts
* 6.3.7.1.5. [[GetOwnProperty]] ( P )
* 7.1.4.2. Processing model
* 8.2.2.2. Determining the character encoding
#browsing-context-containerReferenced in:
* 2.5.1. Terminology
* 2.6.2. Processing model
* 4.7.6. The iframe element
* 4.15.2. Pseudo-classes
* 5.2. Inert subtrees
* 5.4.2. Data model (2) (3) (4) (5) (6)
* 5.4.3. The tabindex attribute
* 5.4.4. Processing model (2) (3) (4) (5) (6) (7)
* 5.4.5. Sequential focus navigation (2)
* 5.4.6. Focus management APIs (2)
* 6.1.1. Nested browsing contexts (2) (3)
* 6.1.1.1. Navigating nested browsing contexts in the DOM (2)
* 6.3.3. Named access on the Window object
* 6.3.7.1.5. [[GetOwnProperty]] ( P )
* 6.4. Origin
* 6.6.4. The Location interface
* 6.7.1. Navigating across documents (2)
* 7.1.4.2. Processing model (2)
* 10.3.2. The page (2) (3) (4)
#parent-browsing-contextReferenced in:
* 4.2.7. Interactions of styling and scripting (2)
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute
* 5.4.6. Focus management APIs
* 6.1. Browsing contexts
* 6.1.1. Nested browsing contexts (2) (3) (4) (5) (6)
* 6.1.1.1. Navigating nested browsing contexts in the DOM (2)
* 6.1.4. Groupings of browsing contexts
* 6.1.5. Browsing context names (2)
* 6.5. Sandboxing
* 6.6.4. The Location interface (2) (3)
* 8.2.2.2. Determining the character encoding
#child-browsing-contextReferenced in:
* 2.1.5. Plugins
* 4.7.6. The iframe element (2) (3) (4) (5)
* 5.4.6. Focus management APIs
* 6.1.1. Nested browsing contexts (2) (3) (4) (5) (6)
* 6.1.1.1. Navigating nested browsing contexts in the DOM
* 6.1.4. Groupings of browsing contexts
* 6.3.2. Accessing other browsing contexts (2) (3)
* 6.3.3. Named access on the Window object (2)
* 6.3.4. Garbage collection and browsing contexts
* 6.3.7.1.5. [[GetOwnProperty]] ( P )
* 6.7.1. Navigating across documents (2)
* 6.7.12. Aborting a document load
#ancestor-browsing-contextReferenced in:
* 4.7.6. The iframe element
* 6.1.1. Nested browsing contexts (2) (3)
* 6.1.3. Security (2) (3) (4) (5)
* 6.7.1. Navigating across documents
#top-level-browsing-contextReferenced in:
* 4.7.6. The iframe element (2)
* 4.7.13.17. Security and privacy considerations
* 4.8.4. Following hyperlinks
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute (2)
(3) (4) (5)
* 4.15.2. Pseudo-classes
* 5.4.2. Data model (2)
* 5.4.4. Processing model (2)
* 5.4.5. Sequential focus navigation (2) (3) (4) (5) (6)
* 5.4.6. Focus management APIs
* 6.1.1. Nested browsing contexts
* 6.1.1.1. Navigating nested browsing contexts in the DOM (2) (3) (4)
* 6.1.2. Auxiliary browsing contexts (2)
* 6.1.3. Security (2) (3) (4) (5) (6) (7)
* 6.1.5. Browsing context names (2) (3) (4) (5) (6)
* 6.3.1. APIs for creating and navigating browsing contexts by name (2)
(3)
* 6.3.4. Garbage collection and browsing contexts (2) (3)
* 6.3.5. Closing browsing contexts
* 6.5. Sandboxing (2) (3) (4) (5)
* 6.6.2. The History interface (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 6.6.4. The Location interface
* 6.7.1. Navigating across documents (2) (3)
* 6.7.9. Navigating to a fragment
* 6.7.10. History traversal (2)
* 7.1.3.1. Definitions
* 7.1.4.2. Processing model (2) (3) (4) (5)
* 7.4.1. Opening the input stream
* 7.9. Animation Frames
#list-of-the-descendant-browsing-contextsReferenced in:
* 6.1.1. Nested browsing contexts
* 6.7.11. Unloading documents (2)
#fully-activeReferenced in:
* 4.2.4.5. Providing users with a means to follow hyperlinks created
using the link element
* 4.5.1. The a element
* 4.7.7. The embed element
* 4.7.8. The object element (2)
* 4.7.13.8. Playing the media resource (2)
* 4.7.15. The area element
* 4.10.5.1.18. Submit Button state (type=submit)
* 4.10.5.1.19. Image Button state (type=image) (2) (3)
* 4.10.5.1.20. Reset Button state (type=reset)
* 4.10.6. The button element (2)
* 6.1.1. Nested browsing contexts (2)
* 6.6.1. The session history of browsing contexts
* 6.6.2. The History interface (2) (3) (4) (5) (6) (7)
* 7.1.3.4. Calling scripts
* 7.1.4.2. Processing model (2) (3) (4) (5) (6) (7) (8)
* 7.5. Timers
* 11.3.1. The applet element
#delaying-load-events-modeReferenced in:
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 6.7.1. Navigating across documents (2)
* 11.3.3. Frames
#document-familyReferenced in:
* 6.1.1. Nested browsing contexts (2) (3)
* 6.6.2. The History interface
* 6.7.9. Navigating to a fragment
* 6.7.10. History traversal
* 7.4.1. Opening the input stream
#content-documentReferenced in:
* 11.3.3. Frames
#dom-window-topReferenced in:
* 1.9.1. Writing secure applications with HTML
* 6.3. The Window object
#dom-window-parentReferenced in:
* 6.3. The Window object
#dom-window-frameelementReferenced in:
* 6.3. The Window object
#auxiliary-browsing-contextsReferenced in:
* 6.1.2. Auxiliary browsing contexts (2) (3)
* 6.1.3. Security
* 6.1.5. Browsing context names (2)
* 6.3.1. APIs for creating and navigating browsing contexts by name (2)
* 6.5. Sandboxing (2)
* 6.7.10. History traversal
#opener-browsing-contextReferenced in:
* 6.1. Browsing contexts
* 6.1.2.1. Navigating auxiliary browsing contexts in the DOM
* 6.1.3. Security
* 6.1.4. Groupings of browsing contexts (2)
* 6.1.5. Browsing context names
#dom-window-openerReferenced in:
* 4.8.6.8. Link type "noopener"
* 6.1.2.1. Navigating auxiliary browsing contexts in the DOM
* 6.3. The Window object
* 7.1.3.1. Definitions
#disowned-its-openerReferenced in:
* 4.8.4. Following hyperlinks
* 4.8.6. Link types
* 4.8.6.8. Link type "noopener"
* 6.1.2.1. Navigating auxiliary browsing contexts in the DOM
* 6.3.1. APIs for creating and navigating browsing contexts by name
#familiar-withReferenced in:
* 6.1.3. Security (2)
* 6.1.5. Browsing context names (2) (3)
#allowed-to-navigateReferenced in:
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.7.1. Navigating across documents
#browsing-context-scope-originReferenced in:
* 4.7.7. The embed element
* 4.7.8. The object element
* 6.1.3. Security
* 6.7.1. Navigating across documents (2)
#directly-reachable-browsing-contextsReferenced in:
* 6.1.4. Groupings of browsing contexts
#unit-of-related-browsing-contextsReferenced in:
* 6.1.4. Groupings of browsing contexts
* 6.6.2. The History interface
* 7.1.4.1. Definitions
#units-of-related-similar-origin-browsing-contextsReferenced in:
* 6.1.4. Groupings of browsing contexts (2)
* 6.1.6. Script settings for browsing contexts
* 7.1.3.4. Calling scripts
* 7.1.3.5. Realms, settings objects, and global objects
* 7.1.4.1. Definitions (2)
#browsing-context-nameReferenced in:
* 4.7.6. The iframe element (2) (3) (4)
* 4.7.7. The embed element
* 4.7.8. The object element (2) (3) (4)
* 6.1.3. Security
* 6.1.5. Browsing context names
* 6.3.1. APIs for creating and navigating browsing contexts by name (2)
* 6.3.3. Named access on the Window object
* 6.7.10. History traversal (2) (3) (4) (5)
* 11.3.3. Frames (2) (3) (4)
#valid-browsing-context-nameReferenced in:
* 4.7.6. The iframe element
* 4.7.8. The object element
* 6.1.5. Browsing context names
#valid-browsing-context-names-or-keywordsReferenced in:
* 4.2.3. The base element
* 4.8.2. Links created by a and area elements
* 4.10.18.6. Form submission
* Attributes (2) (3) (4) (5)
#allowed-to-show-a-popupReferenced in:
* 4.5.1. The a element
* 4.7.15. The area element
* 4.10.5.1.17. File Upload state (type=file)
* 6.1.5. Browsing context names (2)
* 6.7.1. Navigating across documents
#the-rules-for-choosing-a-browsing-context-given-a-browsing-context-nameReferenced
in:
* 4.5.1. The a element
* 4.7.15. The area element
* 4.8.4. Following hyperlinks (2)
* 4.10.21.3. Form submission algorithm
* 6.1.5. Browsing context names
* 6.3.1. APIs for creating and navigating browsing contexts by name (2)
* 6.5. Sandboxing
#prevents-content-from-creating-new-auxiliary-browsing-contextsReferenced
in:
* 6.5. Sandboxing
#set-up-a-browsing-context-environment-settings-objectReferenced in:
* 6.1. Browsing contexts
* 6.7.1. Navigating across documents
* 7.4.1. Opening the input stream
#crossoriginpropertydescriptormapReferenced in:
* 6.2.2. Shared internal slot: [[CrossOriginPropertyDescriptorMap]]
* 6.2.3.3. CrossOriginGetOwnPropertyHelper ( O, P ) (2)
#crossoriginpropertiesReferenced in:
* 6.2.1. Integration with IDL
* 6.2.3.3. CrossOriginGetOwnPropertyHelper ( O, P )
* 6.2.3.6. CrossOriginOwnPropertyKeys ( O )
#isplatformobjectsameoriginReferenced in:
* 6.2.1. Integration with IDL
* 6.3.7.1.1. [[GetPrototypeOf]] ( )
* 6.3.7.1.5. [[GetOwnProperty]] ( P )
* 6.3.7.1.6. [[DefineOwnProperty]] ( P, Desc )
* 6.3.7.1.7. [[Get]] ( P, Receiver )
* 6.3.7.1.8. [[Set]] ( P, V, Receiver )
* 6.3.7.1.9. [[Delete]] ( P )
* 6.3.7.1.10. [[OwnPropertyKeys]] ( )
* 6.6.4.1.1. [[GetPrototypeOf]] ( )
* 6.6.4.1.5. [[GetOwnProperty]] ( P )
* 6.6.4.1.6. [[DefineOwnProperty]] ( P, Desc )
* 6.6.4.1.7. [[Get]] ( P, Receiver )
* 6.6.4.1.8. [[Set]] ( P, V, Receiver )
* 6.6.4.1.9. [[Delete]] ( P )
* 6.6.4.1.10. [[OwnPropertyKeys]] ( )
#crossorigingetownpropertyhelperReferenced in:
* 6.2.2. Shared internal slot: [[CrossOriginPropertyDescriptorMap]]
* 6.3.7.1.5. [[GetOwnProperty]] ( P )
* 6.6.4.1.5. [[GetOwnProperty]] ( P )
#crossoriginpropertydescriptorReferenced in:
* 6.2.3.3. CrossOriginGetOwnPropertyHelper ( O, P )
#crossoriginfunctionwrapperReferenced in:
* 6.2.3.3.1. CrossOriginPropertyDescriptor ( crossOriginProperty,
originalDesc ) (2) (3)
#cross-origin-wrapper-functionReferenced in:
* 6.2.3.3.2. CrossOriginFunctionWrapper ( needsWrapping, functionToWrap
) (2) (3)
#crossorigingetReferenced in:
* 6.3.7.1.7. [[Get]] ( P, Receiver )
* 6.6.4.1.7. [[Get]] ( P, Receiver )
#crossoriginsetReferenced in:
* 6.3.7.1.8. [[Set]] ( P, V, Receiver )
* 6.6.4.1.8. [[Set]] ( P, V, Receiver )
#crossoriginownpropertykeysReferenced in:
* 6.3.7.1.10. [[OwnPropertyKeys]] ( )
* 6.6.4.1.10. [[OwnPropertyKeys]] ( )
#windowReferenced in:
* 2.7.4. Garbage collection (2)
* 3.2.5. Global attributes
* 4.2.4.3. Obtaining a resource from a link element
* 4.3.1. The body element
* 4.10.10. The option element
* 4.12.1.1. Processing model
* 6.1. Browsing contexts (2) (3) (4) (5) (6)
* 6.1.1.1. Navigating nested browsing contexts in the DOM (2) (3)
* 6.1.2.1. Navigating auxiliary browsing contexts in the DOM (2)
* 6.2.1. Integration with IDL
* 6.2.2. Shared internal slot: [[CrossOriginPropertyDescriptorMap]] (2)
* 6.2.3.1. CrossOriginProperties ( O )
* 6.3. The Window object (2) (3) (4) (5)
* 6.3.2. Accessing other browsing contexts (2) (3)
* 6.3.7. The WindowProxy object (2) (3) (4) (5)
* 6.6.1. The session history of browsing contexts
* 6.6.4. The Location interface (2) (3) (4)
* 6.7.1. Navigating across documents (2)
* 6.7.10. History traversal
* 7.1.3.1. Definitions
* 7.1.3.4. Calling scripts
* 7.1.3.5. Realms, settings objects, and global objects
* 7.1.5.1. Event handlers (2) (3) (4) (5) (6) (7)
* 7.1.5.2. Event handlers on elements, Document objects, and Window
objects (2) (3) (4) (5) (6) (7)
* 7.1.5.3. Event firing
* 7.2. The WindowOrWorkerGlobalScope mixin (2)
* 7.4.1. Opening the input stream (2) (3)
* 7.7.1. The Navigator object
* 7.9. Animation Frames (2)
* 8.2.6. The end (2)
* 11.3.3. Frames (2)
* 11.3.4. Other elements, attributes and APIs (2)
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
* Events (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15)
(16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
* Changes between Working Draft 2 and the First Public Working Draft
#callbackdef-framerequestcallbackReferenced in:
* 6.3. The Window object
#dom-window-windowReferenced in:
* 1.9.1. Writing secure applications with HTML
* 6.3. The Window object
* 6.3.7. The WindowProxy object
#dom-window-framesReferenced in:
* 6.3. The Window object
#dom-window-selfReferenced in:
* 6.3. The Window object
#dom-window-documentReferenced in:
* 1.9. A quick introduction to HTML
* 2.7.4. Garbage collection
* 6.3. The Window object
* 6.7.1. Navigating across documents
#dom-document-defaultviewReferenced in:
* 3.1.1. The Document object
#dom-window-openReferenced in:
* 6.3. The Window object
* 7.4.1. Opening the input stream (2)
#dom-window-nameReferenced in:
* 6.3. The Window object
#dom-window-closeReferenced in:
* 6.3. The Window object
* 6.5. Sandboxing
#script-closableReferenced in:
* 6.3.1. APIs for creating and navigating browsing contexts by name
#dom-window-closedReferenced in:
* 6.3. The Window object
#dom-window-stopReferenced in:
* 6.3. The Window object
#number-of-child-browsing-contextsReferenced in:
* 6.3.2. Accessing other browsing contexts (2)
* 6.3.7.1.5. [[GetOwnProperty]] ( P )
* 6.3.7.1.10. [[OwnPropertyKeys]] ( )
#dom-window-lengthReferenced in:
* 6.3. The Window object
* 6.3.2. Accessing other browsing contexts
#child-browsing-context-name-property-setReferenced in:
* 6.2.3.1. CrossOriginProperties ( O )
* 6.3.3. Named access on the Window object
* 6.3.7.1.5. [[GetOwnProperty]] ( P )
#named-objectsReferenced in:
* 6.3.3. Named access on the Window object (2)
* 6.3.7.1.5. [[GetOwnProperty]] ( P )
#discard-the-documentReferenced in:
* 6.7.11. Unloading documents
#a-browsing-context-is-discardedReferenced in:
* 4.7.6. The iframe element (2)
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.3.4. Garbage collection and browsing contexts (2) (3) (4)
* 6.3.5. Closing browsing contexts
* 6.6.1. The session history of browsing contexts (2)
* 11.3.3. Frames
#close-a-browsing-contextReferenced in:
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.3.5. Closing browsing contexts
#barpropReferenced in:
* 6.3. The Window object (2) (3) (4) (5) (6)
* 7.4.1. Opening the input stream
#dom-barprop-visibleReferenced in:
* 6.3.6. Browser interface elements
#the-location-bar-barprop-objectReferenced in:
* 6.3.6. Browser interface elements
#the-menu-bar-barprop-objectReferenced in:
* 6.3.6. Browser interface elements
#the-personal-bar-barprop-objectReferenced in:
* 6.3.6. Browser interface elements
#the-scrollbar-barprop-objectReferenced in:
* 6.3.6. Browser interface elements
#the-status-bar-barprop-objectReferenced in:
* 6.3.6. Browser interface elements
#the-toolbar-barprop-objectReferenced in:
* 6.3.6. Browser interface elements
#dom-window-locationbarReferenced in:
* 6.3. The Window object
#dom-window-menubarReferenced in:
* 6.3. The Window object
#dom-window-personalbarReferenced in:
* 6.3. The Window object
#dom-window-scrollbarsReferenced in:
* 6.3. The Window object
#dom-window-statusbarReferenced in:
* 6.3. The Window object
#dom-window-toolbarReferenced in:
* 6.3. The Window object
#dom-window-statusReferenced in:
* 6.3. The Window object
#windowproxyReferenced in:
* 3.1.1. The Document object (2)
* 3.1.3. DOM tree accessors
* 4.7.6. The iframe element
* 4.7.8. The object element (2)
* 6.1. Browsing contexts (2) (3)
* 6.1.1.1. Navigating nested browsing contexts in the DOM (2) (3) (4)
(5)
* 6.1.2.1. Navigating auxiliary browsing contexts in the DOM
* 6.2.3.1. CrossOriginProperties ( O )
* 6.3. The Window object (2) (3) (4) (5) (6) (7) (8) (9)
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.3.2. Accessing other browsing contexts
* 6.3.7. The WindowProxy object (2) (3) (4) (5) (6) (7) (8)
* 6.3.7.1. The WindowProxy internal methods
* 6.3.7.1.5. [[GetOwnProperty]] ( P ) (2) (3)
* 6.7.1. Navigating across documents (2)
* 7.1.3.1. Definitions
* 7.4.1. Opening the input stream
* 11.3.3. Frames
#window-slotReferenced in:
* 6.3.7.1.1. [[GetPrototypeOf]] ( )
* 6.3.7.1.5. [[GetOwnProperty]] ( P )
* 6.3.7.1.6. [[DefineOwnProperty]] ( P, Desc )
* 6.3.7.1.7. [[Get]] ( P, Receiver )
* 6.3.7.1.8. [[Set]] ( P, V, Receiver )
* 6.3.7.1.9. [[Delete]] ( P )
* 6.3.7.1.10. [[OwnPropertyKeys]] ( )
#windowproxy-getownpropertyReferenced in:
* 6.3.2. Accessing other browsing contexts
#concept-originReferenced in:
* 2.6.2. Processing model
* 2.9.1. Serializable objects
* 3.1.2. Resource metadata management (2)
* 4.7.5. The img element (2) (3) (4) (5)
* 4.7.6. The iframe element (2) (3)
* 4.7.8. The object element (2) (3)
* 4.8.5. Downloading resources (2)
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute (2)
(3) (4)
* 4.12.1. The script element
* 4.12.4.3. Security with canvas elements
* 6.1. Browsing contexts (2) (3) (4)
* 6.1.1. Nested browsing contexts
* 6.1.1.1. Navigating nested browsing contexts in the DOM (2)
* 6.1.3. Security (2) (3) (4) (5)
* 6.1.4. Groupings of browsing contexts
* 6.1.6. Script settings for browsing contexts (2)
* 6.2.3.2. IsPlatformObjectSameOrigin ( O ) (2)
* 6.2.3.3. CrossOriginGetOwnPropertyHelper ( O, P ) (2)
* 6.2.3.3.2. CrossOriginFunctionWrapper ( needsWrapping, functionToWrap
)
* 6.4. Origin (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14)
(15) (16)
* 6.4.1. Relaxing the same-origin restriction (2) (3)
* 6.5. Sandboxing
* 6.6.2. The History interface
* 6.6.4. The Location interface (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24)
(25) (26) (27) (28) (29) (30) (31) (32) (33) (34) (35) (36) (37) (38)
(39) (40)
* 6.7.1. Navigating across documents (2) (3) (4) (5) (6)
* 6.7.10. History traversal (2)
* 7.1.3.1. Definitions
* 7.4.1. Opening the input stream (2)
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods (2)
* 7.8. Images (2) (3) (4) (5) (6) (7)
* 8.2.2.2. Determining the character encoding (2)
* 10.3.2. The page
* 12.1. text/html (2)
#opaque-originReferenced in:
* 3.1.2. Resource metadata management (2)
* 6.1. Browsing contexts
* 6.4. Origin (2) (3) (4) (5) (6) (7) (8) (9)
* 6.4.1. Relaxing the same-origin restriction
#tuple-originReferenced in:
* 6.4. Origin (2) (3) (4) (5)
#origin-schemeReferenced in:
* 6.4. Origin (2) (3) (4)
#origin-hostReferenced in:
* 6.4. Origin (2) (3) (4)
* 6.4.1. Relaxing the same-origin restriction
#origin-portReferenced in:
* 6.4. Origin (2) (3) (4)
#origin-domainReferenced in:
* 6.4. Origin (2) (3) (4) (5)
* 6.4.1. Relaxing the same-origin restriction (2)
#effective-domainReferenced in:
* 6.2.3.3. CrossOriginGetOwnPropertyHelper ( O, P ) (2)
* 6.4.1. Relaxing the same-origin restriction (2)
#forces-content-into-a-unique-originReferenced in:
* 6.5. Sandboxing
#unicode-serializationReferenced in:
* 4.8.3. API for a and area elements
* 6.4. Origin
* 6.6.4. The Location interface (2)
#ascii-serialization-of-an-originReferenced in:
* 6.4. Origin (2)
#same-originReferenced in:
* 2.6.2. Processing model
* 4.7.5. The img element (2) (3) (4)
* 4.7.6. The iframe element
* 4.7.13.5. Loading the media resource (2) (3)
* 4.8.5. Downloading resources
* 4.8.6.11. Link type "stylesheet" (2)
* 6.1.3. Security (2)
* 6.4. Origin (2) (3) (4)
* 6.6.4. The Location interface
* 6.7.1. Navigating across documents (2) (3) (4) (5)
* 6.7.10. History traversal (2)
* 7.1.3.2. Fetching scripts (2)
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods
* 7.8. Images (2)
* 8.2.2.2. Determining the character encoding
* Events
#same-origin-domainReferenced in:
* 4.7.6. The iframe element
* 4.7.8. The object element
* 6.1.1. Nested browsing contexts
* 6.1.1.1. Navigating nested browsing contexts in the DOM
* 6.1.4. Groupings of browsing contexts
* 6.2.3.2. IsPlatformObjectSameOrigin ( O )
* 6.4. Origin
* 6.6.4. The Location interface (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16) (17) (18)
#dom-document-domainReferenced in:
* 3.1.1. The Document object
* 6.1.4. Groupings of browsing contexts
* 6.2.2. Shared internal slot: [[CrossOriginPropertyDescriptorMap]] (2)
(3)
* 6.4. Origin
* 6.4.1. Relaxing the same-origin restriction (2) (3) (4) (5)
* 6.5. Sandboxing
#sandboxing-flag-setReferenced in:
* 6.5. Sandboxing (2) (3) (4) (5) (6)
#sandboxed-navigation-browsing-context-flagReferenced in:
* 6.1.3. Security (2)
* 6.1.5. Browsing context names
* 6.5. Sandboxing (2) (3)
#one-permitted-sandboxed-navigatorReferenced in:
* 4.8.4. Following hyperlinks
* 6.1.3. Security
* 6.1.5. Browsing context names (2) (3)
* 6.3.1. APIs for creating and navigating browsing contexts by name
#sandboxed-auxiliary-navigation-browsing-context-flagReferenced in:
* 6.1.5. Browsing context names
* 6.5. Sandboxing (2) (3) (4)
#sandboxed-top-level-navigation-browsing-context-flagReferenced in:
* 6.1.3. Security
* 6.5. Sandboxing (2) (3)
#sandboxed-plugins-browsing-context-flagReferenced in:
* 4.7.7. The embed element
* 4.7.8. The object element
* 6.5. Sandboxing
* 6.7.7. Page load processing model for content that uses plugins
* 11.3.1. The applet element
#sandboxed-into-a-unique-originReferenced in:
* 3.1.2. Resource metadata management
* 6.4. Origin
* 6.5. Sandboxing
#sandboxed-forms-browsing-context-flagReferenced in:
* 4.10.21.3. Form submission algorithm
* 6.5. Sandboxing
#sandboxed-pointer-lock-browsing-context-flagReferenced in:
* 6.5. Sandboxing
#sandboxed-scripts-browsing-context-flagReferenced in:
* 6.5. Sandboxing
* 7.1.2. Enabling and disabling scripting
#sandboxed-automatic-features-browsing-context-flagReferenced in:
* 4.2.5.3. Pragma directives
* 4.7.13.7. Ready states
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute
* 6.5. Sandboxing
#sandboxed-storage-area-urls-flagReferenced in:
* 6.5. Sandboxing
#sandboxed-fullscreen-browsing-context-flagReferenced in:
* 6.5. Sandboxing
* 6.7.1. Navigating across documents
#sandboxed-documentdomain-browsing-context-flagReferenced in:
* 6.4.1. Relaxing the same-origin restriction
* 6.5. Sandboxing
#sandbox-propagates-to-auxiliary-browsing-contexts-flagReferenced in:
* 6.1.5. Browsing context names
* 6.5. Sandboxing
#sandboxed-modals-flagReferenced in:
* 6.5. Sandboxing
* 6.7.11. Unloading documents
* 7.6.1. Simple dialogs (2) (3)
* 7.6.2. Printing
#sandboxed-presentation-browsing-context-flagReferenced in:
* 6.5. Sandboxing
#parse-the-sandboxing-directiveReferenced in:
* 4.7.6. The iframe element
* 6.5. Sandboxing
#popup-sandboxing-flag-setReferenced in:
* 6.1.5. Browsing context names
* 6.5. Sandboxing (2)
#iframe-sandboxing-flag-setReferenced in:
* 6.5. Sandboxing (2)
#active-sandboxing-flag-setReferenced in:
* 4.2.5.3. Pragma directives
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.13.7. Ready states
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute
* 4.10.21.3. Form submission algorithm
* 6.1.3. Security (2) (3)
* 6.1.5. Browsing context names (2)
* 6.4. Origin
* 6.4.1. Relaxing the same-origin restriction
* 6.5. Sandboxing (2) (3) (4)
* 6.7.1. Navigating across documents
* 6.7.7. Page load processing model for content that uses plugins
* 6.7.11. Unloading documents
* 7.1.2. Enabling and disabling scripting
* 7.6.1. Simple dialogs (2) (3)
* 7.6.2. Printing
* 11.3.1. The applet element
#forced-sandboxing-flag-setReferenced in:
* 6.5. Sandboxing (2) (3)
#implement-the-sandboxingReferenced in:
* 6.1. Browsing contexts
* 6.7.1. Navigating across documents
#session-historyReferenced in:
* 4.7.6. The iframe element
* 6.1. Browsing contexts (2) (3)
* 6.1.1. Nested browsing contexts
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.3.6. Browser interface elements
* 6.6.1. The session history of browsing contexts (2) (3)
* 6.6.2. The History interface (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 6.6.4. The Location interface
* 6.7.1. Navigating across documents (2)
* 6.7.9. Navigating to a fragment
* 7.4.1. Opening the input stream (2)
* 11.3.3. Frames
* Events (2) (3)
#session-history-entryReferenced in:
* 2.9.9. Performing serialization and transferring from other
specifications
* 6.6.1. The session history of browsing contexts (2) (3) (4)
* 6.6.2. The History interface (2)
* 6.7.10.3. The HashChangeEvent interface (2) (3) (4)
#dom-window-historyReferenced in:
* 6.3. The Window object
* 6.6.3. Implementation notes for session history (2) (3)
* 6.6.4. The Location interface
#serialized-stateReferenced in:
* 2.9.9. Performing serialization and transferring from other
specifications
* 6.6.1. The session history of browsing contexts (2) (3) (4) (5) (6)
* 6.6.2. The History interface (2) (3)
* 6.7.10. History traversal
#current-entryReferenced in:
* 6.6.1. The session history of browsing contexts (2) (3)
* 6.6.2. The History interface (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13)
* 6.6.4. The Location interface
* 6.7.1. Navigating across documents (2) (3) (4) (5)
* 6.7.9. Navigating to a fragment (2)
* 6.7.10. History traversal (2) (3) (4) (5) (6) (7) (8)
* 7.4.1. Opening the input stream (2)
* Events (2)
#an-entry-with-persisted-user-stateReferenced in:
* 6.6.2. The History interface
* 6.7.10. History traversal (2) (3)
#scroll-restoration-modeReferenced in:
* 6.6.1. The session history of browsing contexts (2)
* 6.6.2. The History interface (2) (3) (4) (5) (6)
* 6.7.1. Navigating across documents
* 6.7.10.1. Persisted user state restoration
#latest-entryReferenced in:
* 6.6.1. The session history of browsing contexts
* 6.6.2. The History interface
* 6.7.10. History traversal (2)
#enumdef-scrollrestorationReferenced in:
* 6.6.2. The History interface
#historyReferenced in:
* 6.3. The Window object
* 6.6.2. The History interface (2) (3)
* 6.6.3. Implementation notes for session history
* 7.4.1. Opening the input stream
#dom-history-pushstateReferenced in:
* 3.1. Documents
* 6.6.1. The session history of browsing contexts
* 6.6.2. The History interface
* 6.6.3. Implementation notes for session history (2)
#dom-history-replacestateReferenced in:
* 6.6.2. The History interface
* 6.6.3. Implementation notes for session history
#joint-session-historyReferenced in:
* 6.6.2. The History interface (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
#current-entry-of-the-joint-session-historyReferenced in:
* 6.6.2. The History interface (2) (3)
#dom-history-lengthReferenced in:
* 6.6.2. The History interface
#dom-history-scrollrestorationReferenced in:
* 6.6.2. The History interface
#dom-history-stateReferenced in:
* 6.6.2. The History interface (2)
#dom-history-goReferenced in:
* 6.6.2. The History interface
#dom-history-backReferenced in:
* 6.6.2. The History interface
* 7.1.4.3. Generic task sources
#dom-history-forwardReferenced in:
* 6.6.2. The History interface
#session-history-traversal-queueReferenced in:
* 6.6.2. The History interface (2) (3)
#session-history-event-loopReferenced in:
* 6.6.2. The History interface
#explicitly-going-back-or-forwards-in-the-session-historyReferenced in:
* 6.6.2. The History interface (2) (3) (4)
* 6.7.1. Navigating across documents
* 6.7.10. History traversal
#doesnt-necessarily-have-to-affectReferenced in:
* 6.6.2. The History interface
* 6.7.1. Navigating across documents
* 6.7.9. Navigating to a fragment
* 7.4.1. Opening the input stream
#dom-document-locationReferenced in:
* 3.1.1. The Document object
* 6.6.4. The Location interface
#dom-window-locationReferenced in:
* 6.3. The Window object
* 6.6.4. The Location interface
#locationReferenced in:
* 3.1.1. The Document object
* 6.2. Security infrastructure for Window, WindowProxy, and Location
objects
* 6.2.1. Integration with IDL
* 6.2.2. Shared internal slot: [[CrossOriginPropertyDescriptorMap]] (2)
* 6.2.3.1. CrossOriginProperties ( O ) (2)
* 6.3. The Window object
* 6.3.7. The WindowProxy object
* 6.6.4. The Location interface (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24)
(25) (26) (27) (28) (29) (30) (31) (32) (33) (34) (35) (36) (37) (38)
(39) (40) (41) (42) (43) (44) (45) (46) (47) (48) (49) (50) (51) (52)
(53) (54) (55) (56) (57) (58) (59) (60) (61) (62) (63) (64) (65)
* 6.6.4.1. The Location internal methods (2) (3)
#relevant-documentReferenced in:
* 6.6.4. The Location interface (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22)
#ancestor-origins-arrayReferenced in:
* 6.6.4. The Location interface (2)
#location-object-setter-navigateReferenced in:
* 6.6.4. The Location interface (2) (3) (4) (5) (6) (7) (8)
#location-object-navigateReferenced in:
* 6.6.4. The Location interface (2) (3)
#dom-location-hrefReferenced in:
* 3.1.1. The Document object
* 6.3. The Window object
* 6.6.4. The Location interface (2) (3) (4)
#dom-location-originReferenced in:
* 6.6.4. The Location interface (2)
#dom-location-protocolReferenced in:
* 6.6.4. The Location interface (2) (3)
#dom-location-hostReferenced in:
* 6.6.4. The Location interface (2) (3)
#dom-location-hostnameReferenced in:
* 6.6.4. The Location interface (2) (3)
#dom-location-portReferenced in:
* 6.6.4. The Location interface (2) (3)
#dom-location-pathnameReferenced in:
* 6.6.4. The Location interface (2) (3)
#dom-location-searchReferenced in:
* 6.6.4. The Location interface (2) (3)
#dom-location-hashReferenced in:
* 6.6.4. The Location interface (2) (3) (4)
#dom-location-assignReferenced in:
* 6.6.4. The Location interface (2)
#dom-location-replaceReferenced in:
* 6.6.4. The Location interface (2) (3)
#dom-location-reloadReferenced in:
* 6.6.4. The Location interface (2)
#dom-location-ancestororiginsReferenced in:
* 6.6.4. The Location interface (2)
#defaultpropertiesReferenced in:
* 6.6.4. The Location interface
* 6.6.4.1.5. [[GetOwnProperty]] ( P )
* 6.6.4.1.6. [[DefineOwnProperty]] ( P, Desc )
#source-browsing-contextReferenced in:
* 2.6.2. Processing model
* 3.1. Documents (2)
* 4.2.5.3. Pragma directives (2)
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.8.4. Following hyperlinks
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.6.4. The Location interface (2) (3)
* 6.7.1. Navigating across documents (2) (3) (4) (5) (6) (7)
* 6.7.10. History traversal
* 8.2.2.4. Changing the encoding while parsing
* 11.3.3. Frames
#navigatedReferenced in:
* 2.2.4. Interactions with XPath and XSLT
* 2.6.2. Processing model (2)
* 3.1. Documents (2) (3) (4)
* 4.2.3. The base element (2)
* 4.2.5.3. Pragma directives (2)
* 4.5.1. The a element
* 4.7.6. The iframe element (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.15. The area element
* 4.8.1. Introduction
* 4.8.2. Links created by a and area elements (2)
* 4.8.4. Following hyperlinks (2)
* 4.8.5. Downloading resources (2)
* 4.10.21.3. Form submission algorithm
* 4.11.3.1. Facets
* 6.1. Browsing contexts
* 6.1.1. Nested browsing contexts
* 6.1.5. Browsing context names (2) (3)
* 6.3. The Window object
* 6.3.1. APIs for creating and navigating browsing contexts by name (2)
(3) (4)
* 6.3.7. The WindowProxy object
* 6.4. Origin (2) (3)
* 6.5. Sandboxing (2) (3) (4) (5)
* 6.6.2. The History interface
* 6.6.4. The Location interface (2) (3)
* 6.7.1. Navigating across documents (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16)
* 6.7.3. Page load processing model for XML files
* 6.7.4. Page load processing model for text files (2)
* 6.7.5. Page load processing model for multipart/x-mixed-replace
resources (2)
* 6.7.6. Page load processing model for media
* 6.7.7. Page load processing model for content that uses plugins
* 6.7.9. Navigating to a fragment (2)
* 6.7.10. History traversal (2) (3)
* 7.1.3.1. Definitions
* 7.1.4.1. Definitions
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods (2) (3)
* 8.2.2.4. Changing the encoding while parsing
* 10.7.1. Links, forms, and navigation (2) (3)
* 11.3.3. Frames (2) (3) (4) (5)
* Attributes (2)
#exceptions-enabled-flagReferenced in:
* 3.1. Documents
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.6.4. The Location interface (2)
#the-step-labeled-fragmentsReferenced in:
* 6.7.1. Navigating across documents (2)
#reload-triggered-navigationReferenced in:
* 6.6.4. The Location interface
#javascript-urlsReferenced in:
* 6.4. Origin
* 6.7.1. Navigating across documents (2)
* 7.1.1. Introduction
#explicitly-supported-xml-typeReferenced in:
* 6.7.1. Navigating across documents
#json-mime-typeReferenced in:
* 6.7.1. Navigating across documents
#explicitly-supported-json-typeReferenced in:
* 6.7.1. Navigating across documents
#set-the-documents-addressReferenced in:
* 3.1. Documents
* 6.7.1. Navigating across documents
#override-urlReferenced in:
* 3.1. Documents
* 6.7.1. Navigating across documents (2) (3)
#proceed-with-that-mechanism-insteadReferenced in:
* 6.7.1. Navigating across documents (2)
#updating-the-session-history-with-the-new-pageReferenced in:
* 6.7.1. Navigating across documents
* 6.7.2. Page load processing model for HTML files
* 6.7.3. Page load processing model for XML files
* 6.7.4. Page load processing model for text files
* 6.7.6. Page load processing model for media
* 6.7.7. Page load processing model for content that uses plugins
* 6.7.8. Page load processing model for inline content that doesn’t have
a DOM
* 6.7.9. Navigating to a fragment
* 6.7.10. History traversal
#entry-updateReferenced in:
* 6.7.10. History traversal
#maturedReferenced in:
* 6.6.2. The History interface
* 6.7.1. Navigating across documents (2)
#plain-text-fileReferenced in:
* 6.7.1. Navigating across documents
#plugin-documentReferenced in:
* 6.7.7. Page load processing model for content that uses plugins
#display-the-inline-contentReferenced in:
* 6.7.1. Navigating across documents (2)
#navigate-fragmentReferenced in:
* 6.7.1. Navigating across documents
#scroll-to-the-fragmentReferenced in:
* 6.7.1. Navigating across documents
* 6.7.9. Navigating to a fragment
* 6.7.10. History traversal
#an-indicated-part-of-the-documentReferenced in:
* 6.7.1. Navigating across documents
* 6.7.9. Navigating to a fragment (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 12.1. text/html
#target-elementReferenced in:
* 4.15.2. Pseudo-classes
* 5.7.6. Events summary
* 6.7.9. Navigating to a fragment
#traverse-the-historyReferenced in:
* 4.10.18.7.2. Processing model
* 6.6.1. The session history of browsing contexts
* 6.6.2. The History interface (2)
* 6.7.1. Navigating across documents (2)
* 6.7.9. Navigating to a fragment
#gets-resetReferenced in:
* 6.3.1. APIs for creating and navigating browsing contexts by name
#values-are-resetReferenced in:
* 4.10.18.7.2. Processing model
#replacement-must-be-enabledReferenced in:
* 3.1. Documents
* 4.2.5.3. Pragma directives
* 4.7.6. The iframe element (2)
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.8.4. Following hyperlinks
* 4.10.21.3. Form submission algorithm
* 6.1. Browsing contexts
* 6.1.5. Browsing context names (2)
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.6.4. The Location interface (2) (3)
* 6.7.1. Navigating across documents (2) (3) (4)
* 6.7.5. Page load processing model for multipart/x-mixed-replace
resources
* 6.7.10. History traversal (2)
* 8.2.2.4. Changing the encoding while parsing
* 11.3.3. Frames (2)
#restore-persisted-user-stateReferenced in:
* 6.7.10. History traversal
#popstateeventReferenced in:
* Events
#dictdef-popstateeventinitReferenced in:
* 6.7.10.2. The PopStateEvent interface
#dom-popstateevent-stateReferenced in:
* 6.7.10.2. The PopStateEvent interface
#hashchangeeventReferenced in:
* 6.7.10. History traversal
* Events
#dictdef-hashchangeeventinitReferenced in:
* 6.7.10.3. The HashChangeEvent interface
#dom-hashchangeevent-oldurlReferenced in:
* 6.7.10.3. The HashChangeEvent interface
#dom-hashchangeevent-newurlReferenced in:
* 6.7.10.3. The HashChangeEvent interface
#pagetransitioneventReferenced in:
* 8.2.6. The end
* Events (2)
#dictdef-pagetransitioneventinitReferenced in:
* 6.7.10.4. The PageTransitionEvent interface
#dom-pagetransitionevent-persistedReferenced in:
* 6.7.10. History traversal
* 6.7.10.4. The PageTransitionEvent interface (2)
* 6.7.11. Unloading documents
* 8.2.6. The end
#fired-unloadReferenced in:
* 6.7.11. Unloading documents (2)
* 7.4.1. Opening the input stream
#page-showingReferenced in:
* 6.7.10. History traversal (2)
* 6.7.11. Unloading documents (2) (3)
* 8.2.6. The end (2)
#termination-nesting-levelReferenced in:
* 6.7.11. Unloading documents (2) (3) (4)
* 7.6.1. Simple dialogs (2) (3)
#prompt-to-unloadReferenced in:
* 6.3.5. Closing browsing contexts
* 6.6.2. The History interface
* 6.7.1. Navigating across documents (2) (3) (4)
* 6.7.11. Unloading documents
* 7.4.1. Opening the input stream
#refused-to-allow-the-document-to-be-unloadedReferenced in:
* 6.3.5. Closing browsing contexts
* 6.6.2. The History interface
* 6.7.1. Navigating across documents
* 6.7.11. Unloading documents (2)
* 7.4.1. Opening the input stream
* 7.4.3. document.write()
#unloadedReferenced in:
* 4.7.6. The iframe element
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.3.5. Closing browsing contexts
* 6.6.2. The History interface (2)
* 6.7.1. Navigating across documents (2) (3) (4) (5) (6)
* 6.7.11. Unloading documents
* 7.4.1. Opening the input stream (2) (3)
#unloading-document-visibility-change-stepsReferenced in:
* 6.7.11. Unloading documents
#unloading-document-cleanup-stepsReferenced in:
* 6.3.4. Garbage collection and browsing contexts
* 6.7.11. Unloading documents
#beforeunloadeventReferenced in:
* 7.1.5.1. Event handlers
* Events
#dom-beforeunloadevent-returnvalueReferenced in:
* 6.7.11. Unloading documents (2)
* 6.7.11.1. The BeforeUnloadEvent interface (2)
* 7.1.5.1. Event handlers (2)
#abort-the-documentReferenced in:
* 3.1.2. Resource metadata management
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.3.4. Garbage collection and browsing contexts
* 6.7.1. Navigating across documents (2)
* 6.7.10.4. The PageTransitionEvent interface
* 6.7.12. Aborting a document load (2) (3)
* 7.4.1. Opening the input stream
* 9.2. Parsing XML documents
#navigatoronlineReferenced in:
* 7.7.1. The Navigator object
#dom-navigatoronline-onlineReferenced in:
* 6.7.13. Browser state
#scripting-was-enabledReferenced in:
* 4.7.5. The img element
* 4.12.2. The noscript element (2) (3) (4)
* 4.12.4. The canvas element
* 6.5. Sandboxing
* 7.1.2. Enabling and disabling scripting
* 7.1.5.1. Event handlers
* 8.2.3.5. Other parsing state flags
* 8.3. Serializing HTML fragments
#scripting-is-disabledReferenced in:
* 4.7.5. The img element
* 4.7.13.13. User interface
* 4.12.1.1. Processing model (2)
* 4.12.1.5. Interaction of script elements and XSLT
* 4.12.2. The noscript element (2) (3) (4) (5)
* 4.12.4. The canvas element
* 6.7.1. Navigating across documents
* 7.1.2. Enabling and disabling scripting
* 7.1.3.3. Creating scripts (2)
* 7.1.3.4. Calling scripts
#concept-scriptReferenced in:
* 3.1. Documents
* 4.7.5. The img element
* 4.12.1. The script element (2)
* 6.3.4. Garbage collection and browsing contexts
* 6.4. Origin
* 7.1.3.1. Definitions
* 7.1.3.9. Runtime script errors
* 7.1.3.9.1. Runtime script errors in documents
* 7.1.4.1. Definitions
* 7.1.5.1. Event handlers
* 10.9. Unstyled XML documents
#settings-objectReferenced in:
* 6.3.4. Garbage collection and browsing contexts
* 7.1.3.2. Fetching scripts
* 7.1.3.3. Creating scripts (2)
* 7.1.3.4. Calling scripts (2)
* 7.1.3.5.2. Incumbent
* 7.1.3.7.1. EnqueueJob(queueName, job, arguments)
* 7.1.3.8.1. HostResolveImportedModule(referencingModule, specifier)
* 7.1.3.9.1. Runtime script errors in documents
* 7.1.3.10.1. The HostPromiseRejectionTracker implementation
* 7.1.4.1. Definitions
* 10.9. Unstyled XML documents
#classic-scriptReferenced in:
* 3.1.3. DOM tree accessors
* 4.12.1. The script element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.12.1.1. Processing model
* 4.12.1.3. Restrictions for contents of script elements
* 7.1.3.2. Fetching scripts (2)
* 7.1.3.3. Creating scripts
* 7.1.3.4. Calling scripts
* 7.1.3.8. Integration with the JavaScript module system
#source-textReferenced in:
* 7.1.3.3. Creating scripts (2)
* 7.1.3.4. Calling scripts
#muted-errorsReferenced in:
* 7.1.3.3. Creating scripts
* 7.1.3.4. Calling scripts (2)
* 7.1.3.9. Runtime script errors
* 7.1.3.10.1. The HostPromiseRejectionTracker implementation
#module-scriptReferenced in:
* 3.1.3. DOM tree accessors (2)
* 4.12.1. The script element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12)
* 7.1.3.2. Fetching scripts (2) (3) (4) (5)
* 7.1.3.3. Creating scripts
* 7.1.3.4. Calling scripts
* 7.1.3.8. Integration with the JavaScript module system (2) (3)
#module-recordReferenced in:
* 7.1.3.2. Fetching scripts
* 7.1.3.3. Creating scripts
* 7.1.3.4. Calling scripts
* 7.1.3.8.1. HostResolveImportedModule(referencingModule, specifier)
#base-urlReferenced in:
* 6.1. Browsing contexts
* 7.1.3.2. Fetching scripts
* 7.1.3.3. Creating scripts
* 7.1.3.8. Integration with the JavaScript module system
#cryptographic-nonceReferenced in:
* 7.1.3.1. Definitions
* 7.1.3.2. Fetching scripts
* 7.1.3.3. Creating scripts
#parser-stateReferenced in:
* 7.1.3.2. Fetching scripts
* 7.1.3.3. Creating scripts
#environment-settings-objectReferenced in:
* 4.2.4.3. Obtaining a resource from a link element
* 4.7.5. The img element (2)
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.10. The video element
* 4.7.13.5. Loading the media resource
* 4.7.13.11.3. Sourcing out-of-band text tracks
* 4.8.6.5. Link type "icon"
* 4.10.5.1.19. Image Button state (type=image)
* 4.12.1.1. Processing model
* 6.1.6. Script settings for browsing contexts
* 6.3.4. Garbage collection and browsing contexts
* 6.7.1. Navigating across documents
* 7.1.3.1. Definitions (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 7.1.3.3. Creating scripts (2) (3) (4) (5) (6) (7)
* 7.1.3.4. Calling scripts (2) (3)
* 7.1.3.5. Realms, settings objects, and global objects (2) (3) (4) (5)
(6)
* 7.1.3.5.1. Entry
* 7.1.3.5.3. Current
* 7.1.3.5.4. Relevant (2)
* 7.1.3.10. Unhandled promise rejections
* 7.1.4.2. Processing model (2)
* 7.1.5.1. Event handlers
* 7.5. Timers (2)
#realm-execution-contextReferenced in:
* 6.1.6. Script settings for browsing contexts
* 7.1.3.4. Calling scripts (2) (3) (4) (5)
* 7.1.3.5. Realms, settings objects, and global objects
* 7.1.3.5.1. Entry
#responsible-browsing-contextReferenced in:
* 6.1.6. Script settings for browsing contexts
* 6.3.1. APIs for creating and navigating browsing contexts by name (2)
(3)
* 6.3.4. Garbage collection and browsing contexts
* 6.6.4. The Location interface (2)
* 7.1.3.1. Definitions
* 7.1.3.3. Creating scripts (2)
* 7.1.3.4. Calling scripts
* 7.6.1. Simple dialogs (2) (3)
* 7.6.2. Printing
#responsible-event-loopReferenced in:
* 6.1.6. Script settings for browsing contexts
* 7.1.3.1. Definitions
* 7.1.3.7.1. EnqueueJob(queueName, job, arguments)
* 7.1.4.2. Processing model
#responsible-documentReferenced in:
* 6.1.6. Script settings for browsing contexts
* 6.3.4. Garbage collection and browsing contexts
* 6.6.2. The History interface
* 7.1.3.1. Definitions (2) (3)
* 7.1.4.1. Definitions
* 7.4.1. Opening the input stream (2)
* 10.9. Unstyled XML documents
#api-url-character-encodingReferenced in:
* 2.5.2. Parsing URLs
* 6.1.6. Script settings for browsing contexts
#api-base-urlReferenced in:
* 2.5.2. Parsing URLs
* 6.1.6. Script settings for browsing contexts
* 7.1.3.5. Realms, settings objects, and global objects
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods (2)
#security-originReferenced in:
* 6.1.1. Nested browsing contexts
#creation-urlReferenced in:
* 6.1.6. Script settings for browsing contexts
#settings-https-stateReferenced in:
* 6.1.6. Script settings for browsing contexts
* 6.7.1. Navigating across documents
#outstanding-rejected-promises-weak-setReferenced in:
* 7.1.3.1. Definitions
* 7.1.3.10. Unhandled promise rejections
* 7.1.3.10.1. The HostPromiseRejectionTracker implementation (2)
#about-to-be-notified-rejected-promises-listReferenced in:
* 7.1.3.10. Unhandled promise rejections (2)
* 7.1.3.10.1. The HostPromiseRejectionTracker implementation (2)
#set-up-the-requestReferenced in:
* 7.1.3.2. Fetching scripts (2) (3) (4) (5)
#process-the-responseReferenced in:
* 7.1.3.2. Fetching scripts (2) (3) (4) (5)
#fetching-a-classic-scriptReferenced in:
* 4.12.1.1. Processing model
* 7.1.3.2. Fetching scripts
#fetching-a-module-script-treeReferenced in:
* 4.12.1.1. Processing model
* 7.1.3.2. Fetching scripts (2) (3) (4)
#fetching-the-descendants-of-a-module-scriptReferenced in:
* 4.12.1.1. Processing model
* 7.1.3.2. Fetching scripts (2)
#fetching-a-single-module-scriptReferenced in:
* 7.1.3.2. Fetching scripts (2) (3)
#create-a-scriptReferenced in:
* 7.5. Timers
#create-a-classic-scriptReferenced in:
* 4.12.1.1. Processing model
* 6.7.1. Navigating across documents
* 7.1.3.2. Fetching scripts (2) (3)
#creating-a-module-scriptReferenced in:
* 4.12.1.1. Processing model
* 7.1.3.2. Fetching scripts
#run-a-classic-scriptReferenced in:
* 4.12.1.1. Processing model
* 6.7.1. Navigating across documents
* 7.1.3.1. Definitions
* 7.1.3.5.1. Entry
#run-a-module-scriptReferenced in:
* 4.12.1.1. Processing model
* 7.1.3.1. Definitions
#check-if-we-can-run-scriptReferenced in:
* 7.1.3.4. Calling scripts (2)
* 7.1.3.7.1. EnqueueJob(queueName, job, arguments)
#prepare-to-run-scriptReferenced in:
* 2.9.9. Performing serialization and transferring from other
specifications (2)
* 7.1.3.4. Calling scripts (2)
* 7.1.3.7.1. EnqueueJob(queueName, job, arguments)
#clean-up-after-running-scriptReferenced in:
* 7.1.3.4. Calling scripts (2)
* 7.1.3.7.1. EnqueueJob(queueName, job, arguments)
* 7.1.4.2. Processing model
#running-scriptReferenced in:
* 7.1.3.10.1. The HostPromiseRejectionTracker implementation
#global-script-clean-up-jobs-listReferenced in:
* 7.1.3.4. Calling scripts
#run-the-global-script-clean-up-jobsReferenced in:
* 7.1.3.4. Calling scripts
* 7.1.4.2. Processing model
#global-objectReferenced in:
* 4.12.1. The script element
* 6.1.6. Script settings for browsing contexts
* 6.3.4. Garbage collection and browsing contexts
* 6.3.7. The WindowProxy object
* 6.6.4. The Location interface
* 7.1.3.4. Calling scripts
* 7.1.3.5. Realms, settings objects, and global objects (2) (3) (4) (5)
(6)
* 7.1.3.5.1. Entry
* 7.1.3.5.2. Incumbent
* 7.1.3.5.3. Current
* 7.1.3.5.4. Relevant (2) (3) (4)
* 7.1.3.9.1. Runtime script errors in documents
* 7.1.3.10. Unhandled promise rejections
* 7.1.3.10.1. The HostPromiseRejectionTracker implementation
* 7.1.5.1. Event handlers
#entryReferenced in:
* 2.9.9. Performing serialization and transferring from other
specifications
* 7.1.3.5. Realms, settings objects, and global objects (2) (3) (4)
#incumbentReferenced in:
* 2.9.9. Performing serialization and transferring from other
specifications
* 7.1.3.5. Realms, settings objects, and global objects (2) (3) (4)
#currentReferenced in:
* 7.1.3.5. Realms, settings objects, and global objects (2) (3)
#relevantReferenced in:
* 7.1.3.5. Realms, settings objects, and global objects (2) (3)
#entrance-counterReferenced in:
* 7.1.3.4. Calling scripts (2)
* 7.1.3.5.1. Entry
#entry-execution-contextReferenced in:
* 7.1.3.5.1. Entry
#entry-realmReferenced in:
* 7.1.3.5. Realms, settings objects, and global objects
* 7.1.3.5.1. Entry (2)
#entry-settings-objectReferenced in:
* 4.5.1. The a element
* 4.7.15. The area element
* 6.1.1.1. Navigating nested browsing contexts in the DOM
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.6.2. The History interface (2)
* 6.6.4. The Location interface (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22)
* 7.4.1. Opening the input stream (2)
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods (2) (3)
(4) (5)
* 7.8. Images (2)
#incumbent-settings-objectReferenced in:
* 4.7.6. The iframe element
* 4.7.8. The object element
* 6.3.1. APIs for creating and navigating browsing contexts by name (2)
* 6.4. Origin
* 6.6.4. The Location interface
* 7.1.3.5.2. Incumbent (2) (3)
* 7.6.1. Simple dialogs (2) (3)
* 7.6.2. Printing
#incumbent-realmReferenced in:
* 7.1.3.5. Realms, settings objects, and global objects
#current-settings-objectReferenced in:
* 6.1.1. Nested browsing contexts
* 6.2.3.2. IsPlatformObjectSameOrigin ( O )
* 6.2.3.3. CrossOriginGetOwnPropertyHelper ( O, P )
#relevant-settings-objectReferenced in:
* 6.1. Browsing contexts
* 6.2.3.2. IsPlatformObjectSameOrigin ( O )
* 6.6.2. The History interface (2)
* 6.7.1. Navigating across documents
* 7.1.3.5. Realms, settings objects, and global objects
* 7.1.3.5.4. Relevant (2) (3) (4)
* 8.2.6. The end
#relevant-realmReferenced in:
* 7.1.3.5. Realms, settings objects, and global objects (2) (3) (4) (5)
(6)
#abort-a-running-scriptReferenced in:
* 7.1.3.4. Calling scripts (2) (3)
* 7.1.3.6. Killing scripts
#module-mapReferenced in:
* 3.1.1. The Document object
* 6.1.6. Script settings for browsing contexts
* 7.1.3.1. Definitions
* 7.1.3.2. Fetching scripts (2)
* 7.1.3.8. Integration with the JavaScript module system
* 7.1.3.8.1. HostResolveImportedModule(referencingModule, specifier)
#resolve-a-module-specifierReferenced in:
* 7.1.3.1. Definitions
* 7.1.3.2. Fetching scripts
* 7.1.3.8.1. HostResolveImportedModule(referencingModule, specifier)
#runtime-script-errorsReferenced in:
* 7.1.3.10. Unhandled promise rejections
#report-the-errorReferenced in:
* 7.1.3.9.1. Runtime script errors in documents
* 7.1.5.1. Event handlers
#script-handledReferenced in:
* 7.1.3.9. Runtime script errors
* 7.1.3.10. Unhandled promise rejections
#script-not-handledReferenced in:
* 7.1.3.9. Runtime script errors (2)
* 7.1.3.9.1. Runtime script errors in documents
* 7.1.3.10. Unhandled promise rejections
* 7.1.5.1. Event handlers
#in-error-reporting-modeReferenced in:
* 7.1.3.9. Runtime script errors (2)
#report-the-exceptionReferenced in:
* 7.1.3.2. Fetching scripts
* 7.1.3.3. Creating scripts
* 7.1.3.4. Calling scripts (2) (3)
* 7.1.3.7.1. EnqueueJob(queueName, job, arguments)
* 7.1.5.1. Event handlers
* 7.5. Timers
* 7.9. Animation Frames
#erroreventReferenced in:
* 7.1.3.9. Runtime script errors
* 7.1.5.1. Event handlers (2)
#dictdef-erroreventinitReferenced in:
* 7.1.3.9.2. The ErrorEvent interface
#dom-errorevent-messageReferenced in:
* 7.1.3.9. Runtime script errors
* 7.1.3.9.2. The ErrorEvent interface
* 7.1.5.1. Event handlers
#dom-errorevent-filenameReferenced in:
* 7.1.3.9. Runtime script errors
* 7.1.3.9.2. The ErrorEvent interface
* 7.1.5.1. Event handlers
#dom-errorevent-linenoReferenced in:
* 7.1.3.9. Runtime script errors
* 7.1.3.9.2. The ErrorEvent interface
* 7.1.5.1. Event handlers
#dom-errorevent-colnoReferenced in:
* 7.1.3.9. Runtime script errors
* 7.1.3.9.2. The ErrorEvent interface
* 7.1.5.1. Event handlers
#dom-errorevent-errorReferenced in:
* 7.1.3.9. Runtime script errors
* 7.1.3.9.2. The ErrorEvent interface
* 7.1.5.1. Event handlers
#unhandled-promise-rejectionsReferenced in:
* 7.1.3.1. Definitions
#notify-about-rejected-promisesReferenced in:
* 7.1.4.2. Processing model
#promise-handledReferenced in:
* 7.1.3.10. Unhandled promise rejections
#promise-not-handledReferenced in:
* 7.1.3.10. Unhandled promise rejections (2)
#promiserejectioneventReferenced in:
* 7.1.3.10.1. The HostPromiseRejectionTracker implementation
#dictdef-promiserejectioneventinitReferenced in:
* 7.1.3.10.2. The PromiseRejectionEvent interface
#dom-promiserejectionevent-promiseReferenced in:
* 7.1.3.10. Unhandled promise rejections
* 7.1.3.10.1. The HostPromiseRejectionTracker implementation
* 7.1.3.10.2. The PromiseRejectionEvent interface
#dom-promiserejectionevent-reasonReferenced in:
* 7.1.3.10. Unhandled promise rejections
* 7.1.3.10.1. The HostPromiseRejectionTracker implementation
* 7.1.3.10.2. The PromiseRejectionEvent interface
#event-loopReferenced in:
* 2.1. Terminology
* 2.2.4. Interactions with XPath and XSLT
* 2.9.1. Serializable objects
* 2.9.2. Transferable objects
* 2.9.9. Performing serialization and transferring from other
specifications
* 4.2.7. Interactions of styling and scripting (2)
* 4.7.7. The embed element (2)
* 4.7.10. The video element (2)
* 4.7.11. The audio element
* 4.7.13. Media elements (2)
* 4.7.13.5. Loading the media resource (2)
* 4.7.13.7. Ready states
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.9. Seeking (2)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2)
* 4.7.13.11.5. Text track API (2)
* 4.7.13.19. Best practices for implementors of media elements
* 6.1.4. Groupings of browsing contexts (2)
* 6.1.6. Script settings for browsing contexts
* 6.6.2. The History interface (2) (3) (4)
* 6.7.1. Navigating across documents
* 6.7.11. Unloading documents (2) (3) (4) (5)
* 7.1.3.1. Definitions (2)
* 7.1.3.7. Integration with the JavaScript job queue
* 7.1.4.1. Definitions (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16)
* 7.1.4.2. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27)
* 7.6.1. Simple dialogs (2) (3)
* 8.2.5.4.8. The "text" insertion mode
* 9.2. Parsing XML documents
#task-queuesReferenced in:
* 4.7.13.5. Loading the media resource
* 4.10.21.3. Form submission algorithm
* 6.7.2. Page load processing model for HTML files
* 6.7.4. Page load processing model for text files
* 7.1.4.1. Definitions (2) (3) (4) (5) (6)
* 7.1.4.2. Processing model (2) (3) (4) (5) (6)
#tasksReferenced in:
* 2.6.2. Processing model (2)
* 2.9.9. Performing serialization and transferring from other
specifications
* 4.2.4.3. Obtaining a resource from a link element
* 4.2.6. The style element
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.7.6. The iframe element
* 4.7.7. The embed element (2) (3) (4)
* 4.7.8. The object element (2) (3) (4)
* 4.7.13.5. Loading the media resource (2) (3) (4) (5) (6) (7)
* 4.7.13.8. Playing the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13)
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2)
* 4.7.13.11.1. Text track model
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5) (6) (7)
* 4.10.5.1.19. Image Button state (type=image) (2) (3)
* 4.10.5.5. Common event behaviors (2)
* 4.10.21.3. Form submission algorithm (2)
* 4.11.1. The details element
* 6.1.5. Browsing context names (2) (3) (4)
* 6.3.4. Garbage collection and browsing contexts
* 6.6.2. The History interface (2) (3) (4) (5)
* 6.6.4. The Location interface (2) (3)
* 6.7.1. Navigating across documents (2) (3) (4) (5)
* 6.7.2. Page load processing model for HTML files
* 6.7.4. Page load processing model for text files
* 6.7.9. Navigating to a fragment
* 6.7.10. History traversal
* 6.7.12. Aborting a document load (2)
* 6.7.13. Browser state
* 7.1.4.1. Definitions (2) (3) (4) (5) (6)
* 7.1.4.2. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14)
* 7.1.4.3. Generic task sources
* 7.4.1. Opening the input stream (2)
* 7.5. Timers (2) (3) (4) (5) (6)
* 7.6.1. Simple dialogs
* 7.7.1.2. Language preferences
* 8.2.5.4.8. The "text" insertion mode (2)
* 8.2.6. The end
* 9.2. Parsing XML documents (2)
* 11.3.3. Frames
#queuingReferenced in:
* 2.6.2. Processing model
* 4.2.4.3. Obtaining a resource from a link element (2)
* 4.2.6. The style element (2)
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8)
* 4.7.6. The iframe element
* 4.7.7. The embed element (2) (3)
* 4.7.8. The object element (2) (3) (4)
* 4.7.10. The video element
* 4.7.13.5. Loading the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20)
* 4.7.13.6. Offsets into the media resource (2) (3)
* 4.7.13.7. Ready states (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.7.13.8. Playing the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15)
* 4.7.13.9. Seeking (2) (3)
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2)
* 4.7.13.11.1. Text track model
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4) (5)
* 4.7.13.11.5. Text track API
* 4.7.13.13. User interface
* 4.8.4. Following hyperlinks (2)
* 4.10.4. The label element
* 4.10.5.1.2. Text (type=text) state and Search state (type=search)
* 4.10.5.1.17. File Upload state (type=file) (2)
* 4.10.5.1.19. Image Button state (type=image) (2)
* 4.10.5.5. Common event behaviors (2) (3) (4) (5) (6)
* 4.10.7. The select element
* 4.10.11. The textarea element (2)
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute
* 4.10.19. APIs for text field selections (2) (3)
* 4.10.21.3. Form submission algorithm
* 4.11.1. The details element
* 4.11.4. The dialog element (2)
* 4.12.1.1. Processing model (2) (3)
* 4.12.4. The canvas element
* 5.7.3.2. The DataTransferItem interface
* 5.7.5. Drag-and-drop processing model
* 6.3.1. APIs for creating and navigating browsing contexts by name
* 6.6.2. The History interface
* 6.7.1. Navigating across documents (2)
* 6.7.2. Page load processing model for HTML files (2)
* 6.7.4. Page load processing model for text files (2)
* 6.7.10. History traversal (2)
* 6.7.12. Aborting a document load
* 6.7.13. Browser state (2)
* 7.1.3.10. Unhandled promise rejections
* 7.1.3.10.1. The HostPromiseRejectionTracker implementation
* 7.1.4.2. Processing model
* 7.5. Timers
* 7.7.1.2. Language preferences
* 8.2.6. The end (2) (3) (4)
* 10.5.4. The input element as a text entry widget.
* 10.5.15. The textarea element
* 11.3.2. The marquee element (2) (3) (4)
* 11.3.3. Frames (2)
#task-sourceReferenced in:
* 2.6.2. Processing model
* 4.2.4.3. Obtaining a resource from a link element
* 4.2.6. The style element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.13. Media elements
* 4.7.13.11.1. Text track model
* 4.8.4. Following hyperlinks
* 4.10.5.5. Common event behaviors
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute
* 4.10.21.3. Form submission algorithm
* 4.11.1. The details element
* 4.12.4. The canvas element
* 6.3.4. Garbage collection and browsing contexts
* 6.6.2. The History interface
* 6.7.1. Navigating across documents (2)
* 6.7.2. Page load processing model for HTML files
* 6.7.4. Page load processing model for text files
* 6.7.9. Navigating to a fragment
* 6.7.10. History traversal
* 6.7.13. Browser state
* 7.1.4.1. Definitions (2) (3)
* 7.1.4.2. Processing model (2) (3) (4) (5) (6)
* 7.1.4.3. Generic task sources (2) (3) (4) (5)
* 7.4.1. Opening the input stream
* 7.5. Timers
* 7.7.1.2. Language preferences
* 8.2.6. The end
* 11.3.2. The marquee element
* 11.3.3. Frames
#currently-running-taskReferenced in:
* 7.1.4.2. Processing model (2) (3) (4) (5) (6) (7) (8)
#performing-a-microtask-checkpoint-flagReferenced in:
* 7.1.4.2. Processing model (2) (3) (4)
#microtask-queueReferenced in:
* 7.1.4.2. Processing model (2) (3) (4) (5)
#microtaskReferenced in:
* 7.1.4.2. Processing model (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 7.6.1. Simple dialogs
#solitary-callback-microtasksReferenced in:
* 7.1.4.2. Processing model (2)
#compound-microtasksReferenced in:
* 7.1.4.2. Processing model (2) (3) (4)
#queue-a-microtaskReferenced in:
* 2.6.2. Processing model
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 4.7.7. The embed element
* 4.7.8. The object element (2) (3)
* 4.7.13. Media elements
* 4.7.13.5. Loading the media resource
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3)
* 4.10.5.1.19. Image Button state (type=image) (2) (3)
* 4.10.10. The option element
* 4.10.18.5. Enabling and disabling form controls: the disabled
attribute
* 4.10.21.3. Form submission algorithm
* 4.11.1. The details element
* 6.1.5. Browsing context names
* 6.7.12. Aborting a document load (2)
* 7.1.3.7.1. EnqueueJob(queueName, job, arguments)
* 7.1.4.2. Processing model
* 7.1.4.3. Generic task sources
#microtask-task-sourceReferenced in:
* 7.1.4.2. Processing model (2)
#performs-a-microtask-checkpointReferenced in:
* 7.1.3.4. Calling scripts
* 7.1.4.1. Definitions
* 7.1.4.2. Processing model (2) (3) (4) (5)
* 8.2.5.1. Creating and inserting nodes
* 8.2.5.4.8. The "text" insertion mode
* 9.2. Parsing XML documents
#wrap-callbacksReferenced in:
* 7.1.4.2. Processing model (2)
#compound-microtask-subtaskReferenced in:
* 7.1.4.2. Processing model
#provides-a-stable-stateReferenced in:
* 4.7.5. The img element (2)
* 4.7.13.5. Loading the media resource (2) (3)
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.9. Seeking
* 4.7.13.11.3. Sourcing out-of-band text tracks
#synchronous-sectionReferenced in:
* 1.7.2. Typographic conventions
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8)
* 4.7.13.5. Loading the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13) (14) (15) (16) (17) (18) (19)
* 4.7.13.8. Playing the media resource (2)
* 4.7.13.9. Seeking (2) (3)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4)
* 7.1.4.2. Processing model
#spinning-the-event-loopReferenced in:
* 6.7.1. Navigating across documents
* 7.1.4.2. Processing model (2)
* 7.4.2. Closing the input stream
* 8.2.5.4.8. The "text" insertion mode (2)
* 8.2.6. The end (2) (3)
* 9.2. Parsing XML documents
#statedef-useragent-pauseReferenced in:
* 4.7.13.8. Playing the media resource
* 6.7.11. Unloading documents
* 7.6.1. Simple dialogs (2) (3)
* 7.6.2. Printing
#dom-manipulation-task-sourceReferenced in:
* 4.2.4.3. Obtaining a resource from a link element
* 4.2.6. The style element
* 4.7.5. The img element
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 4.7.13.11.1. Text track model
* 4.7.13.11.3. Sourcing out-of-band text tracks (2)
* 4.8.4. Following hyperlinks
* 4.10.21.3. Form submission algorithm
* 4.11.1. The details element
* 6.7.1. Navigating across documents
* 6.7.9. Navigating to a fragment
* 6.7.10. History traversal
* 7.7.1.2. Language preferences
* 8.2.6. The end
* 11.3.2. The marquee element
* 11.3.3. Frames
#user-interaction-task-sourceReferenced in:
* 4.10.5.5. Common event behaviors
* 4.10.7. The select element
* 4.10.10. The option element
* 4.10.18.5. Enabling and disabling form controls: the disabled
attribute
* 4.10.18.6.1. Autofocusing a form control: the autofocus attribute
* 4.10.19. APIs for text field selections (2) (3)
* 7.1.4.1. Definitions
* 7.1.4.3. Generic task sources
* 10.5.4. The input element as a text entry widget.
* 10.5.15. The textarea element
#networking-task-sourceReferenced in:
* 2.6.2. Processing model
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8)
* 4.7.7. The embed element
* 4.7.8. The object element (2)
* 4.7.13.5. Loading the media resource (2) (3)
* 4.7.13.11.3. Sourcing out-of-band text tracks (2) (3) (4)
* 4.10.5.1.19. Image Button state (type=image) (2) (3)
* 6.7.1. Navigating across documents
* 6.7.2. Page load processing model for HTML files (2)
* 6.7.4. Page load processing model for text files (2)
* 6.7.13. Browser state
#history-traversal-task-sourceReferenced in:
* 6.6.2. The History interface (2)
* 6.7.9. Navigating to a fragment
* 6.7.10. History traversal
* 7.4.1. Opening the input stream
#event-handlerReferenced in:
* 3.2.5. Global attributes
* 4.3.1. The body element (2) (3) (4)
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2)
* 4.7.13.11.8. Event handlers for objects of the text track APIs (2) (3)
(4) (5) (6)
* 7.1.5.1. Event handlers (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23)
* 7.1.5.2. Event handlers on elements, Document objects, and Window
objects (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 11.3.2. The marquee element (2)
* 11.3.3. Frames (2) (3)
#event-handler-idl-event-handler-idl-attributeReferenced in:
* 4.3.1. The body element
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects
* 4.7.13.11.8. Event handlers for objects of the text track APIs (2) (3)
* 7.1.1. Introduction
* 7.1.5.1. Event handlers (2) (3) (4) (5) (6)
* 7.1.5.2. Event handlers on elements, Document objects, and Window
objects (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
* 11.3.2. The marquee element
* 11.3.3. Frames
#event-handler-content-event-handler-content-attributeReferenced in:
* 1.9. A quick introduction to HTML
* 1.9.2. Common pitfalls to avoid when using the scripting APIs
* 3.2.5. Global attributes
* 4.3.1. The body element (2) (3)
* 7.1.1. Introduction
* 7.1.3.9. Runtime script errors (2)
* 7.1.5.1. Event handlers (2) (3) (4)
* 7.1.5.2. Event handlers on elements, Document objects, and Window
objects (2) (3) (4) (5)
* 11.3.2. The marquee element
* 11.3.3. Frames
* Attributes (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14)
(15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25) (26) (27) (28)
(29) (30) (31) (32) (33) (34) (35) (36) (37) (38) (39) (40) (41) (42)
(43) (44) (45) (46) (47) (48) (49) (50) (51) (52) (53) (54) (55) (56)
(57) (58) (59) (60) (61) (62) (63) (64) (65) (66) (67) (68) (69) (70)
(71) (72) (73) (74)
#event-handler-event-typeReferenced in:
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2)
* 4.7.13.11.8. Event handlers for objects of the text track APIs (2) (3)
(4) (5) (6)
* 7.1.5.2. Event handlers on elements, Document objects, and Window
objects (2) (3) (4) (5) (6) (7) (8) (9) (10)
* 11.3.2. The marquee element (2)
#the-event-handler-processing-algorithmReferenced in:
* 7.1.3.9. Runtime script errors
* 7.1.5.1. Event handlers
#invokeReferenced in:
* 7.1.5.1. Event handlers (2)
* 7.5. Timers
#callbackdef-eventhandlernonnullReferenced in:
* 7.1.5.1. Event handlers
#typedefdef-eventhandlerReferenced in:
* 3.1.1. The Document object
* 4.7.13.10.1. AudioTrackList and VideoTrackList objects (2) (3) (4) (5)
(6)
* 4.7.13.11.5. Text track API (2) (3) (4) (5) (6)
* 7.1.5.1. Event handlers (2)
* 7.1.5.2.1. IDL definitions (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
(26) (27) (28) (29) (30) (31) (32) (33) (34) (35) (36) (37) (38) (39)
(40) (41) (42) (43) (44) (45) (46) (47) (48) (49) (50) (51) (52) (53)
(54) (55) (56) (57) (58) (59) (60) (61) (62) (63) (64) (65) (66) (67)
(68) (69) (70) (71) (72) (73) (74) (75)
* 11.3.2. The marquee element (2) (3)
#callbackdef-onerroreventhandlernonnullReferenced in:
* 7.1.5.1. Event handlers
#typedefdef-onerroreventhandlerReferenced in:
* 7.1.5.2.1. IDL definitions
#callbackdef-onbeforeunloadeventhandlernonnullReferenced in:
* 7.1.5.1. Event handlers
#typedefdef-onbeforeunloadeventhandlerReferenced in:
* 7.1.5.2.1. IDL definitions
#internal-raw-uncompiled-handlerReferenced in:
* 7.1.5.1. Event handlers (2) (3) (4) (5)
#getting-the-current-value-of-the-event-handlerReferenced in:
* 7.1.5.1. Event handlers (2)
#dom-globaleventhandlers-onabortReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
* Attributes
#dom-globaleventhandlers-onauxclickReferenced in:
* 3.2.5. Global attributes
#dom-globaleventhandlers-oncancelReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-oncanplayReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-oncanplaythroughReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onchangeReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onclickReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-oncloseReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-oncuechangeReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-ondblclickReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-ondragReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-ondragendReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-ondragenterReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-ondragexitReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-ondragleaveReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-ondragoverReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-ondragstartReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-ondropReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-ondurationchangeReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onemptiedReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onendedReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-oninputReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-oninvalidReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onkeydownReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onkeypressReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onkeyupReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onloadeddataReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onloadedmetadataReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onloadendReferenced in:
* 3.2.5. Global attributes
#dom-globaleventhandlers-onloadstartReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onmousedownReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onmouseenterReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onmouseleaveReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onmousemoveReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onmouseoutReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onmouseoverReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onmouseupReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onwheelReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onpauseReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onplayReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onplayingReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onprogressReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onratechangeReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onresetReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onseekedReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onseekingReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onselectReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onshowReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onstalledReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onsubmitReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onsuspendReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-ontimeupdateReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-ontoggleReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onvolumechangeReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onwaitingReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
#dom-globaleventhandlers-onblurReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
* 11.3.3. Frames
#dom-globaleventhandlers-onerrorReferenced in:
* 3.2.5. Global attributes
* 7.1.5.1. Event handlers (2)
* 7.1.5.2.1. IDL definitions
* 11.3.3. Frames
#dom-globaleventhandlers-onfocusReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
* 11.3.3. Frames
#dom-globaleventhandlers-onloadReferenced in:
* 1.9.1. Writing secure applications with HTML
* 1.9.2. Common pitfalls to avoid when using the scripting APIs
* 3.2.5. Global attributes
* 4.3.1. The body element
* 7.1.5.2.1. IDL definitions
* 11.3.3. Frames
#dom-globaleventhandlers-onresizeReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
* 11.3.3. Frames
#dom-globaleventhandlers-onscrollReferenced in:
* 3.2.5. Global attributes
* 7.1.5.2.1. IDL definitions
* 11.3.3. Frames
#dom-windoweventhandlers-onafterprintReferenced in:
* 7.1.5.2.1. IDL definitions
* Elements
#dom-windoweventhandlers-onbeforeprintReferenced in:
* 7.1.5.2.1. IDL definitions
* Elements
#dom-onbeforeunloadeventhandler-onbeforeunloadReferenced in:
* 7.1.5.1. Event handlers
#dom-windoweventhandlers-onhashchangeReferenced in:
* 7.1.5.2.1. IDL definitions
* Elements
#dom-windoweventhandlers-onlanguagechangeReferenced in:
* 7.1.5.2.1. IDL definitions
* Elements
#dom-windoweventhandlers-onmessageReferenced in:
* 7.1.5.2.1. IDL definitions
* Elements
#dom-windoweventhandlers-onofflineReferenced in:
* 7.1.5.2.1. IDL definitions
* Elements
#dom-windoweventhandlers-ononlineReferenced in:
* 7.1.5.2.1. IDL definitions
* Elements
#dom-windoweventhandlers-onpagehideReferenced in:
* 7.1.5.2.1. IDL definitions
* Elements
#dom-windoweventhandlers-onpageshowReferenced in:
* 7.1.5.2.1. IDL definitions
* Elements
#dom-windoweventhandlers-onrejectionhandledReferenced in:
* 7.1.5.2.1. IDL definitions
#dom-windoweventhandlers-onpopstateReferenced in:
* 6.6.1. The session history of browsing contexts
* 7.1.5.2.1. IDL definitions
* Elements
#dom-windoweventhandlers-onstorageReferenced in:
* 7.1.5.2.1. IDL definitions
* Elements
#dom-windoweventhandlers-onunhandledrejectionReferenced in:
* 7.1.5.2.1. IDL definitions
#dom-windoweventhandlers-onunloadReferenced in:
* 7.1.5.2.1. IDL definitions
* Elements
#dom-documentandelementeventhandlers-oncutReferenced in:
* 7.1.5.2.1. IDL definitions
#dom-documentandelementeventhandlers-oncopyReferenced in:
* 7.1.5.2.1. IDL definitions
#dom-documentandelementeventhandlers-onpasteReferenced in:
* 7.1.5.2.1. IDL definitions
#globaleventhandlersReferenced in:
* 3.1.1. The Document object
* 3.2.2. Elements in the DOM
* 6.3. The Window object
#windoweventhandlersReferenced in:
* 4.3.1. The body element
* 6.3. The Window object
* 11.3.3. Frames
#dom-windoweventhandlers-onbeforeunloadReferenced in:
* Elements
#documentandelementeventhandlersReferenced in:
* 3.1.1. The Document object
* 3.2.2. Elements in the DOM
#firing-a-synthetic-mouse-event-named-eReferenced in:
* 7.1.5.3. Event firing
#fire-a-click-eventReferenced in:
* 4.11.3.2. Using the a element to define a command
* 4.11.3.4. Using the input element to define a command
* 4.11.3.8. Using the accesskey attribute to define a command on other
elements
* 5.3. Activation
#windoworworkerglobalscopeReferenced in:
* 7.2. The WindowOrWorkerGlobalScope mixin (2) (3) (4)
* Changes between Working Draft 2 and the First Public Working Draft
#it-can-also-come-from-scriptReferenced in:
* 8.2.1. Overview of the parsing model
* 8.2.4. Tokenization
#throw-on-dynamic-markup-insertion-counterReferenced in:
* 8.2.5.1. Creating and inserting nodes (2) (3)
#dom-document-_openReferenced in:
* 3.1. Documents
* 3.1.1. The Document object (2)
* 6.1. Browsing contexts
* 6.4. Origin
* 7.1.3.1. Definitions
* 7.4. Dynamic markup insertion
* 7.4.1. Opening the input stream (2) (3) (4) (5) (6) (7) (8) (9) (10)
(11) (12)
* 8.2.5.1. Creating and inserting nodes
* 8.2.5.4.8. The "text" insertion mode
#ignore-opens-during-unload-counterReferenced in:
* 6.7.11. Unloading documents (2) (3) (4)
* 7.4.1. Opening the input stream
* 7.4.3. document.write()
#script-created-parserReferenced in:
* 7.4.2. Closing the input stream
* 8.2.2.5. Preprocessing the input stream
#dom-document-closeReferenced in:
* 3.1.1. The Document object
* 7.4. Dynamic markup insertion
* 7.4.1. Opening the input stream (2)
* 7.4.2. Closing the input stream
* 8.2.2.5. Preprocessing the input stream
#ignore-destructive-writes-counterReferenced in:
* 4.12.1.1. Processing model (2)
* 7.4.3. document.write()
#dom-document-writeReferenced in:
* 3.1. Documents
* 3.1.1. The Document object
* 4.12.1. The script element (2)
* 7.1.3.9. Runtime script errors (2) (3)
* 7.4. Dynamic markup insertion
* 7.4.1. Opening the input stream (2)
* 7.4.3. document.write() (2) (3) (4)
* 7.4.4. document.writeln()
* 8.2.1. Overview of the parsing model
* 8.2.2.5. Preprocessing the input stream (2)
* 8.2.5.1. Creating and inserting nodes (2)
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.8. The "text" insertion mode (2)
* 8.2.5.5. The rules for parsing tokens in foreign content
* 9.2. Parsing XML documents
#dom-document-writelnReferenced in:
* 3.1.1. The Document object
* 7.4.4. document.writeln()
* 8.2.5.1. Creating and inserting nodes
#list-of-active-timersReferenced in:
* 6.7.11. Unloading documents
* 7.5. Timers (2) (3) (4) (5) (6)
#timer-initialization-stepsReferenced in:
* 7.5. Timers (2) (3)
#timer-nesting-levelReferenced in:
* 7.5. Timers
#optionally-truncatedReferenced in:
* 6.7.11. Unloading documents
* 7.6.1. Simple dialogs (2) (3)
#dom-window-alertReferenced in:
* 6.3. The Window object (2)
* 7.1.3.6. Killing scripts
* 7.6.1. Simple dialogs
#dom-window-confirmReferenced in:
* 6.3. The Window object
* 7.6.1. Simple dialogs
#dom-window-promptReferenced in:
* 6.3. The Window object
* 7.6.1. Simple dialogs
#dom-window-printReferenced in:
* 6.3. The Window object
* 7.1.3.5. Realms, settings objects, and global objects (2) (3)
* 7.6.2. Printing
#print-when-loadedReferenced in:
* 8.2.6. The end
#printing-stepsReferenced in:
* 7.6.2. Printing (2)
* 8.2.6. The end
#dom-window-navigatorReferenced in:
* 6.3. The Window object
#navigatorReferenced in:
* 6.3. The Window object
* 7.1.3.5. Realms, settings objects, and global objects (2)
* 7.4.1. Opening the input stream
* 7.7.1. The Navigator object (2) (3) (4) (5)
* 11.3.4.1. Plugins
#navigatoridReferenced in:
* 7.7.1. The Navigator object
#dom-navigatorid-appcodenameReferenced in:
* 7.7.1.1. Client identification
#dom-navigatorid-appnameReferenced in:
* 7.7.1.1. Client identification
#dom-navigatorid-appversionReferenced in:
* 7.7.1.1. Client identification
#dom-navigatorid-platformReferenced in:
* 7.7.1.1. Client identification
#dom-navigatorid-productReferenced in:
* 7.7.1.1. Client identification
#dom-navigatorid-useragentReferenced in:
* 7.7.1.1. Client identification
#navigatorlanguageReferenced in:
* 7.7.1. The Navigator object
#dom-navigatorlanguage-languageReferenced in:
* 7.7.1.2. Language preferences
#dom-navigatorlanguage-languagesReferenced in:
* 7.7.1.2. Language preferences
#plausible-languagesReferenced in:
* 7.7.1.2. Language preferences (2)
#navigatorcontentutilsReferenced in:
* 7.7.1. The Navigator object
#dom-navigatorcontentutils-registercontenthandlerReferenced in:
* Changes since HTML 5.1 - Note that these may change if the HTML 5.1
specification is updated.
#dom-navigatorcontentutils-isprotocolhandlerregisteredReferenced in:
* Changes since HTML 5.1 - Note that these may change if the HTML 5.1
specification is updated.
#dom-navigatorcontentutils-iscontenthandlerregisteredReferenced in:
* Changes since HTML 5.1 - Note that these may change if the HTML 5.1
specification is updated.
#a-registered-handlerReferenced in:
* 6.7.1. Navigating across documents (2)
#safelisted-schemesReferenced in:
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods
#type-blocklistReferenced in:
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods
#proto-urlReferenced in:
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods (2) (3)
(4)
#handler-state-stringsReferenced in:
* 7.7.1.3. Custom scheme and content handlers: the
registerProtocolHandler() and registerContentHandler() methods (2)
#navigatorcookiesReferenced in:
* 7.7.1. The Navigator object
#dom-navigatorcookies-cookieenabledReferenced in:
* 7.7.1.4. Cookies
#imagebitmapReferenced in:
* 7.2. The WindowOrWorkerGlobalScope mixin (2)
* 7.8. Images
#typedefdef-imagebitmapsourceReferenced in:
* 7.2. The WindowOrWorkerGlobalScope mixin (2)
#cropped-to-the-source-rectangleReferenced in:
* 7.8. Images (2) (3) (4) (5) (6) (7)
#dom-imagebitmap-widthReferenced in:
* 7.8. Images
#dom-imagebitmap-heightReferenced in:
* 7.8. Images
#list-of-animation-frame-callbacksReferenced in:
* 7.9. Animation Frames (2) (3) (4) (5)
#animation-frame-callback-identifierReferenced in:
* 7.9. Animation Frames (2) (3)
#dom-window-requestanimationframeReferenced in:
* 6.3. The Window object
#dom-window-cancelanimationframeReferenced in:
* 6.3. The Window object
#run-the-animation-frame-callbacksReferenced in:
* 7.1.4.2. Processing model (2) (3) (4)
#the-html-syntaxReferenced in:
* 3.2.1. Semantics
* 9. The XML syntax
#doctypeReferenced in:
* 2.5.1. Terminology
* 4.7.6. The iframe element (2)
* 8.1. Writing HTML documents
#doctype-legacy-stringReferenced in:
* 8.1.1. The DOCTYPE (2)
#kind-of-elementReferenced in:
* 3.2.4.2.5. Phrasing content (2)
* 8.1.2. Elements (2) (3)
#void-elementsReferenced in:
* 3.2.4.1. The "nothing" content model
* 8.1.2. Elements (2) (3) (4)
* 8.1.2.1. Start tags (2)
#raw-textReferenced in:
* 8.1.2. Elements (2) (3)
* 8.1.2.6. Restrictions on the contents of raw text and escapable raw
text elements
#escapable-raw-textReferenced in:
* 3.2.4.2.5. Phrasing content
* 8.1.2. Elements (2) (3)
* 8.1.2.6. Restrictions on the contents of raw text and escapable raw
text elements
#foreign-elementsReferenced in:
* 8.1.2. Elements (2) (3) (4) (5) (6)
* 8.1.2.1. Start tags (2)
* 8.1.2.3. Attributes (2)
#normal-elementsReferenced in:
* 8.1.2. Elements (2) (3) (4) (5)
#tag-nameReferenced in:
* 8.1.2.1. Start tags (2)
* 8.1.2.2. End tags
#syntax-start-tagsReferenced in:
* 1.9. A quick introduction to HTML
* 3.2.3. Element definitions
* 4.1.1. The html element
* 4.2.1. The head element
* 4.3.1. The body element
* 4.9.3. The colgroup element
* 4.9.5. The tbody element
* 4.12.1. The script element
* 8.1.2. Elements
* 8.1.2.3. Attributes
* 8.1.2.4. Optional tags (2) (3) (4) (5) (6) (7)
* 8.1.2.5. Restrictions on content models
* 8.3. Serializing HTML fragments
#syntax-end-tagsReferenced in:
* 1.9. A quick introduction to HTML
* 3.2.3. Element definitions
* 3.2.4.1. The "nothing" content model
* 4.1.1. The html element
* 4.2.1. The head element
* 4.2.4. The link element
* 4.2.5. The meta element
* 4.3.1. The body element
* 4.4.1. The p element
* 4.4.3. The hr element
* 4.4.8. The li element
* 4.4.10. The dt element
* 4.4.11. The dd element
* 4.5.11. The rb element
* 4.5.12. The rt element
* 4.5.13. The rtc element
* 4.5.14. The rp element
* 4.5.29. The br element
* 4.5.30. The wbr element
* 4.7.4. The source element
* 4.7.5. The img element
* 4.7.7. The embed element
* 4.7.9. The param element
* 4.7.12. The track element
* 4.7.15. The area element
* 4.9.3. The colgroup element
* 4.9.4. The col element
* 4.9.5. The tbody element (2)
* 4.9.6. The thead element
* 4.9.7. The tfoot element
* 4.9.8. The tr element
* 4.9.9. The td element
* 4.9.10. The th element
* 4.10.5. The input element
* 4.10.9. The optgroup element
* 4.10.10. The option element
* 4.12.1. The script element
* 8.1.2. Elements
* 8.1.2.4. Optional tags (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
(13) (14) (15) (16) (17) (18) (19) (20) (21)
#attributesReferenced in:
* 1.9. A quick introduction to HTML
* 8.1.2.1. Start tags
#attribute-namesReferenced in:
* 1.9. A quick introduction to HTML
* 8.1.2.3. Attributes (2) (3) (4)
#attribute-valuesReferenced in:
* 1.9. A quick introduction to HTML
* 3.2.5.5. The dir attribute (2) (3)
* 8.1.2.3. Attributes (2) (3)
#unquotedReferenced in:
* 1.9. A quick introduction to HTML
#optional-start-and-end-tagsReferenced in:
* 1.9. A quick introduction to HTML
* 3.2.3. Element definitions
* 4.7.6. The iframe element
* 8.1. Writing HTML documents
* 8.1.2. Elements (2) (3)
#syntax-charrefReferenced in:
* 4.2.5.5. Specifying the document’s character encoding
* 8.1.2. Elements (2) (3) (4)
* 8.1.2.3. Attributes
* 8.1.3.1. Newlines
#ambiguous-ampersandReferenced in:
* 8.1.2. Elements (2) (3) (4)
* 8.1.2.3. Attributes
#syntax-cdataReferenced in:
* 8.1.2. Elements
#syntax-commentsReferenced in:
* 4.1.1. The html element (2)
* 4.2.1. The head element
* 4.3.1. The body element (2)
* 4.7.6. The iframe element (2) (3)
* 8.1. Writing HTML documents (2) (3)
* 8.1.2. Elements (2) (3)
* 8.1.2.4. Optional tags (2) (3) (4) (5) (6) (7)
#html-parserReferenced in:
* 2.2.4. Interactions with XPath and XSLT
* 3.1.2. Resource metadata management (2)
* 3.2.5. Global attributes
* 4.2.6. The style element (2) (3)
* 4.2.7. Interactions of styling and scripting
* 4.7.6. The iframe element
* 4.7.8. The object element (2) (3)
* 4.7.13.11.1. Text track model (2)
* 4.10.11. The textarea element
* 4.10.17.3. Association of controls and forms (2)
* 4.12.1.1. Processing model (2) (3) (4)
* 4.12.2. The noscript element (2)
* 4.12.3.1. Interaction of template elements with XSLT and XPath
* 6.7.2. Page load processing model for HTML files (2)
* 6.7.4. Page load processing model for text files (2) (3)
* 7.1.4.1. Definitions
* 7.4. Dynamic markup insertion
* 7.4.1. Opening the input stream (2)
* 7.4.3. document.write() (2)
* 8.2.2.2. Determining the character encoding (2)
* 8.2.5.4.8. The "text" insertion mode (2)
* 8.2.7. Coercing an HTML DOM into an infoset (2) (3) (4) (5)
* 8.2.8. An introduction to error handling and strange cases in the
parser
* 8.3. Serializing HTML fragments (2) (3) (4)
* 8.4. Parsing HTML fragments (2) (3)
* 9.2. Parsing XML documents (2) (3)
* 11.3.1. The applet element
#parse-errorsReferenced in:
* 1.10.2. Syntax errors
* 4.7.5. The img element (2) (3) (4) (5) (6) (7) (8) (9)
* 4.7.6. The iframe element
* 4.10.17.3. Association of controls and forms
* 4.12.2. The noscript element (2)
* 8.2. Parsing HTML documents (2) (3) (4) (5) (6) (7) (8)
* 8.2.2.5. Preprocessing the input stream (2)
* 8.2.4. Tokenization (2) (3)
* 8.2.4.1. Data state
* 8.2.4.2. RCDATA state
* 8.2.4.3. RAWTEXT state
* 8.2.4.4. Script data state
* 8.2.4.5. PLAINTEXT state
* 8.2.4.6. Tag open state (2)
* 8.2.4.7. End tag open state (2) (3)
* 8.2.4.8. Tag name state (2)
* 8.2.4.20. Script data escaped state (2)
* 8.2.4.21. Script data escaped dash state (2)
* 8.2.4.22. Script data escaped dash dash state (2)
* 8.2.4.27. Script data double escaped state (2)
* 8.2.4.28. Script data double escaped dash state (2)
* 8.2.4.29. Script data double escaped dash dash state (2)
* 8.2.4.32. Before attribute name state
* 8.2.4.33. Attribute name state (2) (3)
* 8.2.4.34. After attribute name state
* 8.2.4.35. Before attribute value state
* 8.2.4.36. Attribute value (double-quoted) state (2)
* 8.2.4.37. Attribute value (single-quoted) state (2)
* 8.2.4.38. Attribute value (unquoted) state (2) (3)
* 8.2.4.39. After attribute value (quoted) state (2)
* 8.2.4.40. Self-closing start tag state (2)
* 8.2.4.42. Markup declaration open state
* 8.2.4.43. Comment start state
* 8.2.4.44. Comment start dash state (2)
* 8.2.4.45. Comment state (2)
* 8.2.4.49. Comment less-than sign bang dash dash state
* 8.2.4.50. Comment end dash state
* 8.2.4.51. Comment end state
* 8.2.4.52. Comment end bang state (2)
* 8.2.4.53. DOCTYPE state (2)
* 8.2.4.54. Before DOCTYPE name state (2) (3)
* 8.2.4.55. DOCTYPE name state (2)
* 8.2.4.56. After DOCTYPE name state (2)
* 8.2.4.57. After DOCTYPE public keyword state (2) (3) (4) (5)
* 8.2.4.58. Before DOCTYPE public identifier state (2) (3)
* 8.2.4.59. DOCTYPE public identifier (double-quoted) state (2) (3)
* 8.2.4.60. DOCTYPE public identifier (single-quoted) state (2) (3)
* 8.2.4.61. After DOCTYPE public identifier state (2) (3) (4)
* 8.2.4.62. Between DOCTYPE public and system identifiers state (2)
* 8.2.4.63. After DOCTYPE system keyword state (2) (3) (4) (5)
* 8.2.4.64. Before DOCTYPE system identifier state (2) (3)
* 8.2.4.65. DOCTYPE system identifier (double-quoted) state (2) (3)
* 8.2.4.66. DOCTYPE system identifier (single-quoted) state (2) (3)
* 8.2.4.67. After DOCTYPE system identifier state (2)
* 8.2.4.69. CDATA section state
* 8.2.4.72. Character reference state (2)
* 8.2.4.74. Hexadecimal character reference start state
* 8.2.4.75. Decimal character reference start state
* 8.2.4.76. Hexadecimal character reference state
* 8.2.4.77. Decimal character reference state
* 8.2.4.78. Numeric character reference end state (2) (3)
* 8.2.5.1. Creating and inserting nodes (2)
* 8.2.5.4.1. The "initial" insertion mode (2)
* 8.2.5.4.2. The "before html" insertion mode (2)
* 8.2.5.4.3. The "before head" insertion mode (2)
* 8.2.5.4.4. The "in head" insertion mode (2) (3) (4)
* 8.2.5.4.5. The "in head noscript" insertion mode (2) (3)
* 8.2.5.4.6. The "after head" insertion mode (2) (3)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22)
(23) (24) (25) (26) (27) (28) (29) (30) (31) (32) (33) (34) (35) (36)
(37) (38) (39) (40) (41) (42) (43) (44)
* 8.2.5.4.8. The "text" insertion mode
* 8.2.5.4.9. The "in table" insertion mode (2) (3) (4) (5) (6) (7)
* 8.2.5.4.10. The "in table text" insertion mode (2)
* 8.2.5.4.11. The "in caption" insertion mode (2) (3) (4) (5)
* 8.2.5.4.12. The "in column group" insertion mode (2) (3) (4)
* 8.2.5.4.13. The "in table body" insertion mode (2) (3) (4)
* 8.2.5.4.14. The "in row" insertion mode (2) (3) (4)
* 8.2.5.4.15. The "in cell" insertion mode (2) (3) (4) (5) (6)
* 8.2.5.4.16. The "in select" insertion mode (2) (3) (4) (5) (6) (7) (8)
* 8.2.5.4.17. The "in select in table" insertion mode (2)
* 8.2.5.4.18. The "in template" insertion mode (2)
* 8.2.5.4.19. The "after body" insertion mode (2) (3)
* 8.2.5.4.20. The "in frameset" insertion mode (2) (3) (4)
* 8.2.5.4.21. The "after frameset" insertion mode (2)
* 8.2.5.4.22. The "after after body" insertion mode
* 8.2.5.4.23. The "after after frameset" insertion mode
* 8.2.5.5. The rules for parsing tokens in foreign content (2) (3) (4)
#reentrantReferenced in:
* 7.4.3. document.write()
* 8.2.5.4.8. The "text" insertion mode (2)
#script-nesting-levelReferenced in:
* 4.12.1.1. Processing model
* 7.4.1. Opening the input stream
* 8.2.5.4.8. The "text" insertion mode (2) (3) (4) (5) (6) (7)
* 8.2.5.5. The rules for parsing tokens in foreign content (2) (3)
#parser-pause-flagReferenced in:
* 8.2.4. Tokenization
* 8.2.5.4.8. The "text" insertion mode (2) (3)
* 8.2.5.5. The rules for parsing tokens in foreign content (2) (3)
#input-byte-streamReferenced in:
* 6.7.2. Page load processing model for HTML files (2)
* 6.7.4. Page load processing model for text files
* 8.2.2. The input byte stream (2) (3)
* 8.2.2.5. Preprocessing the input stream
#confidenceReferenced in:
* 7.4.1. Opening the input stream
* 8.2.2. The input byte stream
* 8.2.2.1. Parsing with a known character encoding
* 8.2.2.2. Determining the character encoding (2) (3) (4) (5) (6) (7)
(8)
* 8.2.2.4. Changing the encoding while parsing (2) (3) (4) (5)
* 8.2.5.4.4. The "in head" insertion mode (2)
* 8.4. Parsing HTML fragments
#encoding-sniffing-algorithmReferenced in:
* 8.2.2. The input byte stream
* 8.2.2.2. Determining the character encoding
* 8.2.2.4. Changing the encoding while parsing (2) (3) (4)
#prescan-a-byte-stream-to-determine-its-encodingReferenced in:
* 8.2.2.2. Determining the character encoding (2) (3) (4)
#get-an-attributeReferenced in:
* 8.2.2.2. Determining the character encoding (2) (3) (4) (5) (6) (7)
(8) (9)
#utf-8Referenced in:
* 4.2.5. The meta element
* 4.2.5.5. Specifying the document’s character encoding (2)
* 4.10.21.5. Selecting a form submission encoding
* 8.2.2.2. Determining the character encoding (2)
* 8.2.2.4. Changing the encoding while parsing
#iso-8859-2Referenced in:
* 8.2.2.2. Determining the character encoding (2) (3)
#iso-8859-8Referenced in:
* 10.3.5. Bidirectional text
#windows-1250Referenced in:
* 8.2.2.2. Determining the character encoding (2) (3)
#windows-1251Referenced in:
* 8.2.2.2. Determining the character encoding (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11) (12)
#windows-1252Referenced in:
* 8.2.2.2. Determining the character encoding (2)
* 8.2.2.4. Changing the encoding while parsing
#windows-1254Referenced in:
* 8.2.2.2. Determining the character encoding (2)
#windows-1256Referenced in:
* 8.2.2.2. Determining the character encoding (2)
#windows-1257Referenced in:
* 8.2.2.2. Determining the character encoding (2) (3)
#gb18030Referenced in:
* 8.2.2.2. Determining the character encoding
#big5Referenced in:
* 8.2.2.2. Determining the character encoding
#iso-2022-jpReferenced in:
* 4.2.5.5. Specifying the document’s character encoding
#shift_jisReferenced in:
* 8.2.2.2. Determining the character encoding
#euc-krReferenced in:
* 8.2.2.2. Determining the character encoding
#utf-16beReferenced in:
* 2.1.6. Character encodings
#utf-16leReferenced in:
* 2.1.6. Character encodings
#x-user-definedReferenced in:
* 8.2.2.2. Determining the character encoding
* 8.2.2.4. Changing the encoding while parsing
#change-the-encodingReferenced in:
* 8.2.2. The input byte stream
* 8.2.5.4.4. The "in head" insertion mode (2)
#input-streamReferenced in:
* 7.4.1. Opening the input stream
* 7.4.2. Closing the input stream
* 7.4.3. document.write() (2)
* 8.2.2. The input byte stream (2)
* 8.2.2.5. Preprocessing the input stream (2) (3)
* 8.2.6. The end
* 8.4. Parsing HTML fragments
#next-input-characterReferenced in:
* 8.2.2.5. Preprocessing the input stream
* 8.2.4. Tokenization
* 8.2.4.1. Data state
* 8.2.4.2. RCDATA state
* 8.2.4.3. RAWTEXT state
* 8.2.4.4. Script data state
* 8.2.4.5. PLAINTEXT state
* 8.2.4.6. Tag open state
* 8.2.4.7. End tag open state
* 8.2.4.8. Tag name state
* 8.2.4.9. RCDATA less-than sign state
* 8.2.4.10. RCDATA end tag open state
* 8.2.4.11. RCDATA end tag name state
* 8.2.4.12. RAWTEXT less-than sign state
* 8.2.4.13. RAWTEXT end tag open state
* 8.2.4.14. RAWTEXT end tag name state
* 8.2.4.15. Script data less-than sign state
* 8.2.4.16. Script data end tag open state
* 8.2.4.17. Script data end tag name state
* 8.2.4.18. Script data escape start state
* 8.2.4.19. Script data escape start dash state
* 8.2.4.20. Script data escaped state
* 8.2.4.21. Script data escaped dash state
* 8.2.4.22. Script data escaped dash dash state
* 8.2.4.23. Script data escaped less-than sign state
* 8.2.4.24. Script data escaped end tag open state
* 8.2.4.25. Script data escaped end tag name state
* 8.2.4.26. Script data double escape start state
* 8.2.4.27. Script data double escaped state
* 8.2.4.28. Script data double escaped dash state
* 8.2.4.29. Script data double escaped dash dash state
* 8.2.4.30. Script data double escaped less-than sign state
* 8.2.4.31. Script data double escape end state
* 8.2.4.32. Before attribute name state
* 8.2.4.33. Attribute name state
* 8.2.4.34. After attribute name state
* 8.2.4.35. Before attribute value state
* 8.2.4.36. Attribute value (double-quoted) state
* 8.2.4.37. Attribute value (single-quoted) state
* 8.2.4.38. Attribute value (unquoted) state
* 8.2.4.39. After attribute value (quoted) state
* 8.2.4.40. Self-closing start tag state
* 8.2.4.41. Bogus comment state
* 8.2.4.43. Comment start state
* 8.2.4.44. Comment start dash state
* 8.2.4.45. Comment state
* 8.2.4.46. Comment less-than sign state
* 8.2.4.50. Comment end dash state
* 8.2.4.51. Comment end state
* 8.2.4.52. Comment end bang state
* 8.2.4.53. DOCTYPE state
* 8.2.4.54. Before DOCTYPE name state
* 8.2.4.55. DOCTYPE name state
* 8.2.4.56. After DOCTYPE name state
* 8.2.4.57. After DOCTYPE public keyword state
* 8.2.4.58. Before DOCTYPE public identifier state
* 8.2.4.59. DOCTYPE public identifier (double-quoted) state
* 8.2.4.60. DOCTYPE public identifier (single-quoted) state
* 8.2.4.61. After DOCTYPE public identifier state
* 8.2.4.62. Between DOCTYPE public and system identifiers state
* 8.2.4.63. After DOCTYPE system keyword state
* 8.2.4.64. Before DOCTYPE system identifier state
* 8.2.4.65. DOCTYPE system identifier (double-quoted) state
* 8.2.4.66. DOCTYPE system identifier (single-quoted) state
* 8.2.4.67. After DOCTYPE system identifier state
* 8.2.4.68. Bogus DOCTYPE state
* 8.2.4.69. CDATA section state
* 8.2.4.70. CDATA section bracket state
* 8.2.4.71. CDATA section end state
* 8.2.4.72. Character reference state (2)
* 8.2.4.73. Numeric character reference state
* 8.2.4.74. Hexadecimal character reference start state
* 8.2.4.75. Decimal character reference start state
* 8.2.4.76. Hexadecimal character reference state
* 8.2.4.77. Decimal character reference state
* 8.2.4.79. Character reference end state
* 8.2.5.4.8. The "text" insertion mode (2)
* 8.2.5.5. The rules for parsing tokens in foreign content
#current-input-characterReferenced in:
* 8.2.4. Tokenization (2)
* 8.2.4.1. Data state (2)
* 8.2.4.2. RCDATA state
* 8.2.4.3. RAWTEXT state
* 8.2.4.4. Script data state
* 8.2.4.5. PLAINTEXT state
* 8.2.4.8. Tag name state (2)
* 8.2.4.11. RCDATA end tag name state (2) (3) (4)
* 8.2.4.14. RAWTEXT end tag name state (2) (3) (4)
* 8.2.4.17. Script data end tag name state (2) (3) (4)
* 8.2.4.20. Script data escaped state
* 8.2.4.21. Script data escaped dash state
* 8.2.4.22. Script data escaped dash dash state
* 8.2.4.25. Script data escaped end tag name state (2) (3) (4)
* 8.2.4.26. Script data double escape start state (2) (3) (4) (5)
* 8.2.4.27. Script data double escaped state
* 8.2.4.28. Script data double escaped dash state
* 8.2.4.29. Script data double escaped dash dash state
* 8.2.4.31. Script data double escape end state (2) (3) (4) (5)
* 8.2.4.32. Before attribute name state
* 8.2.4.33. Attribute name state (2)
* 8.2.4.36. Attribute value (double-quoted) state
* 8.2.4.37. Attribute value (single-quoted) state
* 8.2.4.38. Attribute value (unquoted) state
* 8.2.4.41. Bogus comment state
* 8.2.4.45. Comment state (2)
* 8.2.4.46. Comment less-than sign state (2)
* 8.2.4.54. Before DOCTYPE name state (2)
* 8.2.4.55. DOCTYPE name state (2)
* 8.2.4.56. After DOCTYPE name state (2)
* 8.2.4.59. DOCTYPE public identifier (double-quoted) state
* 8.2.4.60. DOCTYPE public identifier (single-quoted) state
* 8.2.4.65. DOCTYPE system identifier (double-quoted) state
* 8.2.4.66. DOCTYPE system identifier (single-quoted) state
* 8.2.4.69. CDATA section state
* 8.2.4.72. Character reference state
* 8.2.4.73. Numeric character reference state
* 8.2.4.76. Hexadecimal character reference state (2) (3)
* 8.2.4.77. Decimal character reference state
#insertion-pointReferenced in:
* 7.4.1. Opening the input stream
* 7.4.3. document.write() (2) (3) (4)
* 8.2.5.4.8. The "text" insertion mode (2) (3) (4) (5) (6)
* 8.2.5.5. The rules for parsing tokens in foreign content (2) (3) (4)
* 8.2.6. The end
#explicit-eof-characterReferenced in:
* 7.4.2. Closing the input stream (2)
#insertion-modeReferenced in:
* 8.2.3.1. The insertion mode (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19)
* 8.2.3.2. The stack of open elements (2)
* 8.2.4. Tokenization
* 8.2.5. Tree construction
* 8.2.5.2. Parsing elements that contain only text (2)
* 8.2.5.4.1. The "initial" insertion mode (2) (3)
* 8.2.5.4.2. The "before html" insertion mode (2) (3)
* 8.2.5.4.3. The "before head" insertion mode (2) (3) (4)
* 8.2.5.4.4. The "in head" insertion mode (2) (3) (4) (5) (6) (7) (8)
* 8.2.5.4.5. The "in head noscript" insertion mode (2) (3) (4) (5)
* 8.2.5.4.6. The "after head" insertion mode (2) (3) (4) (5) (6) (7)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12)
* 8.2.5.4.8. The "text" insertion mode (2) (3) (4)
* 8.2.5.4.9. The "in table" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11)
* 8.2.5.4.10. The "in table text" insertion mode (2)
* 8.2.5.4.11. The "in caption" insertion mode (2) (3) (4)
* 8.2.5.4.12. The "in column group" insertion mode (2) (3) (4) (5) (6)
* 8.2.5.4.13. The "in table body" insertion mode (2) (3) (4) (5) (6)
* 8.2.5.4.14. The "in row" insertion mode (2) (3) (4) (5) (6)
* 8.2.5.4.15. The "in cell" insertion mode (2) (3) (4)
* 8.2.5.4.16. The "in select" insertion mode (2) (3) (4)
* 8.2.5.4.17. The "in select in table" insertion mode (2)
* 8.2.5.4.18. The "in template" insertion mode (2) (3) (4) (5) (6) (7)
(8)
* 8.2.5.4.19. The "after body" insertion mode (2) (3) (4) (5)
* 8.2.5.4.20. The "in frameset" insertion mode (2) (3) (4)
* 8.2.5.4.21. The "after frameset" insertion mode (2) (3) (4)
* 8.2.5.4.22. The "after after body" insertion mode (2) (3)
* 8.2.5.4.23. The "after after frameset" insertion mode (2) (3)
* 8.2.5.5. The rules for parsing tokens in foreign content
* 8.2.8.1. Misnested tags: <b><i></b></i>
* 8.2.8.2. Misnested tags: <b><p></b></p>
* 8.2.8.3. Unexpected markup in tables (2) (3) (4) (5)
#using-the-rules-forReferenced in:
* 8.2.5.4.3. The "before head" insertion mode
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.5. The "in head noscript" insertion mode (2)
* 8.2.5.4.6. The "after head" insertion mode (2) (3)
* 8.2.5.4.7. The "in body" insertion mode (2)
* 8.2.5.4.9. The "in table" insertion mode (2) (3)
* 8.2.5.4.11. The "in caption" insertion mode
* 8.2.5.4.12. The "in column group" insertion mode (2) (3)
* 8.2.5.4.13. The "in table body" insertion mode
* 8.2.5.4.14. The "in row" insertion mode
* 8.2.5.4.15. The "in cell" insertion mode
* 8.2.5.4.16. The "in select" insertion mode (2) (3)
* 8.2.5.4.17. The "in select in table" insertion mode
* 8.2.5.4.18. The "in template" insertion mode (2)
* 8.2.5.4.19. The "after body" insertion mode (2)
* 8.2.5.4.20. The "in frameset" insertion mode (2)
* 8.2.5.4.21. The "after frameset" insertion mode (2)
* 8.2.5.4.22. The "after after body" insertion mode
* 8.2.5.4.23. The "after after frameset" insertion mode (2)
#original-insertion-modeReferenced in:
* 8.2.5.2. Parsing elements that contain only text
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.8. The "text" insertion mode (2) (3)
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.10. The "in table text" insertion mode
* 8.2.8.3. Unexpected markup in tables
#stack-of-template-insertion-modesReferenced in:
* 8.2.3.1. The insertion mode
* 8.2.5.4.4. The "in head" insertion mode (2)
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.18. The "in template" insertion mode (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11)
* 8.4. Parsing HTML fragments
#current-template-insertion-modeReferenced in:
* 8.2.3.1. The insertion mode
* 8.2.5.4.4. The "in head" insertion mode (2)
* 8.2.5.4.18. The "in template" insertion mode (2) (3) (4) (5) (6) (7)
(8) (9) (10) (11)
* 8.4. Parsing HTML fragments
#reset-the-insertion-mode-appropriatelyReferenced in:
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.9. The "in table" insertion mode (2)
* 8.2.5.4.16. The "in select" insertion mode (2) (3)
* 8.2.5.4.17. The "in select in table" insertion mode (2)
* 8.2.5.4.18. The "in template" insertion mode
* 8.4. Parsing HTML fragments
#stack-of-open-elementsReferenced in:
* 2.2.4. Interactions with XPath and XSLT
* 4.2.6. The style element (2) (3)
* 4.7.8. The object element (2) (3)
* 4.7.13.11.1. Text track model
* 4.10.11. The textarea element
* 8.2.3.1. The insertion mode (2) (3) (4)
* 8.2.3.2. The stack of open elements (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13)
* 8.2.3.3. The list of active formatting elements (2)
* 8.2.4. Tokenization
* 8.2.5. Tree construction
* 8.2.5.1. Creating and inserting nodes (2) (3) (4) (5) (6) (7)
* 8.2.5.3. Closing elements that have implied end tags (2)
* 8.2.5.4.2. The "before html" insertion mode (2)
* 8.2.5.4.4. The "in head" insertion mode (2) (3) (4) (5) (6) (7)
* 8.2.5.4.5. The "in head noscript" insertion mode (2)
* 8.2.5.4.6. The "after head" insertion mode (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22)
(23) (24) (25) (26) (27) (28) (29) (30) (31) (32) (33) (34) (35) (36)
(37) (38) (39) (40) (41) (42) (43) (44) (45) (46) (47) (48) (49) (50)
(51) (52) (53) (54) (55) (56) (57) (58) (59) (60) (61) (62) (63) (64)
(65) (66) (67) (68) (69) (70) (71) (72) (73) (74) (75) (76) (77) (78)
* 8.2.5.4.8. The "text" insertion mode (2) (3)
* 8.2.5.4.9. The "in table" insertion mode (2) (3) (4) (5) (6)
* 8.2.5.4.11. The "in caption" insertion mode (2)
* 8.2.5.4.12. The "in column group" insertion mode (2) (3)
* 8.2.5.4.13. The "in table body" insertion mode (2) (3) (4) (5)
* 8.2.5.4.14. The "in row" insertion mode (2) (3) (4) (5) (6) (7) (8)
* 8.2.5.4.15. The "in cell" insertion mode (2) (3) (4) (5) (6)
* 8.2.5.4.16. The "in select" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13)
* 8.2.5.4.17. The "in select in table" insertion mode (2) (3)
* 8.2.5.4.18. The "in template" insertion mode (2)
* 8.2.5.4.19. The "after body" insertion mode
* 8.2.5.4.20. The "in frameset" insertion mode (2)
* 8.2.5.5. The rules for parsing tokens in foreign content (2) (3) (4)
(5) (6) (7)
* 8.2.6. The end (2)
* 8.2.8.1. Misnested tags: <b><i></b></i> (2)
* 8.2.8.2. Misnested tags: <b><p></b></p> (2)
* 8.2.8.3. Unexpected markup in tables (2) (3) (4) (5)
* 8.2.8.4. Scripts that modify the page as it is being parsed
* 8.4. Parsing HTML fragments
* 9.2. Parsing XML documents
* 11.3.1. The applet element
#current-nodeReferenced in:
* 8.2.3.2. The stack of open elements (2)
* 8.2.5.1. Creating and inserting nodes (2)
* 8.2.5.3. Closing elements that have implied end tags (2) (3) (4)
* 8.2.5.4.4. The "in head" insertion mode (2) (3) (4) (5) (6)
* 8.2.5.4.5. The "in head noscript" insertion mode (2) (3) (4)
* 8.2.5.4.6. The "after head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22)
(23) (24) (25) (26) (27) (28) (29) (30) (31) (32) (33) (34)
* 8.2.5.4.8. The "text" insertion mode (2) (3) (4) (5)
* 8.2.5.4.9. The "in table" insertion mode (2) (3)
* 8.2.5.4.11. The "in caption" insertion mode (2)
* 8.2.5.4.12. The "in column group" insertion mode (2) (3) (4) (5)
* 8.2.5.4.13. The "in table body" insertion mode (2) (3) (4)
* 8.2.5.4.14. The "in row" insertion mode (2) (3) (4) (5)
* 8.2.5.4.15. The "in cell" insertion mode (2)
* 8.2.5.4.16. The "in select" insertion mode (2) (3) (4) (5) (6) (7)
* 8.2.5.4.20. The "in frameset" insertion mode (2) (3) (4) (5) (6)
* 8.2.5.5. The rules for parsing tokens in foreign content (2) (3) (4)
(5) (6)
#adjusted-current-nodeReferenced in:
* 8.2.3.2. The stack of open elements
* 8.2.4.42. Markup declaration open state
* 8.2.5. Tree construction (2) (3) (4) (5) (6)
* 8.2.5.5. The rules for parsing tokens in foreign content (2) (3) (4)
#specialReferenced in:
* 8.2.3.2. The stack of open elements (2) (3)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4)
#formattingReferenced in:
* 8.2.3.3. The list of active formatting elements (2)
#ordinaryReferenced in:
* 8.2.3.2. The stack of open elements (2)
* 8.2.5.4.7. The "in body" insertion mode
#has-that-element-in-the-specific-scopeReferenced in:
* 8.2.3.2. The stack of open elements (2) (3) (4) (5)
#in-scopeReferenced in:
* 8.2.3.2. The stack of open elements (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13)
#have-an-li-element-in-list-item-scopeReferenced in:
* 8.2.5.4.7. The "in body" insertion mode
#has-a-p-element-in-button-scopeReferenced in:
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11)
#in-table-scopeReferenced in:
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.9. The "in table" insertion mode (2) (3)
* 8.2.5.4.11. The "in caption" insertion mode (2)
* 8.2.5.4.13. The "in table body" insertion mode (2)
* 8.2.5.4.14. The "in row" insertion mode (2) (3) (4)
* 8.2.5.4.15. The "in cell" insertion mode (2) (3) (4)
* 8.2.5.4.17. The "in select in table" insertion mode
#have-a-select-element-in-select-scopeReferenced in:
* 8.2.5.4.16. The "in select" insertion mode (2) (3)
#list-of-active-formatting-elementsReferenced in:
* 8.2.3.2. The stack of open elements
* 8.2.3.3. The list of active formatting elements (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11) (12) (13) (14)
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14)
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.14. The "in row" insertion mode
* 8.2.8.1. Misnested tags: <b><i></b></i> (2)
* 8.2.8.2. Misnested tags: <b><p></b></p> (2) (3)
* 8.2.8.3. Unexpected markup in tables (2) (3) (4) (5) (6)
* 8.2.8.6. Unclosed formatting elements
#markersReferenced in:
* 8.2.3.3. The list of active formatting elements (2) (3) (4) (5) (6)
(7)
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4)
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.14. The "in row" insertion mode
* 8.2.8.3. Unexpected markup in tables (2) (3)
#push-onto-the-list-of-active-formatting-elementsReferenced in:
* 8.2.5.4.7. The "in body" insertion mode (2) (3)
#reconstruct-the-active-formatting-elementsReferenced in:
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15) (16)
* 8.2.8.1. Misnested tags: <b><i></b></i>
* 8.2.8.3. Unexpected markup in tables
#clear-the-list-of-active-formatting-elements-up-to-the-last-markerReferenced
in:
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.11. The "in caption" insertion mode (2)
* 8.2.5.4.15. The "in cell" insertion mode (2)
* 8.2.5.4.18. The "in template" insertion mode
#head-element-pointerReferenced in:
* 8.2.3.1. The insertion mode (2)
* 8.2.3.4. The element pointers
* 8.2.5.4.3. The "before head" insertion mode (2)
* 8.2.5.4.6. The "after head" insertion mode (2) (3)
#form-element-pointerReferenced in:
* 8.2.3.4. The element pointers
* 8.2.5.1. Creating and inserting nodes (2) (3)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4)
* 8.2.5.4.9. The "in table" insertion mode (2)
* 8.2.7. Coercing an HTML DOM into an infoset
* 8.4. Parsing HTML fragments (2)
#scripting-flagReferenced in:
* 2.2.1. Conformance classes
* 4.12.2. The noscript element
* 8.2.3.5. Other parsing state flags
* 8.2.5.4.4. The "in head" insertion mode (2)
* 8.2.5.4.7. The "in body" insertion mode
* 8.4. Parsing HTML fragments
#frameset-ok-flagReferenced in:
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.6. The "after head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15) (16)
* 8.2.5.5. The rules for parsing tokens in foreign content
#reconsumeReferenced in:
* 8.2.4. Tokenization
* 8.2.4.6. Tag open state (2) (3)
* 8.2.4.7. End tag open state (2)
* 8.2.4.9. RCDATA less-than sign state
* 8.2.4.10. RCDATA end tag open state (2)
* 8.2.4.11. RCDATA end tag name state
* 8.2.4.12. RAWTEXT less-than sign state
* 8.2.4.13. RAWTEXT end tag open state (2)
* 8.2.4.14. RAWTEXT end tag name state
* 8.2.4.15. Script data less-than sign state
* 8.2.4.16. Script data end tag open state (2)
* 8.2.4.17. Script data end tag name state
* 8.2.4.18. Script data escape start state
* 8.2.4.19. Script data escape start dash state
* 8.2.4.23. Script data escaped less-than sign state (2)
* 8.2.4.24. Script data escaped end tag open state (2)
* 8.2.4.25. Script data escaped end tag name state
* 8.2.4.26. Script data double escape start state
* 8.2.4.30. Script data double escaped less-than sign state
* 8.2.4.31. Script data double escape end state
* 8.2.4.32. Before attribute name state (2)
* 8.2.4.33. Attribute name state
* 8.2.4.34. After attribute name state
* 8.2.4.35. Before attribute value state
* 8.2.4.39. After attribute value (quoted) state
* 8.2.4.40. Self-closing start tag state
* 8.2.4.43. Comment start state
* 8.2.4.44. Comment start dash state
* 8.2.4.46. Comment less-than sign state
* 8.2.4.47. Comment less-than sign bang state
* 8.2.4.48. Comment less-than sign bang dash state
* 8.2.4.49. Comment less-than sign bang dash dash state (2)
* 8.2.4.50. Comment end dash state
* 8.2.4.51. Comment end state
* 8.2.4.52. Comment end bang state
* 8.2.4.53. DOCTYPE state
* 8.2.4.70. CDATA section bracket state
* 8.2.4.71. CDATA section end state
* 8.2.4.72. Character reference state
* 8.2.4.73. Numeric character reference state
* 8.2.4.74. Hexadecimal character reference start state (2)
* 8.2.4.75. Decimal character reference start state (2)
* 8.2.4.76. Hexadecimal character reference state
* 8.2.4.77. Decimal character reference state
* 8.2.4.79. Character reference end state
#temporary-bufferReferenced in:
* 8.2.4.72. Character reference state (2) (3) (4) (5) (6)
* 8.2.4.73. Numeric character reference state
* 8.2.4.78. Numeric character reference end state (2)
* 8.2.4.79. Character reference end state (2)
#return-stateReferenced in:
* 8.2.4.1. Data state
* 8.2.4.2. RCDATA state
* 8.2.4.36. Attribute value (double-quoted) state
* 8.2.4.37. Attribute value (single-quoted) state
* 8.2.4.38. Attribute value (unquoted) state
* 8.2.4.72. Character reference state
* 8.2.4.79. Character reference end state (2)
#force-quirks-flagReferenced in:
* 8.2.4. Tokenization
* 8.2.4.53. DOCTYPE state
* 8.2.4.54. Before DOCTYPE name state (2)
* 8.2.4.55. DOCTYPE name state
* 8.2.4.56. After DOCTYPE name state (2)
* 8.2.4.57. After DOCTYPE public keyword state (2) (3)
* 8.2.4.58. Before DOCTYPE public identifier state (2) (3)
* 8.2.4.59. DOCTYPE public identifier (double-quoted) state (2)
* 8.2.4.60. DOCTYPE public identifier (single-quoted) state (2)
* 8.2.4.61. After DOCTYPE public identifier state (2)
* 8.2.4.62. Between DOCTYPE public and system identifiers state (2)
* 8.2.4.63. After DOCTYPE system keyword state (2) (3)
* 8.2.4.64. Before DOCTYPE system identifier state (2) (3)
* 8.2.4.65. DOCTYPE system identifier (double-quoted) state (2)
* 8.2.4.66. DOCTYPE system identifier (single-quoted) state (2)
* 8.2.4.67. After DOCTYPE system identifier state (2)
* 8.2.5.4.1. The "initial" insertion mode
#self-closing-flagReferenced in:
* 8.2.4. Tokenization (2) (3)
* 8.2.4.40. Self-closing start tag state
* 8.2.5.4.7. The "in body" insertion mode (2)
* 8.2.5.5. The rules for parsing tokens in foreign content
#acknowledgedReferenced in:
* 8.2.5.4.4. The "in head" insertion mode (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6)
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.12. The "in column group" insertion mode
* 8.2.5.4.20. The "in frameset" insertion mode
* 8.2.5.5. The rules for parsing tokens in foreign content (2)
#appropriate-end-tag-tokenReferenced in:
* 8.2.4.11. RCDATA end tag name state (2) (3)
* 8.2.4.14. RAWTEXT end tag name state (2) (3)
* 8.2.4.17. Script data end tag name state (2) (3)
* 8.2.4.25. Script data escaped end tag name state (2) (3)
* 8.4. Parsing HTML fragments
#tokenizer-data-stateReferenced in:
* 8.2.4. Tokenization
* 8.2.4.1. Data state
* 8.2.4.6. Tag open state
* 8.2.4.7. End tag open state
* 8.2.4.8. Tag name state
* 8.2.4.11. RCDATA end tag name state
* 8.2.4.14. RAWTEXT end tag name state
* 8.2.4.17. Script data end tag name state
* 8.2.4.25. Script data escaped end tag name state
* 8.2.4.34. After attribute name state
* 8.2.4.38. Attribute value (unquoted) state
* 8.2.4.39. After attribute value (quoted) state
* 8.2.4.40. Self-closing start tag state
* 8.2.4.41. Bogus comment state
* 8.2.4.43. Comment start state
* 8.2.4.44. Comment start dash state
* 8.2.4.51. Comment end state
* 8.2.4.52. Comment end bang state
* 8.2.4.54. Before DOCTYPE name state
* 8.2.4.55. DOCTYPE name state
* 8.2.4.56. After DOCTYPE name state
* 8.2.4.57. After DOCTYPE public keyword state
* 8.2.4.58. Before DOCTYPE public identifier state
* 8.2.4.59. DOCTYPE public identifier (double-quoted) state
* 8.2.4.60. DOCTYPE public identifier (single-quoted) state
* 8.2.4.61. After DOCTYPE public identifier state
* 8.2.4.62. Between DOCTYPE public and system identifiers state
* 8.2.4.63. After DOCTYPE system keyword state
* 8.2.4.64. Before DOCTYPE system identifier state
* 8.2.4.65. DOCTYPE system identifier (double-quoted) state
* 8.2.4.66. DOCTYPE system identifier (single-quoted) state
* 8.2.4.67. After DOCTYPE system identifier state
* 8.2.4.68. Bogus DOCTYPE state
* 8.2.4.71. CDATA section end state
* 8.4. Parsing HTML fragments (2)
#tokenizer-rcdata-stateReferenced in:
* 8.2.4.2. RCDATA state
* 8.2.4.9. RCDATA less-than sign state
* 8.2.4.10. RCDATA end tag open state
* 8.2.4.11. RCDATA end tag name state
* 8.2.5.2. Parsing elements that contain only text
* 8.2.5.4.7. The "in body" insertion mode
* 8.4. Parsing HTML fragments
#tokenizer-rawtext-stateReferenced in:
* 8.2.4.12. RAWTEXT less-than sign state
* 8.2.4.13. RAWTEXT end tag open state
* 8.2.4.14. RAWTEXT end tag name state
* 8.2.5.2. Parsing elements that contain only text
* 8.4. Parsing HTML fragments (2)
#tokenizer-script-data-stateReferenced in:
* 8.2.4.15. Script data less-than sign state
* 8.2.4.16. Script data end tag open state
* 8.2.4.17. Script data end tag name state
* 8.2.4.18. Script data escape start state
* 8.2.4.19. Script data escape start dash state
* 8.2.4.22. Script data escaped dash dash state
* 8.2.4.29. Script data double escaped dash dash state
* 8.2.5.4.4. The "in head" insertion mode
* 8.4. Parsing HTML fragments
#tokenizer-tag-open-stateReferenced in:
* 8.2.4.1. Data state
#tokenizer-end-tag-open-stateReferenced in:
* 8.2.4.6. Tag open state
#tokenizer-tag-name-stateReferenced in:
* 8.2.4.6. Tag open state
* 8.2.4.7. End tag open state
#tokenizer-rcdata-less-than-sign-stateReferenced in:
* 8.2.4.2. RCDATA state
#tokenizer-rcdata-end-tag-open-stateReferenced in:
* 8.2.4.9. RCDATA less-than sign state
#tokenizer-rcdata-end-tag-name-stateReferenced in:
* 8.2.4.10. RCDATA end tag open state
#tokenizer-rawtext-less-than-sign-stateReferenced in:
* 8.2.4.3. RAWTEXT state
#tokenizer-rawtext-end-tag-open-stateReferenced in:
* 8.2.4.12. RAWTEXT less-than sign state
#tokenizer-rawtext-end-tag-name-stateReferenced in:
* 8.2.4.13. RAWTEXT end tag open state
#tokenizer-script-data-less-than-sign-stateReferenced in:
* 8.2.4.4. Script data state
#tokenizer-script-data-end-tag-open-stateReferenced in:
* 8.2.4.15. Script data less-than sign state
#tokenizer-script-data-end-tag-name-stateReferenced in:
* 8.2.4.16. Script data end tag open state
#tokenizer-script-data-escape-start-stateReferenced in:
* 8.2.4.15. Script data less-than sign state
#tokenizer-script-data-escapse-start-dash-stateReferenced in:
* 8.2.4.18. Script data escape start state
#tokenizer-script-data-escaped-stateReferenced in:
* 8.2.4.21. Script data escaped dash state (2)
* 8.2.4.22. Script data escaped dash dash state (2)
* 8.2.4.23. Script data escaped less-than sign state
* 8.2.4.24. Script data escaped end tag open state
* 8.2.4.25. Script data escaped end tag name state
* 8.2.4.26. Script data double escape start state (2)
* 8.2.4.31. Script data double escape end state
#tokenizer-script-data-escaped-dash-stateReferenced in:
* 8.2.4.20. Script data escaped state
#tokenizer-script-data-escaped-dash-dash-stateReferenced in:
* 8.2.4.19. Script data escape start dash state
* 8.2.4.21. Script data escaped dash state
#tokenizer-script-data-escaped-less-than-sign-stateReferenced in:
* 8.2.4.20. Script data escaped state
* 8.2.4.21. Script data escaped dash state
* 8.2.4.22. Script data escaped dash dash state
#tokenizer-script-data-escaped-end-tag-open-stateReferenced in:
* 8.2.4.23. Script data escaped less-than sign state
#tokenizer-script-data-escaped-end-tag-name-stateReferenced in:
* 8.2.4.24. Script data escaped end tag open state
#tokenizer-script-data-double-escape-start-stateReferenced in:
* 8.2.4.23. Script data escaped less-than sign state
#tokenizer-script-data-double-escaped-stateReferenced in:
* 8.2.4.26. Script data double escape start state
* 8.2.4.28. Script data double escaped dash state (2)
* 8.2.4.29. Script data double escaped dash dash state (2)
* 8.2.4.30. Script data double escaped less-than sign state
* 8.2.4.31. Script data double escape end state (2)
#tokenizer-script-data-double-escaped-dash-stateReferenced in:
* 8.2.4.27. Script data double escaped state
#tokenizer-script-data-double-escaped-dash-dash-stateReferenced in:
* 8.2.4.28. Script data double escaped dash state
#tokenizer-script-data-double-escaped-less-than-sign-stateReferenced in:
* 8.2.4.27. Script data double escaped state
* 8.2.4.28. Script data double escaped dash state
* 8.2.4.29. Script data double escaped dash dash state
#tokenizer-script-data-double-escape-end-stateReferenced in:
* 8.2.4.30. Script data double escaped less-than sign state
#tokenizer-before-attribute-name-stateReferenced in:
* 8.2.4.8. Tag name state
* 8.2.4.11. RCDATA end tag name state
* 8.2.4.14. RAWTEXT end tag name state
* 8.2.4.17. Script data end tag name state
* 8.2.4.25. Script data escaped end tag name state
* 8.2.4.38. Attribute value (unquoted) state
* 8.2.4.39. After attribute value (quoted) state (2)
* 8.2.4.40. Self-closing start tag state
#tokenizer-attribute-name-stateReferenced in:
* 8.2.4.32. Before attribute name state (2)
* 8.2.4.34. After attribute name state
#tokenizer-after-attribute-name-stateReferenced in:
* 8.2.4.32. Before attribute name state
* 8.2.4.33. Attribute name state
#tokenizer-before-attribute-value-stateReferenced in:
* 8.2.4.33. Attribute name state
* 8.2.4.34. After attribute name state
#tokenizer-attribute-value-double-quoted-stateReferenced in:
* 8.2.4.35. Before attribute value state
* 8.2.4.36. Attribute value (double-quoted) state
* 8.2.4.72. Character reference state
* 8.2.4.79. Character reference end state
#tokenizer-attribute-value-single-quoted-stateReferenced in:
* 8.2.4.35. Before attribute value state
* 8.2.4.37. Attribute value (single-quoted) state
* 8.2.4.72. Character reference state
* 8.2.4.79. Character reference end state
#tokenizer-attribute-value-unquoted-stateReferenced in:
* 8.2.4.35. Before attribute value state
* 8.2.4.38. Attribute value (unquoted) state
* 8.2.4.72. Character reference state
* 8.2.4.79. Character reference end state
#tokenizer-after-attribute-value-quoted-stateReferenced in:
* 8.2.4.36. Attribute value (double-quoted) state
* 8.2.4.37. Attribute value (single-quoted) state
#tokenizer-self-closing-start-tag-stateReferenced in:
* 8.2.4.8. Tag name state
* 8.2.4.11. RCDATA end tag name state
* 8.2.4.14. RAWTEXT end tag name state
* 8.2.4.17. Script data end tag name state
* 8.2.4.25. Script data escaped end tag name state
* 8.2.4.34. After attribute name state
* 8.2.4.39. After attribute value (quoted) state
#tokenizer-bogus-comment-stateReferenced in:
* 8.2.4.6. Tag open state
* 8.2.4.7. End tag open state
* 8.2.4.42. Markup declaration open state
#tokenizer-markup-declaration-open-stateReferenced in:
* 8.2.4.6. Tag open state
#tokenizer-comment-start-stateReferenced in:
* 8.2.4.42. Markup declaration open state
#tokenizer-comment-start-dash-stateReferenced in:
* 8.2.4.43. Comment start state
#tokenizer-comment-stateReferenced in:
* 8.2.4.43. Comment start state
* 8.2.4.44. Comment start dash state
* 8.2.4.46. Comment less-than sign state
* 8.2.4.47. Comment less-than sign bang state
* 8.2.4.50. Comment end dash state
* 8.2.4.51. Comment end state
* 8.2.4.52. Comment end bang state
#tokenizer-comment-less-than-sign-stateReferenced in:
* 8.2.4.45. Comment state
#tokenizer-comment-less-than-sign-bang-stateReferenced in:
* 8.2.4.46. Comment less-than sign state
#tokenizer-comment-less-than-sign-bang-dash-stateReferenced in:
* 8.2.4.47. Comment less-than sign bang state
#tokenizer-comment-less-than-sign-bang-dash-dash-stateReferenced in:
* 8.2.4.48. Comment less-than sign bang dash state
#tokenizer-comment-end-dash-stateReferenced in:
* 8.2.4.45. Comment state
* 8.2.4.48. Comment less-than sign bang dash state
* 8.2.4.52. Comment end bang state
#tokenizer-comment-end-stateReferenced in:
* 8.2.4.44. Comment start dash state
* 8.2.4.49. Comment less-than sign bang dash dash state (2)
* 8.2.4.50. Comment end dash state
#tokenizer-comment-end-bang-stateReferenced in:
* 8.2.4.51. Comment end state
#tokenizer-doctype-stateReferenced in:
* 8.2.4.42. Markup declaration open state
#tokenizer-before-doctype-name-stateReferenced in:
* 8.2.4.53. DOCTYPE state (2)
#tokenizer-doctype-name-stateReferenced in:
* 8.2.4.54. Before DOCTYPE name state (2) (3)
#tokenizer-after-doctype-name-stateReferenced in:
* 8.2.4.55. DOCTYPE name state
#tokenizer-after-doctype-public-keyword-stateReferenced in:
* 8.2.4.56. After DOCTYPE name state
#tokenizer-before-doctype-public-identifier-stateReferenced in:
* 8.2.4.57. After DOCTYPE public keyword state
#tokenizer-doctype-public-identifier-double-quoted-stateReferenced in:
* 8.2.4.57. After DOCTYPE public keyword state
* 8.2.4.58. Before DOCTYPE public identifier state
#tokenizer-doctype-public-identifier-single-quoted-stateReferenced in:
* 8.2.4.57. After DOCTYPE public keyword state
* 8.2.4.58. Before DOCTYPE public identifier state
#tokenizer-after-doctype-public-identifier-stateReferenced in:
* 8.2.4.59. DOCTYPE public identifier (double-quoted) state
* 8.2.4.60. DOCTYPE public identifier (single-quoted) state
#tokenizer-between-doctype-public-and-system-identifiers-stateReferenced
in:
* 8.2.4.61. After DOCTYPE public identifier state
#tokenizer-after-doctype-system-keyword-stateReferenced in:
* 8.2.4.56. After DOCTYPE name state
#tokenizer-before-doctype-system-identifier-stateReferenced in:
* 8.2.4.63. After DOCTYPE system keyword state
#tokenizer-doctype-system-identifier-double-quoted-stateReferenced in:
* 8.2.4.61. After DOCTYPE public identifier state
* 8.2.4.62. Between DOCTYPE public and system identifiers state
* 8.2.4.63. After DOCTYPE system keyword state
* 8.2.4.64. Before DOCTYPE system identifier state
#tokenizer-doctype-system-identifier-single-quoted-stateReferenced in:
* 8.2.4.61. After DOCTYPE public identifier state
* 8.2.4.62. Between DOCTYPE public and system identifiers state
* 8.2.4.63. After DOCTYPE system keyword state
* 8.2.4.64. Before DOCTYPE system identifier state
#tokenizer-after-doctype-system-identifier-stateReferenced in:
* 8.2.4.65. DOCTYPE system identifier (double-quoted) state
* 8.2.4.66. DOCTYPE system identifier (single-quoted) state
#tokenizer-bogus-doctype-stateReferenced in:
* 8.2.4.56. After DOCTYPE name state
* 8.2.4.57. After DOCTYPE public keyword state
* 8.2.4.58. Before DOCTYPE public identifier state
* 8.2.4.61. After DOCTYPE public identifier state
* 8.2.4.62. Between DOCTYPE public and system identifiers state
* 8.2.4.63. After DOCTYPE system keyword state
* 8.2.4.64. Before DOCTYPE system identifier state
* 8.2.4.67. After DOCTYPE system identifier state
#tokenizer-cdata-section-stateReferenced in:
* 8.2.4.42. Markup declaration open state
* 8.2.4.70. CDATA section bracket state
* 8.2.4.71. CDATA section end state
#tokenizer-cdata-section-bracket-stateReferenced in:
* 8.2.4.69. CDATA section state
#tokenizer-cdata-section-end-stateReferenced in:
* 8.2.4.70. CDATA section bracket state
#tokenizer-character-reference-stateReferenced in:
* 8.2.4. Tokenization
* 8.2.4.1. Data state
* 8.2.4.2. RCDATA state
* 8.2.4.36. Attribute value (double-quoted) state
* 8.2.4.37. Attribute value (single-quoted) state
* 8.2.4.38. Attribute value (unquoted) state
#tokenizer-numeric-character-reference-stateReferenced in:
* 8.2.4.72. Character reference state
#character-reference-codeReferenced in:
* 8.2.4.76. Hexadecimal character reference state (2) (3) (4) (5) (6)
* 8.2.4.77. Decimal character reference state (2)
* 8.2.4.78. Numeric character reference end state (2) (3) (4)
#tokenizer-hexadecimal-character-reference-start-stateReferenced in:
* 8.2.4.73. Numeric character reference state
#tokenizer-decimal-character-reference-start-stateReferenced in:
* 8.2.4.73. Numeric character reference state
#tokenizer-hexadecimal-character-reference-stateReferenced in:
* 8.2.4.74. Hexadecimal character reference start state
#tokenizer-decimal-character-reference-stateReferenced in:
* 8.2.4.75. Decimal character reference start state
#tokenizer-numeric-character-reference-end-stateReferenced in:
* 8.2.4.76. Hexadecimal character reference state (2)
* 8.2.4.77. Decimal character reference state (2)
#tokenizer-character-reference-end-stateReferenced in:
* 8.2.4.72. Character reference state (2) (3) (4)
* 8.2.4.74. Hexadecimal character reference start state
* 8.2.4.75. Decimal character reference start state
* 8.2.4.78. Numeric character reference end state
#tree-construction-dispatcherReferenced in:
* 8.2.5. Tree construction
#next-tokenReferenced in:
* 8.2.5.4.7. The "in body" insertion mode (2)
#mathml-text-integration-pointReferenced in:
* 8.2.5. Tree construction (2)
* 8.2.5.5. The rules for parsing tokens in foreign content
#html-integration-pointReferenced in:
* 8.2.5. Tree construction (2)
* 8.2.5.5. The rules for parsing tokens in foreign content
* 8.4. Parsing HTML fragments
#foster-parentingReferenced in:
* 8.2.5.1. Creating and inserting nodes (2) (3) (4)
* 8.2.5.4.9. The "in table" insertion mode (2)
* 8.2.8.3. Unexpected markup in tables (2) (3)
#appropriate-place-for-inserting-a-nodeReferenced in:
* 8.2.5.1. Creating and inserting nodes (2) (3)
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode
#create-an-element-for-the-tokenReferenced in:
* 7.4. Dynamic markup insertion
* 8.2.5.1. Creating and inserting nodes
* 8.2.5.4.2. The "before html" insertion mode
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode (2)
#insert-a-foreign-elementReferenced in:
* 8.2.5.1. Creating and inserting nodes
* 8.2.5.4.7. The "in body" insertion mode (2)
* 8.2.5.5. The rules for parsing tokens in foreign content
#insert-an-html-elementReferenced in:
* 8.2.3.3. The list of active formatting elements
* 8.2.5.2. Parsing elements that contain only text
* 8.2.5.4.3. The "before head" insertion mode (2)
* 8.2.5.4.4. The "in head" insertion mode (2) (3) (4)
* 8.2.5.4.6. The "after head" insertion mode (2) (3)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19) (20) (21) (22)
(23) (24) (25)
* 8.2.5.4.9. The "in table" insertion mode (2) (3) (4) (5) (6) (7)
* 8.2.5.4.12. The "in column group" insertion mode
* 8.2.5.4.13. The "in table body" insertion mode (2)
* 8.2.5.4.14. The "in row" insertion mode
* 8.2.5.4.16. The "in select" insertion mode (2)
* 8.2.5.4.20. The "in frameset" insertion mode (2)
#adjust-mathml-attributesReferenced in:
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.5. The rules for parsing tokens in foreign content
#adjust-svg-attributesReferenced in:
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.5. The rules for parsing tokens in foreign content
#adjust-foreign-attributesReferenced in:
* 8.2.5.4.7. The "in body" insertion mode (2)
* 8.2.5.5. The rules for parsing tokens in foreign content
* 8.2.7. Coercing an HTML DOM into an infoset (2)
#insert-a-characterReferenced in:
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.6. The "after head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode (2)
* 8.2.5.4.8. The "text" insertion mode
* 8.2.5.4.10. The "in table text" insertion mode
* 8.2.5.4.12. The "in column group" insertion mode
* 8.2.5.4.16. The "in select" insertion mode
* 8.2.5.4.20. The "in frameset" insertion mode
* 8.2.5.4.21. The "after frameset" insertion mode
* 8.2.5.5. The rules for parsing tokens in foreign content (2) (3)
#insert-a-commentReferenced in:
* 8.2.5.4.1. The "initial" insertion mode
* 8.2.5.4.2. The "before html" insertion mode
* 8.2.5.4.3. The "before head" insertion mode
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.6. The "after head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.12. The "in column group" insertion mode
* 8.2.5.4.16. The "in select" insertion mode
* 8.2.5.4.19. The "after body" insertion mode
* 8.2.5.4.20. The "in frameset" insertion mode
* 8.2.5.4.21. The "after frameset" insertion mode
* 8.2.5.4.22. The "after after body" insertion mode
* 8.2.5.4.23. The "after after frameset" insertion mode
* 8.2.5.5. The rules for parsing tokens in foreign content
#generic-raw-text-element-parsing-algorithmReferenced in:
* 8.2.5.2. Parsing elements that contain only text
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode (2) (3)
#generic-rcdata-element-parsing-algorithmReferenced in:
* 8.2.5.2. Parsing elements that contain only text
* 8.2.5.4.4. The "in head" insertion mode
#generate-implied-end-tagsReferenced in:
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11) (12) (13) (14) (15)
* 8.2.5.4.11. The "in caption" insertion mode (2)
* 8.2.5.4.15. The "in cell" insertion mode (2)
#generate-all-implied-end-tags-thoroughlyReferenced in:
* 8.2.5.4.4. The "in head" insertion mode
#initialReferenced in:
* 8.2.3.1. The insertion mode
* 8.2.5.4.1. The "initial" insertion mode
#before-htmlReferenced in:
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements (2)
* 8.2.5.4.1. The "initial" insertion mode (2)
* 8.2.5.4.2. The "before html" insertion mode
#before-headReferenced in:
* 8.2.3.1. The insertion mode (2)
* 8.2.5.4.2. The "before html" insertion mode (2)
* 8.2.5.4.3. The "before head" insertion mode
#in-headReferenced in:
* 8.2.3.1. The insertion mode (2) (3)
* 8.2.5.4.3. The "before head" insertion mode (2)
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.5. The "in head noscript" insertion mode (2) (3)
* 8.2.5.4.6. The "after head" insertion mode (2)
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.12. The "in column group" insertion mode
* 8.2.5.4.16. The "in select" insertion mode
* 8.2.5.4.18. The "in template" insertion mode
* 8.2.5.4.20. The "in frameset" insertion mode
* 8.2.5.4.21. The "after frameset" insertion mode
* 8.2.5.4.23. The "after after frameset" insertion mode
#used-during-the-parsingReferenced in:
* 8.2.2. The input byte stream
#in-head-noscriptReferenced in:
* 8.2.3.1. The insertion mode
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.5. The "in head noscript" insertion mode
#after-headReferenced in:
* 8.2.3.1. The insertion mode (2)
* 8.2.5.4.4. The "in head" insertion mode (2)
* 8.2.5.4.6. The "after head" insertion mode
#in-bodyReferenced in:
* 8.2.3.1. The insertion mode (2) (3) (4)
* 8.2.5.4.3. The "before head" insertion mode
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.5. The "in head noscript" insertion mode
* 8.2.5.4.6. The "after head" insertion mode (2) (3)
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.9. The "in table" insertion mode (2)
* 8.2.5.4.11. The "in caption" insertion mode
* 8.2.5.4.12. The "in column group" insertion mode (2)
* 8.2.5.4.15. The "in cell" insertion mode
* 8.2.5.4.16. The "in select" insertion mode (2)
* 8.2.5.4.18. The "in template" insertion mode (2) (3)
* 8.2.5.4.19. The "after body" insertion mode (2) (3)
* 8.2.5.4.20. The "in frameset" insertion mode
* 8.2.5.4.21. The "after frameset" insertion mode
* 8.2.5.4.22. The "after after body" insertion mode (2)
* 8.2.5.4.23. The "after after frameset" insertion mode
* 8.2.8.1. Misnested tags: <b><i></b></i>
* 8.2.8.2. Misnested tags: <b><p></b></p>
* 8.2.8.3. Unexpected markup in tables
#close-a-p-elementReferenced in:
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4) (5) (6) (7) (8)
(9) (10) (11)
#adoption-agency-algorithmReferenced in:
* 8.2.3.2. The stack of open elements (2)
* 8.2.5.4.7. The "in body" insertion mode (2) (3) (4)
* 8.2.8.1. Misnested tags: <b><i></b></i>
* 8.2.8.2. Misnested tags: <b><p></b></p>
#in-textReferenced in:
* 8.2.3.1. The insertion mode (2)
* 8.2.5.2. Parsing elements that contain only text
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.8. The "text" insertion mode
#in-tableReferenced in:
* 8.2.3.1. The insertion mode (2) (3)
* 8.2.5.4.7. The "in body" insertion mode (2)
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.10. The "in table text" insertion mode
* 8.2.5.4.11. The "in caption" insertion mode (2)
* 8.2.5.4.12. The "in column group" insertion mode (2)
* 8.2.5.4.13. The "in table body" insertion mode (2) (3)
* 8.2.5.4.14. The "in row" insertion mode
* 8.2.5.4.18. The "in template" insertion mode (2)
* 8.2.8.3. Unexpected markup in tables (2)
#clear-the-stack-back-to-a-table-contextReferenced in:
* 8.2.5.4.9. The "in table" insertion mode (2) (3) (4) (5)
#in-table-textReferenced in:
* 8.2.3.1. The insertion mode (2)
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.10. The "in table text" insertion mode
* 8.2.8.3. Unexpected markup in tables
#in-captionReferenced in:
* 8.2.3.1. The insertion mode (2)
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.11. The "in caption" insertion mode
#in-column-groupReferenced in:
* 8.2.3.1. The insertion mode (2)
* 8.2.5.4.9. The "in table" insertion mode (2)
* 8.2.5.4.12. The "in column group" insertion mode
* 8.2.5.4.18. The "in template" insertion mode (2)
#in-table-bodyReferenced in:
* 8.2.3.1. The insertion mode (2)
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.9. The "in table" insertion mode (2)
* 8.2.5.4.13. The "in table body" insertion mode
* 8.2.5.4.14. The "in row" insertion mode (2) (3)
* 8.2.5.4.18. The "in template" insertion mode (2)
* 8.2.8.3. Unexpected markup in tables (2) (3) (4)
#clear-the-stack-back-to-a-table-body-contextReferenced in:
* 8.2.5.4.13. The "in table body" insertion mode (2) (3) (4)
#in-rowReferenced in:
* 8.2.3.1. The insertion mode (2)
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.13. The "in table body" insertion mode (2)
* 8.2.5.4.14. The "in row" insertion mode
* 8.2.5.4.15. The "in cell" insertion mode (2)
* 8.2.5.4.18. The "in template" insertion mode (2)
* 8.2.8.3. Unexpected markup in tables (2)
#clear-the-stack-back-to-a-table-row-contextReferenced in:
* 8.2.5.4.14. The "in row" insertion mode (2) (3) (4)
#in-cellReferenced in:
* 8.2.3.1. The insertion mode (2)
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.14. The "in row" insertion mode
* 8.2.5.4.15. The "in cell" insertion mode
* 8.2.8.3. Unexpected markup in tables
#close-the-cellReferenced in:
* 8.2.5.4.15. The "in cell" insertion mode (2) (3)
#in-selectReferenced in:
* 8.2.3.1. The insertion mode (2) (3)
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.16. The "in select" insertion mode
* 8.2.5.4.17. The "in select in table" insertion mode
#in-select-in-tableReferenced in:
* 8.2.3.1. The insertion mode (2)
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.17. The "in select in table" insertion mode
#in-templateReferenced in:
* 8.2.3.1. The insertion mode
* 8.2.5.4.4. The "in head" insertion mode (2)
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.18. The "in template" insertion mode
* 8.4. Parsing HTML fragments
#after-bodyReferenced in:
* 8.2.3.1. The insertion mode
* 8.2.5.4.7. The "in body" insertion mode (2)
* 8.2.5.4.19. The "after body" insertion mode
#in-framesetReferenced in:
* 8.2.3.1. The insertion mode (2)
* 8.2.5.4.6. The "after head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.20. The "in frameset" insertion mode
#after-framesetReferenced in:
* 8.2.3.1. The insertion mode
* 8.2.5.4.20. The "in frameset" insertion mode
* 8.2.5.4.21. The "after frameset" insertion mode
#after-after-bodyReferenced in:
* 8.2.3.1. The insertion mode
* 8.2.5.4.19. The "after body" insertion mode
* 8.2.5.4.22. The "after after body" insertion mode
#after-after-framesetReferenced in:
* 8.2.3.1. The insertion mode
* 8.2.5.4.21. The "after frameset" insertion mode
* 8.2.5.4.23. The "after after frameset" insertion mode
#in-foreign-contentReferenced in:
* 4.12.1. The script element
* 8.2.5. Tree construction
#stop-parsingReferenced in:
* 2.2.4. Interactions with XPath and XSLT
* 3.1.2. Resource metadata management
* 4.10.18.7.2. Processing model
* 6.7.1. Navigating across documents
* 6.7.2. Page load processing model for HTML files
* 6.7.6. Page load processing model for media
* 6.7.7. Page load processing model for content that uses plugins
* 6.7.8. Page load processing model for inline content that doesn’t have
a DOM
* 8.2.3.2. The stack of open elements
* 8.2.5.4.7. The "in body" insertion mode
* 8.2.5.4.18. The "in template" insertion mode
* 8.2.5.4.19. The "after body" insertion mode
* 8.2.5.4.20. The "in frameset" insertion mode
* 8.2.5.4.21. The "after frameset" insertion mode
* 8.2.5.4.22. The "after after body" insertion mode
* 8.2.5.4.23. The "after after frameset" insertion mode
* 9.2. Parsing XML documents
#delay-the-load-eventReferenced in:
* 4.2.4.3. Obtaining a resource from a link element (2)
* 4.2.6. The style element
* 4.7.5. The img element
* 4.7.6. The iframe element (2) (3)
* 4.7.7. The embed element (2) (3)
* 4.7.8. The object element (2) (3) (4)
* 4.7.10. The video element
* 4.7.13.5. Loading the media resource (2) (3) (4) (5) (6) (7) (8) (9)
(10) (11) (12) (13)
* 4.10.5.1.19. Image Button state (type=image)
* 4.12.1.1. Processing model
* 6.1.1. Nested browsing contexts
* 11.3.3. Frames (2)
#ready-for-post-load-tasksReferenced in:
* 3.1. Documents
* 4.7.6. The iframe element
* 4.7.7. The embed element
* 4.7.8. The object element
* 6.1. Browsing contexts
* 7.4.1. Opening the input stream (2)
* 7.6.2. Printing
* 11.3.3. Frames
#completely-loadedReferenced in:
* 3.1. Documents
* 4.2.5.3. Pragma directives
* 4.7.6. The iframe element (2)
* 4.10.21.3. Form submission algorithm
* 6.1. Browsing contexts
* 6.6.4. The Location interface
* 7.4.1. Opening the input stream
* 11.3.3. Frames (2)
#abort-the-parserReferenced in:
* 6.7.12. Aborting a document load
* 8.2. Parsing HTML documents
* 8.2.5.4.8. The "text" insertion mode
#html-fragment-serialization-algorithmReferenced in:
* 8.3. Serializing HTML fragments
#attributes-serialized-nameReferenced in:
* 8.3. Serializing HTML fragments
#escaping-a-stringReferenced in:
* 8.3. Serializing HTML fragments (2)
#html-fragment-parsing-algorithmReferenced in:
* 4.7.6. The iframe element
* 4.12.2. The noscript element
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements (2)
* 8.2.3.5. Other parsing state flags
* 8.2.5. Tree construction (2)
* 8.2.5.1. Creating and inserting nodes
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.19. The "after body" insertion mode
* 8.2.5.4.20. The "in frameset" insertion mode
* 8.2.5.5. The rules for parsing tokens in foreign content
#contextReferenced in:
* 4.7.6. The iframe element
* 4.12.2. The noscript element
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements
* 8.2.5. Tree construction
* 8.4. Parsing HTML fragments
#fragment-caseReferenced in:
* 8.2.3.1. The insertion mode (2) (3) (4)
* 8.2.3.2. The stack of open elements (2) (3)
* 8.2.5.1. Creating and inserting nodes
* 8.2.5.4.4. The "in head" insertion mode
* 8.2.5.4.7. The "in body" insertion mode (2)
* 8.2.5.4.9. The "in table" insertion mode
* 8.2.5.4.11. The "in caption" insertion mode (2)
* 8.2.5.4.13. The "in table body" insertion mode
* 8.2.5.4.14. The "in row" insertion mode
* 8.2.5.4.15. The "in cell" insertion mode
* 8.2.5.4.16. The "in select" insertion mode (2) (3)
* 8.2.5.4.18. The "in template" insertion mode
* 8.2.5.4.19. The "after body" insertion mode
* 8.2.5.4.20. The "in frameset" insertion mode (2) (3)
* 8.2.5.5. The rules for parsing tokens in foreign content (2)
* 8.4. Parsing HTML fragments
#the-xml-syntaxReferenced in:
* 3.2.1. Semantics
* 8. The HTML syntax
#xml-parserReferenced in:
* 3.1.2. Resource metadata management (2)
* 4.2.6. The style element (2) (3)
* 4.2.7. Interactions of styling and scripting
* 4.7.8. The object element (2) (3)
* 4.7.13.11.1. Text track model (2)
* 4.10.11. The textarea element
* 4.12.1.1. Processing model (2) (3) (4)
* 4.12.3.1. Interaction of template elements with XSLT and XPath
* 6.7.3. Page load processing model for XML files
* 7.4. Dynamic markup insertion
* 9.2. Parsing XML documents (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12)
* 9.4. Parsing XML fragments
* 11.3.1. The applet element
#xml-scripting-support-disabledReferenced in:
* 9.2. Parsing XML documents (2) (3)
#feed-the-parserReferenced in:
* 9.4. Parsing XML fragments (2) (3)
#relevant-child-nodesReferenced in:
* 9.3. Serializing XML fragments (2) (3)
#xml-fragment-parsing-algorithmReferenced in:
* 9.2. Parsing XML documents
#being-renderedReferenced in:
* 3.2.6. The innerText IDL attribute
* 4.7.5. The img element
* 4.7.7. The embed element (2)
* 4.7.8. The object element (2)
* 4.10.5. The input element
* 4.10.19. APIs for text field selections
* 4.10.20.2. Constraint validation
* 4.10.20.3. The constraint validation API
* 4.11.4. The dialog element
* 4.12.4. The canvas element
* 5.4.2. Data model (2) (3) (4) (5) (6)
* 5.4.3. The tabindex attribute
* 5.4.4. Processing model (2) (3)
* 6.7.9. Navigating to a fragment (2)
* 10.1. Introduction (2)
* 10.3.2. The page
#presentational-hintsReferenced in:
* 10.2. The CSS user agent style sheet and presentational hints (2) (3)
* 10.3.2. The page (2) (3) (4) (5) (6)
* 10.3.3. Flow content (2) (3) (4) (5)
* 10.3.4. Phrasing content (2) (3) (4) (5) (6)
* 10.3.8. Lists
* 10.3.9. Tables (2) (3) (4) (5) (6) (7) (8) (9)
* 10.3.12. The hr element (2) (3) (4) (5)
* 10.4.3. Attributes for embedded content and images (2)
* 10.5.4. The input element as a text entry widget.
* 10.5.11. The marquee element
* 10.5.15. The textarea element (2) (3)
* 10.9. Unstyled XML documents
#maps-to-the-pixel-length-propertyReferenced in:
* 10.3.2. The page
* 10.3.9. Tables (2) (3)
#as-hints-for-the-renderingReferenced in:
* 4.7.19. Dimension attributes
* 10.3.12. The hr element
* 10.4.3. Attributes for embedded content and images (2)
* 10.5.11. The marquee element (2)
#map-to-the-dimension-property-ignoring-zeroReferenced in:
* 10.3.9. Tables (2) (3) (4) (5) (6)
#align-descendantsReferenced in:
* 10.2. The CSS user agent style sheet and presentational hints
* 10.3.3. Flow content (2) (3) (4)
* 10.3.9. Tables (2) (3) (4)
#container-frame-elementReferenced in:
* 10.3.2. The page (2) (3) (4) (5)
#substantialReferenced in:
* 10.3.10. Margin collapsing quirks (2) (3) (4) (5)
#blankReferenced in:
* 10.3.10. Margin collapsing quirks (2)
#elements-with-default-marginsReferenced in:
* 10.3.10. Margin collapsing quirks (2) (3)
#rendered-legendReferenced in:
* 10.3.13. The fieldset and legend elements
#restart-the-animationReferenced in:
* 4.7.5. The img element (2)
#converting-a-character-width-to-pixelsReferenced in:
* 10.5.4. The input element as a text entry widget. (2)
#attr-valuedef-marquee-direction-leftReferenced in:
* 10.5.11. The marquee element (2) (3)
* 11.3.2. The marquee element
#attr-valuedef-marquee-direction-rightReferenced in:
* 11.3.2. The marquee element
#attr-valuedef-marquee-direction-upReferenced in:
* 10.5.11. The marquee element
* 11.3.2. The marquee element
#attr-valuedef-marquee-direction-downReferenced in:
* 10.5.11. The marquee element
* 11.3.2. The marquee element
#width-of-the-selects-labelsReferenced in:
* 10.5.14. The select element (2)
#textarea-effective-widthReferenced in:
* 10.5.15. The textarea element (2)
#textarea-effective-heightReferenced in:
* 10.5.15. The textarea element (2)
#has-a-borderReferenced in:
* 10.6. Frames and framesets (2) (3)
#frame-border-colorReferenced in:
* 10.6. Frames and framesets (2) (3)
#convert-a-list-of-dimensions-to-a-list-of-pixel-valuesReferenced in:
* 10.6. Frames and framesets (2)
#obtain-a-physical-formReferenced in:
* 7.6.2. Printing (2)
* 10.8. Print media
#unstyled-documentReferenced in:
* 10.9. Unstyled XML documents (2)
#an-unstyled-document-viewReferenced in:
* 10.9. Unstyled XML documents
#elementdef-acronymReferenced in:
* 3.2.2. Elements in the DOM
* 11.3.4. Other elements, attributes and APIs
#elementdef-bgsoundReferenced in:
* 3.2.2. Elements in the DOM
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
#elementdef-dirReferenced in:
* 8.2.3.2. The stack of open elements
* 10.3.10. Margin collapsing quirks
* 11.3.4. Other elements, attributes and APIs (2) (3)
#elementdef-noframesReferenced in:
* 3.2.2. Elements in the DOM
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 8.4. Parsing HTML fragments
#elementdef-isindexReferenced in:
* 3.2.2. Elements in the DOM
#elementdef-listingReferenced in:
* 3.2.2. Elements in the DOM
* 8.2.3.2. The stack of open elements
* 10.3.10. Margin collapsing quirks
* 11.3.4. Other elements, attributes and APIs
#elementdef-nextidReferenced in:
* 3.2.2. Elements in the DOM
#elementdef-noembedReferenced in:
* 3.2.2. Elements in the DOM
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 8.4. Parsing HTML fragments
#elementdef-plaintextReferenced in:
* 3.2.2. Elements in the DOM
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 8.4. Parsing HTML fragments
* 10.3.10. Margin collapsing quirks
* 11.3.4. Other elements, attributes and APIs
#elementdef-strikeReferenced in:
* 3.2.2. Elements in the DOM
* 8.2.3.2. The stack of open elements
#elementdef-xmpReferenced in:
* 3.2.2. Elements in the DOM
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 8.4. Parsing HTML fragments
* 10.3.10. Margin collapsing quirks
* 11.3.4. Other elements, attributes and APIs
#elementdef-basefontReferenced in:
* 3.2.2. Elements in the DOM
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
#elementdef-bigReferenced in:
* 3.2.2. Elements in the DOM
* 8.2.3.2. The stack of open elements
* 11.2. Non-conforming features
#elementdef-blinkReferenced in:
* 3.2.2. Elements in the DOM
#elementdef-centerReferenced in:
* 3.2.2. Elements in the DOM
* 8.2.3.2. The stack of open elements
* 10.3.3. Flow content
#elementdef-fontReferenced in:
* 8.2.3.2. The stack of open elements
* 10.3.4. Phrasing content (2) (3) (4)
* 11.3.4. Other elements, attributes and APIs (2)
#elementdef-menuReferenced in:
* 11.2. Non-conforming features
* 11.3.4. Other elements, attributes and APIs
* Changes since HTML 5.1 - Note that these may change if the HTML 5.1
specification is updated.
#elementdef-menuitemReferenced in:
* Changes between Working Draft 6 and Working Draft 5 (2)
#elementdef-multicolReferenced in:
* 3.2.2. Elements in the DOM
#elementdef-nobrReferenced in:
* 3.2.2. Elements in the DOM
* 8.2.3.2. The stack of open elements
#elementdef-spacerReferenced in:
* 3.2.2. Elements in the DOM
#elementdef-ttReferenced in:
* 3.2.2. Elements in the DOM
* 8.2.3.2. The stack of open elements
* 11.2. Non-conforming features
#element-attrdef-a-nameReferenced in:
* 11.1. Obsolete but conforming features (2)
* 11.1.1. Warnings for obsolete but conforming features
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-img-nameReferenced in:
* 4.10.3. The form element (2)
#element-attrdef-area-nohrefReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-input-usemapReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-iframe-longdescReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-img-longdescReferenced in:
* 4.7.5. The img element (2) (3)
* 4.7.5.1. Requirements for providing text to act as an alternative for
images (2)
* 4.7.5.1.4. Graphical Representations: Charts, diagrams, graphs, maps,
illustrations
* 4.7.5.1.5. Images of text
* Elements
#element-attrdef-img-lowsrcReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-meta-schemeReferenced in:
* 11.3.4. Other elements, attributes and APIs (2) (3) (4) (5) (6)
#element-attrdef-object-codebaseReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-object-codetypeReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-param-valuetypeReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-script-languageReferenced in:
* 4.12.1.1. Processing model (2) (3) (4) (5)
* 11.1. Obsolete but conforming features
* 11.1.1. Warnings for obsolete but conforming features
#element-attrdef-script-eventReferenced in:
* 4.12.1.1. Processing model (2)
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-script-forReferenced in:
* 4.12.1.1. Processing model (2)
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-td-scopeReferenced in:
* 4.9.12.2. Forming relationships between data cells and header cells
(2) (3) (4) (5) (6)
#element-attrdef-body-alinkReferenced in:
* 10.3.2. The page
* 11.3.4. Other elements, attributes and APIs (2)
#element-attrdef-body-bgcolorReferenced in:
* 10.3.2. The page
* 11.3.4. Other elements, attributes and APIs (2)
#element-attrdef-body-bottommarginReferenced in:
* 10.3.2. The page
#element-attrdef-body-leftmarginReferenced in:
* 10.3.2. The page
#element-attrdef-body-linkReferenced in:
* 10.3.2. The page
* 11.3.4. Other elements, attributes and APIs (2)
#element-attrdef-body-marginheightReferenced in:
* 10.3.2. The page (2) (3) (4)
#element-attrdef-body-marginwidthReferenced in:
* 10.3.2. The page (2) (3) (4)
#element-attrdef-body-rightmarginReferenced in:
* 10.3.2. The page
#element-attrdef-body-textReferenced in:
* 10.3.2. The page
* 11.3.4. Other elements, attributes and APIs (2)
#element-attrdef-body-topmarginReferenced in:
* 10.3.2. The page
#element-attrdef-body-vlinkReferenced in:
* 10.3.2. The page
* 11.3.4. Other elements, attributes and APIs (2)
#element-attrdef-br-clearReferenced in:
* 10.3.4. Phrasing content
#element-attrdef-col-charReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-col-charoffReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-col-valignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-col-widthReferenced in:
* 10.3.9. Tables
#element-attrdef-div-alignReferenced in:
* 10.3.3. Flow content (2) (3) (4)
#element-attrdef-frame-bordercolorReferenced in:
* 10.6. Frames and framesets
#element-attrdef-hr-colorReferenced in:
* 10.3.12. The hr element (2) (3)
#element-attrdef-hr-noshadeReferenced in:
* 10.3.12. The hr element (2)
#element-attrdef-hr-sizeReferenced in:
* 10.3.12. The hr element (2)
#element-attrdef-hr-widthReferenced in:
* 10.3.12. The hr element
#element-attrdef-iframe-frameborderReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-iframe-marginheightReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-iframe-marginwidthReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-iframe-scrollingReferenced in:
* 10.3.2. The page
#element-attrdef-input-alignReferenced in:
* 10.4.3. Attributes for embedded content and images
#element-attrdef-input-borderReferenced in:
* 10.4.3. Attributes for embedded content and images
#element-attrdef-img-borderReferenced in:
* 11.1. Obsolete but conforming features
* 11.1.1. Warnings for obsolete but conforming features
#element-attrdef-img-hspaceReferenced in:
* 10.4.3. Attributes for embedded content and images
#element-attrdef-img-vspaceReferenced in:
* 10.4.3. Attributes for embedded content and images
#element-attrdef-legend-alignReferenced in:
* 10.3.13. The fieldset and legend elements
#element-attrdef-marquee-bgcolorReferenced in:
* 10.5.11. The marquee element
* 11.3.2. The marquee element
#element-attrdef-marquee-heightReferenced in:
* 10.5.11. The marquee element
#element-attrdef-marquee-hspaceReferenced in:
* 10.5.11. The marquee element
#element-attrdef-marquee-vspaceReferenced in:
* 10.5.11. The marquee element
#element-attrdef-marquee-widthReferenced in:
* 10.5.11. The marquee element
#element-attrdef-table-bgcolorReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-table-borderReferenced in:
* 10.3.9. Tables (2)
* Elements
#element-attrdef-table-bordercolorReferenced in:
* 10.3.9. Tables
#element-attrdef-table-cellpaddingReferenced in:
* 10.3.9. Tables
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-table-cellspacingReferenced in:
* 10.3.9. Tables
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-table-heightReferenced in:
* 10.3.9. Tables
#element-attrdef-table-widthReferenced in:
* 10.3.9. Tables
#element-attrdef-tbody-charReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-tbody-charoffReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-tbody-valignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-td-alignReferenced in:
* 10.3.9. Tables (2) (3) (4)
#element-attrdef-td-bgcolorReferenced in:
* 10.3.9. Tables
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-td-charReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-td-charoffReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-td-heightReferenced in:
* 10.3.9. Tables
#element-attrdef-td-nowrapReferenced in:
* 10.3.9. Tables
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-td-valignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-td-widthReferenced in:
* 10.3.9. Tables (2)
#element-attrdef-tr-bgcolorReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-tr-charReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-tr-charoffReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-tr-heightReferenced in:
* 10.3.9. Tables
#element-attrdef-tr-valignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#element-attrdef-body-backgroundReferenced in:
* 10.3.2. The page
* 10.3.9. Tables
* 11.3.4. Other elements, attributes and APIs (2)
#elementdef-appletReferenced in:
* 2.7.2.1. The HTMLAllCollection interface
* 3.1.3. DOM tree accessors (2) (3) (4)
* 6.3.3. Named access on the Window object (2)
* 6.5. Sandboxing
* 8.2.3.2. The stack of open elements (2)
* 8.2.3.3. The list of active formatting elements (2)
* 10.4.1. Embedded content (2)
* 10.4.3. Attributes for embedded content and images (2) (3) (4)
* 11.2. Non-conforming features (2)
* 11.3.1. The applet element (2) (3) (4) (5) (6) (7) (8)
* 11.3.4. Other elements, attributes and APIs
#dom-htmlappletelement-alignReferenced in:
* 11.3.1. The applet element
#dom-htmlappletelement-altReferenced in:
* 11.3.1. The applet element
#dom-htmlappletelement-archiveReferenced in:
* 11.3.1. The applet element
#dom-htmlappletelement-codeReferenced in:
* 11.3.1. The applet element
#dom-htmlappletelement-heightReferenced in:
* 11.3.1. The applet element
#dom-htmlappletelement-hspaceReferenced in:
* 11.3.1. The applet element
#dom-htmlappletelement-nameReferenced in:
* 11.3.1. The applet element
#dom-htmlappletelement-objectReferenced in:
* 11.3.1. The applet element (2)
#dom-htmlappletelement-vspaceReferenced in:
* 11.3.1. The applet element
#dom-htmlappletelement-widthReferenced in:
* 11.3.1. The applet element
#dom-htmlappletelement-codebaseReferenced in:
* 11.3.1. The applet element
#elementdef-marqueeReferenced in:
* 8.2.3.2. The stack of open elements (2)
* 8.2.3.3. The list of active formatting elements (2)
* 10.5.11. The marquee element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18) (19) (20) (21)
* 11.2. Non-conforming features (2) (3) (4) (5) (6) (7) (8) (9)
* 11.3.2. The marquee element (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16) (17) (18)
#turned-onReferenced in:
* 10.5.11. The marquee element (2) (3) (4)
* 11.3.2. The marquee element (2)
#turned-offReferenced in:
* 11.3.2. The marquee element (2)
#dom-htmlmarqueeelement-startReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-stopReferenced in:
* 11.3.2. The marquee element
#element-attrdef-marquee-behaviorReferenced in:
* 10.5.11. The marquee element (2) (3)
#attr-valuedef-marquee-behavior-scrollReferenced in:
* 10.5.11. The marquee element
#statedef-marquee-behavior-scrollReferenced in:
* 11.3.2. The marquee element
#attr-valuedef-marquee-behavior-slideReferenced in:
* 10.5.11. The marquee element
#attr-valuedef-marquee-behavior-alternateReferenced in:
* 10.5.11. The marquee element
#statedef-marquee-behavior-alternateReferenced in:
* 11.3.2. The marquee element
#element-attrdef-marquee-directionReferenced in:
* 10.5.11. The marquee element (2) (3) (4) (5) (6) (7) (8) (9) (10)
#statedef-marquee-leftReferenced in:
* 11.3.2. The marquee element
#element-attrdef-marquee-truespeedReferenced in:
* 11.3.2. The marquee element (2)
#marquee-scroll-intervalReferenced in:
* 10.5.11. The marquee element
* 11.3.2. The marquee element
#element-attrdef-marquee-scrolldelayReferenced in:
* 11.3.2. The marquee element
#marquee-marquee-scroll-distanceReferenced in:
* 10.5.11. The marquee element
#element-attrdef-marquee-scrollamountReferenced in:
* 11.3.2. The marquee element
#marquee-loop-countReferenced in:
* 11.3.2. The marquee element (2) (3) (4)
#element-attrdef-marquee-loopReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-loopReferenced in:
* 11.3.2. The marquee element
#marquee-current-loop-indexReferenced in:
* 10.5.11. The marquee element (2)
* 11.3.2. The marquee element (2)
#increment-the-marquee-current-loop-indexReferenced in:
* 10.5.11. The marquee element (2) (3)
#dom-htmlmarqueeelement-onbounceReferenced in:
* 11.3.2. The marquee element
#eventdef-marquee-bounceReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-onfinishReferenced in:
* 11.3.2. The marquee element
#eventdef-marquee-finishReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-onstartReferenced in:
* 11.3.2. The marquee element
#eventdef-marquee-startReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-behaviorReferenced in:
* 11.3.2. The marquee element (2)
#dom-htmlmarqueeelement-directionReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-heightReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-hspaceReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-vspaceReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-widthReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-bgcolorReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-scrollamountReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-scrolldelayReferenced in:
* 11.3.2. The marquee element
#dom-htmlmarqueeelement-truespeedReferenced in:
* 11.3.2. The marquee element
#elementdef-framesetReferenced in:
* 2.7.2.1. The HTMLAllCollection interface
* 3.1.3. DOM tree accessors (2) (3) (4)
* 6.1. Browsing contexts
* 6.3.3. Named access on the Window object (2)
* 7.1.5.2. Event handlers on elements, Document objects, and Window
objects (2) (3)
* 8.2.3.1. The insertion mode
* 8.2.3.2. The stack of open elements
* 8.2.5.4.20. The "in frameset" insertion mode
* 10.6. Frames and framesets (2) (3) (4) (5) (6) (7) (8) (9) (10) (11)
(12) (13) (14) (15) (16)
* 11.3.3. Frames (2) (3) (4) (5) (6)
* 11.3.4. Other elements, attributes and APIs (2)
#htmlframesetelementReferenced in:
* 11.3.3. Frames (2)
#element-attrdef-frameset-colsReferenced in:
* 10.6. Frames and framesets
#element-attrdef-frameset-rowsReferenced in:
* 10.6. Frames and framesets
#dom-htmlframesetelement-colsReferenced in:
* 11.3.3. Frames
#dom-htmlframesetelement-rowsReferenced in:
* 11.3.3. Frames
#elementdef-frameReferenced in:
* 2.7.2.1. The HTMLAllCollection interface
* 6.1. Browsing contexts
* 8.2.3.2. The stack of open elements
* 8.3. Serializing HTML fragments
* 10.3.2. The page (2) (3)
* 10.6. Frames and framesets (2) (3) (4) (5) (6)
* 11.2. Non-conforming features (2) (3)
* 11.3.3. Frames (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
(14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25)
#active-frame-elementReferenced in:
* 11.3.3. Frames (2) (3)
#process-the-frame-attributesReferenced in:
* 11.3.3. Frames (2) (3) (4)
#element-attrdef-frame-srcReferenced in:
* 11.3.3. Frames (2)
#element-attrdef-frame-nameReferenced in:
* 11.3.3. Frames
#htmlframeelementReferenced in:
* 11.3.3. Frames
#dom-htmlframeelement-nameReferenced in:
* 11.3.3. Frames
#dom-htmlframeelement-scrollingReferenced in:
* 11.3.3. Frames
#dom-htmlframeelement-srcReferenced in:
* 11.3.3. Frames
#dom-htmlframeelement-frameborderReferenced in:
* 11.3.3. Frames
#element-attrdef-frame-frameborderReferenced in:
* 10.6. Frames and framesets (2)
#dom-htmlframeelement-longdescReferenced in:
* 11.3.3. Frames
#dom-htmlframeelement-noresizeReferenced in:
* 11.3.3. Frames
#element-attrdef-frame-noresizeReferenced in:
* 10.6. Frames and framesets
#dom-htmlframeelement-contentdocumentReferenced in:
* 11.3.3. Frames
#dom-htmlframeelement-contentwindowReferenced in:
* 11.3.3. Frames
#dom-htmlframeelement-marginheightReferenced in:
* 11.3.3. Frames
#dom-htmlframeelement-marginwidthReferenced in:
* 11.3.3. Frames
#dom-htmlanchorelement-coordsReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlanchorelement-charsetReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlanchorelement-nameReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlanchorelement-shapeReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlareaelement-nohrefReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlbodyelement-textReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlbodyelement-linkReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlbodyelement-alinkReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlbodyelement-vlinkReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlbodyelement-bgcolorReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlbodyelement-backgroundReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlbrelement-clearReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecaptionelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecolelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecolelement-widthReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecolelement-chReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecolelement-choffReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecolelement-valignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmldirectoryelement-compactReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmldivelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmldlistelement-compactReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlembedelement-nameReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlembedelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlfontelement-colorReferenced in:
* 10.3.4. Phrasing content
* 11.3.4. Other elements, attributes and APIs
#dom-htmlfontelement-faceReferenced in:
* 10.3.4. Phrasing content
* 11.3.4. Other elements, attributes and APIs
#dom-htmlfontelement-sizeReferenced in:
* 10.3.4. Phrasing content
* 11.3.4. Other elements, attributes and APIs
#dom-htmlheadingelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlhrelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlhrelement-colorReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlhrelement-sizeReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlhrelement-widthReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlhrelement-noshadeReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlhtmlelement-versionReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmliframeelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmliframeelement-scrollingReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmliframeelement-frameborderReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmliframeelement-longdescReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmliframeelement-marginheightReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmliframeelement-marginwidthReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlimageelement-nameReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlimageelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlimageelement-borderReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlimageelement-hspaceReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlimageelement-vspaceReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlimageelement-lowsrcReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlinputelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlinputelement-usemapReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmllegendelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmllielement-typeReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmllinkelement-charsetReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmllinkelement-targetReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlmenuelement-compactReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlmetaelement-schemeReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlobjectelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlobjectelement-archiveReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlobjectelement-borderReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlobjectelement-codeReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlobjectelement-declareReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlobjectelement-hspaceReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlobjectelement-standbyReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlobjectelement-vspaceReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlobjectelement-codebaseReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlobjectelement-codetypeReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlolistelement-compactReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlparagraphelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlparamelement-typeReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlparamelement-valuetypeReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlpreelement-widthReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlscriptelement-eventReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlscriptelement-htmlforReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltableelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltableelement-borderReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltableelement-frameReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltableelement-summaryReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltableelement-rulesReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltableelement-widthReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltableelement-bgcolorReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltableelement-cellpaddingReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltableelement-cellspacingReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablesectionelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablesectionelement-chReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablesectionelement-choffReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablesectionelement-valignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecellelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecellelement-axisReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecellelement-heightReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecellelement-widthReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecellelement-chReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecellelement-choffReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecellelement-nowrapReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecellelement-valignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablecellelement-bgcolorReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablerowelement-alignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablerowelement-chReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablerowelement-choffReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablerowelement-valignReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmltablerowelement-bgcolorReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlulistelement-compactReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-htmlulistelement-typeReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-document-fgcolorReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-document-linkcolorReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-document-vlinkcolorReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-document-alinkcolorReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-document-bgcolorReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-document-anchorsReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-document-appletsReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-document-clearReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-document-captureeventsReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-document-releaseeventsReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-document-allReferenced in:
* 11.3.4. Other elements, attributes and APIs (2) (3) (4) (5) (6) (7)
#dom-window-captureeventsReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-window-releaseeventsReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-window-externalReferenced in:
* 11.3.4. Other elements, attributes and APIs
#externalReferenced in:
* 11.3.4. Other elements, attributes and APIs (2)
#dom-external-addsearchproviderReferenced in:
* 11.3.4. Other elements, attributes and APIs
#dom-external-issearchproviderinstalledReferenced in:
* 11.3.4. Other elements, attributes and APIs
#navigatorpluginsReferenced in:
* 11.3.4.1. Plugins
#pluginarrayReferenced in:
* 11.3.4.1. Plugins
#mimetypearrayReferenced in:
* 11.3.4.1. Plugins
#pluginReferenced in:
* 11.3.4.1. Plugins (2) (3)
#mimetypeReferenced in:
* 11.3.4.1. Plugins (2) (3) (4)
#dom-navigatorplugins-pluginsReferenced in:
* 11.3.4.1. Plugins
#dom-navigatorplugins-mimetypesReferenced in:
* 11.3.4.1. Plugins
#hidden-pluginsReferenced in:
* 11.3.4.1. Plugins (2) (3) (4) (5) (6) (7) (8)
#explicitly-supportsReferenced in:
* 11.3.4.1. Plugins (2) (3) (4) (5) (6) (7) (8) (9)
#dom-pluginarray-lengthReferenced in:
* 11.3.4.1. Plugins
#dom-pluginarray-refreshReferenced in:
* 11.3.4.1. Plugins
#dom-mimetypearray-lengthReferenced in:
* 11.3.4.1. Plugins
#reported-mime-typesReferenced in:
* 11.3.4.1. Plugins (2) (3) (4)
#dom-plugin-lengthReferenced in:
* 11.3.4.1. Plugins
#dom-plugin-nameReferenced in:
* 11.3.4.1. Plugins
#dom-plugin-descriptionReferenced in:
* 11.3.4.1. Plugins
#dom-plugin-filenameReferenced in:
* 11.3.4.1. Plugins
#dom-mimetype-typeReferenced in:
* 11.3.4.1. Plugins
#dom-mimetype-descriptionReferenced in:
* 11.3.4.1. Plugins
#dom-mimetype-suffixesReferenced in:
* 11.3.4.1. Plugins
#dom-mimetype-enabledpluginReferenced in:
* 11.3.4.1. Plugins
#dom-navigatorplugins-javaenabledReferenced in:
* 11.3.4.1. Plugins
#eventdef-global-abortReferenced in:
* Attributes
#eventdef-global-afterprintReferenced in:
* Attributes
#eventdef-global-beforeprintReferenced in:
* Attributes
#eventdef-global-beforeunloadReferenced in:
* Attributes
#eventdef-global-blurReferenced in:
* Attributes
#eventdef-global-cancelReferenced in:
* Attributes
#eventdef-global-changeReferenced in:
* Attributes
* Events
#eventdef-global-closeReferenced in:
* Attributes
#eventdef-global-copyReferenced in:
* Attributes
#eventdef-global-cutReferenced in:
* Attributes
#eventdef-global-errorReferenced in:
* 7.1.3.9. Runtime script errors
* Attributes
#eventdef-global-focusReferenced in:
* Attributes
#eventdef-global-hashchangeReferenced in:
* Attributes
#eventdef-global-inputReferenced in:
* Attributes
* Events
#eventdef-global-invalidReferenced in:
* Attributes
#eventdef-global-languagechangeReferenced in:
* Attributes
#eventdef-global-loadReferenced in:
* 1.9.2. Common pitfalls to avoid when using the scripting APIs (2)
* 11.3.3. Frames (2)
* Attributes
* Events
#eventdef-global-messageReferenced in:
* Attributes
#eventdef-global-offlineReferenced in:
* Attributes
#eventdef-global-onlineReferenced in:
* Attributes
#eventdef-global-pagehideReferenced in:
* Attributes
#eventdef-global-pageshowReferenced in:
* Attributes
#eventdef-global-pasteReferenced in:
* Attributes
#eventdef-global-popstateReferenced in:
* Attributes
#eventdef-global-progressReferenced in:
* Attributes
#eventdef-global-readystatechangeReferenced in:
* 3.1.2. Resource metadata management (2)
* 7.1.5.2. Event handlers on elements, Document objects, and Window
objects
* Events
#eventdef-global-resetReferenced in:
* Attributes
#eventdef-global-selectReferenced in:
* 10.5.15. The textarea element
* Attributes
#eventdef-global-storageReferenced in:
* Attributes
#eventdef-global-submitReferenced in:
* Attributes
#eventdef-global-toggleReferenced in:
* Attributes
#eventdef-global-unloadReferenced in:
* Attributes
]]></plaintext></imagebitmap></imagebitmap></any></any></a></position></position></div></dialog></meter></input type="range" min=0 max=100 step=20 value=50></select></p></div></div></div></div></embed></embed></article></source-size-list></media-condition></source-size-value></length></media-condition></media-condition></whitespace-token></source-size-value></whitespace-token></source-size-value></source-size-value></source-size-value></length></source-size-value></source-size-value></media-condition></source-size></source-size-value></source-size-value></source-size></source-size-list></source></source></source></source></source></source></source></source></source></source></source></source></source></whitespace-token></length></media-condition></p></media-condition></div>
If the element is being added by script, then so long as the event
handlers are added in the same script, the event will still not be missed:
However, if the author first created the img element and then in a
separate script added the event listeners, there’s a chance that the load
event would be fired in between, leading it to be missed: