# CSS admin-contents reloaded

**URL:** <https://meta.discourse.org/t/css-admin-contents-reloaded/25480>\
**Category:** Feature\
**Created:** [21. Februar 2015 um 12:15 UTC](https://meta.discourse.org/t/css-admin-contents-reloaded/25480 "2015-02-21T12:15:57Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![JSey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jsey/32/3540_2.png) [@JSey](https://meta.discourse.org/u/JSey)\
**Post date:** [21. Februar 2015 um 12:15 UTC](https://meta.discourse.org/t/css-admin-contents-reloaded/25480/1 "2015-02-21T12:15:57Z")

</div>

Continuing the discussion from [CSS Clearfix for `admin-contents`](https://meta.discourse.org/t/css-clearfix-for-admin-contents/25424/9):

> [@CSS Clearfix for \`admin-contents\`](https://meta.discourse.org/t/css-clearfix-for-admin-contents/25424/9):
>
> I just pushed a fix that will **automagically** disable custom stylesheets when you’re entering the `/admin` section and enable them back when you’re leaving it 💐

I appreciate the idea, but (risking to sound nit-picky) dislike the result for my site: if you have HTML additions which rely on styles which now become automatically disabled, you end up with garbled admin pages - could this become an optional setting (I wouldn’t mind if it defaulted to “off” for the discussed security reasons)? The alternative looks a bit appalling to me, to put all the styles for the HTML customizations as inline CSS…

---

_[View the full topic](https://meta.discourse.org/t/css-admin-contents-reloaded/25480)._