# HTML Customizations mistakenly applied to admin views?
**URL:** https://meta.discourse.org/t/html-customizations-mistakenly-applied-to-admin-views/26228
**Category:** Bug
**Created:** [March 11, 2015, 6:53pm UTC](https://meta.discourse.org/t/html-customizations-mistakenly-applied-to-admin-views/26228 "2015-03-11T18:53:12Z")
**Posts on this page:** 1
**Showing post:** 2
### Author:  [@elberet](https://meta.discourse.org/u/elberet)
#### Post date: [March 12, 2015, 10:17am UTC](https://meta.discourse.org/t/html-customizations-mistakenly-applied-to-admin-views/26228/2 "2015-03-12T10:17:39Z")
There was a bit of a discussion the other day regarding customizations in `/admin` and the disabling thereof, but I do believe that we’ve reverted back to the old way with full customizations when entering admin through the frontend and no customizations at all when entering admin directly (or refreshing the page):
> [@CSS admin-contents reloaded](https://meta.discourse.org/t/css-admin-contents-reloaded/25480/19):
>
> Yeah … this whole change is just causing too much confusion, we should revert to the old way we did this. Apply everywhere, remove if you refresh admin.
---
_[View the full topic](https://meta.discourse.org/t/html-customizations-mistakenly-applied-to-admin-views/26228)._