View Encapsulation in Angular

View Encapsulation in Angular defines how the styles defined in the template affect the other parts of the application. The angular uses three strategies while rendering the view ViewEncapsulation.Emulated, ViewEncapsulation.ShadowDOM and ViewEncapsulation.None This article describes what is View Encapsulation using an example and how it is implemented in angular. We also learn what is shadow dom in Angular.

Component Styles in Angular

Angular allows us the specify component-specific styles. This is done by specifying either inline-style styles: or using the external style sheet styleUrls: in the @Component decorator or @directive decorator.

Example of External Style sheet

Example of Inline style

The CSS Styles have global scope. CSS rules apply to the entire document. You cannot apply rules to the part of the document. Hence, we use class, id & CSS specificity rules to ensure that the styles do not interfere with each other

In the case of Angular apps, the components co-exist with the other components. Hence it becomes very important to ensure that the CSS Styles specified in one component do not override the rules in another component.

Angular does this by using the View Encapsulation strategies

What is View Encapsulation?

One of the fundamental concepts in object-oriented programming (OOP) is Encapsulation. It defines the idea that all the data and methods that operate on that data are kept private in a single unit (or class). It is like hiding the implementation detail from the outside world. The consumer of encapsulated object know that it works but does not know how it works.

The View Encapsulation in Angular is a strategy that determines how angular hides (encapsulates) the styles defined in the component from bleeding over to the other parts of the application.

The following three strategies are provided by Angular to determine how styles are applied.

• ViewEncapsulation.None
• ViewEncapsulation.Emulated
• ViewEncapsulation.ShadowDOM

The viewEncapsulation Native is deprecated since Angular version 6.0.8, and is replaced by viewEncapsulation ShadowDom

Adding View Encapsulation to components

The Encapsulation methods are added using the encapsulation metadata of the @Component decorator as shown below

ViewEncapsulation.Emulated is the default encapsulation method.

Example Application

Create an angular application using the

app.component.ts

Code

Open the app.component.html

open the src/styles.css and the following CSS

Run the app and you should able to see the paragraph in green.

Open the chrome developer tools and check the elements section. The CSS rules are inserted in the head section of the page

ViewEncapsulation.None

The ViewEncapsulation.None is used, when we do not want any encapsulation. When you use this, the styles defined in one component affect the elements of the other components.

Now, let us look at ViewEncapsulation.None does.

Create a new component ViewNoneComponent and add the following code.

Code

We have added encapsulation: ViewEncapsulation.None. We have also defined the inline style p { color:blue}

Do not forget to import & declare the component in AppModule. You also need to add the <app-none></app-none> selector in app.component.html

Run the code and as expected both the paragraphs turn blue.

That is because of the global scope of CSS styles. The style defined in the ViewNoneComponent is injected into the global style and overrides any previously defined style. The style p {color: blue;} overrides the style p {color: green;} defined in the styles.css.

The important points are

• The styles defined in the component affect the other components
• The global styles affect the element styles in the component

ViewEncapsulation.Emulated

In an HTML page, we can easily add a id or a class to the element to increase the specificity of the CSS rules so that the CSS rules do not interfere with each other.

The ViewEncapsulation.Emulated strategy in angular adds the unique HTML attributes to the component CSS styles and to the markup so as to achieve encapsulation. This is not true encapsulation. The Angular Emulates the encapsulation, Hence the name Emulated.

If you do not specify encapsulations in components, the angular uses the ViewEncapsulation.Emulated strategy

Create a new component in the Angular app and name it as ViewEmulatedComponent. as shown below

Code

We have not added any id in the above component. The only change this component has with one ViewNoneComponent was encapsulation mode, which is set to ViewEncapsulation.Emulated

Update app.component.html

Now, you can see that the style does not spill out to other components when you use emulated mode. i.e because angular adds _ngcontent-c# attributes to the emulated components and makes necessary changes in the generated styles

You can see this by opening the chrome developer console

_ngcontent-c2 attribute is added to the style and to the p element, making the style local to the component

The important points are

• This strategy isolates the component styles. They do not bleed out to other components.
• The global styles may affect the element styles in the component
• The Angular adds the attributes to the styles and marks up

ViewEncapsulation.ShadowDOM

The Shadow DOM is a scoped sub-tree of the DOM. It is attached to an element (called shadow host) of the DOM tree. The shadow dom does not appear as a child node of the shadow host when you traverse the main DOM.

The browser keeps the shadow DOM separate from the main DOM. The rendering of the Shadow dom and the main DOM happens separately. The browser flattens them together before displaying them to the user. The feature, state & style of the Shadow DOM stays private and are not affected by the main DOM. Hence it achieves true encapsulation.

To create shadow dom in angular , all we need to do is to add the ViewEncapsulation.ShadowDom as the encapsulation strategy.

Create a new component ViewShadowdomComponent and add the following code

The component renders as follows

The angular renders the component inside the #shadow root element. The styles from the component along with the styles from the parent and other components are also injected inside the shadow root

Shadow dom terminology

The app-shadowdom is the CSS selector in the ViewShadowdomComponent. We used it in our app-component.html. The Angular renders component as shadow dom and attaches it to the app-shadowdom selector. Hence, we call the element as Shadow host

The Shadow DOM starts from #shadow-root element. Hence, we call this element as shadow root. The Angular injects the component into the shadow root.

The Shadow boundary starts from the #shadow-root. The browser encapsulates everything inside this element including the node #shadow-root

The shadow dom archives the true encapsulation. It truly isolates the component from the styles from the other parts of the app.

The styles from the parent component & sibling components are still injected into the shadow dom. but that is an angular feature. The angular wants the component to share the parent & sibling styles. Without this the component may look out of place with the other component

The important points are

• The shadow dom achieves the true encapsulation
• The parent and sibling styles still affect the component. but that is angular’s implementation of shadow dom
• The shadow dom not yet supported in all the browsers. You can check it from the this link.

Summary

We learned what view encapsulation is and how to make use of the three different view encapsulation strategies. i.e. None, Emulated & ShadowDOM. In the next tutorial, we shall look into how to style an Angular Component.