whatwg/html

Developers of stylus-based drawing applications (e.g., Google Keep) have found this hint to be critical in order to be competitive with native applications. It has been prototyped in Chromium and yields significant latency improvements there.

Tests: will be added as part of https://bugs.chromium.org/p/chromium/issues/detail?id=788439.

Supersedes #4234. Partial fix for #4087.

Co-authored-by: Miguel Casas-Sanchez <mcasas@chromium.org>

Also describe what happens when the browsing context is discarded.

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

Follow-up: #4431.

Fixes #2579.

"Nested browsing context" belongs to an element. What objects contains are potentially browsing contexts.

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

Fixes #4403.

This is a follow-up of #4239, and
fixes an issue pointed out in web-platform-tests/wpt#14637.

Follows heycam/webidl@c705ce6.

close() needed to queue a task to close, though closed needs to immediately know when close() is invoked too.

Tests: web-platform-tests/wpt#15561 & web-platform-tests/wpt#15649.

Fixes #4405. Helps with #4363.

This aligns the standard with Chromium/WebKit and an upcoming release of Firefox.

In particular, the two cases that need to work are:

* <img> (without alt) creates a replaced box, regardless of specified dimensions or what not.

* <img src="foo" alt="bar"> creates a replaced box while the image is loading, rather than an inline.

Tests are in https://phabricator.services.mozilla.com/D11194.

Tests: web-platform-tests/wpt#15461 & web-platform-tests/wpt#15518.

Tests: will be upstreamed as part of https://bugzilla.mozilla.org/show_bug.cgi?id=1530048.

Fixes #4391.

Previously, it was indented into the middle of "process a navigate
response", which made that algorithm really hard to read. There was also
a standalone "set the Document's address" algorithm which was never
called, but said it must be performed at the appropriate time.

This moves the algorithm out to be a sibling of "process a navigate
response", with appropriate inputs, and includes the step to set the URL
directly in the algorithm.

Closes #3327.

This attempts to make the navigation algorithm slightly more
comprehensible by factoring out the conversion of javascript: URL
requests into responses into a dedicated algorithm, instead of having it
occupy about half of the main "navigate" algorithm. The factored-out
algorithm is also slightly modernized and cleaned up in various ways.

It's not implemented and complicates navigation.

Closes #2656.

Helps with #4335.

This fixes #3846, though does not clarify the situation for all callers necessarily.

Removing this concept altogether is tricky as it's used in workers for disabled scripts. #1580 tracks that.

This allows preloading responsive images. Closes w3c/preload#120.

All these references are already explicit (usually via "internal slots" on the objects) and they are strong by default, so there's no need to state this separately.

Closes #4386.

This is not defined to have an effect. I.e., the ideas in https://www.w3.org/Bugs/Public/show_bug.cgi?id=25734 never materialized.

See also #3862 and whatwg/fetch#846.

The grouping concepts unit of related browsing contexts and unit of similar-origin browsing contexts were not accurate, due to browsing contexts being able to hold a sequence of (potentially cross-site) documents.

Fixes #4198.

In particular when there's a null browsing context, for #4363.

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

This should fix the issue seen in whatwg/fullscreen#145.

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

Helps with #4363.

Previously, a Document could sometimes "have no browsing context". Now,
"a Document's browsing context" is either a browsing context or null.

Previously, "a Window's browsing context" was not defined, despite being
referenced extensively. Now, it is defined to be the Window's associated
Document's browsing context.

Related to #3846, #4363, and #4366.

Calling cancelAnimationFrame() from within a requestAnimationFrame()
callback should cancel any animation frame callbacks that are
pending for the current frame. The currently specified behavior does not
permit that, however, since it clones the set of callbacks before
iterating over them.

This patch updates the algorithm to run animation frame callbacks such
that it is possible to cancel a pending animation frame callback.
This also brings the specified behavior into line with its
implementation in Blink, EdgeHTML, and WebKit.

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

Closes #4359.

See https://bugzilla.mozilla.org/show_bug.cgi?id=1460158 for context.

Name attributes of elements that can create nested browsing contexts (embed, frame, iframe, object) are only to be considered when the nested browsing context is created.

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

In particular to enable noopener, noreferrer, and opener values.

Also default <form target=_blank> to noopener.

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

Fixes #2983.

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

Fixes #4111.

Fixes #4171.