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 @@
-

Serialisability of script execution

+

Serializability of script execution

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.

@@ -801,7 +801,7 @@
The HTML syntax
The XHTML syntax
-
All of these features would be for naught if they couldn't be represented in a serialised +
All of these features would be for naught if they couldn't be represented in a serialized form and sent to other people, and so these sections define the syntaxes of HTML and XHTML, along with rules for how to parse content using those syntaxes.
@@ -936,7 +936,7 @@ device, or from network to network, their IP address will change; similarly, NAT routing, proxy servers, and shared computers enable packets that appear to all come from a single IP address to actually map to multiple users. Technologies such as onion routing can be used to further - anonymise requests so that requests from a single user at one node on the Internet appear to come + anonymize requests so that requests from a single user at one node on the Internet appear to come from many disparate parts of the network.

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 d

It 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.

@@ -1448,7 +1448,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
-
Unintuitive error-handling behaviour
+
Unintuitive error-handling behavior
@@ -1478,14 +1478,14 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
-
Errors where the error-handling behaviour is not compatible with streaming user agents
+
Errors where the error-handling behavior is not compatible with streaming user agents
-

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.

@@ -1592,7 +1592,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

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.

@@ -1738,7 +1738,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
-

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 d

Another 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.

@@ -1859,16 +1859,16 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

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.

+ intended to keep the two synchronized.

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.

@@ -1985,7 +1985,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

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.

@@ -2026,7 +2026,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d -

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 whose isTrusted attribute is - initialised to true.

+ initialized to true.

Plugins

@@ -2418,12 +2418,12 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

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.

@@ -2572,7 +2572,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

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

  • An HTTP(S) scheme
  • A network scheme
  • A fetch scheme -
  • The URL serialiser +
  • The URL serializer
  • The host parser -
  • The host serialiser +
  • The host serializer
  • Host equals
  • URL equals -
  • serialise an integer +
  • serialize an integer
  • Default encode set
  • UTF-8 percent encode
  • Percent decode @@ -3232,8 +3232,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d data-x="">click" or "if the event name is 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
      • @@ -3387,8 +3387,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

      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.

      @@ -3505,7 +3505,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

        -
      • named colour
        • +
      • named color
      • <color>
      • The 'color' property
      @@ -3646,7 +3646,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
    • CSS style sheet set name
    • preferred CSS style sheet set name
    • change the preferred CSS style sheet set name
      • -
    • Serialising a CSS value
      • +
    • Serializing a CSS value
    • run the resize steps
    • run the scroll steps
    • evaluate media queries and report changes
      • @@ -4097,8 +4097,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
        -

      • 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.

      • @@ -4181,7 +4181,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

        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 d

        This 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.)

        @@ -4375,8 +4375,8 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

        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 d

        The 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.

          @@ -5019,7 +5019,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

          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.

            @@ -5618,9 +5618,9 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
          -

          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:

            @@ -6531,28 +6531,28 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d -

            Colours

            +

            Colors

            -

            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.

            + either a simple color or an error.

              @@ -6567,7 +6567,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

            1. If the last six characters of input are not all ASCII hex digits, then return an error.

              2. -

            2. Let result be a simple colour.

              +

            3. Let result be a simple color.

            4. 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 d
            -

            The 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:

              @@ -6595,17 +6596,17 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d result, in the order red, green, blue.

            1. Return result, which will be a valid lowercase simple - colour.

              2. + color.

            -

            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.

              @@ -6621,12 +6622,12 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

            1. 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.

              2. @@ -6637,7 +6638,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
                -

              1. Let result be a simple colour.

                +

              2. Let result be a simple color.

              3. 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 d

              4. If length is still greater than two, truncate each component, leaving only the first two characters in each.

                5. -

              5. Let result be a simple colour.

                +

              6. Let result be a simple color.

              7. Interpret the first component as a hexadecimal number; let the red component of result be the resulting number.

                8. @@ -6699,7 +6700,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

                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 d

              8. If urlRecord is failure, then abort these steps with an error.

              9. Let urlString be the result of applying the URL serialiser to urlRecord.

                10. + data-x="concept-url-serializer">URL serializer to urlRecord.

              10. Return urlString as the resulting URL string and urlRecord as the resulting URL record.

                11. @@ -7380,7 +7381,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, 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.

                + initialized to null.

            @@ -9475,12 +9476,12 @@ partial interface Document { being syntactically correct, because the data placed in the cells is clearly not tabular data, and the 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);
          1. Text
      -

      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.

      + behavior 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.

      @@ -11171,7 +11172,7 @@ Transport Protocol">HTTP</abbr> today.</p> @@ -13076,7 +13077,7 @@ interface HTMLMetaElement : HTMLElement {

      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.

      @@ -13389,9 +13390,9 @@ interface HTMLMetaElement : HTMLElement {

      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 meta element with its name attribute set to the value HTMLMetaElement : HTMLElement {

      -

      This standard itself uses "WHATWG green" as its theme colour:

      +

      This standard itself uses "WHATWG green" as its theme color:

      <!DOCTYPE HTML>
 <title>HTML Standard</title>
@@ -13410,7 +13411,7 @@ interface HTMLMetaElement : HTMLElement {
 
     
      
 
-     
      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:
      
 
      
        
       
      1. 
@@ -13435,11 +13436,11 @@ interface HTMLMetaElement : HTMLElement {
         element's content attribute.
        2. 
 
         
      2. If value can be parsed as a CSS <color> value, return
-        the parsed colour.
        3. 
+        the parsed color.
        
        
      
       
 
-      
    • If this step is reached, the page has no theme colour.
      • 
+      
    • If this step is reached, the page has no theme color.
      • 
      
 
      
      If any meta elements are WHATWG Wiki PragmaExtensions page. 
      
 
   
      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.
 
    
    • The character encoding name given must be an ASCII case-insensitive match for
    one of the labels of the character
-   encoding used to serialise the file. 
      • 
+   encoding used to serialize the file. 
 
-   
    • The character encoding declaration must be serialised without the use of The character encoding declaration must be serialized without the use of character references or character escapes of any kind.
      • 
 
    
    • The element containing the character encoding
-   declaration must be serialised completely within the first 1024 bytes of the
+   declaration must be serialized completely within the first 1024 bytes of the
    document.
      •
    @@ -14338,8 +14339,8 @@ c-end = "-->" @@ -14443,7 +14444,7 @@ c-end = "-->"

    Left at its default value.

    CSS rules
    -

    Left uninitialised.

    +

    Left uninitialized.

    • @@ -14547,10 +14548,10 @@ c-end = "-->"

    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.

    @@ -14883,7 +14884,7 @@ interface HTMLBodyElement : HTMLElement {};

    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.)

    + sometimes used to minimize the amount of inter-element whitespace.)

    <!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.)

    -

  • 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.

  • @@ -16207,7 +16208,7 @@ Space is not the only void section.

  • 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.

    • @@ -16261,7 +16262,7 @@ Space is not the only void element.

  • 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.

    • @@ -17123,7 +17124,7 @@ To move the error from the markup to the rhyming.</p>

    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.

    @@ -18009,7 +18010,7 @@ interface HTMLDListElement : HTMLElement {}; 
    <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.

    -

    The activation behaviour of a elements that create The activation behavior of a elements that create hyperlinks is to run the following steps:

      @@ -18797,7 +18798,7 @@ interface HTMLAnchorElement : HTMLElement { 
      <p>Cats are <em>cute</em> animals.</p>

      Similarly, if someone asserted that cats were vegetables, someone correcting this might - emphasise the last word:

      + emphasize the last word:

      <p>Cats are cute <em>animals</em>.</p>
      @@ -19696,7 +19697,7 @@ this specification: the <abbr>WHATWG</abbr> and the Segments are described in terms of DOM ranges; annotation segment ranges always consist of exactly one element.

      -

      At any particular time, the segmentation and categorisation of content of a ruby +

      At any particular time, the segmentation and categorization of content of a ruby element is the result that would be obtained from running the following algorithm:

        @@ -21003,10 +21004,10 @@ brighter. A <b>rat</b> scurries past the corner wall.</p> particular part of a quotation:

        <p lang="en-US">Consider the following quote:</p>
-<blockquote lang="en-GB">
+<blockquote lang="en-GB">
  <p>Look around and you will find, no-one's really
- <mark>colour</mark> blind.</p>
-</blockquote>
+ <mark>colour</mark> blind.</p>
+</blockquote>
 <p lang="en-US">As we can tell from the <em>spelling</em> of the word,
 the person writing this quote is clearly not American.</p>
        @@ -21072,7 +21073,7 @@ end.</code></pre> <p>Did you notice the subtle joke in the joke on panel 4?</p> <blockquote> <p class="bubble">I didn't <em>want</em> to believe. <mark>Of course - on some level I realised it was a known-plaintext attack.</mark> But I + on some level I realized it was a known-plaintext attack.</mark> But I couldn't admit it until I saw for myself.</p> </blockquote> <p>(Emphasis mine.) I thought that was great. It's so pedantic, yet it @@ -21241,7 +21242,7 @@ interface HTMLSpanElement : HTMLElement {};

        In this example, a code fragment is marked up using span elements and class attributes so that its keywords and identifiers can be - colour-coded from CSS:

        + color-coded from CSS:

        @@ -21588,7 +21589,7 @@ document.body.appendChild(wbr); context that will be used. User agents use this name when following hyperlinks.

        -

        When an a or area element's activation behaviour is +

        When an a or area element's activation behavior is invoked, the user agent may allow the user to indicate a preference regarding whether the hyperlink is to be used for navigation or whether the resource it specifies is to be downloaded.

        @@ -21642,7 +21643,7 @@ document.body.appendChild(wbr); tokens.

        The rel attribute has no default value. If the - attribute is omitted or if none of the values in the attribute are recognised by the user agent, + attribute is omitted or if none of the values in the attribute are recognized by the user agent, then the document has no particular relationship with the destination resource other than there being a hyperlink between the two.

        @@ -21785,8 +21786,9 @@ interface HTMLHyperlinkElementUtils { parsing them involves the StructuredClone abstract operation.

        -

        An element implementing the HTMLHyperlinkElementUtils mixin has an associated reinitialise url algorithm, which runs these steps:

        +

        An element implementing the HTMLHyperlinkElementUtils mixin has an associated + reinitialize url algorithm, which + runs these steps:

        1. If element's url is non-null, its HTMLHyperlinkElementUtils {

          To update href, set the element's href content attribute's value to the element's url, serialised.

          + data-x="concept-url-serializer">serialized.

          @@ -21807,7 +21809,7 @@ interface HTMLHyperlinkElementUtils { steps:

            -

          1. Reinitialise url.

            2. +

          2. Reinitialize url.

          3. Let url be this element's url.

            4. @@ -21818,7 +21820,7 @@ interface HTMLHyperlinkElementUtils {

          4. Otherwise, if url is null, return this element's href content attribute's value.

            5. -

          5. Return url, serialised.

            6. +

          6. Return url, serialized.

          The href attribute's setter must set this element's @@ -21828,24 +21830,24 @@ interface HTMLHyperlinkElementUtils { these steps:

            -

          1. Reinitialise url.

            2. +

          2. Reinitialize url.

          3. If this element's url is null, return the empty string.

            4. -

          4. Return the Unicode serialization +

          5. Return the Unicode serialization of this element'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 these steps:

            -

          1. Reinitialise url.

            2. +

          2. Reinitialize url.

          3. If this element's url is null, return ":".

            4. @@ -21858,7 +21860,7 @@ interface HTMLHyperlinkElementUtils { steps:

              -

            1. Reinitialise url.

              2. +

            2. Reinitialize url.

            3. If this element's url is null, terminate these steps.

              4. @@ -21874,7 +21876,7 @@ interface HTMLHyperlinkElementUtils { run these steps:

                -

              1. Reinitialise url.

                2. +

              2. Reinitialize url.

              3. If this element's url is null, return the empty string.

                4. @@ -21887,7 +21889,7 @@ interface HTMLHyperlinkElementUtils { steps:

                  -

                1. Reinitialise url.

                  2. +

                2. Reinitialize url.

                3. Let url be this element's url.

                  4. @@ -21905,7 +21907,7 @@ interface HTMLHyperlinkElementUtils { run these steps:

                    -

                  1. Reinitialise url.

                    2. +

                  2. Reinitialize url.

                  3. Let url be this element's url.

                    4. @@ -21920,7 +21922,7 @@ interface HTMLHyperlinkElementUtils { steps:

                      -

                    1. Reinitialise url.

                      2. +

                    2. Reinitialize url.

                    3. Let url be this element's url.

                      4. @@ -21938,7 +21940,7 @@ interface HTMLHyperlinkElementUtils { steps:

                        -

                      1. Reinitialise url.

                        2. +

                      2. Reinitialize url.

                      3. Let url be this element's url.

                        4. @@ -21948,18 +21950,18 @@ interface HTMLHyperlinkElementUtils {

                      4. If url's port is null, return url's host, serialised.

                        5. + serializer">serialized.

                      5. Return url's host, serialised, followed by ":" and url's port, serialised.

                        6. + serializer">serialized, followed by ":" and url's port, serialized.

                      The host attribute's setter must run these steps:

                        -

                      1. Reinitialise url.

                        2. +

                      2. Reinitialize url.

                      3. Let url be this element's url.

                        4. @@ -21978,7 +21980,7 @@ interface HTMLHyperlinkElementUtils { run these steps:

                          -

                        1. Reinitialise url.

                          2. +

                        2. Reinitialize url.

                        3. Let url be this element's url.

                          4. @@ -21987,14 +21989,14 @@ interface HTMLHyperlinkElementUtils { return the empty string.

                        4. Return url's host, serialised.

                          5. + serializer">serialized.

                        The hostname attribute's setter must run these steps:

                          -

                        1. Reinitialise url.

                          2. +

                        2. Reinitialize url.

                        3. Let url be this element's url.

                          4. @@ -22013,7 +22015,7 @@ interface HTMLHyperlinkElementUtils { steps:

                            -

                          1. Reinitialise url.

                            2. +

                          2. Reinitialize url.

                          3. Let url be this element's url.

                            4. @@ -22022,13 +22024,13 @@ interface HTMLHyperlinkElementUtils { return the empty string.

                          4. Return url's port, serialised.

                            5. + data-x="serialize an integer">serialized.

                          The port attribute's setter must run these steps:

                            -

                          1. Reinitialise url.

                            2. +

                          2. Reinitialize url.

                          3. Let url be this element's url.

                            4. @@ -22049,7 +22051,7 @@ interface HTMLHyperlinkElementUtils { run these steps:

                              -

                            1. Reinitialise url.

                              2. +

                            2. Reinitialize url.

                            3. Let url be this element's url.

                              4. @@ -22068,7 +22070,7 @@ interface HTMLHyperlinkElementUtils { steps:

                                -

                              1. Reinitialise url.

                                2. +

                              2. Reinitialize url.

                              3. Let url be this element's url.

                                4. @@ -22090,7 +22092,7 @@ interface HTMLHyperlinkElementUtils { these steps:

                                  -

                                1. Reinitialise url.

                                  2. +

                                2. Reinitialize url.

                                3. Let url be this element's url.

                                  4. @@ -22107,7 +22109,7 @@ interface HTMLHyperlinkElementUtils { steps:

                                    -

                                  1. Reinitialise url.

                                    2. +

                                  2. Reinitialize url.

                                  3. Let url be this element's url.

                                    4. @@ -22141,7 +22143,7 @@ interface HTMLHyperlinkElementUtils { steps:

                                      -

                                    1. Reinitialise url.

                                      2. +

                                    2. Reinitialize url.

                                    3. Let url be this element's url.

                                      4. @@ -22157,7 +22159,7 @@ interface HTMLHyperlinkElementUtils {

                                      The hash attribute's setter must run these steps:

                                        -

                                      1. Reinitialise url.

                                        2. +

                                      2. Reinitialize url.

                                      3. Let url be this element's url.

                                        4. @@ -22564,7 +22566,7 @@ interface HTMLHyperlinkElementUtils {

                                        This may be done in parallel with the primary fetch, and is independent of the result of that fetch.

                                        -

                                        User agents should allow the user to adjust this behaviour, for example in conjunction with a +

                                        User agents should allow the user to adjust this behavior, for example in conjunction with a setting that disables the sending of HTTP `Referer` (sic) headers. Based on the user's preferences, UAs may either ignore the ping attribute altogether, or selectively ignore URLs in the @@ -22601,7 +22603,7 @@ interface HTMLHyperlinkElementUtils {

                                      4. It allows the user to disable the notifications without losing the underlying link functionality.
                                        5. -
                                      5. It allows the UA to optimise the use of available network bandwidth so that the target page +
                                      6. It allows the UA to optimize the use of available network bandwidth so that the target page loads faster.
                                        7. @@ -23336,10 +23338,10 @@ interface HTMLHyperlinkElementUtils { data-x="concept-request-referrer">referrer to "no-referrer".

                                        For historical reasons, the noreferrer - keyword implies the behaviour associated with the noopener + keyword implies the behavior associated with the noopener keyword when present on a hyperlink that creates a new browsing context. That is, <a - href="..." rel="noreferrer" target="_blank"> has the same behaviour as has the same behavior as <a href="..." rel="noreferrer noopener" target="_blank">.

                                        @@ -23605,7 +23607,7 @@ interface HTMLHyperlinkElementUtils {

                                        Left at its default value.

                                        CSS rules
                                        -

                                        Left uninitialised.

                                        +

                                        Left uninitialized.

                                        @@ -23644,7 +23646,7 @@ interface HTMLHyperlinkElementUtils {

                                        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:

                                        @@ -24201,9 +24203,9 @@ interface HTMLModElement : HTMLElement {

                                        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, ...
                                        
    
                                      7. 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.
                                        8. 
+   optimization will also be disabled.
                                        
 
   
 
@@ -25134,7 +25136,7 @@ interface HTMLSourceElement : HTMLElement {
   
                                        
    
                                        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.
                                        
 
-       
                                      8. Normalise the source densities of source set.
                                        9. 
+       
                                      9. Normalize the source densities of source set.
                                        10. 
 
        
                                      10. Let el's source set be source set.
                                        11. 
 
@@ -26149,7 +26151,7 @@ interface HTMLImageElement : HTMLElement {
      
                                      11. If child has a type attribute, and its
      value is an unknown or unsupported MIME type, continue to the next child.
                                        12. 
 
-     
                                      12. Normalise the source densities of source set.
                                        13. 
+     
                                      13. Normalize the source densities of source set.
                                        14. 
 
      
                                      14. Let el's source set be source set.
                                        15. 
 
@@ -26208,7 +26210,7 @@ interface HTMLImageElement : HTMLElement {
 
     
                                          
 
-     
                                        1. Descriptor tokeniser: Skip whitespace
                                          2. 
+     
                                        2. Descriptor tokenizer: Skip whitespace
                                          3. 
 
      
                                        3. Let current descriptor be the empty string.
                                          4. 
 
@@ -26510,12 +26512,12 @@ interface HTMLImageElement : HTMLElement {
   and protect against simple author errors such as a final trailing comma.
                                          
 
   
                                          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:
                                          
 
   
                                            
 
@@ -26813,7 +26815,7 @@ interface HTMLImageElement : HTMLElement {
   optical character recognition (OCR) of text found within the image.
                                            
 
   
                                            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.
                                            
 
@@ -26842,7 +26844,7 @@ interface HTMLImageElement : HTMLElement {
   with an 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.
                                            
 
@@ -27075,7 +27077,7 @@ the time Maria had stuck her tongue out...</p>
                                        
    
                                        <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>
                                        
 
   
                                        
 
-   
                                        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 the src
   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>
                                        
   
                                        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 alt attribute must be present but must be empty.
                                        
@@ -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.
                                        
 
    
                                        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.

                                        - +

                                      15. 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 the embed 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.)

                                        16. @@ -29293,7 +29295,7 @@ interface HTMLObjectElement : HTMLElement {

                                      16. 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 the object 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.

                                        17. @@ -30247,7 +30249,7 @@ interface HTMLVideoElement : HTMLMediaElement { audio from the media resource, at the current playback position.

                                        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.

                                        @@ -31186,7 +31188,7 @@ interface HTMLMediaElement : HTMLElement { type.

                                        A type that the user agent knows it cannot render is one that describes a resource - that the user agent definitely does not support, for example because it doesn't 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)
                                        -
                                        The element has not yet been initialised. All attributes are in their initial states.
                                        +
                                        The element has not yet been initialized. All attributes are in their initial states.
                                        NETWORK_IDLE (numeric value 1)
                                        @@ -31839,7 +31841,7 @@ interface HTMLMediaElement : HTMLElement {
                                      17. -

                                        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).

                                        @@ -32069,7 +32071,7 @@ interface HTMLMediaElement : HTMLElement { 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 + data-x="dom-TrackEvent-track">track                                         attribute initialized to the new AudioTrack object, at this AudioTrackList object.

                                      @@ -32118,7 +32120,7 @@ interface HTMLMediaElement : HTMLElement { 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 + 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 None - Hints to the user agent that either the author does not expect the user to need the media resource, or that the server wants to minimise unnecessary traffic. + Hints to the user agent that either the author does not expect the user to need the media resource, or that the server wants to minimize unnecessary traffic. This state does not provide a hint regarding how aggressively to actually download the media resource if buffering starts anyway (e.g. once the user hits "play"). 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.

                                    @@ -32740,7 +32742,7 @@ interface HTMLMediaElement : HTMLElement { 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 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.

                                    + video to play, so as to allow the user to override the behavior if so desired.

    @@ -33069,7 +33071,7 @@ interface HTMLMediaElement : HTMLElement {

    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.

    @@ -33370,7 +33372,7 @@ interface HTMLMediaElement : HTMLElement {

    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.

    @@ -33677,7 +33679,7 @@ interface HTMLMediaElement : HTMLElement {

    1. 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.

    2. 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.

      3. @@ -34010,7 +34012,7 @@ interface HTMLMediaElement : HTMLElement {

      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.

      @@ -34022,7 +34024,7 @@ interface HTMLMediaElement : HTMLElement { value (which would equal the time of the last frame, and might be positive Infinity).

      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) - No explicit kind, or the kind given by the track's metadata is not recognised by the user agent. + No explicit kind, or the kind given by the track's metadata is not recognized by the user agent. Audio and video. @@ -34920,7 +34922,7 @@ interface VideoTrack { some legacy formats can be found in the Sourcing In-band Media Resource Tracks from Media Containers into HTML specification.

      -

      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 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.

      @@ -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.

      @@ -36497,9 +36499,10 @@ red:89 if called with an index argument greater than or equal to the number of ranges represented by the 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:

    @@ -42219,9 +42222,9 @@ interface HTMLInputElement : HTMLElement { A slider control or similar color - Colour - An sRGB colour with 8-bit red, green, and blue components - A colour picker + Color + An sRGB color with 8-bit red, green, and blue components + A color picker checkbox Checkbox @@ -42308,7 +42311,7 @@ interface HTMLInputElement : HTMLElement { 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 { Local Date and Time Number Range - Colour + Color Checkbox, Radio Button File Upload @@ -42364,7 +42367,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · Yes @@ -42388,7 +42391,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42412,7 +42415,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes Yes - Yes + Yes · · @@ -42436,7 +42439,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · Yes · @@ -42460,7 +42463,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42484,7 +42487,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42508,7 +42511,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42532,7 +42535,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42556,7 +42559,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42580,7 +42583,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42604,7 +42607,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42628,7 +42631,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42652,7 +42655,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes Yes - Yes + Yes · · @@ -42676,7 +42679,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes Yes - · + · · · @@ -42700,7 +42703,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42724,7 +42727,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes Yes - · + · · · @@ -42748,7 +42751,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42772,7 +42775,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · Yes @@ -42796,7 +42799,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42820,7 +42823,7 @@ interface HTMLInputElement : HTMLElement { · Yes · - · + · · · @@ -42844,7 +42847,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes · - · + · · · @@ -42868,7 +42871,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes · - · + · Yes Yes @@ -42892,7 +42895,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42916,7 +42919,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42940,7 +42943,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes Yes - · + · · · @@ -42964,7 +42967,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -42992,7 +42995,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · Yes · @@ -43016,7 +43019,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · Yes @@ -43040,7 +43043,7 @@ interface HTMLInputElement : HTMLElement { value value value - value + value default/on filename @@ -43064,7 +43067,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -43088,7 +43091,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes Yes - · + · · · @@ -43112,7 +43115,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes Yes - Yes + Yes · · @@ -43136,7 +43139,7 @@ interface HTMLInputElement : HTMLElement { Yes† Yes† · - Yes† + Yes† · Yes† @@ -43160,7 +43163,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -43184,7 +43187,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -43208,7 +43211,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -43232,7 +43235,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -43256,7 +43259,7 @@ interface HTMLInputElement : HTMLElement { · · · - · + · · · @@ -43280,7 +43283,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes Yes - · + · · · @@ -43304,7 +43307,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes Yes - · + · · · @@ -43332,7 +43335,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes Yes - Yes + Yes Yes Yes @@ -43356,7 +43359,7 @@ interface HTMLInputElement : HTMLElement { Yes Yes Yes - Yes + Yes Yes Yes @@ -43468,8 +43471,8 @@ interface 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.

    @@ -43519,7 +43522,7 @@ interface HTMLInputElement : HTMLElement { data-x="dom-input-value-filename">filename mode, then set the value of the element to the empty string.

    -

  • 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.)

    • @@ -43540,7 +43543,7 @@ interface HTMLInputElement : HTMLElement { The 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.

    @@ -44156,7 +44159,7 @@ interface HTMLInputElement : HTMLElement { data-x="concept-fe-value">values.

    + necessarily want to remove from the UI but that we do want to remove before serializing. -->

  • Strip leading and trailing whitespace from each value in latest values.

    • @@ -45052,14 +45055,14 @@ ldh-str = < as defined in     value, as obtained by parsing a date and time from it. User agents must not allow the user to set the value to a non-empty string that is not a valid - normalised local date and time string. If the user agent provides a user interface for + normalized local date and time string. If the user agent provides a user interface for selecting a local date and time, then the value must be set to a valid normalised local date and time + data-x="concept-fe-value">value must be set to a valid normalized local date and time string representing the user's selection. User agents should allow the user to set the value to the empty string.

    Constraint validation: While the user interface describes input that the user - agent cannot convert to a valid 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.

    @@ -45077,7 +45080,7 @@ ldh-str = < as defined in value of the element is a valid local date and time - string, then set it to a valid normalised local date and time string + string, then set it to a valid normalized local date and time string representing the same date and time; otherwise, set it to the empty string instead.

    @@ -45108,7 +45111,7 @@ ldh-str = < as defined in     algorithm to convert a number to a string, given a number input, is as follows: Return a - valid normalised local date and time string that represents the date and time that is + valid normalized local date and time string that represents the date and time that is input milliseconds after midnight on the morning of 1970-01-01 (the time represented by the value "1970-01-01T00:00:00.0").

    @@ -45476,10 +45479,10 @@ ldh-str = < as defined in     +

    A vertical slider control whose primary color is black and whose background color is beige, with the slider having five tick marks, one long one at each extremity, and three short ones clustered around the midpoint.

    Note how the 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 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)

    When an input element's type attribute is in - the Colour state, the rules in this section apply.

    + the Color state, the rules in this section apply.

    -

    The input element represents a colour well control, for setting the +

    The input element represents a color well control, for setting the element's value to a string representing a simple - colour.

    + color.

    -

    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.

    + have a value that is a valid simple color.

    The value sanitization algorithm is as follows: If the value of the element is a valid simple 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".

    @@ -45753,14 +45756,14 @@ ldh-str = < as defined in     checkedness and the element's 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:

    + activation behavior is to run the following steps:

      @@ -46075,7 +46078,7 @@ ldh-str = < as defined in change at the input element.

      If the element is not mutable, it has no activation - behaviour and the user agent must not allow the user to change the element's selection.

      + behavior and the user agent must not allow the user to change the element's selection.

      Constraint validation: If the element is required and the list of mutable, then the element's - activation behaviour is as follows: if the element has a form owner, + activation behavior is as follows: if the element has a form owner, and the element's node document is fully active, submit the form owner from the input element; otherwise, do nothing.

      If the element is not mutable, it has no activation - behaviour.

      + behavior.

    @@ -46499,7 +46502,7 @@ ldh-str = < as defined in src attribute; if the element is mutable, the user agent should allow the user to select this coordinate, and the element's activation - behaviour is as follows: if the element has a form owner, and the element's + behavior is as follows: if the element has a form owner, and the element's node document is fully active, take the user's selected coordinate, and submit the input element's form owner @@ -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.

    @@ -46677,13 +46680,13 @@ ldh-str = < as defined in mutable, then the element's - activation behaviour, if the element has a form owner and the element's + activation behavior, if the element has a form owner and the element's node document is fully active, is to reset the form owner; otherwise, it is to do nothing.

    If the element is not mutable, it has no activation - 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 a value 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 the input 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:

    + attribute is in one of the following modes, which define its behavior:

    @@ -47993,7 +47996,7 @@ You cannot submit this form when the field is incorrect.
    -
    Common event behaviours
    +
    Common event behaviors

    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.

    @@ -48208,7 +48211,7 @@ interface HTMLButtonElement : HTMLElement { validation.

    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:

    @@ -48250,7 +48253,7 @@ interface HTMLButtonElement : HTMLElement { data-x="concept-events-trusted">trusted event with the name 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:

      @@ -49645,7 +49649,7 @@ interface HTMLTextAreaElement : HTMLElement {

      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.

      @@ -49714,7 +49718,7 @@ interface HTMLTextAreaElement : HTMLElement { The 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.

      @@ -53743,8 +53747,8 @@ MIT Room 32-G524 method must do nothing.

      For instance, in a user agent where <input type=color> is rendered as a colour well with a - picker, as opposed to a text control accepting a hexadecimal colour code, there would be no + data-x="attr-input-type-color"><input type=color> is rendered as a color well with a + picker, as opposed to a text control accepting a hexadecimal color code, there would be no selectable text, and thus calls to the method are ignored.

      @@ -54484,10 +54488,10 @@ control.setSelectionRange(oldStart + prefix.length, oldEnd + prefix.length, oldD element satisfies its constraints, then return the empty string.

      -

    1. Return a suitably localised message that the user agent would show the user if this were +

    2. Return a suitably localized message that the user agent would show the user if this were the only form control with a validity constraint problem. If the user agent would not actually show a textual message in such a situation (e.g., it would show a graphical cue instead), then - return a suitably localised message that expresses (one or more of) the validity constraint(s) + return a suitably localized message that expresses (one or more of) the validity constraint(s) that the control does not satisfy. If the element is a candidate for constraint validation and is suffering from a custom error, then the custom validity error message should be present in the return value.

      3. @@ -54570,12 +54574,12 @@ fur

      If the user agent supports letting the user submit a form implicitly (for example, on some platforms hitting the "enter" key while a text control is focused implicitly submits the form), then doing so for a form whose default button has a defined - activation behaviour must cause the user agent to run synthetic click + activation behavior must cause the user agent to run synthetic click activation steps on that default button.

      Consequently, if the default button is disabled, the form is not submitted when such an implicit - submission mechanism is used. (A button has no activation behaviour when + submission mechanism is used. (A button has no activation behavior when disabled.)

      There are pages on the Web that are only usable if there is a way to implicitly @@ -54750,14 +54754,14 @@ fur

      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 {
 
   
      
 
-  
      The form IDL attribute's behaviour depends on
+  
      The form IDL attribute's behavior depends on
   whether the legend element is in a fieldset element or not. If the
   legend has a fieldset element as its parent, then the form IDL attribute must return the same value as the HTMLLegendElement : HTMLElement {
   email fields might translate that into a value of "awesome@example.com" (without the leading whitespace).
      
 
-  
      To define the behaviour of constraint validation in the face of the input
+  
      To define the behavior of constraint validation in the face of the input
   element's multiple attribute, input elements
   can also have separately defined values.
      
 
@@ -51212,7 +51216,7 @@ interface HTMLLegendElement : HTMLElement {
   element being associated with a form element that is not its ancestor.
      
 
   
      When a form-associated element is created, its form owner must be
-  initialised to null (no owner).
      
+  initialized to null (no owner).
      
 
   
      When a form-associated element is to be associated with a form, its form owner must
@@ -51413,7 +51417,7 @@ interface HTMLLegendElement : HTMLElement {
   
      A form control maxlength attribute,
   controlled by a dirty value flag, declares a limit on the number of characters
   a user can input. The "number of characters" is measured using code-unit length and,
-  in the case of textarea elements, with all line breaks normalised to a single
+  in the case of textarea elements, with all line breaks normalized to a single
   character (as opposed to CRLF pairs).
      
 
   
      If an element has its form control HTMLLegendElement : HTMLElement {
 
   
      In the case of textarea elements, the API value and value
-  differ. In particular, the textarea line break normalisation transformation is
+  differ. In particular, the textarea line break normalization transformation is
   applied before the maximum allowed value length is checked (whereas the
   textarea wrapping transformation is not applied).
      
 
@@ -51450,7 +51454,7 @@ interface HTMLLegendElement : HTMLElement {
   
      A form control minlength attribute,
   controlled by a dirty value flag, declares a lower bound on the number of
   characters a user can input. The "number of characters" is measured using code-unit
-  length and, in the case of textarea elements, with all line breaks normalised
+  length and, in the case of textarea elements, with all line breaks normalized
   to a single character (as opposed to CRLF pairs).
      
 
   
      The minlength attribute does not imply the
@@ -51860,10 +51864,10 @@ interface HTMLLegendElement : HTMLElement {
 
   
      
 
-  
      User agents must recognise all the keywords and corresponding states given below, but need not
+  
      User agents must recognize all the keywords and corresponding states given below, but need not
   support all of the corresponding states. If a keyword's state is not supported, the user agent
   must act as if the keyword instead mapped to the given state's fallback state, as defined below.
-  This fallback behaviour is transitive.
      
+  This fallback behavior is transitive.
      
 
   
      For example, if a user agent with a QWERTY keyboard layout does not support text
   prediction and automatic capitalization, then it could treat the 
       The user agent picks the month from the listed options, either by noticing there are twelve
-      options and picking the 7th, or by recognising that one of the strings (three characters "Jul"
+      options and picking the 7th, or by recognizing that one of the strings (three characters "Jul"
       followed by a newline and a space) is a close match for the name of the month (July) in one of
       the user agent's supported languages, or through some other similar mechanism.
      Mail as body
      -

      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:

        @@ -54798,7 +54802,7 @@ fur
      -

      The behaviours are as follows:

      +

      The behaviors are as follows:

      @@ -55168,12 +55172,12 @@ fur (CRLF) character pair.

      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.

      + normalized.

      @@ -55492,7 +55496,7 @@ interface HTMLDetailsElement : HTMLElement { <dt>Local filename:</dt> <dd>/home/rpausch/raycd.m4v</dd> <dt>Remote filename:</dt> <dd>/var/www/lectures/raycd.m4v</dd> <dt>Duration:</dt> <dd>01:16:27</dd> - <dt>Colour profile:</dt> <dd>SD (6-1-6)</dd> + <dt>Color profile:</dt> <dd>SD (6-1-6)</dd> <dt>Dimensions:</dt> <dd>320×240</dd> </dl> </details> @@ -55517,7 +55521,7 @@ interface HTMLDetailsElement : HTMLElement {

      -

      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.

    @@ -55526,7 +55530,7 @@ interface HTMLDetailsElement : HTMLElement {

    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 {
     a click event, either directly or via the run
     synthetic click activation steps algorithm, then the relatedTarget attribute of that click 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:
    
 
   
    
@@ -55998,7 +56002,7 @@ interface HTMLMenuItemElement : HTMLElement {
 
    
    Otherwise
    
 
-   
    The element's activation behaviour is to do nothing.
    
+   
    The element's activation behavior is to do nothing.
    
 
   
    
 
@@ -56008,7 +56012,7 @@ interface HTMLMenuItemElement : HTMLElement {
   
 
   
    If the element's Disabled State is true
-  (disabled) then the element has no activation behaviour.
    
+  (disabled) then the element has no activation behavior.
    • @@ -56100,7 +56104,7 @@ interface HTMLMenuItemElement : HTMLElement { data-x="concept-events-trusted">trusted event with the name 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.

    @@ -56306,7 +56310,7 @@ dictionary RelatedEventInit : EventInit { true if the element or one of its ancestors is inert, and false otherwise.

    The Action of the command, if the element has a - defined activation 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.

    @@ -56375,7 +56379,7 @@ dictionary RelatedEventInit : EventInit { data-x="concept-fe-disabled">disabled state is set, and false otherwise.

    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.

    @@ -56432,7 +56436,7 @@ dictionary RelatedEventInit : EventInit { data-x="attr-menuitem-disabled">disabled     attribute, and false otherwise.

    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.

    @@ -56515,10 +56519,10 @@ dictionary RelatedEventInit : EventInit {
  • Run the focusing steps for the element.
    • -
  • If the element has a defined activation behaviour, run synthetic click +
  • If the element has a defined activation behavior, run synthetic click activation steps on the element.
    • -
  • Otherwise, if the element does not have a defined activation behaviour, +
  • Otherwise, if the element does not have a defined activation behavior, fire a click event at the element.
    • @@ -56647,7 +56651,7 @@ interface HTMLDialogElement : HTMLElement {

    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.

    + initialized to be empty.

    When an element is added to the pending dialog stack, it must also be added to the top layer. When an element is removed from the pending dialog stack, it @@ -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.

    + being parsed, in this case to initialize the form's output.

    <script>
  function calculate(form) {
@@ -58129,7 +58133,7 @@ o............A....e
     
    If the script is from an external file, or
     the script's type is "module",
     then increment the ignore-destructive-writes counter of the script
-    element's node document. Let neutralised doc be that
+    element's node document. Let neutralized doc be that
     Document.
    
 
    
@@ -58192,7 +58196,7 @@ o............A....e
 
    
  • 
 
-    
    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.
    
 
    
    • 
 
@@ -58278,7 +58282,7 @@ o............A....e
   relevant parameter was 'e4x', and it's gone for now -->
 
   
    For example, types that include the charset parameter will
-  not be recognised as referencing any of the scripting languages listed above.
    
+  not be recognized as referencing any of the scripting languages listed above.
    
 
   
 
@@ -58898,7 +58902,7 @@ interface HTMLTemplateElement : HTMLElement {
 <table>
  <thead>
   <tr>
-   <th>Name <th>Colour <th>Sex <th>Legs
+   <th>Name <th>Color <th>Sex <th>Legs
  <tbody>
   <template id="row">
    <tr><td><td><td><td>
@@ -59210,7 +59214,7 @@ callback BlobCallback = void (Blob? blob);

    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).

    @@ -59387,8 +59391,8 @@ callback BlobCallback = void (Blob? blob); protocol">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.

    • @@ -59424,8 +59428,9 @@ callback BlobCallback = void (Blob? blob);

  • 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.

    • + task source for this task is the + canvas blob serialization task + source.

    @@ -59525,7 +59530,7 @@ interface CanvasImageSmoothing { [NoInterfaceObject] interface CanvasFillStrokeStyles { - // colours and styles (see also the CanvasPathDrawingStyles and CanvasTextDrawingStyles interfaces) + // colors and styles (see also the CanvasPathDrawingStyles and CanvasTextDrawingStyles interfaces) attribute (DOMString or CanvasGradient or CanvasPattern) strokeStyle; // (default black) attribute (DOMString or CanvasGradient or CanvasPattern) fillStyle; // (default black) CanvasGradient createLinearGradient(double x0, double y0, double x1, double y1); @@ -59762,7 +59767,7 @@ interface Path2D {

    A CanvasRenderingContext2D object has an output bitmap that - is initialised when the object is created.

    + is initialized when the object is created.

    The output bitmap has an Path2D {

  • Create a new CanvasRenderingContext2D object.

    • -

  • Initialise its canvas attribute to point to +

  • Initialize its canvas attribute to point to target.

  • Let the new CanvasRenderingContext2D object's output bitmap be @@ -59894,7 +59899,7 @@ interface Path2D { and clear it to fully transparent black.

  • Let canvas be the canvas element to which the rendering - context's canvas attribute was initialised.

    • + context's canvas attribute was initialized.

  • If the numeric value of canvas's width content attribute differs from width, then set canvas's

    The canvas attribute must return the - value it was initialised to when the object was created.

    + value it was initialized to when the object was created.

    @@ -59990,11 +59995,11 @@ context.fillRect(100,0,50,50); // only this square remains -->

    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.

    + "element in question" at the time that the color 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).

    @@ -60687,7 +60692,7 @@ transform. ack Shaun Morris. -->

    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.

    @@ -60716,7 +60721,7 @@ transform. ack Shaun Morris. --> spec=CSSFONTS>

    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).

    @@ -61054,7 +61059,7 @@ transform. ack Shaun Morris. --> set.

    When an object implementing the CanvasPath interface is created, its path must be initialised to zero subpaths.

    + data-x="concept-path">path must be initialized to zero subpaths.

    @@ -61526,7 +61531,7 @@ try {

    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.

    + matrix must be initialized 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.

    @@ -62112,7 +62117,7 @@ try {

    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.

    @@ -62123,7 +62128,7 @@ try { serialization of a color for a color + value is a string, computed as follows: if it has alpha equal to 1.0, then the string is a + lowercase six-digit hex value, prefixed with a "#" character (U+0023 NUMBER SIGN), with the first + two digits representing the red component, the next two digits representing the green component, + and the last two digits representing the blue component, the digits being lowercase ASCII + hex digits. Otherwise, the color value has alpha less than 1.0, and the string is the color value in the CSS 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.

    @@ -62210,11 +62215,11 @@ try { objects implementing the opaque 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.

    @@ -62223,12 +62228,12 @@ try {
    -

    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.

    + the color cannot be parsed.

    @@ -62266,18 +62271,18 @@ try { color cannot be parsed as a CSS <color> value, then a "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.

    + initialized 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.

    • + and the repetition behavior 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.)

    • @@ -62468,7 +62473,7 @@ try {

    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.

    @@ -63081,7 +63086,7 @@ v6DVT (also check for '- -' bits in the part above) --> clipping region, without affecting the actual subpaths. The new clipping region replaces the current clipping region.

    -

    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.

    Color spaces and color correction
    -

    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 ImageBitmapRenderingContextSettings { -

    Serialising bitmaps to a file
    +
    Serializing bitmaps to a file
    -

    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.

    @@ -65618,7 +65623,7 @@ dictionary ImageBitmapRenderingContextSettings {

    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.

    @@ -65697,7 +65702,7 @@ dictionary ImageBitmapRenderingContextSettings { existing platform features (like the elements of HTML) in terms of lower-level author-exposed extensibility points (like custom element definition). Although today there are many limitations on the capabilities of custom elements—both functionally and semantically—that prevent them from - fully explaining the behaviours of HTML's existing elements, we hope to shrink this gap over + fully explaining the behaviors of HTML's existing elements, we hope to shrink this gap over time.

    Creating an autonomous custom element
    @@ -65775,19 +65780,19 @@ document.body.appendChild(flagIcon)

    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, <plastic-button>Click me?</plastic-button> will simply create an HTMLElement with no special - behaviour.

    + behavior.

    If you need to create a type-extended element programmatically, you can use the following form of createElement():

    @@ -65837,7 +65842,7 @@ console.log(plasticButton2.localName); // will output "button" console.log(plasticButton2.getAttribute("is")); // will output "plastic-button"

    Notably, all the of the ways in which 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.

    @@ -65872,7 +65877,7 @@ console.log(plasticButton2.getAttribute("is")); // will output "plastic-button"< data-x="attr-aria-disabled">aria-disabled     to "true" when the button is logically disabled conveys to accessibility technology the button's disabled state.

    -

  • 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 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"<

    Even with this rather-complicated element definition, the element is not a pleasure to use for consumers: it will be continually "sprouting" 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).

    + the consumer to override default behavior).

    In contrast, a simple customized built-in element, as shown in the previous - section, would automatically inherit the semantics and behaviour of the 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.

    @@ -66104,7 +66109,7 @@ console.log(plasticButton2.getAttribute("is")); // will output "plastic-button"<

    After a custom element is created, changing the value of the is attribute does not - change the element's behaviour, as it is saved on the element as its is value.

    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:

    A custom element reactions stack consists of a stack of element queues. Zooming in on a particular queue, we see that it contains a number of elements (in our example, <x-a>, then <x-b>, then <x-c>). Any particular element in the queue then has a custom element reaction queue. Zooming in on the custom element reaction queue, we see that it contains a variety of queued-up reactions (in our example, upgrade, then attribute changed, then another attribute changed, then connected).

    @@ -67207,7 +67212,7 @@ customElements.define("x-foo", class extends HTMLElement {

    The actual frequency of each tag is given using the 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.

    The ul element is used (rather than ol) because the order is not @@ -67771,9 +67776,9 @@ contradict people?

    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.

    @@ -68816,7 +68821,7 @@ Demos:
    product-code
    -
    An integer that names the product in the manufacturer's catalogue.
    +
    An integer that names the product in the manufacturer's catalog.
    name
    A brief description of the product.
    scale
    @@ -71392,7 +71397,7 @@ END:VCARD - +
    last-modified
    @@ -71851,7 +71856,7 @@ END:VCARD

  • Add an entry to result called "items" whose value is the array items.

    • -

  • 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 "e" used, when appropriate, in the @@ -72171,7 +72176,7 @@ END:VCARD

    Activation

    -

    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 click event, as described below.

    @@ -72179,8 +72184,8 @@ END:VCARD

    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.

    @@ -72201,7 +72206,7 @@ END:VCARD

  • Fire a click event at the element. If the run synthetic click activation steps algorithm was invoked because the click() method was invoked, then the isTrusted attribute must be initialised to false.

    • + data-x="dom-event-isTrusted">isTrusted     attribute must be initialized to false.

  • @@ -72267,7 +72272,7 @@ END:VCARD script. The click() method can be used to make the run synthetic click activation steps algorithm happen programmatically.

    -

    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.

    @@ -72276,7 +72281,7 @@ END:VCARD
      -

    1. If target has a defined activation behaviour, then return +

    2. If target has a defined activation behavior, then return target and abort these steps.

    3. 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 click event that was - fired by the steps above leading up to this point.

      + the activation behavior defined for that element, + if any. Activation behaviors can refer to the click event that + was fired by the steps above leading up to this point.

      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 click + processing an activation behavior whose click event was trusted.

      • @@ -72380,7 +72385,7 @@ END:VCARD -
      • Otherwise, if the element's default behaviour +
      • Otherwise, if the element's default behavior is true-by-default, then checking is enabled.
        • -
      • Otherwise, if the element's default behaviour +
      • Otherwise, if the element's default behavior is false-by-default, then checking is disabled.
        • @@ -74417,7 +74422,7 @@ body { display:none } already present when the page was loaded, or that the user did not type, or text in controls that the user has not focused, or in parts of e-mail addresses that the user agent is not confident were misspelt). The forceSpellCheck() method, - when invoked on an element, must override this 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 }

      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 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 {

      The 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.

      @@ -75654,13 +75659,13 @@ dictionary DragEventInit : MouseEventInit {

    4. Let dataTransfer be a newly created DataTransfer object associated with the given drag data store.

      5. -

    5. Set the

      Set the effectAllowed attribute to the drag data store's drag data store allowed effects state.

    6. -

      Set the

      Set the dropEffect attribute to "none" if e is dragstart, drag, DragEventInit : MouseEventInit {

    7. Create a trusted 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">view attribute initialized to window, the detail attribute initialized to zero, the mouse and key + attributes initialized according to the state of the input devices as they would be for user interaction events, the relatedTarget - attribute 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.

      @@ -76553,7 +76558,7 @@ dictionary DragEventInit : MouseEventInit { ✓ Cancelable Protected mode - Based on effectAllowed value + Based on effectAllowed value Reject immediate user selection as potential target element @@ -76586,7 +76591,7 @@ dictionary DragEventInit : MouseEventInit { ✓ Cancelable Protected mode - Based on effectAllowed value + Based on effectAllowed value Reset the current drag operation to "none" @@ -76634,7 +76639,7 @@ dictionary DragEventInit : MouseEventInit { missing value default.

      The true state means the element is draggable; the false state means that it is - not. The auto state uses the default 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 {

    8. If browsingContext has a creator browsing context, then set document's referrer to the serialisation of creator URL.

      9. + data-x="concept-url-serializer">serialization of creator URL.

    9. 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.

      @@ -78176,7 +78181,7 @@ console.assert(iframeWindow.frameElement === null);
      CrossOriginGetOwnPropertyHelper ( O, P )
      -

      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 "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.

        @@ -79383,8 +79388,8 @@ callback FrameRequestCallback = void (DOMHighResTimeStamp
        An opaque origin
        -

        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.

        A tuple origin
        @@ -79498,7 +79503,7 @@ callback FrameRequestCallback = void (DOMHighResTimeStampcreateDocument()         API, etc)
        -

        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:

        1. If origin is an opaque origin, then @@ -79581,21 +79586,21 @@ callback FrameRequestCallback = void (DOMHighResTimeStampport.

        2. -

          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:

          @@ -79608,11 +79613,11 @@ callback FrameRequestCallback = void (DOMHighResTimeStamp

          Append "://" to result.

        1. Append origin's host, serialised, to result.

          2. + data-x="host serializer">serialized, to result.

        2. 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.

        3. Return result.

          4. @@ -79732,7 +79737,7 @@ callback FrameRequestCallback = void (DOMHighResTimeStamp, then return the empty string.

        4. Return effectiveDomain, serialised.

          5. + serializer">serialized.

        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.

        + transitions would otherwise have to involve cross-event-loop synchronization.

        @@ -81071,7 +81076,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O

      1. Let current be current's parent browsing context.

        2. -

      2. Append the Unicode serialisation +

      3. Append the Unicode serialization of current's active document's origin to output as a new value.

        4. @@ -81093,7 +81098,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O completely loaded, or
      4. In the task in which the algorithm is running, an - activation behaviour is currently being processed whose activation behavior is currently being processed whose click event was trusted, or
        5. @@ -81125,7 +81130,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O was created, then the navigation must be done with replacement enabled.

        + shows the IE/Firefox behavior is required here. -->
      @@ -81139,7 +81144,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O "SecurityError" DOMException.

    10. Return this Location object's url, - serialised.

      11. + serialized.

    The href attribute's setter must run these steps:

    @@ -81164,12 +81169,12 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O object's origin, then throw a "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.

    • + serializer">serialized.

  • Return url's host, serialised, followed by ":" and url's port, serialised.

    • + serializer">serialized, followed by ":" and url's port, serialized.

    The host attribute's setter must run these steps:

    @@ -81271,7 +81276,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O

  • Return this Location object's url's host, serialised.

    • + data-x="host serializer">serialized.

    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.

    • + data-x="serialize an integer">serialized.

    The port attribute's setter must run these steps:

    @@ -81809,7 +81814,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O

  • 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:

    @@ -82353,7 +82358,7 @@ State: <OUTPUT NAME=I>1</OUTPUT> <INPUT VALUE="Increment" TYPE=BUTTON O

  • 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 O

  • Fragment loop: Spin the event loop for a user-agent-defined amount of time, as desired by the user agent implementor. (This is intended to allow the user agent to - optimise the user experience in the face of performance concerns.)

    • + optimize the user experience in the face of performance concerns.)

  • If the Document object has no parser, or its parser has stopped parsing, or the user agent has reason to believe the user is no longer @@ -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

    At the time of writing, the XML specification community had not actually yet specified how XML and the DOM interact.

    -

    After the Document is created, the user agent must initialise the +

    After the Document is created, the user agent must initialize the Document object.

    The actual HTTP headers and other metadata, not the headers as mutated or implied by the @@ -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, set its content type to the computed MIME type of the resource (type in the - navigate algorithm), initialise the 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 one be the result of applying the URL serialiser algorithm to urlRecordOne, + data-x="concept-url-serializer">URL serializer algorithm to urlRecordOne, with the exclude fragment flag set.

    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).

    @@ -85141,15 +85147,15 @@ NETWORK:

  • 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.

    • @@ -85275,7 +85281,7 @@ NETWORK:

  • 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.

    • @@ -86848,7 +86854,7 @@ interface NavigatorOnLine {

    1. Let script be a new classic script that this algorithm will - subsequently initialise.

      2. + subsequently initialize.

    2. Set script's settings object to the environment settings object provided.

      3. @@ -86874,7 +86880,7 @@ interface NavigatorOnLine {

      1. Let script be a new module script that this algorithm will - subsequently initialise.

        2. + subsequently initialize.

      2. Set script's settings object to the environment settings object provided.

        3. @@ -87095,7 +87101,7 @@ interface NavigatorOnLine { field of a JavaScript realm.

        In this specification, all JavaScript - realms are initialised with are initialized with global objects that are either Window or WorkerGlobalScope objects.

        @@ -87676,7 +87682,7 @@ document.querySelector("button").addEventListener("click", bound); the many "implementation defined" sections of the algorithm, to contort it to our purposes. However, the end result is a mass of messy indirection and workarounds that essentially bypasses the job queue infrastructure entirely, albeit in a way that is technically sanctioned within the - bounds of implementation-defined behaviour. We do not take this path, and instead introduce the + bounds of implementation-defined behavior. We do not take this path, and instead introduce the following willful violation.

        As such, user agents must instead use the following definition in place of that in the @@ -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.

        -

      3. Initialise event's message +

      4. Initialize event's message attribute to message.

        5. -

      5. Initialise event's

        Initialize event's filename attribute to location.

        6. -

      6. Initialise event's lineno +

      7. Initialize event's lineno attribute to line.

        8. -

      8. Initialise event's colno +

      9. Initialize event's colno attribute to col.

        10. -

      10. Initialise event's error +

      11. Initialize event's error attribute to errorValue.

      12. Dispatch event at target.

        13. @@ -87939,21 +87945,21 @@ dictionary ErrorEventInit : EventInit { };

        The message attribute must return the - value it was initialised to. It represents the error message.

        + value it was initialized 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.

        + it was initialized to. It represents the column number where the error occurred in the script.

        The error attribute must return the value - it was 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).

        Unhandled promise rejections
        @@ -87993,10 +87999,10 @@ dictionary ErrorEventInit : EventInit { PromiseRejectionEvent object that does not bubble but is cancelable, and which has the event name unhandledrejection.

        -

      13. Initialise event's

        Initialize event's promise attribute to p.

        14. -

      14. Initialise event's

        Initialize event's reason attribute to the value of p's [[PromiseResult]] internal slot.

        15. @@ -88077,11 +88083,11 @@ dictionary ErrorEventInit : EventInit { which has the event name rejectionhandled.

        -

      15. Initialise event's

        Initialize event's promise attribute to promise.

        16. -

      16. Initialise event's

        Initialize event's reason attribute to the value of promise's [[PromiseResult]] internal slot.

        17. @@ -88109,10 +88115,10 @@ dictionary PromiseRejectionEventInit : EventInit { };

        The promise attribute must - return the value it was initialised to. It represents the promise which this notification is about.

        + return the value it was initialized to. It represents the promise which this notification is about.

        The reason attribute must - return the value it was initialised to. It represents the rejection reason for the promise.

        + return the value it was initialized to. It represents the rejection reason for the promise.

        HostEnsureCanCompileStrings(callerRealm, calleeRealm)
        @@ -89413,13 +89419,13 @@ interface DocumentAndElementEventHandlers { dispatched at the given target. The event object must have its 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 = self . origin
        -

        Returns the global object's origin, serialised as string.

        +

        Returns the global object's origin, serialized as string.

        @@ -89495,8 +89501,8 @@ document.body.appendChild(frame)

        The origin attribute's getter must return this object's relevant setting object's origin, serialised.

        + data-x="concept-settings-object-origin">origin, serialized.

        Base64 utility methods

        @@ -89557,8 +89563,8 @@ document.body.appendChild(frame)
          - timer initialization steps, which + are invoked with some method arguments, a method context, a repeat flag + which can be true or false, and optionally (and only if the repeat flag is true) a + previous handle, are as follows:

            @@ -90444,7 +90450,7 @@ document.body.appendChild(frame) -

          1. If the repeat flag is true, then call timer initialisation +

          2. 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.

            3. @@ -90521,7 +90527,7 @@ setTimeout({ toString: function () {

            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 { 

            http://example.com/soup?url=http://www.example.net/chickenk%C3%AFwi.soup

            This site could then fetch the chickenkïwi.soup file and do - whatever it is that it does with soup (synthesise it and ship it to the user, or whatever).

            + whatever it is that it does with soup (synthesize it and ship it to the user, or whatever).

        @@ -92783,18 +92789,18 @@ dictionary ImageBitmapOptions {

      17. 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.

        18. + the color space conversion behavior is implementation-specific, and should be chosen according + to the color space that the implementation uses for drawing images onto the canvas.

      18. 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.

      + it was initialized 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.

      @@ -93274,12 +93280,12 @@ dictionary EventSourceInit {

      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.

      + must return the value to which it was last initialized. When the object is created, it must be + initialized to false.

      The readyState attribute represents the state of the connection. It can have the following values:

      @@ -93520,7 +93526,7 @@ any-char = %x0000-0009 / %x000B-000C / %x000E-10FFFF

      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 string

      Lines must be processed, in the order they are received, as follows:

      @@ -93652,11 +93658,11 @@ any-char = %x0000-0009 / %x000B-000C / %x000E-10FFFF

    3. Create 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.

      4. @@ -94015,7 +94021,7 @@ interface WebSocket : EventTarget {

      The url attribute's getter must return this WebSocket object's url, serialised.

      + data-x="concept-url-serializer">serialized.

      The readyState attribute represents the state of the connection. It can have the following values:

      @@ -94393,25 +94399,25 @@ socket.onopen = function () { -

    4. Initialise event's origin - attribute to the Unicode serialisation +

    5. Initialize event's origin + attribute to the Unicode serialization of the origin of the URL that was passed to the WebSocket object's constructor.

    6. -

      If type indicates that the data is Text, then initialise event's If type indicates that the data is Text, then initialize event's data attribute to data.

      If type indicates that the data is Binary, and 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.

      If type indicates that the data is Binary, and binaryType is set to "arraybuffer", then initialise event's + data-x="dom-BinaryType-arraybuffer">arraybuffer", then initialize event's data attribute to a new ArrayBuffer object whose contents are data.

      @@ -94486,11 +94492,11 @@ socket.onopen = function () {

    7. 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.

      8. @@ -94574,14 +94580,14 @@ dictionary CloseEventInit : EventInit { };

      The wasClean attribute must return the - value it was initialised to. It represents whether the connection closed cleanly or not.

      + value it was initialized 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.

      @@ -94871,15 +94877,15 @@ function receiver(e) {

    8. 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.

      9. @@ -95407,9 +95413,9 @@ interface MessagePort : EventTarget {

    9. 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.

      10. + be initialized to newPorts.

    10. 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.

        @@ -95709,11 +95715,11 @@ interface BroadcastChannel : EventTarget {

      1. 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.

        2. @@ -95853,7 +95859,7 @@ function showLogout() { 
        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.

        @@ -96765,10 +96771,10 @@ interface SharedWorkerGlobalScope : WorkerGlobalScope { data-x="concept-events-trusted">trusted event that uses the 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 {

      2. If url's port is null, return url's host, serialised.

        3. + serializer">serialized.

      3. Return url's host, serialised, followed by ":" and url's port, serialised.

        4. + serializer">serialized, followed by ":" and url's port, serialized.

      The hostname attribute's getter @@ -97534,7 +97540,7 @@ interface WorkerLocation {

    11. If host is null, return the empty string.

      12. -

    12. Return host, serialised.

      13. +

    13. 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:

      @@ -97935,21 +97942,21 @@ interface WindowLocalStorage {

      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.

      + and 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).

      @@ -97975,19 +97982,19 @@ dictionary StorageEventInit : EventInit { };

      The key attribute must return the value - it was initialised to. It represents the key being changed.

      + it was initialized 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 value it was initialized 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 value it was initialized 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.

      + it was initialized 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.

      @@ -98078,7 +98085,7 @@ dictionary StorageEventInit : EventInit {
      Site-specific safelisting of access to local storage areas

      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.

      @@ -98221,7 +98228,7 @@ dictionary StorageEventInit : EventInit {

      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.

      @@ -98705,7 +98712,7 @@ dictionary StorageEventInit : EventInit {

      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.

      Optional tags
      @@ -99272,7 +99279,7 @@ dictionary StorageEventInit : EventInit {

    The text is allowed to end with the string - "<!", as in <!--My favourite operators are > and + "<!", as in <!--My favorite operators are > and <!-->.

    @@ -99306,7 +99313,7 @@ dictionary StorageEventInit : EventInit { returns to a non-SGML basis.

    Authors interested in using SGML tools in their authoring pipeline are encouraged to use XML - tools and the XML serialisation of HTML.

    + tools and the XML serialization of HTML.

    @@ -100048,7 +100055,7 @@ dictionary StorageEventInit : EventInit {

  • 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).

    • + algorithm, is distinct from an unrecognized 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.)

    @@ -100741,7 +100748,7 @@ dictionary StorageEventInit : EventInit {
      -

    1. Initialise node to be the current node (the bottommost +

    2. Initialize node to be the current node (the bottommost node of the stack).

    3. If node is the target node, terminate in a match state.

      4. @@ -100976,12 +100983,12 @@ dictionary StorageEventInit : EventInit {

      Tokenization

      -

      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.

      @@ -103507,7 +103514,7 @@ dictionary StorageEventInit : EventInit { XLink Namespace, that is a parse error.

    4. 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.)

      5. @@ -103907,7 +103914,7 @@ document.body.appendChild(text);

      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.

    5. Otherwise, run the application cache selection @@ -104946,7 +104953,7 @@ document.body.appendChild(text);

    6. Set the frameset-ok flag to "not ok".

      7. -

    7. Initialise node to be the current +

    8. Initialize node to be the current node (the bottommost node of the stack).

    9. @@ -105005,7 +105012,7 @@ document.body.appendChild(text);

    10. Set the frameset-ok flag to "not ok".

      11. -

    11. Initialise node to be the current +

    12. Initialize node to be the current node (the bottommost node of the stack).

    13. @@ -105426,7 +105433,7 @@ document.body.appendChild(text); stack of open elements has a p element in button scope, then close a p element.

      Insert an HTML element for the token.

      @@ -105714,7 +105721,7 @@ document.body.appendChild(text); + that is just an optimization, as that detracts from the spec itself --> @@ -105737,7 +105744,7 @@ document.body.appendChild(text);
        -

      1. Initialise node to be the current node (the bottommost +

      2. Initialize node to be the current node (the bottommost node of the stack).

      3. Loop: If node is an HTML @@ -107773,7 +107780,7 @@ document.body.appendChild(text);

          -

        1. Initialise node to be the current node (the bottommost +

        2. Initialize node to be the current node (the bottommost node of the stack).

        3. 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 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.

        @@ -108340,19 +108347,19 @@ document.body.appendChild(text); -

        Serialising HTML fragments

        +

        Serializing HTML fragments

        -

        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 Element, Document, or DocumentFragment referred to as the node, and returns a string.

        -

        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.

          -

        1. Let s be a string, and initialise it to the empty string.

          2. +

        2. Let s be a string, and initialize it to the empty string.

        3. If the node is a template element, then let the node instead be the template element's template contents (a DocumentFragment node).

          4. @@ -108386,13 +108393,14 @@ document.body.appendChild(text); lowercase.

          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, a U+003D EQUALS SIGN character (=), a U+0022 QUOTATION MARK character ("), the attribute's value, escaped as described below in attribute mode, and a second U+0022 QUOTATION MARK character (").

          -

          An attribute's 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:

          @@ -108400,7 +108408,7 @@ document.body.appendChild(text);
          -

          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 Element.setAttribute(), the local name will be @@ -108411,39 +108419,39 @@ document.body.appendChild(text);

          If the attribute is in the XML namespace
          -

          The attribute's serialised name is the string "xml:" followed +

          The attribute's serialized name is the string "xml:" followed by the attribute's local name.

          If the attribute is in the XMLNS namespace and the attribute's local name is xmlns
          -

          The attribute's serialised name is the string "

          The attribute's serialized name is the string "xmlns".

          If the attribute is in the XMLNS namespace and the attribute's local name is not xmlns
          -

          The attribute's serialised name is the string "xmlns:" +

          The attribute's serialized name is the string "xmlns:" followed by the attribute's local name.

          If the attribute is in the XLink namespace
          -

          The attribute's serialised name is the string "xlink:" +

          The attribute's serialized name is the string "xlink:" followed by the attribute's local name.

          If the attribute is in some other namespace
          -

          The attribute's 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 (>).

          @@ -108456,14 +108464,14 @@ document.body.appendChild(text); then continue on to the next child node at this point.

          + more a "macro", and thus we should never serialize it -->

          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.

          @@ -108601,7 +108609,7 @@ document.body.appendChild(text);
          • 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.

          @@ -109016,11 +109024,11 @@ document.body.appendChild(text); -

          Serialising XHTML fragments

          +

          Serializing XHTML fragments

          -

          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 Documents, 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.

          @@ -109052,7 +109060,7 @@ document.body.appendChild(text);
    • -

    For Elements, if any of the elements in the serialisation are in no namespace, the +

    For Elements, if any of the elements in the serialization are in no namespace, the default namespace in scope for those elements must be explicitly declared as the empty string. (This doesn't apply in the Document case.) @@ -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:

    @@ -109196,7 +109204,7 @@ document.body.appendChild(text); section provides a set of suggestions for rendering HTML documents that, if followed, are likely to lead to a user experience that closely resembles the experience intended by the documents' authors. So as to avoid confusion regarding the normativity of this section, RFC2119 terms have - not been used. Instead, the term "expected" is used to indicate behaviour that will lead to this + not been used. Instead, the term "expected" is used to indicate behavior that will lead to this experience. For the purposes of conformance for user agents designated as supporting the suggested default rendering, the term "expected" in this section has the same conformance implications as the RFC2119-defined term "must".

    @@ -109206,7 +109214,7 @@ document.body.appendChild(text);

    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.

    + element's 'background-color' property to the resulting color.

    When a body element has a text attribute, its - value is expected to be parsed using the rules for parsing a legacy 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.

    + 'color' property to the resulting color.

    When a body element has a link attribute, its - value is expected to be parsed using the rules for parsing a legacy 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.

    + pseudo-class to the resulting color.

    When a body element has a vlink attribute, - its value is expected to be parsed using the rules for parsing a legacy 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.

    + data-x="selector-visited">:visited     pseudo-class to the resulting color.

    When a body element has an alink attribute, - its value is expected to be parsed using the rules for parsing a legacy 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.

    + data-x="selector-visited">:visited     pseudo-class to the resulting color.

    @@ -109557,7 +109565,7 @@ area:link[rel~=help i], area:visited[rel~=help i] { cursor: help; } :focus { outline: auto; } -mark { background: yellow; color: black; } /* this colour is just a suggestion and can be changed based on implementation feedback */ +mark { background: yellow; color: black; } /* this color is just a suggestion and can be changed based on implementation feedback */ abbr[title], acronym[title] { text-decoration: dotted underline; } ins, u { text-decoration: underline; } @@ -109587,7 +109595,7 @@ br[clear=all i], br[clear=both i] { clear: both; } spec=CSSRUBY>

    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.

    + element's 'color' property to the resulting color.

    The font element is expected to override the color of any text decoration that spans the text of the element to the @@ -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.

    + 'background-color' property to the resulting color.

    When a table element has a bordercolor - attribute, its value is expected to be parsed using the rules for parsing a legacy 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.

    + resulting color.

    @@ -110383,10 +110391,10 @@ hr[color], hr[noshade] { border-style: solid; } to the dimension property 'width' on the element.

    When an hr element has a color attribute, its - value is expected to be parsed using the rules for parsing a legacy 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.

    + 'color' property to the resulting color.

    @@ -110604,7 +110612,7 @@ iframe { border: 2px inset; }

    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 {

    -

    The input element as a colour well

    +

    The input element as a color + well

    An 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.

    @@ -111103,10 +111112,10 @@ details[open] > summary { given by the marquee scroll distance with each frame.

    When a marquee element has a bgcolor - attribute set, the value is expected to be parsed using the rules for parsing a legacy 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.

    + 'background-color' property to the resulting color.

    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.

    + around the rectangles, using the element's frame border color.

    For each rectangle, if there is an element assigned to that rectangle, and that element has a border, draw an inner set of borders around that rectangle, using the - element's frame border 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:

    1. 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.

      2. + rules for parsing a legacy color value to that attribute's value does not result + in an error, then return the color so obtained.

    2. Otherwise, if the element has a parent element that is a frameset element, - then return the frame border colour of that element.

      + then return the frame border color of that element.

    3. Otherwise, return gray.

      4. @@ -111752,7 +111762,7 @@ details[open] > summary {

      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.

      @@ -111914,7 +111924,7 @@ if (s = prompt('What is your name?')) { distinguish between likely mistakes (regular conformance errors) and mere vestigial markup or unusual and discouraged practices (these warnings).

      -

      The following features must be categorised as described +

      The following features must be categorized as described above:

        @@ -112090,7 +112100,7 @@ if (s = prompt('What is your name?')) {

        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 elements
        @@ -112135,7 +112145,7 @@ if (s = prompt('What is your name?')) {

        Repeat the object element completely each time the resource is to be reused.

        standby on object elements
        -

        Optimise 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 elements
        valuetype on param elements
        @@ -113210,7 +113220,7 @@ interface HTMLFontElement : HTMLElement {

        User agents must treat plaintext elements in a manner equivalent to pre elements in terms of semantics and for purposes of rendering. (The parser has - special behaviour for this element, though.)

        + special behavior for this element, though.)

        @@ -113374,7 +113384,7 @@ interface HTMLFontElement : HTMLElement {

        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.)

        @@ -113446,7 +113456,7 @@ interface HTMLFontElement : HTMLElement { elements.

        The object returned for all has several unusual - behaviours:

        + behaviors:

          @@ -113545,7 +113555,7 @@ interface External { document's character encoding, overriding any character encoding declarations in the document other than a Byte Order Mark (BOM). The parameter's value must be one of the labels of the character encoding used to serialise the file. character encoding used to serialize the file.

          @@ -118400,7 +118410,7 @@ INSERT INTERFACES HERE click MouseEvent Elements - Normally a mouse event; also synthetically fired at an element before its activation behaviour is run, when an element is activated from a non-pointer input device (e.g. a keyboard) + Normally a mouse event; also synthetically fired at an element before its activation behavior is run, when an element is activated from a non-pointer input device (e.g. a keyboard) close @@ -118909,7 +118919,7 @@ INSERT INTERFACES HERE
          UI Events Specification, G. Kacmarcik, T. Leithead. W3C.
          [DOMPARSING]
          -
          DOM Parsing and Serialization, T. Leithead. W3C.
          +
          DOM Parsing and Serialization, T. Leithead. W3C.
          [DOT]
          (Non-normative) The DOT Language. Graphviz.