Admin interface CSS classes should be prefixed


I’m not sure if this is considered a bug, but I’ll report it here anyways.

I have run into the problem that the admin interface css crashes with the styles of the site I am implementing.
The example here is that I have a class, .button, on the site but is is getting some of the styles from the admin interface. This is only when editing of course but still a problem.

I would suggest that the admin interface styles are prefixed with your namespace, “enonic”, “xp” or some other thing. It would never prevent this perfectly, but using classes like .button without any nesting is very general for a system that has a preview like Enonic XP.

1 Like


I know that we have experienced similar issues earlier, I will make sure to inform the developers about it, and we will find a way to handle this.

1 Like