From 4089e5c2d38c97366f04b8fead62abc96f83611b Mon Sep 17 00:00:00 2001
From: "Michael[tm] Smith" <mike@w3.org>
Date: Tue, 3 Oct 2017 21:42:34 +0900
Subject: [PATCH 1/3] Require UTF-8
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This change adds a “must” requirement for UTF-8 in all but one of the places in
the spec that define a means for specifying a character encoding.

Specifically, it makes UTF-8 required for any “character encoding declaration”,
which includes the HTTP Content-Type header sent with any document, the
`<meta charset>` element, and the `<meta http-equiv=content-type>` element.

Along with those, this change also makes UTF-8 required for `<script charset>`
but also moves `<script charset>` to being obsolete-but-conforming (because now
that both documents and scripts are required to use UTF-8, it’s redundant to
specify `charset` on the `script` element, since it inherits from the document).

To make the normative source of those requirements clear, this change also adds
a specific citation to the relevant requirement from the Encoding standard, and
updates the in-spec IANA registration for text/html media type to indicate that
UTF-8 is required. Finally, it changes an existing requirement for authoring
tools to use UTF-8 from a “should” to a “must”.

The one place where this change doesn’t yet add a requirement for UTF-8 is for
the `form` element’s `accept-charset` attribute. For that, see issue #3097.
---
 source | 165 +++++++++++++++++++++++++--------------------------------
 1 file changed, 71 insertions(+), 94 deletions(-)

diff --git a/source b/source
index 8a4dc573e05..7a2887da57c 100644
--- a/source
+++ b/source
@@ -13646,15 +13646,14 @@ interface <dfn>HTMLMetaElement</dfn> : <span>HTMLElement</span> {
   specified, then the <code data-x="attr-meta-content">content</code> attribute must also be
   specified. Otherwise, it must be omitted.</p>
 
-  <p>The <dfn><code data-x="attr-meta-charset">charset</code></dfn> attribute specifies the character
-  encoding used by the document. This is a <span>character encoding declaration</span>. If the
-  attribute is present in an <span data-x="XML documents">XML document</span>, its value must be an
-  <span>ASCII case-insensitive</span> match for the string "<code data-x="">utf-8</code>" (and the
-  document is therefore forced to use <span>UTF-8</span> as its encoding).</p>
+  <p>The <dfn><code data-x="attr-meta-charset">charset</code></dfn> attribute specifies the <span
+  data-x="encoding">character encoding</span> used by the document. This is a <span>character
+  encoding declaration</span>. If the attribute is present, its value must be an <span>ASCII
+  case-insensitive</span> match for the string "<code data-x="">utf-8</code>".</p>
 
   <p class="note">The <code data-x="attr-meta-charset">charset</code> attribute on the
-  <code>meta</code> element has no effect in XML documents, and is only allowed in order to
-  facilitate migration to and from XML.</p>
+  <code>meta</code> element has no effect in XML documents, but is allowed in XML documents in order
+  to facilitate migration to and from XML.</p>
 
   <p>There must not be more than one <code>meta</code> element with a <code
   data-x="attr-meta-charset">charset</code> attribute per document.</p>
@@ -14299,9 +14298,7 @@ people expect to have work and what is necessary.
     state</span>, the <code data-x="attr-meta-content">content</code> attribute must have a value
     that is an <span>ASCII case-insensitive</span> match for a string that consists of: the literal
     string "<code data-x="">text/html;</code>", optionally followed by any number of <span>ASCII
-    whitespace</span>, followed by the literal string "<code data-x="">charset=</code>", followed by
-    one of the <span data-x="encoding label">labels</span> of the <span data-x="encoding">character
-    encoding</span> of the <span>character encoding declaration</span>.</p>
+    whitespace</span>, followed by the literal string "<code data-x="">charset=utf-8</code>".</p>
 
     <p>A document must not contain both a <code>meta</code> element with an <code
     data-x="attr-meta-http-equiv">http-equiv</code> attribute in the <span
@@ -14731,22 +14728,27 @@ people expect to have work and what is necessary.
   <p>A <dfn>character encoding declaration</dfn> is a mechanism by which the <span
   data-x="encoding">character encoding</span> used to store or transmit a document is specified.</p>
 
-  <p>The following restrictions apply to <span data-x="character encoding declaration">character
-  encoding declarations</span>:</p>
+  <p>The Encoding standard requires use of the <span>UTF-8</span> <span data-x="encoding">character
+  encoding</span> and requires use of the "<code data-x="">utf-8</code>" <span>encoding label</span>
+  to identify it. Those requirements necessitate that the document's <span>character encoding
+  declaration</span>, if it exists, specify an <span>encoding label</span> using an <span>ASCII
+  case-insensitive</span> match for the string "<code data-x="">utf-8</code>". Regardless of whether
+  a <span>character encoding declaration</span> is present or not, the actual <span
+  data-x="document's character encoding">character encoding</span> used to store or transmit the
+  document must be <span>UTF-8</span>. <ref spec=ENCODING></p>
 
-  <ul>
+  <p w-nodev>To enforce the above rules, authoring tools must default to using <span>UTF-8</span>
+  for newly-created documents.</p>
 
-   <li>The character encoding name given must be an <span>ASCII case-insensitive</span> match for
-   one of the <span data-x="encoding label">labels</span> of the <span data-x="encoding">character
-   encoding</span> used to serialize the file. <ref spec=ENCODING></li>
+  <p>The following restrictions also apply:</p>
 
+  <ul>
    <li>The character encoding declaration must be serialized without the use of <span
    data-x="syntax-charref">character references</span> or character escapes of any kind.</li>
 
    <li id="charset1024"><span data-x="" id="charset512">The element containing the character encoding
    declaration must be serialized completely within the first 1024 bytes of the
    document.</span></li> <!-- span is for historical reasons, to keep an old ID alive -->
-
   </ul>
 
   <p>In addition, due to a number of restrictions on <code>meta</code> elements, there can only be
@@ -14759,50 +14761,27 @@ people expect to have work and what is necessary.
   <p>If an <span data-x="HTML documents">HTML document</span> does not start with a BOM, and its
   <span>encoding</span> is not explicitly given by <span data-x="Content-Type">Content-Type
   metadata</span>, and the document is not <span>an <code>iframe</code> <code
-  data-x="attr-iframe-srcdoc">srcdoc</code> document</span>, then the character encoding used must be
-  an <span>ASCII-compatible encoding</span>, and the encoding must be specified using a
-  <code>meta</code> element with a <code data-x="attr-meta-charset">charset</code> attribute or a
-  <code>meta</code> element with an <code data-x="attr-meta-http-equiv">http-equiv</code> attribute
-  in the <span data-x="attr-meta-http-equiv-content-type">Encoding declaration state</span>.</p>
+  data-x="attr-iframe-srcdoc">srcdoc</code> document</span>, then the encoding must be specified
+  using a <code>meta</code> element with a <code data-x="attr-meta-charset">charset</code> attribute
+  or a <code>meta</code> element with an <code data-x="attr-meta-http-equiv">http-equiv</code>
+  attribute in the <span data-x="attr-meta-http-equiv-content-type">Encoding declaration
+  state</span>.</p>
 
-  <p class="note">A character encoding declaration is required (either in the <span
-  data-x="Content-Type">Content-Type metadata</span> or explicitly in the file) even when all
-  characters are in the ASCII range, because a character encoding is needed to process non-ASCII
-  characters entered by the user in forms, in URLs generated by scripts, and so forth.</p>
+  <div class="note">
+   <p>A character encoding declaration is required (either in the <span
+   data-x="Content-Type">Content-Type metadata</span> or explicitly in the file) even when all
+   characters are in the ASCII range, because a character encoding is needed to process non-ASCII
+   characters entered by the user in forms, in URLs generated by scripts, and so forth.</p>
+
+   <p>Using non-UTF-8 encodings can have unexpected results on form submission and URL encodings,
+   which use the <span>document's character encoding</span> by default.</p>
+  </div>
 
   <p>If the document is <span>an <code>iframe</code> <code data-x="attr-iframe-srcdoc">srcdoc</code>
   document</span>, the document must not have a <span>character encoding declaration</span>. (In
   this case, the source is already decoded, since it is part of the document that contained the
   <code>iframe</code>.)</p>
 
-  <p>If an <span data-x="HTML documents">HTML document</span> contains a <code>meta</code> element
-  with a <code data-x="attr-meta-charset">charset</code> attribute or a <code>meta</code> element
-  with an <code data-x="attr-meta-http-equiv">http-equiv</code> attribute in the <span
-  data-x="attr-meta-http-equiv-content-type">Encoding declaration state</span>, then the character
-  encoding used must be an <span>ASCII-compatible encoding</span>.</p>
-
-  <p>Authors should use <span>UTF-8</span>. Conformance checkers may advise authors against using
-  legacy encodings. <ref spec=ENCODING></p>
-
-  <div w-nodev>
-
-  <p>Authoring tools should default to using <span>UTF-8</span> for newly-created documents. <ref
-  spec=ENCODING></p>
-
-  </div>
-
-  <p>Authors must not use encodings that are not defined in the WHATWG Encoding standard.
-  Additionally, authors should not use <span>ISO-2022-JP</span>. <ref spec=ENCODING></p>
-
-  <p class="note">Some encodings that are not defined in the WHATWG Encoding standard use bytes in
-  the range 0x20 to 0x7E, inclusive, to encode characters other than the corresponding characters in
-  the range U+0020 to U+007E, inclusive, and represent a potential security vulnerability: a user
-  agent might end up interpreting supposedly benign plain text content as HTML tags and
-  JavaScript.</p>
-
-  <p class="note">Using non-UTF-8 encodings can have unexpected results on form submission and URL
-  encodings, which use the <span>document's character encoding</span> by default.</p>
-
   <p>In XML, the XML declaration should be used for inline character encoding information, if
   necessary.</p>
 
@@ -57251,7 +57230,6 @@ interface <dfn>HTMLScriptElement</dfn> : <span>HTMLElement</span> {
   [<span>CEReactions</span>] attribute USVString <span data-x="dom-script-src">src</span>;
   [<span>CEReactions</span>] attribute DOMString <span data-x="dom-script-type">type</span>;
   [<span>CEReactions</span>] attribute boolean <span data-x="dom-script-noModule">noModule</span>;
-  [<span>CEReactions</span>] attribute DOMString <span data-x="dom-script-charset">charset</span>;
   [<span>CEReactions</span>] attribute boolean <span data-x="dom-script-async">async</span>;
   [<span>CEReactions</span>] attribute boolean <span data-x="dom-script-defer">defer</span>;
   [<span>CEReactions</span>] attribute DOMString? <span data-x="dom-script-crossOrigin">crossOrigin</span>;
@@ -57276,16 +57254,16 @@ interface <dfn>HTMLScriptElement</dfn> : <span>HTMLElement</span> {
     case-insensitive</span> match for a <span>JavaScript MIME type</span>, means that the script is
     a <span>classic script</span>, to be interpreted according to the JavaScript <i
     data-x="js-prod-Script">Script</i> top-level production. Classic scripts are affected by the
-    <code data-x="attr-script-charset">charset</code>, <code
-    data-x="attr-script-async">async</code>, and <code data-x="attr-script-defer">defer</code>
-    attributes. Authors should omit the attribute instead of redundantly setting it.</p></li>
+    <code data-x="attr-script-async">async</code> and <code data-x="attr-script-defer">defer</code>
+    attributes (as well as the legacy <code data-x="attr-script-charset">charset</code> attribute).
+    Authors should omit the attribute instead of redundantly setting it.</p></li>
 
     <li><p>Setting the attribute to an <span>ASCII case-insensitive</span> match for the string
     "<code data-x="">module</code>" means that the script is a <span>module script</span>, to be
     interpreted according to the JavaScript <i data-x="js-prod-Module">Module</i> top-level
-    production. Module scripts are not affected by the <code
-    data-x="attr-script-charset">charset</code> and <code data-x="attr-script-defer">defer</code>
-    attributes.</p></li>
+    production. Module scripts are not affected by the <code data-x="attr-script-defer">defer</code>
+    attribute (or by the legacy <code data-x="attr-script-charset">charset</code>
+    attribute).</p></li>
 
     <li><p>Setting the attribute to any other value means that the script is a <dfn>data
     block</dfn>, which is not processed. None of the <code>script</code> attributes (except <code
@@ -57316,10 +57294,9 @@ interface <dfn>HTMLScriptElement</dfn> : <span>HTMLElement</span> {
   spec="JAVASCRIPT"></p>
 
   <p>When used to include <span data-x="data block">data blocks</span>, the data must be embedded
-  inline, the format of the data must be given using the <code
-  data-x="attr-script-type">type</code> attribute, and the contents of the <code>script</code>
-  element must conform to the requirements defined for the format used. The <code
-  data-x="attr-script-src">src</code>, <code data-x="attr-script-charset">charset</code>, <code
+  inline, the format of the data must be given using the <code data-x="attr-script-type">type</code>
+  attribute, and the contents of the <code>script</code> element must conform to the requirements
+  defined for the format used. The <code data-x="attr-script-src">src</code>, <code
   data-x="attr-script-async">async</code>, <code data-x="attr-script-nomodule">nomodule</code>,
   <code data-x="attr-script-defer">defer</code>, <code
   data-x="attr-script-crossorigin">crossorigin</code>, <code data-x="attr-script-nonce">nonce</code>
@@ -57334,16 +57311,6 @@ interface <dfn>HTMLScriptElement</dfn> : <span>HTMLElement</span> {
   specified on <span data-x="module script">module scripts</span> (and will be ignored if it
   is).</p>
 
-  <p>The <dfn><code data-x="attr-script-charset">charset</code></dfn> attribute gives the character
-  encoding of the external script resource. The attribute must not be specified if the <code
-  data-x="attr-script-src">src</code> attribute is not present, or if the script is not a
-  <span>classic script</span>. (<span data-x="module script">Module scripts</span> are always
-  interpreted as UTF-8.) If the attribute is set, its value must be an <span>ASCII
-  case-insensitive</span> match for one of the <span data-x="encoding label">labels</span> of an
-  <span>encoding</span>, and must specify the same <span>encoding</span> as the <code
-  data-x="">charset</code> parameter of the <span data-x="Content-Type">Content-Type
-  metadata</span> of the external file, if any. <ref spec=ENCODING></p>
-
   <p>The <dfn><code data-x="attr-script-async">async</code></dfn> and <dfn><code
   data-x="attr-script-defer">defer</code></dfn> attributes are <span data-x="boolean
   attribute">boolean attributes</span> that indicate how the script should be evaluated. <span
@@ -57421,19 +57388,18 @@ interface <dfn>HTMLScriptElement</dfn> : <span>HTMLElement</span> {
 
 
   <p>Changing the <code data-x="attr-script-src">src</code>, <code
-  data-x="attr-script-type">type</code>, <code data-x="attr-script-charset">charset</code>, <code
-  data-x="attr-script-nomodule">nomodule</code>, <code
+  data-x="attr-script-type">type</code>, <code data-x="attr-script-nomodule">nomodule</code>, <code
   data-x="attr-script-async">async</code>, <code data-x="attr-script-defer">defer</code>, <code
   data-x="attr-script-crossorigin">crossorigin</code>, <code data-x="attr-script-nonce">nonce</code>
-  and <code data-x="attr-script-integrity">integrity</code> attributes dynamically has no direct
-  effect; these attributes are only used at specific times described below.</p> <!-- by implication,
-  changes to the base URL also have no effect -->
+  <code data-x="attr-script-integrity">integrity</code> attributes dynamically has no direct effect;
+  these attributes are only used at specific times described below. (The same is true for the legacy
+  <code data-x="attr-script-charset">charset</code> attribute.</p> <!-- by implication, changes to
+  the base URL also have no effect -->
 
   <div w-nodev>
 
   <p>The IDL attributes <dfn><code data-x="dom-script-src">src</code></dfn>, <dfn><code
   data-x="dom-script-type">type</code></dfn>, <dfn><code
-  data-x="dom-script-charset">charset</code></dfn>, <dfn><code
   data-x="dom-script-defer">defer</code></dfn>, <dfn><code
   data-x="dom-script-integrity">integrity</code></dfn>, and <dfn><code
   data-x="dom-script-nonce">nonce</code></dfn>, must each <span>reflect</span> the respective
@@ -112784,6 +112750,12 @@ if (s = prompt('What is your name?')) {
   <code>img</code> element. If the attribute is present, its value must be the string "<code
   data-x="">0</code>". CSS should be used instead.</p>
 
+  <p>Authors should not specify a <code data-x="attr-script-charset">charset</code> attribute on a
+  <code>script</code> element. If the attribute is present, its value must be an <span>ASCII
+  case-insensitive</span> match for "<code data-x="">utf-8</code>". (This has no effect in a
+  document that conforms to the requirements elsewhere in this standard of being encoded as
+  <span>UTF-8</span>.)</p>
+
   <p>Authors should not specify a <code data-x="attr-script-language">language</code> attribute on a
   <code>script</code> element. If the attribute is present, its value must be an <span>ASCII
   case-insensitive</span> match for the string "<code data-x="">JavaScript</code>" and either the
@@ -112843,6 +112815,10 @@ if (s = prompt('What is your name?')) {
    <li><p>The presence of a <code data-x="attr-img-border">border</code> attribute on an
    <code>img</code> element if its value is the string "<code data-x="">0</code>".</p></li>
 
+   <li><p>The presence of a <code data-x="attr-script-charset">charset</code> attribute on a
+   <code>script</code> element if its value is an <span>ASCII case-insensitive</span> match for
+   "<code data-x="">utf-8</code>".</p></li>
+
    <li><p>The presence of a <code data-x="attr-script-language">language</code> attribute on a
    <code>script</code> element if its value is an <span>ASCII case-insensitive</span> match for the
    string "<code data-x="">JavaScript</code>" and if there is no <code
@@ -112985,6 +112961,12 @@ if (s = prompt('What is your name?')) {
    <dt><dfn><code data-x="attr-link-charset">charset</code></dfn> on <code>link</code> elements</dt>
    <dd><p>Use an HTTP `<code>Content-Type</code>` header on the linked resource instead.</p></dd>
 
+   <dt><dfn><code data-x="attr-script-charset">charset</code></dfn> on <code>script</code>
+   elements (except as noted in the previous section)</dt>
+   <dd><p>Omit the attribute. Both documents and scripts are required to use <span>UTF-8</span>,
+   so it is redundant to specify it on the <code>script</code> element since it inherits from the
+   document.</p></dd>
+
    <dt><dfn><code data-x="attr-a-coords">coords</code></dfn> on <code>a</code> elements</dt>
    <dt><dfn><code data-x="attr-a-shape">shape</code></dfn> on <code>a</code> elements</dt>
    <dd><p>Use <code>area</code> instead of <code>a</code> for image maps.</p></dd>
@@ -114085,13 +114067,14 @@ interface <dfn>HTMLFontElement</dfn> : <span>HTMLElement</span> {
   <hr>
 
   <pre class="idl">partial interface <span id="HTMLScriptElement-partial">HTMLScriptElement</span> {
+  [<span>CEReactions</span>] attribute DOMString <span data-x="dom-script-charset">charset</span>;
   [<span>CEReactions</span>] attribute DOMString <span data-x="dom-script-event">event</span>;
   [<span>CEReactions</span>] attribute DOMString <span data-x="dom-script-htmlFor">htmlFor</span>;
 };</pre>
 
-  <p>The <dfn><code data-x="dom-script-event">event</code></dfn> IDL attribute of the
-  <code>script</code> element must <span>reflect</span> the element's
-  <code data-x="attr-script-event">event</code> content attribute.</p>
+  <p>The <dfn><code data-x="dom-script-event">event</code></dfn> and <dfn><code
+  data-x="dom-script-charset">charset</code></dfn> IDL attributes of the <code>script</code> element
+  must <span>reflect</span> the respective content attributes of the same name.</p>
 
   <p>The <dfn><code data-x="dom-script-htmlFor">htmlFor</code></dfn> IDL attribute of the
   <code>script</code> element must <span>reflect</span> the element's
@@ -114373,10 +114356,9 @@ interface <dfn>External</dfn> {
 
       <p>The <code data-x="">charset</code> parameter may be provided to specify the
       <span>document's character encoding</span>, overriding any <span data-x="character encoding
-      declaration">character encoding declarations</span> in the document other than a Byte Order Mark (BOM). The parameter's value
-      must be one of the <span data-x="encoding label">labels</span> of the <span
-      data-x="encoding">character encoding</span> used to serialize the file. <ref
-      spec=ENCODING></p>
+      declaration">character encoding declarations</span> in the document other than a Byte Order
+      Mark (BOM). The parameter's value must be an <span>ASCII case-insensitive</span> match for the
+      string "<code data-x="">utf-8</code>". <ref spec=ENCODING></p>
 
      </dd>
     </dl>
@@ -117250,12 +117232,7 @@ interface <dfn>External</dfn> {
      <th> <code data-x="">charset</code>
      <td> <code data-x="attr-meta-charset">meta</code>
      <td> <span>Character encoding declaration</span>
-     <td> <span>Encoding label</span>*
-    <tr>
-     <th> <code data-x="">charset</code>
-     <td> <code data-x="attr-script-charset">script</code>
-     <td> Character encoding of the external script resource
-     <td> <span>Encoding label</span>*
+     <td> "<code data-x="">utf-8</code>"
     <tr>
      <th> <code data-x="">checked</code>
      <td> <code data-x="attr-input-checked">input</code>

From 79508553eb433b0e2b6d44f190497c66aa951d6e Mon Sep 17 00:00:00 2001
From: "Michael[tm] Smith" <mike@w3.org>
Date: Fri, 6 Oct 2017 10:32:35 +0900
Subject: [PATCH 2/3] Further minor cleanup around charset obsolescence

---
 source | 2 --
 1 file changed, 2 deletions(-)

diff --git a/source b/source
index 7a2887da57c..5311902a89a 100644
--- a/source
+++ b/source
@@ -57216,7 +57216,6 @@ interface <dfn>HTMLDialogElement</dfn> : <span>HTMLElement</span> {
    <dd><code data-x="attr-script-src">src</code></dd>
    <dd><code data-x="attr-script-type">type</code></dd>
    <dd><code data-x="attr-script-nomodule">nomodule</code></dd>
-   <dd><code data-x="attr-script-charset">charset</code></dd>
    <dd><code data-x="attr-script-async">async</code></dd>
    <dd><code data-x="attr-script-defer">defer</code></dd>
    <dd><code data-x="attr-script-crossorigin">crossorigin</code></dd>
@@ -116267,7 +116266,6 @@ interface <dfn>External</dfn> {
      <td><span data-x="global attributes">globals</span>;
          <code data-x="attr-script-src">src</code>;
          <code data-x="attr-script-type">type</code>;
-         <code data-x="attr-script-charset">charset</code>;
          <code data-x="attr-script-async">async</code>;
          <code data-x="attr-script-defer">defer</code>;
          <code data-x="attr-script-crossorigin">crossorigin</code>;

From 716ab5fa31b61e79216a6bf44f069abbb161036d Mon Sep 17 00:00:00 2001
From: Anne van Kesteren <annevk@annevk.nl>
Date: Fri, 6 Oct 2017 11:23:10 +0200
Subject: [PATCH 3/3] address various nits and some grammar issues

---
 source | 34 +++++++++++++++-------------------
 1 file changed, 15 insertions(+), 19 deletions(-)

diff --git a/source b/source
index 5311902a89a..75971b72d92 100644
--- a/source
+++ b/source
@@ -14731,11 +14731,11 @@ people expect to have work and what is necessary.
   <p>The Encoding standard requires use of the <span>UTF-8</span> <span data-x="encoding">character
   encoding</span> and requires use of the "<code data-x="">utf-8</code>" <span>encoding label</span>
   to identify it. Those requirements necessitate that the document's <span>character encoding
-  declaration</span>, if it exists, specify an <span>encoding label</span> using an <span>ASCII
-  case-insensitive</span> match for the string "<code data-x="">utf-8</code>". Regardless of whether
-  a <span>character encoding declaration</span> is present or not, the actual <span
-  data-x="document's character encoding">character encoding</span> used to store or transmit the
-  document must be <span>UTF-8</span>. <ref spec=ENCODING></p>
+  declaration</span>, if it exists, specifies an <span>encoding label</span> using an <span>ASCII
+  case-insensitive</span> match for "<code data-x="">utf-8</code>". Regardless of whether a
+  <span>character encoding declaration</span> is present or not, the actual <span data-x="document's
+  character encoding">character encoding</span> used to encode the document must be
+  <span>UTF-8</span>. <ref spec=ENCODING></p>
 
   <p w-nodev>To enforce the above rules, authoring tools must default to using <span>UTF-8</span>
   for newly-created documents.</p>
@@ -57254,15 +57254,13 @@ interface <dfn>HTMLScriptElement</dfn> : <span>HTMLElement</span> {
     a <span>classic script</span>, to be interpreted according to the JavaScript <i
     data-x="js-prod-Script">Script</i> top-level production. Classic scripts are affected by the
     <code data-x="attr-script-async">async</code> and <code data-x="attr-script-defer">defer</code>
-    attributes (as well as the legacy <code data-x="attr-script-charset">charset</code> attribute).
-    Authors should omit the attribute instead of redundantly setting it.</p></li>
+    attributes. Authors should omit the attribute instead of redundantly setting it.</p></li>
 
     <li><p>Setting the attribute to an <span>ASCII case-insensitive</span> match for the string
     "<code data-x="">module</code>" means that the script is a <span>module script</span>, to be
     interpreted according to the JavaScript <i data-x="js-prod-Module">Module</i> top-level
     production. Module scripts are not affected by the <code data-x="attr-script-defer">defer</code>
-    attribute (or by the legacy <code data-x="attr-script-charset">charset</code>
-    attribute).</p></li>
+    attribute.</p></li>
 
     <li><p>Setting the attribute to any other value means that the script is a <dfn>data
     block</dfn>, which is not processed. None of the <code>script</code> attributes (except <code
@@ -57385,15 +57383,13 @@ interface <dfn>HTMLScriptElement</dfn> : <span>HTMLElement</span> {
   <span>module script</span> or when the <code data-x="attr-script-src">src</code> attribute is not
   specified. <ref spec="SRI"></p>
 
-
   <p>Changing the <code data-x="attr-script-src">src</code>, <code
   data-x="attr-script-type">type</code>, <code data-x="attr-script-nomodule">nomodule</code>, <code
   data-x="attr-script-async">async</code>, <code data-x="attr-script-defer">defer</code>, <code
-  data-x="attr-script-crossorigin">crossorigin</code>, <code data-x="attr-script-nonce">nonce</code>
-  <code data-x="attr-script-integrity">integrity</code> attributes dynamically has no direct effect;
-  these attributes are only used at specific times described below. (The same is true for the legacy
-  <code data-x="attr-script-charset">charset</code> attribute.</p> <!-- by implication, changes to
-  the base URL also have no effect -->
+  data-x="attr-script-crossorigin">crossorigin</code>, <code
+  data-x="attr-script-nonce">nonce</code>, and <code data-x="attr-script-integrity">integrity</code>
+  attributes dynamically has no direct effect; these attributes are only used at specific times
+  described below.</p> <!-- by implication, changes to the base URL also have no effect -->
 
   <div w-nodev>
 
@@ -112962,8 +112958,8 @@ if (s = prompt('What is your name?')) {
 
    <dt><dfn><code data-x="attr-script-charset">charset</code></dfn> on <code>script</code>
    elements (except as noted in the previous section)</dt>
-   <dd><p>Omit the attribute. Both documents and scripts are required to use <span>UTF-8</span>,
-   so it is redundant to specify it on the <code>script</code> element since it inherits from the
+   <dd><p>Omit the attribute. Both documents and scripts are required to use <span>UTF-8</span>, so
+   it is redundant to specify it on the <code>script</code> element since it inherits from the
    document.</p></dd>
 
    <dt><dfn><code data-x="attr-a-coords">coords</code></dfn> on <code>a</code> elements</dt>
@@ -114071,8 +114067,8 @@ interface <dfn>HTMLFontElement</dfn> : <span>HTMLElement</span> {
   [<span>CEReactions</span>] attribute DOMString <span data-x="dom-script-htmlFor">htmlFor</span>;
 };</pre>
 
-  <p>The <dfn><code data-x="dom-script-event">event</code></dfn> and <dfn><code
-  data-x="dom-script-charset">charset</code></dfn> IDL attributes of the <code>script</code> element
+  <p>The <dfn><code data-x="dom-script-charset">charset</code></dfn> and <dfn><code
+  data-x="dom-script-event">event</code></dfn> IDL attributes of the <code>script</code> element
   must <span>reflect</span> the respective content attributes of the same name.</p>
 
   <p>The <dfn><code data-x="dom-script-htmlFor">htmlFor</code></dfn> IDL attribute of the