whatwg / html

Fixes #5252.

Closes #4968.

Currently the spec suggests authors to use :focus to hide an outline when an element is focused, but actually :focus-visible should be the pseudo-class used for that.

This patch also modifies the example to use a textarea instead of a link, as links not always show a focus ring when focused, while textarea elements always do it.

Complements whatwg/fetch#696. See that pull request for context and tests.

And drop dated mention of offline caching.

Closes #6412.

Closes #6388.

Re-closes #5407

Closes w3c/ServiceWorker#1356.

Part of #4980.

Tests: web-platform-tests/wpt#17571.

Fixes #4716.

Loop through all queue elements when processing the queues, regardless of their state being custom or not.

Dequeue elements from queue while processing to avoid the backup queue causing a memory leak.

Fixes #6385.

This replaces the "intrinsic aspect ratio" concept, instead using a presentational hint for the 'aspect-ratio' property. This applies to <img>, <canvas>, <video>, and <input type=image>.

Fixes #5907.

Fixes #6374.

Nobody but XMLHttpRequest take a dependency on this please. You have been warned.

Context: whatwg/xhr#311.

Also, network scheme is now reduced to HTTP(S) scheme.

Helps with #5375, but form submission issue remains.

See whatwg/fetch#1166 for context.

@@iterator is implicitly installed by defining an indexed property getter. Since there is no other way to define it exclusively, this restores some methods back to being indexed getters.

This fixes an inadvertent observable behavior change in d4f07b8.

Closes #5407.

Part of #6003.

A follow-up to:

* #5694
* #5916

With Flash not being supported anymore, the CSP directive plugin-types has lost its main reason for being and is being removed from the Content Security Policy specification: w3c/webappsec-csp#456.

This change removes references to the relevant algorithm from the Content Security Policy spec.

It has been found in #6306 that this was an oversight at the time of its introduction. Current behavior goes against author expectations and no implementer has opposed the change to "no-clip".

Tests: web-platform-tests/wpt#27040.

Closes #6306.

Closes #5213.

Complements whatwg/fetch#1149.

Fixes #6328.

They are only supported by one engine (Gecko).

Closes #2957.

This contains a small bug fix, in that confirm() and prompt() said
"return" in some cases instead of "return false" or "return null" as
appropriate.

Other notable changes, all editorial, are:

* Factoring out repeated "cannot show simple dialogs" steps, which will
  likely expand over time (see e.g. #6297).
* Separating out and explaining the no-argument overload of alert().
* Passing the document through to the "printing steps", instead of just
  having them talk about "this Window object".

The new version matches implementation reality and CSSWG resolution.

The algorithm was also inconsistent, as it looked at whether
the element was in a shadow tree or in the document tree, but it was
only specified to be re-run if the element becomes connected or
disconnected.

The CSSWG discussed this in
w3c/csswg-drafts#3096 (comment)
and http://wpt.live/shadow-dom/ShadowRoot-interface.html tests this.

This also matches closer the definition of <link rel="stylesheet">,
which does use connectedness (though it uses "browsing-context
connected", which is a bit different):
https://html.spec.whatwg.org/#link-type-stylesheet

See w3c/csswg-drafts#4278.

We use en-US these days. Spotted in https://twitter.com/iso2022jp/status/1352601086519955456.