# Plugin CSS takes priority over theme CSS?

**URL:** <https://meta.discourse.org/t/plugin-css-takes-priority-over-theme-css/144828>\
**Category:** Product Support\
**Created:** [March 19, 2020, 2:15pm UTC](https://meta.discourse.org/t/plugin-css-takes-priority-over-theme-css/144828 "2020-03-19T14:15:07Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [March 19, 2020, 3:37pm UTC](https://meta.discourse.org/t/plugin-css-takes-priority-over-theme-css/144828/8 "2020-03-19T15:37:14Z")

</div>

> [@WorldIsMine](#):
>
> Prior to 2.4 applying changes to theme CSS worked, so is this considered an unintentional bug?

Plugin CSS used to be all bundled up together, and loaded after the core stylesheets. So yes, this is an unintentional side-effect of us debundling it. I think we can backport this fix to stable, it is very low risk. I don’t think anyone will be relying on this behaviour.

Opened a PR here:

[https://github.com/discourse/discourse/pull/9240](https://github.com/discourse/discourse/pull/9240)

---

_[View the full topic](https://meta.discourse.org/t/plugin-css-takes-priority-over-theme-css/144828)._
