diff --git a/source b/source index f5abd19d003..8db44d03e36 100644 --- a/source +++ b/source @@ -21,7 +21,7 @@ !--> - +
@@ -524,7 +524,7 @@The following year, the W3C membership decided to stop evolving HTML and instead begin work on an XML-based equivalent, called XHTML. This effort started with a reformulation of HTML4 in XML, known as XHTML 1.0, which added no new - features except the new serialisation, and which was completed in 2000. After XHTML 1.0, the W3C's + features except the new serialization, and which was completed in 2000. After XHTML 1.0, the W3C's focus turned to making it easier for other working groups to extend XHTML, under the banner of XHTML Modularization. In parallel with this, the W3C also worked on a new language that was not compatible with the earlier HTML and XHTML languages, calling it XHTML2.
@@ -610,14 +610,14 @@To avoid exposing Web authors to the complexities of multithreading, the HTML and DOM APIs are designed such that no script can ever detect the simultaneous execution of other scripts. Even - with workers, the intent is that the behaviour of implementations can - be thought of as completely serialising the execution of all scripts in all workers, the intent is that the behavior of implementations can + be thought of as completely serializing the execution of all scripts in all browsing contexts.
However, the IP address used for a user's requests is not the only mechanism by which a user's @@ -961,7 +961,7 @@ prevented from voting in an election.
Since the malevolent purposes can be remarkably evil, user agent implementors are encouraged to - consider how to provide their users with tools to minimise leaking information that could be used + consider how to provide their users with tools to minimize leaking information that could be used to fingerprint a user.
Unfortunately, as the first paragraph in this section implies, sometimes there is great benefit @@ -1131,7 +1131,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
HTML documents represent a media-independent description of interactive content. HTML documents - might be rendered to a screen, or through a speech synthesiser, or on a braille display. To + might be rendered to a screen, or through a speech synthesizer, or on a braille display. To influence exactly how such rendering takes place, authors can use a styling language such as CSS.
@@ -1403,7 +1403,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute dIt is significantly easier to maintain a site written in such a way that the markup is
- style-independent. For example, changing the colour of a site that uses <font color="">
throughout requires changes across the entire site,
whereas a similar change to a site based on CSS can be done by changing a single file.
Some error-handling behaviour, such as the behaviour for the Some error-handling behavior, such as the behavior for the
<table><hr>...
example mentioned above, are incompatible with streaming
user agents (user agents that process HTML files in one pass, without storing state). To avoid
- interoperability problems with such user agents, any syntax resulting in such behaviour is
+ interoperability problems with such user agents, any syntax resulting in such behavior is
considered invalid.
Another example of this is the DOCTYPE, which is required to trigger no-quirks - mode, because the behaviour of legacy user agents in quirks mode is often + mode, because the behavior of legacy user agents in quirks mode is often largely undocumented.
Certain elements have default styles or behaviours that make certain combinations likely to +
Certain elements have default styles or behaviors that make certain combinations likely to lead to confusion. Where these have equivalent alternatives without this problem, the confusing combinations are disallowed.
@@ -1753,7 +1753,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute dAnother example would be the way interactive content cannot be
nested. For example, a button
element cannot contain a textarea
- element. This is because the default behaviour of such nesting interactive elements would be
+ element. This is because the default behavior of such nesting interactive elements would be
highly confusing to users. Instead of nesting these elements, they can be placed side by
side.
Some authors like to write files that can be interpreted as both XML and HTML with similar results. Though this practice is discouraged in general due to the myriad of subtle complications involved (especially when involving scripting, styling, or any kind of automated - serialisation), this specification has a few restrictions intended to at least somewhat mitigate + serialization), this specification has a few restrictions intended to at least somewhat mitigate the difficulties. This makes it easier for authors to use this as a transitionary step when migrating between HTML and XHTML.
For example, there are somewhat complicated rules surrounding the lang
and xml:lang
attributes
- intended to keep the two synchronised.
Another example would be the restrictions on the values of xmlns
attributes in the HTML serialisation, which are intended to ensure that
+ data-x="">xmlns attributes in the HTML serialization, which are intended to ensure that
elements in conforming documents end up in the same namespaces whether processed as HTML or
XML.
This specification uses the term document to refer to any use of HTML,
ranging from short static documents to long essays or reports with rich multimedia, as well as to
fully-fledged interactive applications. The term is used to refer both to Document
- objects and their descendant DOM trees, and to serialised byte streams using the HTML syntax or XHTML syntax, depending
on context.
The term "transparent black" refers to the colour with red, green, blue, and alpha channels all +
The term "transparent black" refers to the color with red, green, blue, and alpha channels all set to zero.
@@ -2172,7 +2172,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d data-x="concept-event-dispatch">dispatching an event means to follow the steps that propagate the event through the tree. The term trusted event is used to refer to events whoseisTrusted
attribute is
- initialised to true.
+ initialized to true.
This is not required. In particular, even user agents that do implement the suggested default rendering are encouraged to offer settings that override this default to improve the experience - for the user, e.g. changing the colour contrast, using different focus styles, or otherwise + for the user, e.g. changing the color contrast, using different focus styles, or otherwise making the experience more accessible and usable to the user.
User agents that are designated as supporting the suggested default rendering must, while so designated, implement the rules the rendering section defines as the - behaviour that user agents are expected to implement.
+ behavior that user agents are expected to implement.Some conformance requirements are phrased as requirements on elements, attributes, methods or objects. Such requirements fall into two categories: those describing content model restrictions, - and those describing implementation behaviour. Those in the former category are requirements on + and those describing implementation behavior. Those in the former category are requirements on documents and authoring tools. Those in the second category are requirements on user agents. Similarly, some conformance requirements are phrased as requirements on authors; such requirements are to be interpreted as conformance requirements on the documents that authors produce. (In other @@ -2646,7 +2646,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
Implementations that support the XHTML syntax must support some version of XML, as well as its corresponding namespaces specification, because that syntax uses an XML - serialisation with namespaces.
+ serialization with namespaces.The attribute with the tag name xml:space
in the XML namespace is defined by
@@ -2726,12 +2726,12 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
keypress
". The terms
"name" and "type" for events are synonymous.
- The following features are defined in the DOM Parsing and - Serialization specification:
+The following features are defined in the DOM Parsing and Serialization + specification:
DOMParser
For example, user agents are required to close all open constructs upon
finding the end of a style sheet unexpectedly. Thus, when parsing the string "rgb(0,0,0
" (with a missing close-parenthesis) for a colour value, the close
- parenthesis is implied by this error handling rule, and a value is obtained (the colour 'black').
+ data-x="">rgb(0,0,0" (with a missing close-parenthesis) for a color value, the close
+ parenthesis is implied by this error handling rule, and a value is obtained (the color 'black').
However, the similar construct "rgb(0,0,
" (with both a missing parenthesis
and a missing "blue" value) cannot be parsed, as closing the open construct does not result in a
viable value.
For markup-level features that can be limited to the XML serialisation and need not be - supported in the HTML serialisation, vendors should use the namespace mechanism to define custom +
For markup-level features that can be limited to the XML serialization and need not be + supported in the HTML serialization, vendors should use the namespace mechanism to define custom namespaces in which the non-standard elements and attributes are supported.
When vendor-neutral extensions to this specification are needed, either this specification can be updated accordingly, or an extension specification can be written that overrides the requirements in this specification. When someone applying this specification to their activities - decides that they will recognise the requirements of such an extension specification, it becomes + decides that they will recognize the requirements of such an extension specification, it becomes an applicable specification for the purposes of conformance requirements in this specification.
@@ -4295,7 +4295,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute dThis requirement is a willful violation of the XSLT 1.0 specification, required because this specification changes the namespaces and case-sensitivity rules of HTML in a manner that would otherwise be incompatible with DOM-based XSLT - transformations. (Processors that serialise the output are unaffected.)
Implementors are strongly urged to carefully examine any third-party libraries they might consider using to implement the parsing of syntaxes described below. For example, date - libraries are likely to implement error handling behaviour that differs from what is required in - this specification, since error-handling behaviour is often not defined in specifications that + libraries are likely to implement error handling behavior that differs from what is required in + this specification, since error-handling behavior is often not defined in specifications that describe date syntaxes similar to those used in this specification, and thus implementations tend to vary greatly in how they handle errors.
@@ -4942,7 +4942,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute dThe rules for parsing dimension values are as given in the following algorithm. When invoked, the steps must be followed in the order given, aborting at the first step that returns a value. This algorithm will return either a number greater than or equal to 0.0, or an error; if a - number is returned, then it is further categorised as either a percentage or a length.
+ number is returned, then it is further categorized as either a percentage or a length.The rules for parsing non-zero dimension values are as given in the following algorithm. When invoked, the steps must be followed in the order given, aborting at the first step that returns a value. This algorithm will return either a number greater than 0.0, or an error; if - a number is returned, then it is further categorised as either a percentage or a length.
+ a number is returned, then it is further categorized as either a percentage or a length.A string is a valid - normalised local date and time string representing a date and time if it consists of the - following components in the given order:
+A string is a valid normalized local date and time string representing a date and time if + it consists of the following components in the given order:
A simple colour consists of three 8-bit numbers in the range - 0..255, representing the red, green, and blue components of the colour respectively, in the sRGB - colour space.
+A simple color consists of three 8-bit numbers in the + range 0..255, representing the red, green, and blue components of the color respectively, in the + sRGB color space.
-A string is a valid simple colour if it is exactly seven - characters long, and the first character is a U+0023 NUMBER SIGN character (#), and the remaining - six characters are all ASCII hex digits, with the first two digits representing the - red component, the middle two digits representing the green component, and the last two digits - representing the blue component, in hexadecimal.
+A string is a valid simple color if it is + exactly seven characters long, and the first character is a U+0023 NUMBER SIGN character (#), and + the remaining six characters are all ASCII hex digits, with the first two digits + representing the red component, the middle two digits representing the green component, and the + last two digits representing the blue component, in hexadecimal.
-A string is a valid lowercase simple colour if it - is a valid simple colour and doesn't use any characters in the range U+0041 LATIN - CAPITAL LETTER A to U+0046 LATIN CAPITAL LETTER F.
+A string is a valid lowercase simple + color if it is a valid simple color and doesn't use any characters in the range + U+0041 LATIN CAPITAL LETTER A to U+0046 LATIN CAPITAL LETTER F.
The rules for parsing simple colour
+ The rules for parsing simple color
values are as given in the following algorithm. When invoked, the steps must be followed in
the order given, aborting at the first step that returns a value. This algorithm will return
- either a simple colour or an error.
If the last six characters of input are not all ASCII hex digits, then return an error.
Let result be a simple colour.
+Let result be a simple color.
Interpret the second and third characters as a hexadecimal number and let the result be the red component of result.
@@ -6582,8 +6582,9 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute dThe rules for serialising simple colour - values given a simple colour are as given in the following algorithm:
+The rules for serializing + simple color values given a simple color are as given in the following + algorithm:
Return result, which will be a valid lowercase simple - colour.
Some obsolete legacy attributes parse colours in a more complicated manner, using the - rules for parsing a legacy colour value, - which are given in the following algorithm. When invoked, the steps must be followed in the order - given, aborting at the first step that returns a value. This algorithm will return either a - simple colour or an error.
+Some obsolete legacy attributes parse colors in a more complicated manner, using the + rules for parsing a legacy color + value, which are given in the following algorithm. When invoked, the steps must be followed + in the order given, aborting at the first step that returns a value. This algorithm will return + either a simple color or an error.
If input is an ASCII case-insensitive match for one of the - named colours, then return the simple - colour corresponding to that keyword.
+ named colors, then return the simple + color corresponding to that keyword.CSS2 System - Colors are not recognised.
+ Colors are not recognized.Let result be a simple colour.
+Let result be a simple color.
Interpret the second character of input as a hexadecimal digit; let the red component of result be the resulting number multiplied by 17.
@@ -6682,7 +6683,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute dIf length is still greater than two, truncate each component, leaving only the first two characters in each.
Let result be a simple colour.
+Let result be a simple color.
Interpret the first component as a hexadecimal number; let the red component of result be the resulting number.
The 2D graphics context has a separate - colour syntax that also handles opacity.
+ color syntax that also handles opacity. @@ -6993,7 +6994,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute dIf urlRecord is failure, then abort these steps with an error.
Let urlString be the result of applying the URL serialiser to urlRecord.
Return urlString as the resulting URL string and urlRecord as the resulting URL record.
If a reflecting IDL attribute has an unsigned integer type (unsigned long
) that is limited to only non-negative numbers
- greater than zero, then the behaviour is similar to the previous case, but zero is not
+ greater than zero, then the behavior is similar to the previous case, but zero is not
allowed. On getting, the content attribute must first be parsed according to the rules for
parsing non-negative integers, and if that is successful, and the value is in the range 1
to 2147483647 inclusive, the resulting value must be returned. If, on the other hand, it fails or
@@ -7395,7 +7396,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
If a reflecting IDL attribute has an unsigned integer type (unsigned long
) that is limited to only non-negative numbers
- greater than zero with fallback, then the behaviour is similar to the previous case, but
+ greater than zero with fallback, then the behavior is similar to the previous case, but
disallowed values are converted to the default value. On getting, the content attribute must first
be parsed according to the rules for parsing non-negative integers, and if that is
successful, and the value is in the range 1 to 2147483647 inclusive, the resulting value must be
@@ -7417,7 +7418,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
If a reflecting IDL attribute has a floating-point number type (double
or unrestricted
- double
) that is limited to numbers greater than zero, then the behaviour is
+ double) that is limited to numbers greater than zero, then the behavior is
similar to the previous case, but zero and negative values are not allowed. On getting, the
content attribute must be parsed according to the rules for parsing floating-point number
values, and if that is successful and the value is greater than 0.0, the resulting value
@@ -7850,7 +7851,7 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20html%3E..
On getting, the length
attribute must return the number of nodes represented by the collection.
On setting, the behaviour depends on whether the new value is equal to, greater than, or less +
On setting, the behavior depends on whether the new value is equal to, greater than, or less
than the number of nodes represented by the collection at that time. If the number is
the same, then setting the attribute must do nothing. If the new value is greater, then n new option
elements with no attributes and no child nodes must be
appended to the select
element on which the HTMLOptionsCollection
is
@@ -9264,7 +9265,7 @@ partial interface Document {
The currentScript
attribute, on
getting, must return the value to which it was most recently set. When the Document
is created, the currentScript
must be
- initialised to null.
cite
element mis-used:
- <!DOCTYPE HTML> +<!DOCTYPE HTML> <html lang="en-GB"> <head> <title> Demonstration </title> </head> <body> <table> - <tr> <td> My favourite animal is the cat. </td> </tr> + <tr> <td> My favourite animal is the cat. </td> </tr> <tr> <td> —<a href="http://example.org/~ernest/"><cite>Ernest</cite></a>, @@ -9499,12 +9500,12 @@ partial interface Document {A corrected version of this document might be:
-<!DOCTYPE HTML> +<!DOCTYPE HTML> <html lang="en-GB"> <head> <title> Demonstration </title> </head> <body> <blockquote> - <p> My favourite animal is the cat. </p> + <p> My favourite animal is the cat. </p> </blockquote> <p> —<a href="http://example.org/~ernest/">Ernest</a>, @@ -10079,7 +10080,7 @@ console.assert(image.height === 200);Metadata content
-Metadata content is content that sets up the presentation or behaviour of the rest of +
Metadata content is content that sets up the presentation or behavior of the rest of the content, or that sets up the relationship of the document with other documents, or that conveys other "out of band" information.
@@ -10100,7 +10101,7 @@ console.assert(image.height === 200);-Thus, in the XML serialisation, one can use RDF, like this:
+Thus, in the XML serialization, one can use RDF, like this:
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:r="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xml:lang="en"> @@ -10122,14 +10123,14 @@ console.assert(image.height === 200);</body> </html> -This isn't possible in the HTML serialisation, however.
+This isn't possible in the HTML serialization, however.
Flow content
-Most elements that are used in the body of documents and applications are categorised as +
Most elements that are used in the body of documents and applications are categorized as flow content.
@@ -10334,8 +10335,8 @@ console.assert(image.height === 200);
Most elements that are categorised as phrasing content can only contain elements - that are themselves categorised as phrasing content, not any flow content.
+Most elements that are categorized as phrasing content can only contain elements + that are themselves categorized as phrasing content, not any flow content.
Text, in the context of content models, means either nothing,
or Text
nodes. Text is sometimes used as a content
@@ -11018,9 +11019,9 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
The XML specification also allows the use of the xml:space
attribute in the XML namespace on any element in an XML
document. This attribute has no effect on HTML elements, as the default
- behaviour in HTML is to preserve whitespace.
There is no way to serialise the xml:space
+
There is no way to serialize the xml:space
attribute on HTML elements in the text/html
syntax.
The meta
element can represent document-level metadata with the name
attribute, pragma directives with the http-equiv
attribute, and the file's character encoding
- declaration when an HTML document is serialised to string form (e.g. for transmission over
+ declaration when an HTML document is serialized to string form (e.g. for transmission over
the network or for disk storage) with the charset
attribute.
The value must be a string that matches the CSS <color> production, defining - a suggested colour that user agents should use to customize the display of the page or of the - surrounding user interface. For example, a browser might colour the page's title bar with the - specified value, or use it as a colour highlight in a tab bar or task switcher.
+ a suggested color that user agents should use to customize the display of the page or of the + surrounding user interface. For example, a browser might color the page's title bar with the + specified value, or use it as a color highlight in a tab bar or task switcher.There must not be more than one This standard itself uses "WHATWG green" as its theme colour: This standard itself uses "WHATWG green" as its theme color: To obtain a page's theme colour, user agents must run the following steps: To obtain a page's theme color, user agents must run the following steps: If value can be parsed as a CSS <color> value, return
- the parsed colour. If this step is reached, the page has no theme colour. If this step is reached, the page has no theme color. If any Such extensions must use a name that is identical to an HTTP header registered in the Permanent
- Message Header Field Registry, and must have behaviour identical to that described for the HTTP
+ Message Header Field Registry, and must have behavior identical to that described for the HTTP
header. Pragma directives corresponding to headers describing metadata, or not requiring specific user
agent processing, must not be registered; instead, use metadata names. Pragma directives corresponding to headers
that affect the HTTP processing model (e.g. caching) must not be registered, as they would result
- in HTTP-level behaviour being different for user agents that implement HTML than for user agents
+ in HTTP-level behavior being different for user agents that implement HTML than for user agents
that do not. Anyone is free to edit the WHATWG Wiki PragmaExtensions page at any time to add a pragma
@@ -14157,13 +14158,13 @@ people expect to have work and what is necessary.
Left at its default value. Left uninitialised. Left uninitialized. Giving up on a style sheet before the style sheet loads, if the style sheet
eventually does still load, means that the script might end up operating with incorrect
- information. For example, if a style sheet sets the colour of an element to green, but a script
+ information. For example, if a style sheet sets the color of an element to green, but a script
that inspects the resulting style is executed before the sheet is loaded, the script will find
- that the element is black (or whatever the default colour is), and might thus make poor choices
- (e.g. deciding to use black as the colour elsewhere on the page, instead of green). Implementors
+ that the element is black (or whatever the default color is), and might thus make poor choices
+ (e.g. deciding to use black as the color elsewhere on the page, instead of green). Implementors
have to balance the likelihood of a script using incorrect information with the performance impact
of doing nothing while waiting for a slow network request to finish. Here is a graduation programme with two sections, one for the list of people graduating, and
one for the description of the ceremony. (The markup in this example features an uncommon style
- sometimes used to minimise the amount of inter-element whitespace.) Create a stack to hold elements, which is used to handle nesting. Initialise this stack to
+ Create a stack to hold elements, which is used to handle nesting. Initialize this stack to
empty. Let there be a new outline for the new current outline
- target, initialised with just the new current section as the only
+ target, initialized with just the new current section as the only
section in the outline. Let there be a new outline for the new current outline
- target, initialised with just the new current section as the only
+ target, initialized with just the new current section as the only
section in the outline. and is further discussed below. The solution is to realise that a paragraph, in HTML terms, is not a
+ The solution is to realize that a paragraph, in HTML terms, is not a
logical concept, but a structural one. In the fantastic example above, there are actually
five paragraphs as defined by this specification: one
before the list, one for each bullet, and one after the list. The activation behaviour of Left at its default value. Left uninitialised. Left uninitialized.meta
element with its name
attribute set to the value HTMLMetaElement : HTMLElement {
<!DOCTYPE HTML>
<title>HTML Standard</title>
@@ -13410,7 +13411,7 @@ interface HTMLMetaElement : HTMLElement {
- content
attribute.meta
elements are WHATWG Wiki PragmaExtensions page. <!DOCTYPE Html>
<Html Lang=En
@@ -15982,8 +15983,8 @@ Space is not the only void
<p>They taste lovely.</p>
<h6>Sweet</h6>
<p>Red apples are sweeter than green ones.</p>
- <h1>Colour</h1>
- <p>Apples come in various colours.</p>
+ <h1>Color</h1>
+ <p>Apples come in various colors.</p>
</section>
</body>
@@ -16001,8 +16002,8 @@ Space is not the only void
</section>
</section>
<section>
- <h2>Colour</h2>
- <p>Apples come in various colours.</p>
+ <h2>Color</h2>
+ <p>Apples come in various colors.</p>
</section>
</body>
@@ -16024,8 +16025,8 @@ Space is not the only void
</section>
</section>
<section>
- <h1>Colour</h1>
- <p>Apples come in various colours.</p>
+ <h1>Color</h1>
+ <p>Apples come in various colors.</p>
</section>
</body>
@@ -16133,7 +16134,7 @@ Space is not the only void
data-x="concept-section">section, so that elements in the DOM can all be associated with a
section.)
- <dl>
<dt lang="en-US"> <dfn>color</dfn> </dt>
- <dt lang="en-GB"> <dfn>colour</dfn> </dt>
+ <dt lang="en-GB"> <dfn>colour</dfn> </dt>
<dd> A sensation which (in humans) derives from the ability of
the fine structure of the eye to distinguish three differently
filtered analyses of a view. </dd>
@@ -18499,17 +18500,17 @@ interface HTMLDivElement : HTMLElement {};
<article lang="en-US">
<h1>My use of language and my cats</h1>
- <p>My cat's behaviour hasn't changed much since her absence, except
+ <p>My cat's behavior hasn't changed much since her absence, except
that she plays her new physique to the neighbors regularly, in an
attempt to get pets.</p>
<div lang="en-GB">
- <p>My other cat, coloured black and white, is a sweetie. He followed
+ <p>My other cat, coloured black and white, is a sweetie. He followed
us to the pool today, walking down the pavement with us. Yesterday
- he apparently visited our neighbours. I wonder if he recognises that
+ he apparently visited our neighbours. I wonder if he recognises that
their flat is a mirror image of ours.</p>
<p>Hm, I just noticed that in the last paragraph I used British
English. But I'm supposed to write in American English. So I
- shouldn't say "pavement" or "flat" or "colour"...</p>
+ shouldn't say "pavement" or "flat" or "colour"...</p>
</div>
<p>I should say "sidewalk" and "apartment" and "color"!</p>
</article>
@@ -18612,7 +18613,7 @@ interface HTMLAnchorElement : HTMLElement {
attributes may be used to indicate to the user the likely nature of the target resource before the
user follows the link.
- a
elements that create The activation behavior of a
elements that create hyperlinks is to run the following steps:
This document is about some gems, and so it is tagged with "https://en.wikipedia.org/wiki/Gemstone
" to unambiguously categorise it as applying
+ data-x="">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:
In the following example, a list that started with just fruit was replaced by a list with just - colours.
+ colors. -<h1>List of <del>fruits</del><ins>colours</ins></h1> +<h1>List of <del>fruits</del><ins>colors</ins></h1> <ul> <li><del>Lime</del><ins>Green</ins></li> <li><del>Apple</del></li> @@ -24547,7 +24549,7 @@ was an English <a href="/wiki/Music_hall">music hall</a> singer, ...
If the author avoids specifying any image in the HTML markup and instead instantiates a single download from script, that avoids the double download problem above but then no image will be downloaded at all for users with scripting disabled and the aggressive image downloading - optimisation will also be disabled.
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 behaviour:
source
element and trigger fallback behavior:
<script>
function fallback(video) {
@@ -26116,7 +26118,7 @@ interface HTMLImageElement : HTMLElement {
and no image source with a width descriptor,
append child's src
attribute value to source set.
-
Normalise the source densities of source set.
Normalize the source densities of source set.
Let el's source set be source set.
If child has a type
attribute, and its
value is an unknown or unsupported MIME type, continue to the next child.
Normalise the source densities of source set.
Normalize the source densities of source set.
Let el's source set be source set.
Descriptor tokeniser: Skip whitespace
Descriptor tokenizer: Skip whitespace
Let current descriptor be the empty string.
An image source can have a pixel density descriptor, a width descriptor, or - no descriptor at all accompanying its URL. Normalising a source set gives every image + no descriptor at all accompanying its URL. Normalizing a source set gives every image source a pixel density descriptor.
-When asked to normalise the source - densities of a source set source set, the user agent must do the - following:
+When asked to normalize + the source densities of a source set source set, the user agent must + do the following:
While user agents are encouraged to repair cases of missing alt
attributes, authors must not rely on such behaviour. 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.
href
attribute.
The usemap
and ismap
attributes can result in confusing behaviour when used
+ data-x="attr-img-ismap">ismap attributes can result in confusing behavior when used
together with source
elements with the media
attribute specified in a picture
element.
<article> <h1>My cats</h1> <h2>Fluffy</h2> - <p>Fluffy is my favourite.</p> + <p>Fluffy is my favorite.</p> <img src="fluffy.jpg" alt="She likes playing with a ball of yarn."> <p>She's just too cute.</p> <h2>Miles</h2> @@ -27155,11 +27157,11 @@ the time Maria had stuck her tongue out...</p>
In this example, a user is asked to pick their preferred colour from a list of three. Each colour +
In this example, a user is asked to pick their preferred color from a list of three. Each color is given by an image, but for users who have configured their user agent not to display images, - the colour names are used instead:
+ the color names are used instead: -<h1>Pick your colour</h1> +<h1>Pick your color</h1> <ul> <li><a href="green.html"><img src="green.jpeg" alt="Green"></a></li> <li><a href="blue.html"><img src="blue.jpeg" alt="Blue"></a></li> @@ -27170,7 +27172,7 @@ the time Maria had stuck her tongue out...</p>-@@ -30247,7 +30249,7 @@ interface HTMLVideoElement : HTMLMediaElement { audio from the media resource, at the current playback position.In this example, each button has a set of images to indicate the kind of colour output desired +
In this example, each button has a set of images to indicate the kind of color output desired by the user. The first image is used in each case to give the alternative text.
<button name="rgb"><img src="red" alt="RGB"><img src="green" alt=""><img src="blue" alt=""></button> @@ -27205,7 +27207,7 @@ the time Maria had stuck her tongue out...</p>the same message as the image specified in thesrc
attribute. -It is important to realise that the alternative text is a replacement for the image, +
It is important to realize that the alternative text is a replacement for the image, not a description of the image.
@@ -27261,7 +27263,7 @@ Tokenizer."></p>@@ -29293,7 +29295,7 @@ interface HTMLObjectElement : HTMLElement {A short phrase or label with an alternative graphical representation: icons, logos
A document can contain information in iconic form. The icon is intended to help users of visual - browsers to recognise features at a glance.
+ browsers to recognize features at a glance.In some cases, the icon is supplemental to a text label conveying the same meaning. In those cases, the
@@ -27524,7 +27526,7 @@ Standards mode, and about 9% triggered the Standards mode.</p> an image that, through a style sheet, is floated to the right. The image is not purely decorative, as it is relevant to the story. The image is not entirely redundant with the story either, as it shows what the politician looks like. Whether any alternative text need be provided - is an authoring decision, in part influenced by whether the image colours the interpretation of + is an authoring decision, in part influenced by whether the image colors the interpretation of the prose.alt
attribute must be present but must be empty.In this first variant, the image is shown without context, and no alternative text is @@ -27992,7 +27994,7 @@ href="?audio">audio</a> test instead.)</p>
Guidance for markup generators
Markup generators (such as WYSIWYG authoring tools) should, wherever possible, obtain - alternative text from their users. However, it is recognised that in many cases, this will not be + 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 @@ -28339,7 +28341,7 @@ interface HTMLIFrameElement : HTMLElement { steps.
- +Let resource be a new request whose url is url and whose HTMLIFrameElement : HTMLElement { e.g. - 240x200 default - the attributes/params are sent in a name-value pair list as follows (for Gecko): + attributes of the element, in source order - + a synthesised 'src' attribute, if there was no 'src' but + + a synthesized 'src' attribute, if there was no 'src' but there was a 'data', with the value of the 'data' attribute + the params, in source order (WebKit does something different still) @@ -29107,8 +29109,8 @@ attribute's value is a type that a plugin supports, then the value
The
HTMLEmbedElement
object representing the element must expose the scriptable interface of the plugin instantiated for theembed
element, if any. At a minimum, this interface must implement the legacy caller - operation. (It is suggested that the default behaviour of this legacy caller operation, e.g. - the behaviour of the default plugin's legacy caller operation, be to throw a + 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
"DOMException
.)If the user has indicated a preference that this
object
element's fallback - content be shown instead of the element's usual behaviour, then jump to the step below + 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 @@ -29900,7 +29902,7 @@ interface HTMLObjectElement : HTMLElement {
All
object
elements have a legacy caller operation. If theobject
element has an instantiated plugin that supports a scriptable interface that defines a legacy caller operation, then that must be the - behaviour of the object's legacy caller operation. Otherwise, the object's legacy caller operation + behavior of the object's legacy caller operation. Otherwise, the object's legacy caller operation must be to throw a "NotSupportedError
"DOMException
.Any audio associated with the media resource must, if played, be played - synchronised with the current playback position, at the element's effective + 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.
@@ -30517,7 +30519,7 @@ interface HTMLAudioElement : HTMLMediaElement {};
When an audio
element is potentially playing, it must have its audio
- data played synchronised with the current playback position, at the element's
+ 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.
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 recognise the + 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
@@ -31292,7 +31294,7 @@ interface HTMLMediaElement : HTMLElement {
NETWORK_EMPTY
(numeric value 0)NETWORK_IDLE
(numeric value 1)Optionally, run the following substeps. This is the expected behaviour if the user agent +
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).
addtrack
, that does not bubble and is not cancelable,
and that uses the TrackEvent
interface, with the track
attribute initialised to the new
+ data-x="dom-TrackEvent-track">track attribute initialized to the new
AudioTrack
object, at this AudioTrackList
object.addtrack
, that does not bubble and is not cancelable,
and that uses the TrackEvent
interface, with the track
attribute initialised to the new
+ data-x="dom-TrackEvent-track">track attribute initialized to the new
VideoTrack
object, at this VideoTrackList
object.
@@ -32455,7 +32457,7 @@ interface HTMLMediaElement : HTMLElement {
none
metadata
@@ -32530,7 +32532,7 @@ interface HTMLMediaElement : HTMLElement {
The buffered
attribute must return a new
- static normalised TimeRanges
object that represents the ranges of the
+ 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.
removetrack
, that does not bubble and is not cancelable, and that
uses the TrackEvent
interface, with the track
attribute initialised to the AudioTrack
or
+ data-x="dom-TrackEvent-track">track attribute initialized to the AudioTrack
or
VideoTrack
object representing the track, at the media element's
aforementioned AudioTrackList
or VideoTrackList
object.
@@ -33034,7 +33036,7 @@ interface HTMLMediaElement : HTMLElement {
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 behaviour if so desired.
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 behaviour at all, and instead to
+ 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 played
attribute must return a new static
- normalised TimeRanges
object that represents the ranges of points on the
+ 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.
Let current cues be a list of cues, initialised to contain all the cues of all + cue">cues, initialized to contain all the cues of all the hidden or showing text tracks of the media element (not the disabled ones) whose HTMLMediaElement : HTMLElement { greater than the current playback position.
Let other cues be a list of cues, - initialised to contain all the cues of cues of hidden and showing text tracks of the media element that are not present in current cues.
The seekable
attribute must return a new
- static normalised TimeRanges
object that represents the ranges of the
+ 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.
The range might be continuously changing, e.g. if the user agent is buffering a - sliding window on an infinite stream. This is the behaviour seen with DVRs viewing live TV, for + 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 @@ -34391,7 +34393,7 @@ interface VideoTrack {
" (empty string)
- When a media resource contains data that the user agent recognises and supports as +
When a media resource contains data that the user agent recognizes and supports as being equivalent to a text track, the user agent runs the steps to expose a media-resource-specific text track with the relevant data, as follows.
@@ -35037,7 +35039,7 @@ interface VideoTrack { data-x="concept-events-trusted">trusted event with the nameaddtrack
, that does not bubble and is not cancelable, and that uses
the TrackEvent
interface, with the track
- attribute initialised to the text track's TextTrack
object, at the
+ attribute initialized to the text track's TextTrack
object, at the
media element's textTracks
attribute's
TextTrackList
object.
@@ -35118,7 +35120,7 @@ interface VideoTrack {
data-x="concept-events-trusted">trusted event with the name addtrack
, that does not bubble and is not cancelable, and that uses
the TrackEvent
interface, with the track
- attribute initialised to the text track's TextTrack
object, at the
+ attribute initialized to the text track's TextTrack
object, at the
media element's textTracks
attribute's
TextTrackList
object.
@@ -35129,7 +35131,7 @@ interface VideoTrack {
data-x="concept-events-trusted">trusted event with the name removetrack
, that does not bubble and is not cancelable, and that
uses the TrackEvent
interface, with the track
attribute initialised to the text track's
+ data-x="dom-TrackEvent-track">track attribute initialized to the text track's
TextTrack
object, at the media element's textTracks
attribute's TextTrackList
object.
@@ -35209,7 +35211,7 @@ interface VideoTrack {
events and stuff: we can expect authors to forget that default doesn't mean that it'll always be
turned on, and that they'll still rely on events firing even if it doesn't show. But it is
commented out, because we can equally expect authors to expect only one track is getting events,
- so we've got problems either way, and might as well go with the simpler behaviour. -->
+ so we've got problems either way, and might as well go with the simpler behavior. -->
For example, the user could have set a browser preference to the effect of "I
want French captions whenever possible", or "If there is a subtitle track with 'Commentary' in
@@ -35667,7 +35669,7 @@ interface TextTrack : EventTarget {
data-x="concept-events-trusted">trusted event with the name addtrack
, that does not bubble and is not cancelable, and
that uses the TrackEvent
interface, with the track
attribute initialised to the new text
+ data-x="dom-TrackEvent-track">track attribute initialized to the new text
track's TextTrack
object, at the media element's textTracks
attribute's TextTrackList
object.
When a TimeRanges
object is said to be a normalised TimeRanges
object, the ranges it represents must
- obey the following criteria:
When a TimeRanges
object is said to be a
+ normalized
+ TimeRanges
object, the ranges it represents must obey the following
+ criteria:
The track
attribute must return the value
- it was initialised to. It represents the context information for the event.
The activation behaviour of area
elements is to run the following
+
The activation behavior of area
elements is to run the following
steps:
If we wanted just the coloured areas to be clickable, we could do it as follows:
+If we wanted just the colored areas to be clickable, we could do it as follows:
<p> Please select a shape: @@ -37951,7 +37954,7 @@ interface HTMLAreaElement : HTMLElement {The corresponding IDL attributes for
+ sections, as they are slightly more specific to those elements' other behaviors.img
andinput
elements are defined in those respective elements' - sections, as they are slightly more specific to those elements' other behaviours.
tfoot
element, still in tree order.
- The behaviour of the insertRow(index)
method depends on the state of the table. When it is called,
+
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:
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 serialising the entire contents of the table in source order.
+ than serializing the entire contents of the table in source order.Authors are encouraged to use CSS to achieve these effects.
@@ -40190,7 +40193,7 @@ interface HTMLTableCellElement : HTMLElement {A form is a component of a Web page that has form controls, such as text, buttons, checkboxes,
- range, or colour picker controls. A user can interact with such a form, providing data that can
+ range, or color picker controls. 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
@@ -41254,13 +41257,13 @@ interface HTMLTableCellElement : HTMLElement {
data-x="attr-input-type-text"><input type=text>. If the page is asking for the user's
full name, then the relevant autocomplete
value is name
. But if the user is Japanese, and the page is asking
- for the user's Japanese name and the user's romanised name, then it would be helpful to the user
+ for the user's Japanese name and the user's romanized name, then it would be helpful to the user
if the first field defaulted to a Japanese input modality, while the second defaulted to a Latin
input modality (ideally with automatic capitalization of each word). This is where the inputmode
attribute can help:
<p><label>Japanese name: <input name="j" type="text" autocomplete="section-jp name" inputmode="kana"></label> -<label>Romanised name: <input name="e" type="text" autocomplete="section-en name" inputmode="latin-name"></label>+<label>Romanized name: <input name="e" type="text" autocomplete="section-en name" inputmode="latin-name"></label>
In this example, the "section-*
" keywords in
the autocomplete
attributes' values tell the user agent
@@ -41419,7 +41422,7 @@ interface HTMLTableCellElement : HTMLElement {
Some elements, not all of them form-associated,
- are categorised as labelable elements. These are elements that
+ are categorized as labelable elements. These are elements that
can be associated with a label
element.
@@ -41898,13 +41901,13 @@ interface HTMLLabelElement : HTMLElement {
then the first such descendant in tree order is the label
element's
labeled control.
The label
element's exact default presentation and behaviour, in particular what
- its activation behaviour might be, if anything, should match the platform's label
- behaviour. The activation behaviour of a label
element for events targeted
+
The label
element's exact default presentation and behavior, in particular what
+ its activation behavior might be, if anything, should match the platform's label
+ behavior. The activation behavior of a label
element for events targeted
at interactive content descendants of a label
element, and any
descendants of those interactive content descendants, must be to do nothing.
<label><input type=checkbox name=lost> Lost</label>-
On other platforms, the behaviour might be just to focus the control, or do nothing.
+On other platforms, the behavior might be just to focus the control, or do nothing.
@@ -42219,9 +42222,9 @@ interface HTMLInputElement : HTMLElement {color
- checkbox
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 behaviour of
+ 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 HTMLInputElement : HTMLElement {
When an input
element is first created, the element's rendering and behaviour must
- be set to the rendering and behaviour defined for the type
+
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.
Update the element's rendering and behaviour to the new state's.
Update the element's rendering and behavior to the new state's.
Signal a type change for the element. (The Radio Button state uses this, in particular.)
form
attribute is used to explicitly associate the input
element with its form owner.
The autofocus
attribute controls focus.
The inputmode
attribute controls the user interface's input modality for the control.
- The autocomplete
attribute controls how the user agent provides autofill behaviour.
+ The autocomplete
attribute controls how the user agent provides autofill behavior.
Strip leading and trailing whitespace from each value in latest values.
Constraint validation: While the user interface describes input that the user - agent cannot convert to a valid normalised local date and time string, the control is + agent cannot convert to a valid normalized local date and time string, the control is suffering from bad input.
1970-01-01T00:00:00.0
").
@@ -45476,10 +45479,10 @@ ldh-str = < as defined in
+
Note how the UA determined the orientation of the control from the ratio of the
- style-sheet-specified height and width properties. The colours were similarly derived from 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 When an The The step
attribute has not affected the placement of tick marks,
the UA deciding to only use the author-specified completion values and then adding longer tick
@@ -45615,47 +45618,47 @@ ldh-str = < as defined in Colour state (type=color
)
+ Color state (
type=color
)input
element's type
attribute is in
- the Colour state, the rules in this section apply.input
element represents a colour well control, for setting the
+ input
element represents a color well control, for setting the
element's value to a string representing a simple
- colour.
In this state, there is always a colour picked, and there is no way to set the +
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 colour represented by its value, as - obtained from applying the rules for parsing simple colour values to it. User agents + 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 colour. If the user agent provides a user interface for - selecting a colour, then the value must be set to the result - of using the rules for serialising simple colour values to the user's selection. User + 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 colour, the control is + 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 colour.
The value sanitization algorithm is as follows: If the value of the element is a valid simple colour, then
+ data-x="concept-fe-value">value of the element is a valid simple color, then
set it to the value of the element converted to ASCII
lowercase; otherwise, set it to the string "#000000
".
indeterminate
IDL attribute back to the values they had
- before the pre-click activation steps were run. The activation behaviour
+ 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 - behaviour.
+ behavior.Constraint validation: If the element is required and its 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 behaviour for
+ data-x="concept-fe-checked">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 - behaviour.
+ behavior.Constraint validation: If an element in the radio button group is required, and all of the input
elements in the
@@ -46038,7 +46041,7 @@ ldh-str = < as defined in mutable, then the element's
- activation behaviour is to run the following steps:
input
element's form owner
@@ -46508,7 +46511,7 @@ ldh-str = < as defined in alt attribute; if the element is mutable, then the element's activation behaviour is as
+ data-x="concept-fe-mutable">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
@@ -46516,8 +46519,8 @@ ldh-str = < as defined in mutable but has no
form owner or the element's node document is not fully active,
- then its activation behaviour must be to do nothing. If the element is not mutable, it has no activation behaviour.
+ 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
@@ -46628,7 +46631,7 @@ ldh-str = < as defined in Many aspects of this state's behaviour are similar to the behaviour of the
+ 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.
If the element is not mutable, it has no activation - behaviour.
+ behavior.Constraint validation: The element is barred from constraint validation.
@@ -46755,7 +46758,7 @@ ldh-str = < as defined in value attribute, though it may be the empty string. If the element has avalue
attribute, the button's label must be the value of that
@@ -46765,10 +46768,10 @@ ldh-str = < as defined in mutable, the element's activation
- behaviour is to do nothing.
+ behavior is to do nothing.
If the element is not mutable, it has no activation - behaviour.
+ behavior.Constraint validation: The element is barred from constraint validation.
@@ -47492,7 +47495,7 @@ You cannot submit this form when the field is incorrect. existing entry in theinput
element's values to have the value given by the selected
suggestion's value, as if the user had themself added
- an entry with that value, or edited an existing entry to be that value. Which behaviour is to be
+ an entry with that value, or edited an existing entry to be that value. Which behavior is to be
applied depends on the user interface in a user-agent-defined manner.
@@ -47748,7 +47751,7 @@ You cannot submit this form when the field is incorrect.
The value
IDL attribute allows scripts to
manipulate the value of an input
element. The
- attribute is in one of the following modes, which define its behaviour:
When the input
and change
events apply
@@ -48008,7 +48011,7 @@ You cannot submit this form when the field is incorrect.
In all cases, the input
event comes before the corresponding
change
event (if any).
When an input
element has a defined activation behaviour, the rules
+
When an input
element has a defined activation behavior, the rules
for dispatching these events, if they apply, are given
in the section above that defines the type
attribute's
state. (This is the case for all input
controls with the
data-x="attr-input-type-radio">Radio Button state, or the File Upload state.)
For input
elements without a defined activation behaviour, but to
+
For input
elements without a defined activation behavior, but to
which these events apply, and for which the user
interface involves both interactive manipulation and an explicit commit action, then when the user
changes the element's value, the user agent must
@@ -48034,7 +48037,7 @@ You cannot submit this form when the field is incorrect.
whereas the change
event would only fire when the user
let go of the knob, committing to a specific value.
For input
elements without a defined activation behaviour, but to
+
For input
elements without a defined activation behavior, but to
which these events apply, and for which the user
interface involves an explicit commit action but no intermediate manipulation, then any time the
user commits a change to the element's value, the user
@@ -48044,10 +48047,10 @@ You cannot submit this form when the field is incorrect.
data-x="event-change">change at the input
element.
An example of a user interface with a commit action would be a Colour control that consists of a single button that brings - up a colour wheel: if the value only changes when the dialog + data-x="attr-input-type-color">Color control that consists of a single button that brings + up a color wheel: if the value only changes when the dialog is closed, then that would be the explicit commit action. On the other hand, if manipulating the - control changes the colour interactively, then there might be no commit action.
+ control changes the color interactively, then there might be no commit action.Another example of a user interface with a commit action would be a Date control that allows both text-based user input and user @@ -48055,7 +48058,7 @@ You cannot submit this form when the field is incorrect. selecting a date from the drop down calendar and then dismissing the drop down would be a commit action.
-For input
elements without a defined activation behaviour, but to
+
For input
elements without a defined activation behavior, but to
which these events apply, any time the user causes the
element's value to change without an explicit commit
action, the user agent must queue a task to fire a simple event that
@@ -48162,7 +48165,7 @@ interface HTMLButtonElement : HTMLElement {
The element is a button.
-The type
attribute controls the behaviour of
+
The type
attribute controls the behavior of
the button when it is activated. It 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.
When a button
element is not disabled,
- its activation behaviour element is to run the steps defined in the following list for
+ its activation behavior element is to run the steps defined in the following list for
the current state of the element's type
attribute:
show
at menu, using the RelatedEvent
interface, with the relatedTarget
attribute
- initialised to the button
element. The event must be cancelable.
If the event is not canceled, then build and
@@ -48599,7 +48602,7 @@ interface HTMLSelectElement : HTMLElement {
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 behaviour.
+ The autocomplete
attribute controls how the user agent provides autofill behavior.
A select
element that is not disabled is
@@ -49310,7 +49313,7 @@ interface HTMLOptionElement : HTMLElement {
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 behaviour depends on
+
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
@@ -49586,24 +49589,25 @@ interface HTMLTextAreaElement : HTMLElement {
For historical reasons, the element's value is normalised in three different ways for three +
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 normalised. The API
+ it was originally set. It is not normalized. The API
value is the value used in the value
IDL
attribute, textLength
IDL attribute, and by the
maxlength
and minlength
content attributes. It is normalised so that line
+ data-x="attr-fe-minlength">minlength content attributes. 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 normalised so that line breaks use U+000D CARRIAGE RETURN U+000A LINE
+ 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 algorithm for obtaining the element's API value is to return the element's raw value with the - textarea line break normalisation transformation applied. The textarea line - break normalisation transformation is the following algorithm, as applied to a string:
+ textarea line break normalization transformation applied. The + textarea line break + normalization transformation is the following algorithm, as applied to a string: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 line break normalisation
+ element's textContent
IDL attribute with the textarea line break normalization
transformation applied is equal to or less than the element's maximum allowed value
length.
inputmode
attribute controls the user interface's input
modality for the control.
The autocomplete
attribute controls how the user agent
- provides autofill behaviour.
+ provides autofill behavior.
@@ -49915,7 +49919,7 @@ interface HTMLKeygenElement : HTMLElement {
enumerated attribute. The following table lists the keywords and states for the
attribute — the keywords in the left column map to the states listed in the cell in the
second column on the same row as the keyword. User agents are not required to support these
- values, and must only recognise values whose corresponding algorithms they support.
+ values, and must only recognize values whose corresponding algorithms they support.
Keyword | State
@@ -50886,7 +50890,7 @@ and a height of <meter value=2>2cm</meter>.</p> <!-- BAD!
- The following example shows how a gauge could fall back to localised or pretty-printed + The following example shows how a gauge could fall back to localized or pretty-printed text. <p>Disk usage: <meter min=0 value=170261928 max=233257824>170 261 928 bytes used @@ -51122,7 +51126,7 @@ interface HTMLLegendElement : HTMLElement { |
---|
If scheme is not one of those listed in this table, then the behaviour is +
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 behaviours described below, when the
+ 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:
The behaviours are as follows:
+The behaviors are as follows:
In the case of the value of
- textarea
elements, this newline normalisation is already performed during the
+ 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
- normalised.
In these examples, the summary really just summarises what the controls can change, and not +
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 colour of the summary
+ differently based on its state. Here, a stylesheet is used to animate the color of the summary
when the element is opened or closed:
<style> @@ -55667,7 +55671,7 @@ interface HTMLMenuElement : HTMLElement { aclick
event, either directly or via the run synthetic click activation steps algorithm, then therelatedTarget
attribute of thatclick
event must be initialised to subject. + data-x="event-click">click event must be initialized to subject.Pop-up menus must not, while being shown, reflect changes in the DOM. The menu is constructed from the DOM before being shown, and is then immutable.
@@ -55968,7 +55972,7 @@ interface HTMLMenuItemElement : HTMLElement {
If the element's Disabled State is false - (enabled) then the element's activation behaviour depends on the element's
activation behavior depends on the element's
type
attribute, as follows:
The element's activation behaviour is to do nothing.
The element's activation behavior is to do nothing.
If the element's Disabled State is true - (disabled) then the element has no activation behaviour.
+ (disabled) then the element has no activation behavior.contextmenu
, that bubbles and is cancelable, and that uses the
MouseEvent
interface, at the element for which the menu was requested. The context
- information of the event must be initialised to the same values as the last
+ information of the event must be initialized to the same values as the last
MouseEvent
user interaction event that was fired as part of the gesture that was
interpreted as a request for the context menu.
@@ -56131,7 +56135,7 @@ interface HTMLMenuItemElement : HTMLElement {
agent must fire a trusted event with the name show
at menu, using the RelatedEvent
interface,
- with the relatedTarget
attribute initialised
+ with the relatedTarget
attribute initialized
to subject. The event must be cancelable.
@@ -56142,7 +56146,7 @@ interface HTMLMenuItemElement : HTMLElement {
The user agent may also provide access to its default context menu, if any, with the context menu shown. For example, it could merge the menu items from the two menus together, or provide the page's context menu as a submenu of the default menu. In general, user agents are encouraged to - de-emphasise their own contextual menu items, so as to give the author's context menu the + de-emphasize their own contextual menu items, so as to give the author's context menu the appearance of legitimacy — to allow documents to feel like "applications" rather than "mere Web pages".
@@ -56214,7 +56218,7 @@ dictionary RelatedEventInit : EventInit {The relatedTarget
attribute
- must return the value it was initialised to. It represents the other event target that is related
+ must return the value it was initialized to. It represents the other event target that is related
to the event.
The Action of the command, if the element has a
- defined activation behaviour, is to run synthetic click activation steps
+ 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.
The Action of the command, if the element has a
- defined activation behaviour, is to run synthetic click activation steps
+ 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.
The Action of the command, if the element has a
- defined activation behaviour, is to
+ 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.
click
event at the element.Each Document
has a stack of dialog
elements known as the
pending dialog stack. When a Document
is created, this stack must be
- initialised 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
@@ -57311,7 +57315,7 @@ interface HTMLScriptElement : HTMLElement {
data-x="attr-script-async">async attribute is specified, to cause legacy Web browsers that
only support defer
(and not async
) to fall back to the defer
behaviour instead of the blocking behaviour that
+ data-x="attr-script-defer">defer behavior instead of the blocking behavior that
is the default.
The crossorigin
attribute is a
@@ -57415,7 +57419,7 @@ o............A....e
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 initialise the form's output.
<script> function calculate(form) { @@ -58129,7 +58133,7 @@ o............A....eIf the script is from an external file, or the script's type is "
module
", then increment the ignore-destructive-writes counter of thescript
- element's node document. Let neutralised doc be that + element's node document. Let neutralized doc be thatDocument
.
Decrement the ignore-destructive-writes counter of neutralised doc, if it was incremented in the earlier step.
+Decrement the ignore-destructive-writes counter of neutralized doc, if it was incremented in the earlier step.
For example, types that include the charset
parameter will
- not be recognised as referencing any of the scripting languages listed above.
Returns null if the given context ID is not supported, if the canvas has already been
- initialised with the other context type (e.g. trying to get a "2d
" context after getting a "webgl
" context).
data:
URL; it represents the empty string in a text/plain
resource.)
- Let file be a
- serialisation of this canvas
element's bitmap as a file, passing
+
Let file be a
+ serialization of this canvas
element's bitmap as a file, passing
type and quality if they were given.
Return a data:
URL representing
@@ -59415,7 +59419,7 @@ callback BlobCallback = void (Blob? blob);
dimension or its vertical dimension is zero) then let result be null.
Otherwise, let result be a Blob
object representing a serialisation of the canvas
element's
+ serialization of the bitmap as a file">a serialization of the canvas
element's
bitmap as a file, passing type and quality if they were given.
Queue a task to invoke
the BlobCallback
callback with result as its argument. The
- task source for this task is the canvas blob serialisation task source.
A CanvasRenderingContext2D
object has an output bitmap that
- is initialised when the object is created.
The output bitmap has an Path2D {
Create a new Initialise its Initialize its Let the new Let canvas be the CanvasRenderingContext2D
object.canvas
attribute to point to
+ canvas
attribute to point to
target.CanvasRenderingContext2D
object's output bitmap be
@@ -59894,7 +59899,7 @@ interface Path2D {
and clear it to fully transparent black.canvas
element to which the rendering
- context's canvas
attribute was initialised.canvas
attribute was initialized.
If the numeric value of canvas's The width
content attribute differs from width, then set canvas's
canvas
attribute must return the
- value it was initialised to when the object was created.
Whenever the CSS value currentColor
is used as a colour in the CanvasRenderingContext2D
+ data-x="">currentColor is used as a color in the CanvasRenderingContext2D
API, the computed value of the currentColor
keyword is
the computed value of the 'color' property on the canvas
- element at the time that the colour is specified (e.g. when the appropriate attribute is set, or
- when the method is called; not when the colour is rendered or otherwise used). If the computed
+ element at the time that the color is specified (e.g. when the appropriate attribute is set, or
+ when the method is called; not when the color is rendered or otherwise used). If the computed
value of the 'color' property is undefined for a particular case (e.g. because the element is
not in a document), then the computed value of the 'color' property
for the purposes of determining the computed value of the currentColor
@@ -60009,7 +60014,7 @@ context.fillRect(100,0,50,50); // only this square remains
This is because CanvasGradient
objects are
canvas
-neutral — a CanvasGradient
object created by one
canvas
can be used by another, and there is therefore no way to know which is the
- "element in question" at the time that the colour is specified.
Similar concerns exist with font-related properties; the rules for those are described in detail in the relevant section below.
@@ -60249,7 +60254,7 @@ idea from Mihai:Returns a copy of the current line dash pattern. The array returned will always have an even - number of entries (i.e. the pattern is normalised).
+ number of entries (i.e. the pattern is normalized).Objects that implement the CanvasTextDrawingStyles
interface have attributes
- (defined in this section) that control how text is laid out (rasterised or outlined) by the
+ (defined in this section) that control how text is laid out (rasterized or outlined) by the
object. Such objects can also have a font style source object. For
CanvasRenderingContext2D
objects, this is the canvas
element
referenced by the context's canvas property.
On getting, the font
attribute must return the serialised form of the current font of the context (with
+ data-x="serializing a CSS value">serialized form of the current font of the context (with
no 'line-height' component).
When an object implementing the CanvasPath
interface is created, its path must be initialised to zero subpaths.
The arcTo(x1, y1, x2, y2, radiusX,
radiusY, rotation)
method must first
- ensure there is a subpath for (x1, y1). Then, the behaviour depends on the arguments and the last point in the
+ ensure there is a subpath for (x1, y1). Then, the behavior depends on the arguments and the last point in the
subpath, as described below.
Negative values for radiusX or radiusY must cause the @@ -61805,7 +61810,7 @@ try {
Objects that implement the CanvasTransform
interface have a current
transformation matrix, as well as methods (described in this section) to manipulate it. When
an object implementing the CanvasTransform
interface is created, its transformation
- matrix must be initialised to the identity transform.
The current transformation matrix is applied to coordinates when creating the
current default path, and when painting text, shapes, and Path2D
@@ -62099,7 +62104,7 @@ try {
Can be set, to change the fill style.
-The style can be either a string containing a CSS colour, or a CanvasGradient
or
+
The style can be either a string containing a CSS color, or a CanvasGradient
or
CanvasPattern
object. Invalid values are ignored.
Can be set, to change the stroke style.
-The style can be either a string containing a CSS colour, or a CanvasGradient
or
+
The style can be either a string containing a CSS color, or a CanvasGradient
or
CanvasPattern
object. Invalid values are ignored.
rgba()
functional-notation format: the literal string
"rgba
" (U+0072 U+0067 U+0062 U+0061) followed by a U+0028 LEFT PARENTHESIS,
a base-ten integer in the range 0-255 representing the red component (using ASCII
@@ -62199,8 +62204,8 @@ try {
must initially have the string value #000000
.
- When the value is a colour, it must not be affected by the transformation matrix when used to - draw on bitmaps.
+When the value is a color, it must not be affected by the transformation matrix when used to + draw on bitmaps.
CanvasGradient
interface.
Once a gradient has been created (see below), stops are placed along it to - define how the colours are distributed along the gradient. The colour of the - gradient at each stop is the colour specified for that stop. Between each such stop, the colours and + define how the colors are distributed along the gradient. The color of the + gradient at each stop is the color specified for that stop. Between each such stop, the colors and the alpha component must be linearly interpolated over the RGBA space without premultiplying the - alpha value to find the colour to use at that offset. Before the first stop, the colour must be the - colour of the first stop. After the last stop, the colour must be the colour of the last stop. When + alpha value to find the color to use at that offset. Before the first stop, the color must be the + color of the first stop. After the last stop, the color must be the color of the last stop. When there are no stops, the gradient is transparent black.
Adds a colour stop with the given colour to the gradient at the given offset. 0.0 is the offset +
Adds a color stop with the given color to the gradient at the given offset. 0.0 is the offset at one end of the gradient, 1.0 is the offset at the other end.
Throws an "IndexSizeError
" DOMException
if the offset
is out of range. Throws a "SyntaxError
" DOMException
if
- the colour cannot be parsed.
SyntaxError
" DOMException
must be thrown. Otherwise, the
gradient must have a new stop placed, at offset offset relative to the whole gradient,
- and with the colour obtained by parsing
+ and with the color obtained by parsing
color as a CSS <color> value. If multiple stops are added at the same
offset on a gradient, they must be placed in the order added, with the first one closest to the
start of the gradient, and each subsequent one infinitesimally further along towards the end point
(in effect causing all but the first and last stop added at each point to be ignored).
The createLinearGradient(x0, y0, x1, y1)
method takes four arguments that represent the start point (x0, y0) and end point (x1, y1) of the gradient. The method must return a linear CanvasGradient
- initialised with the specified line.
Linear gradients must be rendered such that all points on a line perpendicular to the line that - crosses the start and end points have the colour at the point where those two lines cross (with the - colours coming from the interpolation and extrapolation described + crosses the start and end points have the color at the point where those two lines cross (with the + colors coming from the interpolation and extrapolation described above). The points in the linear gradient must be transformed as described by the current transformation matrix when rendering.
@@ -62291,7 +62296,7 @@ try { (x1, y1) and radius r1. The values are in coordinate space units. If either of r0 or r1 are negative, an "IndexSizeError
" DOMException
must be thrown.
- Otherwise, the method must return a radial CanvasGradient
initialised with the two
+ Otherwise, the method must return a radial CanvasGradient
initialized with the two
specified circles.
Radial gradients must be rendered by following these steps:
@@ -62309,22 +62314,22 @@ try {Let r(ω) = (r1-r0)ω + r0
-Let the colour at ω be the colour at that position on the gradient - (with the colours coming from the interpolation and extrapolation +
Let the color at ω be the color at that position on the gradient + (with the colors coming from the interpolation and extrapolation described above).
For all values of ω where r(ω) > 0, starting with the value of ω nearest to positive infinity and ending with the value of ω nearest to negative infinity, draw the circumference of the circle with radius r(ω) at position (x(ω), y(ω)), with the - colour at ω, but only painting on the parts of the bitmap that have not + color at ω, but only painting on the parts of the bitmap that have not yet been painted on by earlier circles in this step for this rendering of the gradient.
This effectively creates a cone, touched by the two circles defined in the - creation of the gradient, with the part of the cone before the start circle (0.0) using the colour - of the first offset, the part of the cone after the end circle (1.0) using the colour of the last + creation of the gradient, with the part of the cone before the start circle (0.0) using the color + of the first offset, the part of the cone after the end circle (1.0) using the color of the last offset, and areas outside the cone untouched by the gradient (transparent black).
The resulting radial gradient must then be transformed as described by the "SyntaxError
" DOMException
and abort these steps.
Create a new CanvasPattern
object with the image image
- and the repetition behaviour given by repetition.
If the image argument is not origin-clean, then mark the @@ -62430,9 +62435,9 @@ try {
Place a copy of the image on the bitmap, anchored such that its top left corner is at the
origin of the coordinate space, with one coordinate space unit per CSS
pixel of the image, then place repeated copies of this image horizontally to the left and
- right, if the repetition behaviour is "repeat-x
", or vertically up and
- down, if the repetition behaviour is "repeat-y
", or in all four
- directions all over the bitmap, if the repetition behaviour is "repeat-x
", or vertically up and
+ down, if the repetition behavior is "repeat-y
", or in all four
+ directions all over the bitmap, if the repetition behavior is "repeat
".
If the original image data is a bitmap image, the value painted at a point in the area of the @@ -62444,8 +62449,8 @@ try { data-x="dom-context-2d-imageSmoothingQuality">imageSmoothingQuality attribute to guide the choice of filtering algorithm. When such a filtering algorithm requires a pixel value from outside the original image data, it must instead use the value from wrapping the pixel's - coordinates to the original image's dimensions. (That is, the filter uses 'repeat' behaviour, - regardless of the value of the pattern's repetition behaviour.)
+ coordinates to the original image's dimensions. (That is, the filter uses 'repeat' behavior, + regardless of the value of the pattern's repetition behavior.)If a radial gradient or repeated pattern is used when the transformation matrix is singular, the resulting style must be transparent black (otherwise the gradient or pattern would be collapsed to a point or line, leaving the other pixels undefined). Linear gradients and solid - colours always define all points even with singular transformation matrices.
+ colors always define all points even with singular transformation matrices.When the context is initialised, the clipping region must be set to the largest infinite +
When the context is initialized, the clipping region must be set to the largest infinite surface (i.e. by default, no clipping occurs).
rectangle is computed by filtering the original image data. The user agent may use any filtering algorithm (for example bilinear interpolation or nearest-neighbor). When the filtering algorithm requires a pixel value from outside the original image data, it must instead use the value from - the nearest edge pixel. (That is, the filter uses 'clamp-to-edge' behaviour.) When the filtering + the nearest edge pixel. (That is, the filter uses 'clamp-to-edge' behavior.) When the filtering algorithm requires a pixel value from outside the source rectangle but inside the original image data, then the value from the original image data must be used.The canvas
APIs must perform colour correction at only two points: when rendering
- images with their own gamma correction and colour space information onto a bitmap, to convert the
- image to the colour space used by the bitmaps (e.g. using the 2D Context's The
canvas
APIs must perform color correction at only two points: when rendering
+ images with their own gamma correction and color space information onto a bitmap, to convert the
+ image to the color space used by the bitmaps (e.g. using the 2D Context's drawImage()
method with an
HTMLOrSVGImageElement
object), and when rendering the actual canvas bitmap to the
output device.
Thus, in the 2D context, colours used to draw shapes onto the canvas will exactly
- match colours obtained through the Thus, in the 2D context, colors used to draw shapes onto the canvas will exactly
+ match colors obtained through the
getImageData()
method.
The toDataURL()
method must not include colour space
- information in the resources they return. Where the output format allows it, the colour of pixels
+
The toDataURL()
method must not include color space
+ information in the resources they return. Where the output format allows it, the color of pixels
in resources created by toDataURL()
must match those
returned by the getImageData()
method.
In user agents that support CSS, the colour space used by a canvas
element must
- match the colour space used for processing any colours for that element in CSS.
In user agents that support CSS, the color space used by a canvas
element must
+ match the color space used for processing any colors for that element in CSS.
The gamma correction and colour space information of images must be handled in such a way that
- an image rendered directly using an img
element would use the same colours as one
+
The gamma correction and color space information of images must be handled in such a way that
+ an image rendered directly using an img
element would use the same colors as one
painted on a canvas
element that is then itself rendered. Furthermore, the rendering
- of images that have no colour correction information (such as those returned by the toDataURL()
method) must be rendered with no colour
+ of images that have no color correction information (such as those returned by the toDataURL()
method) must be rendered with no color
correction.
Thus, in the 2D context, calling the When a user agent is to create a
- serialisation of the bitmap as a file, given an optional type and
+ When a user agent is to create a
+ serialization of the bitmap as a file, given an optional type and
quality, it must create an image file in the format given by type, or if
type was not supplied, in the PNG format. User agents must convert the provided type to ASCII
lowercase before establishing if they support that type. For image types that do not support an alpha channel, the serialised image must be the bitmap
+ For image types that do not support an alpha channel, the serialized image must be the bitmap
image composited onto a solid black background using the source-over operator. If type is an image format that supports variable quality (such as
@@ -65688,7 +65693,7 @@ dictionary ImageBitmapRenderingContextSettings {
Custom elements provide a way for authors to build their
own fully-featured DOM elements. Although authors could always use non-standard elements in their
- documents, with application-specific behaviour added after the fact by scripting or similar, such
+ documents, with application-specific behavior added after the fact by scripting or similar, such
elements have historically been non-conforming and not very functional. By defining a custom element, authors can inform the parser how to
properly construct an element and how elements of that class should react to changes. Customized built-in elements are a distinct
kind of custom element, which are defined slightly differently and used very
differently compared to autonomous custom
- elements. They exist to allow reuse of behaviours from the existing elements of HTML, by
+ elements. They exist to allow reuse of behaviors from the existing elements of HTML, by
extending those elements with new custom functionality. This is important since many of the
- existing behaviours of HTML elements can unfortunately not be duplicated by using purely autonomous custom elements. Instead, customized built-in elements allow the installation of
- custom construction behaviour, lifecycle hooks, and prototype chain onto existing elements,
+ custom construction behavior, lifecycle hooks, and prototype chain onto existing elements,
essentially "mixing in" these capabilities on top of the already-existing element. Customized built-in elements require a
distinct syntax from autonomous custom elements
because user agents and other software key off an element's local name in order to identify the
- element's semantics and behaviour. That is, the concept of customized built-in elements building on top of existing behaviour depends
+ element's semantics and behavior. That is, the concept of customized built-in elements building on top of existing behavior depends
crucially on the extended elements retaining their original local name. In this example, we'll be creating a customized built-in element named Trying to use a customized built-in element as an autonomous custom
element will not work; that is, If you need to create a type-extended element programmatically, you can use the following form
of Notably, all the of the ways in which The addition of event handlers to handle commonly-expected button behaviours helps convey
+ The addition of event handlers to handle commonly-expected button behaviors helps convey
the semantics of the button to Web browser users. In this case, the most relevant event handler
would be one that proxies appropriate Even with this rather-complicated element definition, the element is not a pleasure to use for
consumers: it will be continually "sprouting" In contrast, a simple customized built-in element, as shown in the previous
- section, would automatically inherit the semantics and behaviour of the After a custom element is created,
changing the value of the Autonomous custom elements have the following
@@ -66795,7 +66800,7 @@ customElements.define("x-foo", class extends HTMLElement {
callback function as well as a list of arguments. This is all summarised in the following schematic diagram: This is all summarized in the following schematic diagram: The actual frequency of each tag is given using the The An element is said to be in a formal activation state between the time the user
- begins to indicate an intent to trigger the element's activation behaviour and
+ begins to indicate an intent to trigger the element's activation behavior and
either the time the user stops indicating an intent to trigger the element's activation
- behaviour, or the time the element's activation behaviour has finished
+ behavior, or the time the element's activation behavior has finished
running, which ever comes first. An element is said to be being actively pointed at while the user indicates the
@@ -68264,7 +68269,7 @@ Demos:
Sometimes, it is desirable to annotate content with specific machine-readable labels, e.g. to
- allow generic scripts to provide services that are customised to the page, or to enable content
+ allow generic scripts to provide services that are customized to the page, or to enable content
from a variety of cooperating authors to be processed by a single script in a consistent
manner. Add an entry to result called " Return the result of serialising result to JSON in the shortest
+ Return the result of serializing result to JSON in the shortest
possible way (meaning no whitespace between tokens, no unnecessary zero digits in numbers, and
only using Unicode escapes in strings for characters that do not have a dedicated escape
sequence), and with a lowercase " Certain elements in HTML have an activation behaviour, which means that the user
+ 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 The user agent should allow the user to manually trigger elements that have an activation
- behaviour, for instance using keyboard or voice input, or through mouse clicks. When the
- user triggers an element with a defined activation behaviour in a manner other than
+ 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. Fire a Click-focusing behaviour (e.g., the focusing of a text control when user clicks in
+ Click-focusing behavior (e.g., the focusing of a text control when user clicks in
one) typically happens before the click, when the mouse button is first depressed, and is
therefore not discussed here. If target has a defined activation behaviour, then return
+ If target has a defined activation behavior, then return
target and abort these steps. If target has a parent element, then set target to
@@ -72293,16 +72298,16 @@ END:VCARD
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 behaviour defined for that element, if any.
- Activation behaviours can refer to the An algorithm is triggered by user
activation if any of the following conditions is true: The task in which the algorithm is running is currently
- processing an activation behaviour whose When a drag data store is created, it
- must be initialised such that its drag data store item list is empty, it has no
+ 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
@@ -74941,7 +74946,7 @@ body { display:none }
set to the new value. Other values must be ignored. The The Let dataTransfer be a newly created Set the Set the Set the Set the Create a trusted ImageBitmapRenderingContextSettings {
-
Serialising bitmaps to a file
+ Serializing bitmaps to a file
Creating an autonomous custom element
@@ -65775,19 +65780,19 @@ document.body.appendChild(flagIcon)
<plastic-button>Click
me?</plastic-button>
will simply create an HTMLElement
with no special
- behaviour.createElement()
:button
is special apply to such "plastic
- buttons" as well: their focus behaviour, ability to participate in form submission, the disabled
attribute, and so on.true
" when the button
is logically disabled conveys to accessibility technology the button's disabled state.
- keydown
events to
become click
events, so that you can activate the button both
@@ -65958,14 +65963,14 @@ console.log(plasticButton2.getAttribute("is")); // will output "plastic-button"<
tabindex
and
aria-*
attributes of its own volition. This is because as of now
- there is no way to specify default accessibility semantics or focus behaviour for custom elements,
+ there is no way to specify default accessibility semantics or focus behavior for custom elements,
forcing the use of these attributes to do so (even though they are usually reserved for allowing
- the consumer to override default behaviour).button
- element, with no need to implement these behaviours manually. In general, for any elements with
- nontrivial behaviour and semantics that build on top of existing elements of HTML, button
+ element, with no need to implement these behaviors manually. In general, for any elements with
+ nontrivial behavior and semantics that build on top of existing elements of HTML, customized built-in elements will be easier to
develop, maintain, and consume.is
attribute does not
- change the element's behaviour, as it is saved on the element as its is
value.title
attribute. A CSS style sheet is provided to convert the markup into a cloud of differently-sized
words, but for user agents that do not support CSS or are not visual, the markup contains
- annotations like "(popular)" or "(rare)" to categorise the various tags by frequency, thus
+ annotations like "(popular)" or "(rare)" to categorize the various tags by frequency, thus
enabling all users to benefit from the information.ul
element is used (rather than ol
) because the order is not
@@ -67771,9 +67776,9 @@ contradict people?
last-modified
items
" whose
value is the array items.e
" used, when appropriate, in the
@@ -72171,7 +72176,7 @@ END:VCARD
Activation
- click
event, as
described below.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 initialised to false.click()
method can be used to make the run
synthetic click activation steps algorithm happen programmatically.
-
-
click
event that was
- fired by the steps above leading up to this point.click
event that
+ was fired by the steps above leading up to this point.
click
+ processing an activation behavior whose click
event was trusted.forceSpellCheck()
method,
- when invoked on an element, must override this behaviour, forcing the user agent to consider all
+ 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.
@@ -74782,7 +74787,7 @@ body { display:none }
effectAllowed
attribute is
- used in the drag-and-drop processing model to initialise the dropEffect
attribute during the dragenter
and dragover
events. When the DataTransfer
object is
@@ -75622,7 +75627,7 @@ dictionary DragEventInit : MouseEventInit {
dataTransfer
attribute of the
- DragEvent
interface must return the value it was initialised to. It represents the
+ DragEvent
interface must return the value it was initialized to. It represents the
context information for the event.DataTransfer
object
associated with the given drag data store.effectAllowed
attribute to the drag data
store's drag data store allowed effects state.dropEffect
attribute to "none
" if e is dragstart
, drag
, DragEventInit : MouseEventInit {
attribute initialized to window, the DragEvent
object
- and initialise it to have the given name e, to bubble, to be cancelable unless
+ 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 initialised to window, the detail
attribute initialised to zero, the mouse and key
- attributes initialised according to the state of the input devices as they would be for user
+ data-x="dom-UIEvent-view">viewdetail
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 initialised to related target, and the dataTransfer
attribute initialised to
+ attribute initialized to related target, and the dataTransfer
attribute initialized to
dataTransfer, the DataTransfer
object created above.✓ Cancelable
Protected mode
- Based on
+ effectAllowed
valueBased on
effectAllowed
valueReject immediate user selection as potential target element
effectAllowed
valueeffectAllowed
valueThe true state means the element is draggable; the false state means that it is - not. The auto state uses the default behaviour of the user agent.
+ 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
@@ -77191,7 +77196,7 @@ dictionary DragEventInit : MouseEventInit {
If browsingContext has a creator browsing context, then set document's referrer to the serialisation of creator URL.
If browsingContext has a creator browsing context, then set
document's referrer policy to
@@ -77645,7 +77650,7 @@ console.assert(iframeWindow.frameElement === null);
_top
.
These values have different meanings based on whether the page is sandboxed or not, as
- summarised in the following (non-normative) table. In this table, "current" means the
+ 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
@@ -77850,7 +77855,7 @@ console.assert(iframeWindow.frameElement === null);
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 behaviour (if the user agent doesn'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 abstract operation returns undefined and there is no custom behaviour, the
+ If this abstract operation returns undefined and there is no custom behavior, the
caller needs to throw a "CrossOriginGetOwnPropertyHelper ( O, P )
- SecurityError
" DOMException
.
@@ -78450,8 +78455,8 @@ callback FrameRequestCallback = void (DOMHighResTimeStampDocument
.
The Document
object associated with a Window
object can
- change in exactly one case: when the navigate algorithm initialises a new Document
object for the first page loaded
+ 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.
An internal value, with no serialisation it can be recreated from (it is serialised as
- "null
" per ASCII serialisation of an origin), for which the
+
An internal value, with no serialization it can be recreated from (it is serialized as
+ "null
" per ASCII serialization of an origin), for which the
only meaningful operation is testing for equality.
The default behaviour as defined in the WHATWG DOM standard applies. .
+The default behavior as defined in the WHATWG DOM standard applies. .
The origin is a unique opaque origin assigned when the Document
is
@@ -79560,9 +79565,9 @@ callback FrameRequestCallback = void (DOMHighResTimeStamp
-
The Unicode serialisation of an - origin is the string obtained by applying the following algorithm to the given - origin origin:
+The Unicode + serialization of an origin is the string obtained by applying the following algorithm to the + given origin origin:
If origin is an opaque origin, then @@ -79581,21 +79586,21 @@ callback FrameRequestCallback = void (DOMHighResTimeStampport.
Return the ASCII serialisation of an origin, given unicodeOrigin.
+Return the ASCII serialization of an origin, given unicodeOrigin.
-The name ASCII serialisation of an origin is misleading, as it
- merely serialises an origin, which are all ASCII by default due to the URL
+ The name ASCII serialization of an origin is misleading, as it
+ merely serializes an origin, which are all ASCII by default due to the URL
parser.
The Unicode
- serialisation of ("https
", "The Unicode
+ serialization of ("
https
", "xn--maraa-rta.example
", null, null) is "https://maraña.example
".
The ASCII serialisation of an - origin is the string obtained by applying the following algorithm to the given +
The ASCII serialization + of an origin is the string obtained by applying the following algorithm to the given origin origin:
Append "://
" to result.
Append origin's host, serialised, to result.
If origin's port is non-null, append a U+003A COLON character (:), and origin's port, serialised, + data-x="concept-origin-port">port, serialized, to result.
Return result.
Return effectiveDomain, serialised.
The domain
attribute's setter must run these
@@ -80487,7 +80492,7 @@ interface History {
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 synchronisation.
Let current be current's parent browsing context.
Append the Unicode serialisation +
Append the Unicode serialization of current's active document's origin to output as a new value.
activation behavior is currently being processed whose click
event was trusted, or
SecurityError
" DOMException
.
Return this Location
object's url,
- serialised.
The href
attribute's setter must run these steps:
SecurityError
" DOMException
.
- Return the Unicode serialization +
Return the Unicode serialization
of this Location
object's url's origin.
It returns the Unicode rather than the ASCII serialisation for +
It returns the Unicode rather than the ASCII serialization for
compatibility with MessageEvent
.
The protocol
attribute's getter must run
@@ -81228,12 +81233,12 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O
If url's port is null, return url's host, serialised.
Return url's host, serialised, followed by ":
" and url's port, serialised.
:
" and url's port, serialized.
The host
attribute's setter must run these steps:
Return this Location
object's url's host, serialised.
The hostname
attribute's setter must run these
@@ -81310,7 +81315,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O
Return this Location
object's url's port, serialised.
The port
attribute's setter must run these steps:
Cancel any preexisting but not yet mature
attempt to navigate browsingContext, including canceling any instances of the fetch algorithm started by those attempts. If one of those attempts
- has already created and initialised a new
+ 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
@@ -81888,7 +81893,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O
and jump to the step labeled process result below.
Let urlString be the result of running the URL serialiser on resource's URL serializer on resource's url.
Remove the leading "javascript:
" string from
@@ -82288,8 +82293,8 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O
data-x="javascript protocol">dereferencing a javascript:
URL and when
performing an overridden reload.
Initialising a new Document
object: when a
+
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:
If resource is a request, then set the document's referrer to the serialisation of resource's serialization of resource's referrer, if resource's referrer is a URL record, and the empty string otherwise.
@@ -82507,7 +82512,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON OFragment 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 - optimise the user experience in the face of performance concerns.)
If the At the time of writing, the XML specification community had not actually yet
specified how XML and the DOM interact. After the After the The actual HTTP headers and other metadata, not the headers as mutated or implied by the
@@ -82585,7 +82590,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O
the element is inserted into the document,
the user agent must parse the value of that attribute relative
to that element's node document, and if that is successful, must apply the URL serialiser algorithm to the resulting URL
+ data-x="concept-url-serializer">URL serializer algorithm to the resulting URL
record with the exclude fragment flag set to obtain manifest URL, and
then run the application cache selection algorithm
with manifest URL as the manifest URL, passing in the newly-created
@@ -82624,7 +82629,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O
data-x="HTML documents">HTML document Let part one be the result of applying the URL serialiser algorithm to urlRecordOne,
+ data-x="concept-url-serializer">URL serializerDocument
object has no parser, or its parser has stopped parsing, or the user agent has reason to believe the user is no longer
@@ -82531,7 +82536,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O
queue a task to create a Document
object, mark it as being an HTML document, set its content type to "text/html
",
- initialise the Document
object, and finally create an 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
@@ -82570,7 +82575,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O
Document
is created, the user agent must initialise the
+ Document
is created, the user agent must initialize the
Document
object.Document
object,
+ 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
Let part two be the result of applying the URL serialiser algorithm to urlRecordTwo, + data-x="concept-url-serializer">URL serializer algorithm to urlRecordTwo, with the exclude fragment flag set.
If part one is already in the fallback URLs mapping @@ -84603,7 +84609,7 @@ NETWORK: start of line.
Let new URL be the result of applying the URL serialiser algorithm to urlRecord, with + data-x="concept-url-serializer">URL serializer algorithm to urlRecord, with the exclude fragment flag set.
Add new URL to the online safelist namespaces.
@@ -84936,12 +84942,12 @@ NETWORK: that the user agent failed to save the application for offline use.Otherwise, associate the Document
for this entry with cache; store the resource for this entry in cache, if it
- isn't already there, and categorise its entry as a master entry. If applying the URL parser
algorithm to the resource's URL results in a URL record that has a
non-null fragment component, the URL
used for the entry in cache must instead be the absolute URL
- obtained from applying the URL serialiser
+ obtained from applying the URL serializer
algorithm to the URL record with the exclude fragment flag set
(application caches never include fragments).
If the URL being processed was flagged as an "explicit entry" in file - list, then categorise the entry as an explicit + list, then categorize the entry as an explicit entry.
If the URL being processed was flagged as a "fallback entry" in file - list, then categorise the entry as a fallback + list, then categorize the entry as a fallback entry.
If the URL being processed was flagged as an "master entry" in file - list, then categorise the entry as a master + list, then categorize the entry as a master entry.
As an optimization, if the resource is an HTML or XML file whose document
@@ -85236,7 +85242,7 @@ NETWORK:
Otherwise, store the resource for this entry in new cache, if it isn't
- already there, and categorise its entry as a master
+ already there, and categorize its entry as a master
entry.
Otherwise, store manifest in new cache, if it's not - there already, and categorise its entry as the + there already, and categorize its entry as the manifest.
Let script be a new classic script that this algorithm will - subsequently initialise.
Set script's settings object to the environment settings object provided.
Let script be a new module script that this algorithm will - subsequently initialise.
Set script's settings object to the environment settings object provided.
In this specification, all JavaScript
- realms are initialised with are initialized with global objects that are either Window
or
WorkerGlobalScope
objects.
As such, user agents must instead use the following definition in place of that in the
@@ -87877,19 +87883,19 @@ document.querySelector("button").addEventListener("click", bound);
ErrorEvent
object that does not bubble but is cancelable, and which has the event
name error
.
Initialise event's message
+
Initialize event's message
attribute to message.
Initialise event's Initialize event's filename
attribute to location.
Initialise event's lineno
+
Initialize event's lineno
attribute to line.
Initialise event's colno
+
Initialize event's colno
attribute to col.
Initialise event's error
+
Initialize event's error
attribute to errorValue.
Dispatch event at target.
The message
attribute must return the
- value it was initialised to. It represents the error message.
The filename
attribute must return the
- value it was initialised to. It represents the absolute URL of the script in which
+ 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 initialised to. It represents the line number where the error occurred in 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 initialised to. It represents the column number where the error occurred in the script.
The error
attribute must return the value
- it was initialised to. Where appropriate, it is set to the object representing the error (e.g.,
+ 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).
PromiseRejectionEvent
object that does not bubble but is cancelable, and which
has the event name unhandledrejection
.
- Initialise event's Initialize event's promise
attribute to p.
Initialise event's Initialize event's reason
attribute to the value of
p's [[PromiseResult]] internal slot.
rejectionhandled
.
- Initialise event's Initialize event's promise
attribute to
promise.
Initialise event's Initialize event's reason
attribute to the value of
promise's [[PromiseResult]] internal slot.
The promise
attribute must
- return the value it was initialised to. It represents the promise which this notification is about.
The reason
attribute must
- return the value it was initialised to. It represents the rejection reason for the promise.
screenX
, screenY
, clientX
, clientY
, and button
- attributes initialised to 0, its ctrlKey
, shiftKey
,
- altKey
, and metaKey
attributes initialised according
+ 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 initialised to 1, its relatedTarget
attribute initialised to null (except
+ its detail
attribute initialized to 1, its relatedTarget
attribute initialized to null (except
where otherwise stated), and its view
attribute initialised 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
+ data-x="dom-UIEvent-view">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.
@@ -89473,7 +89479,7 @@ interface WindowOrWorkerGlobalScope {
origin
Returns the global object's origin, serialised as string.
Returns the global object's origin, serialized as string.
The origin
attribute's getter must return this
object's relevant setting object's origin, serialised.
If the repeat flag is true, then call timer initialisation
+ 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. Optionally, wait a further user-agent defined length of time. This is intended to allow user agents to pad timeouts as needed to optimise the
+ 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
@@ -91402,7 +91408,7 @@ interface NavigatorContentUtils {
This site could then fetch the http://example.com/soup?url=http://www.example.net/chickenk%C3%AFwi.soup
chickenkïwi.soup
file and do
- whatever it is that it does with soup (synthesise it and ship it to the user, or whatever).
If val is "default
",
- the colour space conversion behavior is implementation-specific, and should be chosen according
- to the colour space that the implementation uses for drawing images onto the canvas.
If val is "none
", output must be decoded
- without performing any colour space conversions. This means that the image decoding algorithm
+ without performing any color space conversions. This means that the image decoding algorithm
must ignore color profile metadata embedded in the source data as well as the display device
color profile.
The native colour space of canvas is currently unspecified, but this is expected +
The native color space of canvas is currently unspecified, but this is expected to change in the future.
@@ -93072,21 +93078,21 @@ dictionary MessageEventInit : EventInit {The data
attribute must return the value
- it was initialised to. It represents the message being sent.
The origin
attribute must return the
- value it was initialised to. It represents, in server-sent events and
+ value it was initialized to. It represents, in server-sent events and
cross-document messaging, the origin of the document that sent the
message (typically the scheme, hostname, and port of the document, but not its path or fragment).
The lastEventId
attribute must
- return the value it was initialised to. It represents, in server-sent events, the
+ return the value it was initialized to. It represents, in server-sent events, the
last event ID string of the event
source.
The source
attribute must return the
- value it was initialised to. It represents, in cross-document messaging, the
+ value it was initialized to. It represents, in cross-document messaging, the
WindowProxy
of the browsing context of the Window
object
from which the message came; and in the connect
events used by MessageEventInit : EventInit {
MessagePort
.
The ports
attribute must return the
- value it was initialised to. It represents, in cross-document messaging and
+ value it was initialized to. It represents, in cross-document messaging and
channel messaging, the MessagePort
array being sent, if any.
The initMessageEvent()
- method must initialise the event in a manner analogous to the similarly-named initEvent()
method.
The url
attribute's getter must return the
- serialisation of this EventSource
+ serialization of this EventSource
object's url.
The withCredentials
attribute
- must return the value to which it was last initialised. When the object is created, it must be
- initialised to false.
The readyState
attribute represents
the state of the connection. It can have the following values:
When a stream is parsed, a data buffer, an event type buffer, and a last event ID buffer must be associated with it. They must be - initialised to the empty string
+ initialized to the empty stringLines must be processed, in the order they are received, as follows:
@@ -93652,11 +93658,11 @@ any-char = %x0000-0009 / %x000B-000C / %x000E-10FFFFCreate an event that uses the MessageEvent
interface, with the event type
message
, which does not bubble, is not cancelable, and has no
default action. The data
attribute must be
- initialised to the value of the data buffer, the origin
attribute must be initialised to the Unicode serialisation of the
+ initialized to the value of the data buffer, the origin
attribute must be initialized to the Unicode serialization of the
origin of the event stream's final URL (i.e. the URL after redirects), and the lastEventId
attribute must be initialised to the
+ data-x="dom-MessageEvent-lastEventId">lastEventId attribute must be initialized to the
last event ID string of the event
source. This event is not trusted.
The url
attribute's getter must return this
WebSocket
object's url, serialised.
The readyState
attribute represents
the state of the connection. It can have the following values:
Initialise event's origin
- attribute to the Unicode serialisation
+
Initialize event's origin
+ attribute to the Unicode serialization
of the origin of the URL that was passed to the WebSocket
object's constructor.
If type indicates that the data is Text, then initialise event's If type indicates that the data is Binary, and If type indicates that the data is Binary, and If type indicates that the data is Text, then initialize event's
", then initialize event's
data
attribute to data.
binaryType
is set to "blob
", then initialise event's blob
", then initialize event's data
attribute to a new Blob
object that
represents data as its raw data. binaryType
is set to "arraybuffer
", then initialise event's
+ data-x="dom-BinaryType-arraybuffer">arraybufferdata
attribute to a new ArrayBuffer
object whose contents are data.
Create a trusted event that uses the
CloseEvent
interface, with the event type close
,
which does not bubble, is not cancelable, has no default action, whose wasClean
attribute is initialised to true if the
+ data-x="dom-CloseEvent-wasClean">wasClean attribute is initialized to true if the
connection closed cleanly and false otherwise, whose code
attribute is initialised to code attribute is initialized to the WebSocket connection close code, and whose reason
attribute is initialised to the result of applying
+ data-x="dom-CloseEvent-reason">reason attribute is initialized to the result of applying
UTF-8 decode without BOM to the WebSocket
connection close reason, and dispatch the event
at the WebSocket
object.
The wasClean
attribute must return the
- value it was initialised to. It represents whether the connection closed cleanly or not.
The code
attribute must return the value
- it was initialised to. It represents the WebSocket connection close code provided by the
+ it was initialized to. It represents the WebSocket connection close code provided by the
server.
The reason
attribute must return the
- value it was initialised to. It represents the WebSocket connection close reason provided by the
+ value it was initialized to. It represents the WebSocket connection close reason provided by the
server.
Create a trusted event e that uses
the MessageEvent
interface, with the event type message
, which does not bubble and is not cancelable. The data
attribute must be initialised to
+ data-x="dom-MessageEvent-data">data attribute must be initialized to
messageClone, the origin
attribute must
- be initialised to the Unicode
- serialisation of incumbentSettings's Unicode
+ serialization of incumbentSettings's origin, the source
attribute must be initialised to the
+ data-x="dom-MessageEvent-source">source attribute must be initialized to the
WindowProxy
object corresponding incumbentSettings's global object (a Window
object), and
- the ports
attribute must be initialised to
+ the ports
attribute must be initialized to
newPorts.
Create an event e that uses the MessageEvent
interface, with the
name message
, which does not bubble and is not
- cancelable. The data
attribute must be initialised to
+ cancelable. The data
attribute must be initialized to
messageClone and the ports
attribute must
- be initialised to newPorts.
Add a task that runs the following steps to the port
@@ -95448,7 +95454,7 @@ interface MessagePort : EventTarget {
-
+
@@ -95569,7 +95575,7 @@ interface MessagePort : EventTarget {
send notifications to each other, for example "hey, the user logged in over here, check your
credentials again".
For elaborate cases, e.g. to manage locking of shared state, to manage synchronisation of +
For elaborate cases, e.g. to manage locking of shared state, to manage synchronization of
resources between a server and multiple local clients, to share a WebSocket
connection with a remote host, and so forth, shared workers are
the most appropriate solution.
Create an event e that uses the MessageEvent
interface, with the
event type message
, which does not bubble and is not
- cancelable. The data
attribute must be initialised
+ cancelable. The data
attribute must be initialized
to StructuredClone(clonedMessage, targetRealm)
- and the origin
attribute must be initialised to
- the Unicode serialisation of
+ and the origin
attribute must be initialized to
+ the Unicode serialization of
sourceSettings's origin.
EXAMPLE workers/primes/worker.js-
The bulk of this code is simply an unoptimised search for a prime number. The The bulk of this code is simply an unoptimized search for a prime number. The
postMessage()
method is used to send a
message back to the page when a prime is found.
MessageEvent
interface, with the name connect
, which
does not bubble, is not cancelable, has no default action, has a data
attribute whose value is initialised to the empty
+ data-x="dom-MessageEvent-data">data attribute whose value is initialized to the empty
string, has a ports
attribute whose value is
- initialised to a new frozen array containing inside port, has a source
attribute whose value is initialised to
+ initialized to a new frozen array containing inside port, has a source
attribute whose value is initialized to
inside port. Queue a task, using the DOM manipulation task
source, to dispatch the event at worker
global scope.
@@ -96893,8 +96899,8 @@ interface SharedWorkerGlobalScope : WorkerGlobalScope {
data-x="dom-ErrorEvent-message">message, filename
, lineno
, colno
,
- attributes initialised appropriately, and with the error
attribute initialised to null, at the
+ attributes initialized appropriately, and with the error
attribute initialized to null, at the
Worker
object associated with the worker. If the event is not canceled, the user
agent must act as if the uncaught runtime script error had occurred in the global scope that the
Worker
object is in, thus repeating the entire runtime script error reporting process
@@ -97308,10 +97314,10 @@ interface SharedWorker : EventTarget {
MessageEvent
interface, with the name connect
, which does not bubble, is not
cancelable, has no default action, has a data
- attribute whose value is initialised to the empty string, has a ports
attribute whose value is initialised to a new
+ attribute whose value is initialized to the empty string, has a ports
attribute whose value is initialized to a new
frozen array containing only the newly created port, and has a source
attribute whose value is initialised to the
+ data-x="dom-MessageEvent-source">source attribute whose value is initialized to the
newly created port. Queue a task, using the DOM manipulation task
source, to dispatch the event at
worker global scope.
@@ -97485,15 +97491,15 @@ interface WorkerLocation {
return the associated WorkerGlobalScope
object's
url, serialised.
+ data-x="concept-url-serializer">serialized.
The origin
attribute's getter must
- return the Unicode serialization of the
+ return the Unicode serialization of the
associated WorkerGlobalScope
object's url's origin.
It returns the Unicode rather than the ASCII serialisation for +
It returns the Unicode rather than the ASCII serialization for
compatibility with MessageEvent
.
The protocol
attribute's getter
@@ -97515,12 +97521,12 @@ interface WorkerLocation {
If url's port is null, return url's host, serialised.
Return url's host, serialised, followed by ":
" and url's port, serialised.
:
" and url's port, serialized.
The hostname
attribute's getter
@@ -97534,7 +97540,7 @@ interface WorkerLocation {
If host is null, return the empty string.
Return host, serialised.
Return host, serialized.
The port
attribute's getter must run
@@ -97548,7 +97554,7 @@ interface WorkerLocation {
If port is null, return the empty string.
Return port, serialised.
Return port, serialized.
The pathname
attribute's getter
@@ -97869,8 +97875,9 @@ interface WindowLocalStorage {
could access that data is running.
When the localStorage
attribute is accessed, the user
- agent must run the following steps, which are known as the Storage
object
- initialisation steps:
Storage
object
+ initialization steps:
If the event is being fired due to an invocation of the setItem()
or removeItem()
methods, the event must have its key
attribute initialised to the name of the key in question,
- its oldValue
attribute initialised to the old
+ data-x="dom-StorageEvent-key">key attribute initialized to the name of the key in question,
+ its oldValue
attribute initialized to the old
value of the key in question, or null if the key is newly added, and its newValue
attribute initialised to the new value of the
+ data-x="dom-StorageEvent-newValue">newValue attribute initialized to the new value of the
key in question, or null if the key was removed.
Otherwise, if the event is being fired due to an invocation of the clear()
method, the event must have its key
, oldValue
,
- and newValue
attributes initialised to null.
newValue
attributes initialized to null.
In addition, the event must have its url
attribute
- initialised to the URL of the document whose
+ initialized to the URL of the document whose
Storage
object was affected; and its storageArea
attribute initialised to the
+ data-x="dom-StorageEvent-storageArea">storageArea attribute initialized to the
Storage
object from the Window
object of the target
Document
that represents the same kind of Storage
area as was affected
(i.e. session or local).
The key
attribute must return the value
- it was initialised to. It represents the key being changed.
The oldValue
attribute must return
- the value it was initialised to. It represents the old value of the key being changed.
The newValue
attribute must return
- the value it was initialised to. It represents the new value of the key being changed.
The url
attribute must return the value
- it was initialised to. It represents the URL of the document whose key changed.
The storageArea
attribute must
- return the value it was initialised to. It represents the Storage
object that was
+ return the value it was initialized to. It represents the Storage
object that was
affected.
User agents may allow sites to access session storage areas in - an unrestricted manner, but require the user to authorise access + an unrestricted manner, but require the user to authorize access to local storage areas.
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 serialised, as discussed in the + declaration">character encoding declarations are to be serialized, as discussed in the section on that topic.
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 serialised using the HTML syntax.
+ syntax rules if the attributes are serialized using the HTML syntax.The text is allowed to end with the string
- "<!
", as in <!--My favourite operators are > and
+ "
<!
", as in <!--My favorite operators are > and
<!-->
.
Authors interested in using SGML tools in their authoring pipeline are encouraged to use XML - tools and the XML serialisation of HTML.
+ tools and the XML serialization of HTML.Let need pragma be null.
Let charset be the null value (which, for the purposes of this - algorithm, is distinct from an unrecognised encoding or the empty string).
Attributes: Get an attribute and its value. If no attribute was sniffed, then jump to the @@ -100347,7 +100354,7 @@ dictionary StorageEventInit : EventInit {
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 behaviour.
@@ -100661,7 +100668,7 @@ dictionary StorageEventInit : EventInit { then added to the stack.In the fragment case, the stack of open elements is
- initialised to contain an html
element that is created as part of that algorithm. (The fragment case skips the
"before html" insertion mode.)
Initialise node to be the current node (the bottommost +
Initialize node to be the current node (the bottommost node of the stack).
If node is the target node, terminate in a match state.
Implementations must act as if they used the following state machine to tokenise HTML. The +
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 behaviour and can consume several + 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.
@@ -100989,7 +100996,7 @@ dictionary StorageEventInit : EventInit { 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 behaviour of certain states depends on the insertion mode and the +
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 @@ -103301,7 +103308,7 @@ dictionary StorageEventInit : EventInit {
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 recognised that practical concerns will likely force user agents to impose nesting
depth constraints.
If element is a resettable element, invoke - its reset algorithm. (This initialises the + its reset algorithm. (This initializes the element's value and checkedness based on the element's attributes.)
Conformance checkers may, based on the values (including presence or lack thereof) of the DOCTYPE token's name, public identifier, or system identifier, switch to a conformance checking - mode for another language (e.g. based on the DOCTYPE token a conformance checker could recognise + mode for another language (e.g. based on the DOCTYPE token a conformance checker could recognize that the document is an HTML4-era document, and defer to an HTML4 conformance checker.)
Append a DocumentType
node to the Document
node, with the node document, and if that is successful, run the application cache selection algorithm passing the
Document
object with the result of applying the URL serialiser algorithm to the resulting URL
+ data-x="concept-url-serializer">URL serializer algorithm to the resulting URL
record with the exclude fragment flag set.
Otherwise, run the application cache selection
@@ -104946,7 +104953,7 @@ document.body.appendChild(text);
Set the frameset-ok flag to "not ok". Initialise node to be the current
+ Initialize node to be the current
node (the bottommost node of the stack). Set the frameset-ok flag to "not ok". Initialise node to be the current
+ Initialize node to be the current
node (the bottommost node of the stack). Insert an HTML element for the token. Initialise node to be the current node (the bottommost
+ Initialize node to be the current node (the bottommost
node of the stack). Loop: If node is an HTML
@@ -107773,7 +107780,7 @@ document.body.appendChild(text);
Initialise node to be the current node (the bottommost
+ Initialize node to be the current node (the bottommost
node of the stack). If node's tag name, converted to ASCII lowercase, is
@@ -107912,7 +107919,7 @@ document.body.appendChild(text);
data-x="concept-event-target-override">target override set to the The following steps form the HTML fragment serialisation algorithm. The algorithm takes as input a DOM
+ The following steps form the HTML fragment serialization algorithm. The algorithm takes as input a DOM
This algorithm serialises the children of the node being serialised, not
+ This algorithm serializes the children of the node being serialized, not
the node itself. Let s be a string, and initialise it to the empty string. Let s be a string, and initialize it to the empty string. If the node is a For each attribute that the element has, append a U+0020 SPACE character, the attribute's serialised name as described below, a
+ data-x="attribute's serialized name">attribute's serialized name as described below An attribute's serialised
- name for the purposes of the previous paragraph must be determined as follows: An attribute's
+ serialized name for the purposes of the previous paragraph must be determined as
+ follows: The attribute's serialised name is the attribute's local name. The attribute's serialized name is the attribute's local name. For attributes on HTML elements set by the HTML
parser or by The attribute's serialised name is the string " The attribute's serialized name is the string " The attribute's serialised name is the string " The attribute's serialized name is the string " The attribute's serialised name is the string " The attribute's serialized name is the string " The attribute's serialised name is the string " The attribute's serialized name is the string " The attribute's serialised name is the attribute's qualified name. 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 serialise an element's attributes in the
+ such that consecutive invocations of this algorithm serialize an element's attributes in the
same order. Append a U+003E GREATER-THAN SIGN character (>).p
element in button scope, then close a p
element.
-
-
@@ -108340,19 +108347,19 @@ document.body.appendChild(text);
- Document
object,
using the PageTransitionEvent
interface, with the persisted
attribute initialised to false. This
+ data-x="dom-PageTransitionEvent-persisted">persisted attribute initialized to false. This
event must not bubble, must not be cancelable, and has no default action.Serialising HTML fragments
+ Serializing HTML fragments
- Element
, Document
, or DocumentFragment
referred to as
the node, and returns a string.
-
template
element, then let the node instead be the template
element's template
contents (a DocumentFragment
node).
@@ -108400,7 +108408,7 @@ document.body.appendChild(text);
Element.setAttribute()
, the local name will be
@@ -108411,39 +108419,39 @@ document.body.appendChild(text);
xml:
" followed
+ xml:
" followed
by the attribute's local name.xmlns
xmlns
".xmlns
xmlns:
"
+ xmlns:
"
followed by the attribute's local name.xlink:
"
+ xlink:
"
followed by the attribute's local name.
If current node is a pre
, textarea
, or
listing
element, and the first child node of the element, if any, is a
Text
node whose character data has as its first character a U+000A LINE FEED
(LF) character, then append a U+000A LINE FEED (LF) character.
Append the value of running the HTML fragment serialisation algorithm on the +
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 @@ -108542,16 +108550,16 @@ document.body.appendChild(text);
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 serialise and reparse step can also be produced by the HTML parser itself, although + a serialize and reparse step can also be produced by the HTML parser itself, although such cases are non-conforming.
For instance, if a textarea
element to which a Comment
- node has been appended is serialised and the output is then reparsed, the comment will end up
+ node has been appended is serialized and the output is then reparsed, the comment will end up
being displayed in the text control. Similarly, if, as a result of DOM manipulation, an element
contains a comment that contains the literal string "-->
", then when
- the result of serialising the element is parsed, the comment will be truncated at that point and
+ 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
@@ -108561,7 +108569,7 @@ document.body.appendChild(text);
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 serialisation of that style
element: if the user enters
+ 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
@@ -108580,7 +108588,7 @@ document.body.appendChild(text);
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 serialised and reparsed, the <form
+ Now, if this tree structure is serialized and reparsed, the
<form
id="inner">
start tag will be ignored, and so the input
element will be
associated with the outer form
element instead.
html
head
body
a
a
table
That is, the a
elements are nested, because the second a
element is
- foster parented. After a serialise-reparse roundtrip, the
+ 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.
The XML fragment serialisation algorithm
- for a Document
or Element
node either returns a fragment of XML that
- represents that node or throws an exception.
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 Document
s, the algorithm must return a string in the form of a document entity, if none of the error cases
@@ -109031,8 +109039,8 @@ document.body.appendChild(text);
error cases below apply.
In both cases, the string returned must be XML namespace-well-formed and must be an isomorphic
- serialisation of all of that node's relevant child nodes, in tree order.
- User agents may adjust prefixes and namespace declarations in the serialisation (and indeed might
+ 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.
For Element
s, if any of the elements in the serialisation are in no namespace, the
+
For Element
s, 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.)
@@ -109062,7 +109070,7 @@ document.body.appendChild(text);
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 serialised, then the +
If any of the following error cases are found in the DOM subtree being serialized, then the
algorithm must throw an "InvalidStateError
" DOMException
instead of returning a string:
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 behaviour by translating from the CSS rules given in this section.
+ 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 @@ -109403,38 +109411,38 @@ html, body { display: block; }
When a body
element has a bgcolor
attribute set, the new value is expected to be parsed using the rules for parsing a legacy
- colour value, and if that does not return an error, the user agent is expected to treat the
+ 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 colour.
When a body
element has a text
attribute, its
- value is expected to be parsed using the rules for parsing a legacy colour value, and
+ 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 colour.
When a body
element has a link
attribute, its
- value is expected to be parsed using the rules for parsing a legacy colour value, and
+ 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 colour.
When a body
element has a vlink
attribute,
- its value is expected to be parsed using the rules for parsing a legacy colour value,
+ 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 colour.
When a body
element has an alink
attribute,
- its value is expected to be parsed using the rules for parsing a legacy colour value,
+ 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 colour.
When a particular part of a ruby has more than one annotation, the annotations should be - distributed on both sides of the base text so as to minimise the stacking of ruby annotations on + distributed on both sides of the base text so as to minimize the stacking of ruby annotations on one side.
When it becomes possible to do so, the preceding requirement will be updated to be @@ -109612,10 +109620,10 @@ br[clear=all i], br[clear=both i] { clear: both; }
When a font
element has a color
- attribute, its value is expected to be parsed using the rules for parsing a legacy colour
+ 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 colour.
The font
element is expected to
override the color of any text decoration that spans the text of the element to the
@@ -110230,17 +110238,17 @@ table {
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
- colour value, and if that does not return an error, the user agent is expected to treat the
+ 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 colour.
When a table
element has a bordercolor
- attribute, its value is expected to be parsed using the rules for parsing a legacy colour
+ 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 colour.
When an hr
element has a color
attribute, its
- value is expected to be parsed using the rules for parsing a legacy colour value, and
+ 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 colour.
All animated images with the same absolute URL and the same image data are - expected to be rendered synchronised to the same timeline as a group, with the timeline starting + 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.
In other words, when a second image with the same absolute URL and @@ -110915,16 +110923,17 @@ details[open] > summary {
input
element as a colour wellinput
element as a color
+ wellAn input
element whose type
attribute is in
- the Colour state is expected to render as an
- 'inline-block' box depicting a colour well, which, when activated, provides the user
- with a colour picker (e.g. a colour wheel or colour palette) from which the colour can be
+ the Color state 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 colour picker interface, not on the colour well
+ attribute) are expected to be shown in the color picker interface, not on the color well
itself.
When a marquee
element has a bgcolor
- attribute set, the value is expected to be parsed using the rules for parsing a legacy colour
+ 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 colour.
The width
and height
attributes on a marquee
element
@@ -111429,11 +111438,11 @@ details[open] > summary {
If the frameset
element has a border, draw an outer set of borders
- around the rectangles, using the element's frame border colour.
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 colour.
+ element's frame border color.For each (visible) border that does not abut a rectangle that is assigned a
frame
element with a noresize
@@ -111462,17 +111471,18 @@ details[open] > summary {
-
The frame border colour of a frameset
or
- frame
element is the colour obtained from the following algorithm:
The frame border color of a
+ frameset
or frame
element is the color obtained from the following
+ algorithm:
If the element has a bordercolor
attribute, and applying the
- rules for parsing a legacy colour value to that attribute's value does not result
- in an error, then return the colour so obtained.
Otherwise, if the element has a parent element that is a frameset
element,
- then return the frame border colour of that element.
Otherwise, return gray.
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 behaviour of U+000A LINE FEED (LF)
+ 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.
The following features must be categorised as described +
The following features must be categorized as described above:
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 behaviours: use +
When used for triggering specific user agent behaviors: use
a link
element instead.
version
on html
elementsRepeat the object
element completely each time the resource is to be reused.
standby
on object
elementsOptimise the linked resource so that it loads quickly or, at least, incrementally.
Optimize the linked resource so that it loads quickly or, at least, incrementally.
type
on param
elementsvaluetype
on param
elementsUser 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 behaviour for this element, though.)
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 behaviour for
+ elements in terms of semantics and for purposes of rendering. (The parser has special behavior for
this element though.)
The object returned for all
has several unusual
- behaviours:
click
MouseEvent
close
@@ -118909,7 +118919,7 @@ INSERT INTERFACES HERE