diff --git a/reports/2022.html b/reports/2022.html index 27fe7c3..66d75af 100644 --- a/reports/2022.html +++ b/reports/2022.html @@ -177,10 +177,10 @@

Table of Contents

- Imperative Slot Assignement - - + Imperative Slot Assignment + whatwg/html#3534 + Partial Implementation CSS Properties and values inside shadow root @@ -1371,16 +1371,16 @@

Open Questions

-

Imperative Slot Assignement

+

Imperative Slot Assignment

Links

Previous WCCG Report(s)
N/A
GitHub issues:
-
---
+
whatwg/html#3534
Browser positions:
-
---
+
Firefox
@@ -1390,16 +1390,26 @@

Description

Status

Initial API Summary/Quick API Proposal

-

Summary or proposal based on current status; paragraph(s) and code.

+

Currently the Slot API only supports a declarative API, meaning that slot usage can only be expressed through adding the name attribute on an element. But there are valid cases where from multiple sources of slotted content, the Web Components author may want to programmatically set the content of a slot instead. Take this example from the proposal.

+
+          <custom-tab show-panel="2">
+            <tab-panel></tab-panel>
+            <tab-panel></tab-panel>
+            <tab-panel></tab-panel>
+          </custom-tab>
+        
+

Without an imperative API, how would an author be able to set the contents of a single available slot to the selected panel index?

Key Scenarios

-

---

+

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.

Concerns

@@ -1422,7 +1432,7 @@

Related Specs

Open Questions

    -
  • ---
  • +
  • What is Safari's timeline for shipping? Their feature tracker confirms it is supported, but this example doesn't work on iOS.