whatwg / html Public

It seems like this was missed in #2518.

Part of #4082

Force inner display type to flow-root and ignore overflow

drop-down select is display: inline-block

Require text inputs to be scroll containers

And only support scrolling in the inline axis.

This should address the third bullet point in
#4082 (comment)

Currently the check that disallows creation of CSS module scripts in worker contexts only happens after the fetch for that import is performed. This change moves the check to where we check that the assertion type is a valid value. By doing so, failing that check prevents the fetch.

Closes #7047.

Fixes #5624.

Closes #7049.

Also remove the reference to filesystem: URLs since those are no longer acknowledged in spec-land.

Closes #7045.

Closes #6836. Closes #6992 by superseding it.

Changes the description of datalist matching to use the term "search within" instead of "substring match", and adds examples of some of the textual variation issues that user agents might consider.

Closes #4814.

This example no longer makes any sense after e0b554b.

Fixes #7018.

Closes #6472. See also the explainer at https://github.com/horo-t/explainers/blob/main/script_element_supports.md.

This creates a dedicated algorithm that underlies whether a URL can be rewritten using history.pushState()/replaceState(). The algorithm is phrased differently than the old inline steps, but it has the same normative effect, and is clearer since it involves less negatives.

This also adds a table of examples for "can have its URL rewritten", and modernizes and expands the domintros for the pushState() and replaceState() methods.

We previously used static getters since static class properties did not have great browser support. Now they are in all engines.

Fixes #6952.

Instead, sandboxed documents are just never allowed to display plugins. (Which, in the modern world, just means PDFs.)

Closes #3958. Helps with #6003.

Closes #6972.

Fixes #6474.

Fixes #6571. Closes #6610.

Fixes #6971.

These were missed in 88c994a. Closes #6969.

This adds a cancelable contextlost event, a contextrestored event, and an isContextLost() method.

Closes #4809. Closes #2303.

It's a legacy feature so we shouldn't be encouraging developers to use it.

Closes #6948.

For iframes: previously, we did a confusing thing where we would navigate to a non-initial about:blank. 2/3 engines instead just fire a synchronous load event at the iframe element, with no navigation. This is a bit simpler, and matches the popup case a bit better (after the below modifications).

For popups: previously, we fired the load event (but not the pageshow event) when the popup stays on the initial about:blank. 2/3 engines instead fire no events in this case, and the remaining one only fires it in the explicit "about:blank" case but not in the empty string case.

In both cases, it wasn't quite clear what to do when navigating to something like about:blank#foo or about:blank?foo. The spec now makes it clear that such cases cause URL updates of the new browsing context but not full navigations. In particular, for now at least the the initial about:blank-ness of the Document is retained. (In browsers, it seems like it's always retained for replacement vs. push purposes, but is only sometimes retained for Window object reuse purposes. #3267 tracks sorting that out.)

This also refactors the window open steps so that they have two primary branches, depending on whether to create a new window or not. Previously the steps were sorta unified, but there were a lot of consultations of the "new" variable throughout, which made it hard to understand the differences between the cases.

Closes #6863.

Closes #4051.

This also changes the rendering model of hidden <details> content to use content-visibility: none instead of being "removed from the rendering".

With Flash no longer being supported, it shouldn't be listed as an example of the use of plugins. Furthermore, since #6003 aims to remove any complexity around plugins except for that which is needed for PDF viewers, it is clear that plugins in general are no longer an extensibility mechanism.

Closes #6925 and closes #6926.

This came up in the context of https://bugs.chromium.org/p/chromium/issues/detail?id=1144736#c72.

Per spec, removing the src attribute does not release resources, so the best practices section shouldn't suggest doing so. See https://html.spec.whatwg.org/multipage/media.html#location-of-the-media-resource.

Helps with w3c/pointerevents#384. See also #6758.

Adding VideoFrame as a CanvasImageSource allows drawImage(), createImageBitmap(), and texImage() to interoperate with VideoFrames. VideoFrames are effectively the same as the existing point-in-time capture done for HTMLVideoElement on each of these interfaces.

Fixes w3c/webcodecs#158.