# Ensure admin isn't messed up by customizations

**URL:** https://meta.discourse.org/t/ensure-admin-isnt-messed-up-by-customizations/33747
**Category:** Feature
**Created:** [September 25, 2015, 1:56pm UTC](https://meta.discourse.org/t/ensure-admin-isnt-messed-up-by-customizations/33747 "2015-09-25T13:56:19Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![calmh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/calmh/32/115466_2.png) [@calmh](https://meta.discourse.org/u/calmh)
#### Post date: [September 25, 2015, 2:19pm UTC](https://meta.discourse.org/t/ensure-admin-isnt-messed-up-by-customizations/33747/9 "2015-09-25T14:19:15Z")

</div>

Ah, this is a duplicate.

> [@CSS admin-contents reloaded](https://meta.discourse.org/t/css-admin-contents-reloaded/25480):
>
> Continuing the discussion from [CSS Clearfix for admin-contents](https://meta.discourse.org/t/css-clearfix-for-admin-contents/25424/9): 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 inli…

---

_[View the full topic](https://meta.discourse.org/t/ensure-admin-isnt-messed-up-by-customizations/33747)._