# Any plans to integrate CSS Cascade layers?

**URL:** https://meta.discourse.org/t/any-plans-to-integrate-css-cascade-layers/223950
**Category:** Development
**Created:** [April 11, 2022, 6:36pm UTC](https://meta.discourse.org/t/any-plans-to-integrate-css-cascade-layers/223950 "2022-04-11T18:36:20Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![keegan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/keegan/32/383395_2.png) [@keegan](https://meta.discourse.org/u/keegan)
#### Post date: [April 11, 2022, 6:36pm UTC](https://meta.discourse.org/t/any-plans-to-integrate-css-cascade-layers/223950/1 "2022-04-11T18:36:20Z")

</div>

CSS recently introduced the ability to define your own cascade layers, and it seems like it is gaining browser support. Hopefully will be available in all major browsers soon.

References:  
[https://developer.mozilla.org/en-US/docs/Web/CSS/@layer](https://developer.mozilla.org/en-US/docs/Web/CSS/@layer)  
[https://css-tricks.com/css-cascade-layers/](https://css-tricks.com/css-cascade-layers/)  
[https://www.youtube.com/watch?v=NDNRGW-\_1EE](https://www.youtube.com/watch?v=NDNRGW-_1EE)

Was curious to know whether this is being discussed to include in Discourse’s codebase?

I think it could be a great addition and could help with specificity difficulties and can also help us avoid using the `!important` flag.

Perhaps a set of layers could be defined in the main codebase. Perhaps something like:

```css
@layer base, layout, theme, utilities;

```

and theme developers can leverage the “theme” layer to easily add customizations without having to be so specific with selectors or use `!important` flags.

---

<div class="post-metadata">

### Author: ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [April 11, 2022, 6:47pm UTC](https://meta.discourse.org/t/any-plans-to-integrate-css-cascade-layers/223950/2 "2022-04-11T18:47:33Z")

</div>

This does seem like it would be useful, but we really have to wait for more established browser support (especially because I don’t think this has a reasonable fallback?). Most browsers have only added this in the past month… so I can’t imagine implementing it for at least another year.