# Inconsistent body class for /admin paths? (disabling top navigation)

**URL:** <https://meta.discourse.org/t/inconsistent-body-class-for-admin-paths-disabling-top-navigation/60694>\
**Category:** Product Support\
**Created:** [9 Abril, 2017 22:44 UTC](https://meta.discourse.org/t/inconsistent-body-class-for-admin-paths-disabling-top-navigation/60694 "2017-04-09T22:44:22Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**Post date:** [10 Abril, 2017 18:41 UTC](https://meta.discourse.org/t/inconsistent-body-class-for-admin-paths-disabling-top-navigation/60694/7 "2017-04-10T18:41:45Z")

</div>

> [@sam](#):
>
> For a very very long time, we disabled all customizations on first load for /admin path.

I realized my post might not have been clear. I’m 100% in favor of not using custom CSS or JS when looking at any `/admin` path - I was just trying to clarify that I’ve noticed inconsistency too.

---

_[View the full topic](https://meta.discourse.org/t/inconsistent-body-class-for-admin-paths-disabling-top-navigation/60694)._
