Slots Without Shadow Dom

  1. Web Components Slots Without Shadow Dom
  2. Slots Without Shadow Dominus
  3. Slots Without Shadow Domain

Since the browser does not in the least know how to paint / layout your custom element, you need to equip it with shadow DOM / custom template via JS. You can not obviously force it to render light DOM, without it having a shadow tree to scope/distribute it to and you naturally can not expect it to render anything without a template. No deposit bonus. When the best new online casino games are released, the casino can award a small no deposit for the new gamblers to draw new customers and allow them to play the new slots free. No deposit bonus means you are getting a certain amount of money (usually about $10) to play new slots online right after you create your casino account. Components with no useShadowDOM decorator and a single default slot don't use shadow DOM. The content from the usage site gets hoisted directly into the location of the slot inside the element's view (while maintaining its binding context to the content site origin).

index.js
// Custom Template/Slot without Shadow DOM
// template refers to <template></template>
// context refers to stuff inside <your-custom-element> <span slot='bork'>🍭</span> </your-custom-element>
// overall flow of operation translates to YOUR-HTML = TEMPLATE(CONTEXT)
// a map of all <slot name='bork'> elements, where key is the name attribute, and value the <slot name='bork'> node;
consttemplate=newMap(Array.from(this.querySelectorAll('slot').values()).map(i=>[i.name,i]));
// an array of [[name, element]] where name is the slot attribute of html element <span slot='bork'>🍭</span>
constcontext=Array.from(this.querySelectorAll(':scope > *[slot]').values()).map(i=>[i.slot,i]);
console.log(context)
// traverse context, the list of elements with slot='*' property
// name is taken from context (see above)
// element is the thing we want to replace <slot> with
for(const[slotName,element]ofcontext){
// slot is the <slot name='bork'> referenced by <span slot='bork'>🍭</span> inside your custom element
constslot=template.get(slotName);
// if template had the slot bork, replace the entire <slot name='bork'>*</slot> with <span slot='bork'>🍭</span>
if(slot)slot.parentElement.replaceChild(element,slot);// Syntax: replacedNode = parentNode.replaceChild(newChild, oldChild);
// remove the remove slot='bork' from <span slot='bork'>🍭</span>
// NOTE: THIS IS NON SPEC, YOU SHOULD COMMENT THIS OUT FOR FUTURE COMPAT
// element.removeAttribute('slot');
}
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Shadow DOM may include both <style> and <link href='…'> tags. In the latter case, stylesheets are HTTP-cached, so they are not redownloaded for multiple components that use same template.

As a general rule, local styles work only inside the shadow tree, and document styles work outside of it. But there are few exceptions.

:host

The :host selector allows to select the shadow host (the element containing the shadow tree).

For instance, we’re making <custom-dialog> element that should be centered. For that we need to style the <custom-dialog> element itself.

That’s exactly what :host does:

Cascading

Slots Without Shadow Dom

The shadow host (<custom-dialog> itself) resides in the light DOM, so it’s affected by document CSS rules.

If there’s a property styled both in :host locally, and in the document, then the document style takes precedence.

For instance, if in the document we had:

…Then the <custom-dialog> would be without padding.

It’s very convenient, as we can setup “default” component styles in its :host rule, and then easily override them in the document.

The exception is when a local property is labelled !important, for such properties, local styles take precedence.

:host(selector)

Same as :host, but applied only if the shadow host matches the selector.

For example, we’d like to center the <custom-dialog> only if it has centered attribute:

Now the additional centering styles are only applied to the first dialog: <custom-dialog centered>.

:host-context(selector)

Same as :host, but applied only if the shadow host or any of its ancestors in the outer document matches the selector.

E.g. :host-context(.dark-theme) matches only if there’s dark-theme class on <custom-dialog> on anywhere above it:

To summarize, we can use :host-family of selectors to style the main element of the component, depending on the context. These styles (unless !important) can be overridden by the document.

Styling slotted content

Now let’s consider the situation with slots.

Slotted elements come from light DOM, so they use document styles. Local styles do not affect slotted content.

In the example below, slotted <span> is bold, as per document style, but does not take background from the local style:

The result is bold, but not red.

If we’d like to style slotted elements in our component, there are two choices.

First, we can style the <slot> itself and rely on CSS inheritance:

Here <p>John Smith</p> becomes bold, because CSS inheritance is in effect between the <slot> and its contents. But in CSS itself not all properties are inherited.

Another option is to use ::slotted(selector) pseudo-class. It matches elements based on two conditions:

  1. That’s a slotted element, that comes from the light DOM. Slot name doesn’t matter. Just any slotted element, but only the element itself, not its children.
  2. The element matches the selector.

In our example, ::slotted(div) selects exactly <div slot='username'>, but not its children:

Please note, ::slotted selector can’t descend any further into the slot. These selectors are invalid:

Also, ::slotted can only be used in CSS. We can’t use it in querySelector.

CSS hooks with custom properties

How do we style internal elements of a component from the main document?

Selectors like :host apply rules to <custom-dialog> element or <user-card>, but how to style shadow DOM elements inside them?

There’s no selector that can directly affect shadow DOM styles from the document. But just as we expose methods to interact with our component, we can expose CSS variables (custom CSS properties) to style it.

Custom CSS properties exist on all levels, both in light and shadow.

For example, in shadow DOM we can use --user-card-field-color CSS variable to style fields, and the outer document can set its value:

Then, we can declare this property in the outer document for <user-card>:

Custom CSS properties pierce through shadow DOM, they are visible everywhere, so the inner .field rule will make use of it.

Here’s the full example:

Summary

Shadow DOM can include styles, such as <style> or <link>.

Local styles can affect:

Web Components Slots Without Shadow Dom

  • shadow tree,
  • shadow host with :host-family pseudoclasses,
  • slotted elements (coming from light DOM), ::slotted(selector) allows to select slotted elements themselves, but not their children.

Document styles can affect:

  • shadow host (as it lives in the outer document)
  • slotted elements and their contents (as that’s also in the outer document)

When CSS properties conflict, normally document styles have precedence, unless the property is labelled as !important. Then local styles have precedence.

Slots Without Shadow Dominus

CSS custom properties pierce through shadow DOM. They are used as “hooks” to style the component:

Slots Without Shadow Domain

  1. The component uses a custom CSS property to style key elements, such as var(--component-name-title, <default value>).
  2. Component author publishes these properties for developers, they are same important as other public component methods.
  3. When a developer wants to style a title, they assign --component-name-title CSS property for the shadow host or above.
  4. Profit!