Web Component Style Encapsulation In 5 Minutes

jmckenney — Sun, 10 Mar 2019 02:14:15 +0000

The Problem

Since the dawn of the data webs (well, shortly after the dawn), every ui element was governed solely and entirely by one overarching style cascade. What happens when you want to carefully protect an area of your UI from css overrides?

The Solution

Shadow DOM. Shadow DOM touches on many topics under the umbrella of web components and also provides JS encapsulation. Today we are going to hone in on a few key aspects of style encapsulation.

Custom elements by themselves provide only a minimal amount of change from the historic methods of styling. In the following example you will see that because a custom element is unique in name, a style author can utilize the custom element quote/unquote namespace to provide a healthy amount of specificity to custom styling thereby offering a minimal amount of protection from css overrides.

As you can see, the p styling was overrideen by the parent-element p styling. Please take note that lit-element enables Shadow DOM by default and the example above disabled that via the createRenderRoot() override. This enabled us to utilize lit-element while still showing a Custom Element without Shadow DOM enabled.

The Big Reveal

Now we get our example of style encapsulation.

A few questions may come to mind after looking at this example:

Why does it say Hello World rather than the template's string of Style me carefully?

The answer is due to the magic of slots. Notice how the browser treats this area somewhat like a symlink in linux file systems. Though the node lives inside the shadow root, the content and styles reference the link back in the light DOM.

Why are we able to style the slotted content from outside, but we are unable to style the content existing inside the Shadow DOM that doesn't reference slotted content?

Shadow DOM protects, slots allow for styling. This is starting to get fun.

The Styling API

Now we have this clean and beautiful specification that allows us to continue composing html elements together while simultaneously encapsulating styles. I have to hand it to the specification creators for browsers. This had to have taken a lot of forethought and creativity.

In the event that the author of the encapsulated area wants to allow branding and some styling to be brought in from the outside, the spec has options for this as demonstrated below.

In the next article I'll discuss how web components also provide a way to encapsulate JavaScript. Keep a look out for a video walkthrough of this article.

Credit Where Credit Is Due

https://gist.github.com/praveenpuglia/0832da687ed5a5d7a0907046c9ef1813

Web Component Course Brainstorming

jmckenney — Thu, 28 Feb 2019 14:41:11 +0000

It has begun.

Web Components, Overview, Ep. 1

jmckenney — Sat, 02 Feb 2019 17:54:51 +0000

Bootcamp Grad Interview - Was it Worth it?

jmckenney — Mon, 10 Dec 2018 15:28:55 +0000

Firebase and Jest Testing, Episode 3

jmckenney — Tue, 06 Nov 2018 03:38:14 +0000

Firebase + Jest Testing Episode 2

jmckenney — Wed, 31 Oct 2018 04:33:53 +0000

Brian and Josh take the next step in adding Jest unit tests to a Firebase web app.

Jest testing with a hernia

jmckenney — Mon, 22 Oct 2018 15:19:13 +0000

Josh and Brian cover the basics of adding tests to a small app that was put together quickly as an experiment.

Forem: jmckenney