You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/going-buildless/css.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,7 +83,7 @@ The style rules which are ultimately applied to an element depend on all the rul
83
83
84
84
While the cascade is fundamental to CSS, and is certainly useful, it can at times make it more difficult to control the styles applied to a portion of a document. This is particularly important when designing reusable components, which should maintain their style no matter where they're used.
85
85
86
-
While a number of toolchains and techniques for achieving style encapsulation, like [BEM](http://getbem.com/introduction/) and [Styled Components](https://github.com/styled-components/styled-components), the web platform itself provides a native mechanism for isolating styles, called [Shadow DOM](https://www.w3.org/TR/shadow-dom/).
86
+
While a number of toolchains and techniques exist for achieving style encapsulation, like [BEM](http://getbem.com/introduction/) and [Styled Components](https://github.com/styled-components/styled-components), the web platform itself provides a native mechanism for isolating styles, called [Shadow DOM](https://www.w3.org/TR/shadow-dom/).
87
87
88
88
Isolating a portion of a document within a shadow root allows designers to write the CSS for that component without worrying about how their CSS will affect the rest of the document. Shadow DOM removes the need for complex CSS toolchains or naming conventions. Designers can use simple type, id, or class selectors, in that order.
0 commit comments