Imperative Slot Assignment

[Westbrook]

Description

The ability to imperatively assign content to a <slot> element is available in Chrome and Firefox, and while merged in WebKit not currently available in Safari.

Rationale

Some of the scenarios called out in the proposal include not having to pre-compute the slot names ahead of time, as well as being able to conditionally load content into a slot.

Specification

whatwg/html#6561

Tests

• In WPT: https://wpt.fyi/results/shadow-dom/slots-imperative-slot-api.tentative.html?label=master&label=experimental&aligned&q=slots-imperative-slot-api.tentative.html
• In WPT: https://wpt.fyi/results/shadow-dom/slots

[gsnedders]

Tests

• In WPT: https://wpt.fyi/results/shadow-dom/slots-imperative-slot-api.tentative.html?label=master&label=experimental&aligned&q=slots-imperative-slot-api.tentative.html
• In WPT: https://wpt.fyi/results/shadow-dom/slots

Maybe https://wpt.fyi/results/shadow-dom?label=master&label=experimental&aligned&view=subtest&q=imperative%20slot%20path%3A%2Fshadow-dom (the other two don't seem to point at anything at this point)?

[foolip]

In the MDN short survey on APIs & JavaScript, "Web Components (custom elements, Shadow DOM, etc.)" was the most popular choice by a fairly wide margin, selected by ~39% of survey takers.

Web Components was split into many granular proposals, and the survey results don't tell us which aspects web developers want the most, but it's fair to say that something about Web Components is important. (I'm posting this comment on each of the split proposals.)

[nairnandu]

Thank you for proposing Imperative Slot Assignment for inclusion in Interop 2023.

We wanted to let you know that this proposal was not selected to be part of Interop this year. We looked at the results in WPT, and found that this feature is already largely interoperable between browsers.

For an overview of our process, see the proposal selection summary. Thank you again for contributing to Interop 2023!

Posted on behalf of the Interop team.