whatwg/html

Regressed in 29afad4.

Regressed in a68a1f7.

Fixes #3107.

Also move a comment to the correct place.

This change adds a “must” requirement for UTF-8 in all but one of the places in the standard 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-document 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.

Closes #3004.

See bmeck/I-D#2 for context.

Closes #2315.

This propagates an appropriate base URL for all instances of creating a
classic script. This has no effect by itself (and indeed looks kind of
pointless as of this commit), but it sets the stage for making import()
use this base URL (#2315).

The primary normative content of this commit is that it fixes #2382 by
passing the integrity metadata to the fetch call for the top-level
module script, in <script type=module>.

However, the way it does this is via a larger refactoring, which is
setting the stage for #2315. It creates a new struct, the script fetch
options, which is now shared by both module and classic scripts. Storing
this for classic scripts is not currently useful, but will be for #2315
when, via import(), classic scripts are able to import module scripts,
and need these fetch options to do so.

This will also be useful for when we revive #2383, as
<link rel=modulepreload> can have referrerpolicy="" specified on it,
which will need to be passed down. (It would also be useful if we ever
do w3c/webappsec-referrer-policy#96 and add
referrerpolicy="" to <script>.) With this structure in place, it's a
simple matter of adding a referrer policy item to the script fetch
options.

Fixes #3066.

See WebAudio/web-audio-api#1266 for details.

Test plan: WebAudio/web-audio-api#1388.

Fixes #3081.

This change updates various URLs in the spec to avoid redirects and to
replace more http URLs with https URLs where we can (e.g., for all the
links to unicode.org documents in the References section). It also
tweaks the header links to fix #2906.

Fixes #3015.

This change fixes some links — both external and internal — mostly links with
broken fragments. Some specific notes about a couple complete removals of links:

* Removes stale link to WebIDL `RegExp` , which the WebIDL spec no longer has —
  and all references for which were already dropped from the HTML spec anyway.

* Removes broken link to the definition of the CSS `<position>` data type, which
  isn’t actually currently referenced in the HTML spec.

* Removes crufty link to Service Workers “use cache”, which has already been
  superseded by other language in the Service Workers spec and HTML spec.

The HTML spec depends on having a CSS Overflow spec that defines the CSS
‘overflow’ property, but the spec at https://drafts.csswg.org/css-overflow/
no longer defines the ‘overflow’ property; instead, the ‘overflow’ property
definition is in the spec at https://drafts.csswg.org/css-overflow-3/. So, for
the time being at least, we have the HTML spec reference use that version
(the Level 3 version) of the CSS Overflow spec.

This change also drops *‘Level N’* qualifiers from a couple other CSS spec
names in the References section — because, regardless of what version of a
particular CSS module spec we’re referencing, our style is to consistently just
cite the name of the spec without the *‘Level N’* qualifier.

Fixes #2854.

This change adds Secure Contexts to the References section. (We had somehow overlooked this til now…)

The old text associates “pick” with <select multiple> elements and “toggle” with other <select> elements [0], but the defining instances of “pick” [1] and “toggle” [2] make the converse association.

[0] § 4.11.3.5 “Using the <option> element to define a command” https://html.spec.whatwg.org/multipage/interactive-elements.html#using-the-option-element-to-define-a-command

[1] “picked” in § 4.10.7 “The <select> element” https://html.spec.whatwg.org/multipage/form-elements.html#concept-select-pick

[2] “toggle” in § 4.10.7 “The <select> element” https://html.spec.whatwg.org/multipage/form-elements.html#concept-select-toggle

The serialization steps were upstreamed in
w3c/FileAPI@828c3b6.

Fixes #2845.

Tests: w3c/web-platform-tests#7473

Require that they are all connected to a document (except for <a>) that is fully active (including <a>). There is enough difference between implementations that this appears to be web compatible.

Also perform a second connected check for <form>.

Tests:

* w3c/web-platform-tests#5758
* w3c/web-platform-tests#5759
* w3c/web-platform-tests#5761

Fixes #2615 and fixes #2708.

To do this we introduced a new concept called parallel queue, which is also expected to be used by other specifications, such as Background Fetch.

Fixes #1843.

The createImageBitmap() algorithm should fail step 1 with a RangeError,
not the deprecated "IndexSizeError" DOMException.

Attempting to set the width or height attribute of a canvas element
after it has transferred control to an OffscreenCanvas should throw an
exception. Before this change, the behavior was to silently ignore
changes to these attributes, which was not clear because that case was
not specifically mentioned in the spec.

78009c8 suggests this was once introduced for a contextMenu IDL attribute which has since been removed. The remaining IDL attributes that return an HTMLElement (or subclass) have dedicated algorithms.

As discussed in #2898, there are two primary problems being addressed:

* By not delaying a microtask, we are not properly waiting for any image
  data updates. This introduces such a delay.
* By testing for the presence of src or srcset, we do not work for <img>
  elements who get the current request from a containing <picture>
  element. This removes that check.

Closes #2898.

Fixes #2301 and fixes #3037.

This change adds a link in the `template` *Content model* header
directly to the related example in the prose of the `template` section
that helps make clear why the content model is `Nothing`.

This change also adds the `template` element as a new (sixth) element
type in the HTML Syntax: Writing HTML documents: Elements section.

Fixes #3021.

Fixes #2507.

They have seen extremely poor adoption unfortunately and were not implemented in line with the standard.

Tests: w3c/web-platform-tests#7349.

Fixes #630.

* De-genericizes <style> and <link rel="stylesheet"> to only deal with
  CSS. Fixes #2995.
* Makes type="" on <style> "obsolete but conforming", since it is always
  redundant.
* Makes type="(a JS MIME type)" on <script> obsolete but conforming as
  well. Previously we had a "should" requirement but had not recorded it
  in the centralized obsolete-but-conforming section that collects such
  requirements.
* Makes <style> operate on child text content. Fixes #2996.
* Replaces the conformance requirement (noted in the source as
  "temporary") prohibiting unmatched comment-like syntax inside <style>
  with a conformance requirement to be valid CSS.
* Adds pointers to #2997.
* Makes it clearer that parameters are not allowed in the content type
  value for script or style. Fixes #3022.