Many types of components, such as tabs, menus, image galleries, and so on, need the content to render.
Just like built-in browser
Named slots
Let’s see how slots work on a simple example.
Here, shadow DOM provides two slots, filled from light DOM:
In the shadow DOM, defines an “insertion point”, a place where elements with slot=“X” are rendered.
Then the browser performs “composition”: it takes elements from the light DOM and renders them in corresponding slots of the shadow DOM. At the end, we have exactly what we want – a component that can be filled with data.
Here’s the DOM structure after the script, not taking composition into account:
We created the shadow DOM, so here it is, under #shadow-root. Now the element has both light and shadow DOM.
For rendering purposes, for each in shadow DOM, the browser looks for slot=“…” with the same name in the light DOM. These elements are rendered inside the slots:
The result is called “flattened” DOM:
…But the flattened DOM exists only for rendering and event-handling purposes. It’s kind of “virtual”. That’s how things are shown. But the nodes in the document are actually not moved around!
That can be easily checked if we run querySelectorAll: nodes are still at their places.
So, the flattened DOM is derived from shadow DOM by inserting slots. The browser renders it and uses for style inheritance, event propagation (more about that later). But JavaScript still sees the document “as is”, before flattening.
John Smith
01.01.2001
If there are multiple elements in light DOM with the same slot name, they are appended into the slot, one after another.
For example, this:
Gives this flattened DOM with two elements in :
Slot fallback content
If we put something inside a , it becomes the fallback, “default” content. The browser shows it if there’s no corresponding filler in light DOM.
For example, in this piece of shadow DOM, Anonymous renders if there’s no slot=“username” in light DOM.
Default slot: first unnamed
The first in shadow DOM that doesn’t have a name is a “default” slot. It gets all nodes from the light DOM that aren’t slotted elsewhere.
For example, let’s add the default slot to our that shows all unslotted information about the user:
All the unslotted light DOM content gets into the “Other information” fieldset.
Elements are appended to a slot one after another, so both unslotted pieces of information are in the default slot together.
The flattened DOM looks like this:
Menu example
Now let’s back to , mentioned at the beginning of the chapter.
We can use slots to distribute elements.
Here’s the markup for :
The shadow DOM template with proper slots:
1. goes into .
2. There are many
in the , but only one in the template. So all such
are appended to one after another, thus forming the list.
The flattened DOM becomes:
One might notice that, in a valid DOM,
must be a direct child of
. But that’s flattened DOM, it describes how the component is rendered, such thing happens naturally here.
We just need to add a click handler to open/close the list, and the is ready:
Here’s the full demo:
[iframe src=“menu” height=140 edit]
Of course, we can add more functionality to it: events, methods and so on.
Updating slots
What if the outer code wants to add/remove menu items dynamically?
The browser monitors slots and updates the rendering if slotted elements are added/removed.
Also, as light DOM nodes are not copied, but just rendered in slots, the changes inside them immediately become visible.
So we don’t have to do anything to update rendering. But if the component code wants to know about slot changes, then slotchange event is available.
For example, here the menu item is inserted dynamically after 1 second, and the title changes after 2 seconds:
The menu rendering updates each time without our intervention.
There are two slotchange events here:
1. At initialization:
slotchange: title triggers immediately, as the slot=“title” from the light DOM gets into the corresponding slot.
2. After 1 second:
slotchange: item triggers, when a new
is added.
Please note: there’s no slotchange event after 2 seconds, when the content of slot=“title” is modified. That’s because there’s no slot change. We modify the content inside the slotted element, that’s another thing.
If we’d like to track internal modifications of light DOM from JavaScript, that’s also possible using a more generic mechanism: MutationObserver.
Slot API
Finally, let’s mention the slot-related JavaScript methods.
As we’ve seen before, JavaScript looks at the “real” DOM, without flattening. But, if the shadow tree has {mode: ‘open’}, then we can figure out which elements assigned to a slot and, vice-versa, the slot by the element inside it:
- node.assignedSlot – returns the element that the node is assigned to.
- slot.assignedNodes({flatten: true/false}) – DOM nodes, assigned to the slot. The flatten option is false by default. If explicitly set to true, then it looks more deeply into the flattened DOM, returning nested slots in case of nested components and the fallback content if no node assigned.
- slot.assignedElements({flatten: true/false}) – DOM elements, assigned to the slot (same as above, but only element nodes).
These methods are useful when we need not just show the slotted content, but also track it in JavaScript.
For example, if component wants to know, what it shows, then it could track slotchange and get the items from slot.assignedElements:
Summary
Usually, if an element has shadow DOM, then its light DOM is not displayed. Slots allow to show elements from light DOM in specified places of shadow DOM.
There are two kinds of slots:
- Named slots: … – gets light children with slot=“X”.
- Default slot: the first without a name (subsequent unnamed slots are ignored) – gets unslotted light children.
- If there are many elements for the same slot – they are appended one after another.
- The content of element is used as a fallback. It’s shown if there are no light children for the slot.
The process of rendering slotted elements inside their slots is called “composition”. The result is called a “flattened DOM”.
Composition does not really move nodes, from JavaScript point of view the DOM is still same.
JavaScript can access slots using methods:
- slot.assignedNodes/Elements() – returns nodes/elements inside the slot.
- node.assignedSlot – the reverse property, returns slot by a node.
If we’d like to know what we’re showing, we can track slot contents using:
- slotchange event – triggers the first time a slot is filled, and on any add/remove/replace operation of the slotted element, but not its children. The slot is event.target.
- MutationObserver to go deeper into slot content, watch changes inside it.
Now, as we know how to show elements from light DOM in shadow DOM, let’s see how to style them properly. The basic rule is that shadow elements are styled inside, and light elements – outside, but there are notable exceptions.
We’ll see the details in the next chapter.