.navbar conflict

  • flpetersen


    I’m not sure what the rules are for naming conventions, but after fussing with a few plugins that kept breaking the site, or not working, I discovered that the CSS reference to .navbar seems to be too common.

    The most recent conflict I found is Memphis Document Library.

    If I were to be honest, everyone (them and you) should likely have it named .xxx-navbar distinctly to your product: .mdl-navbar, .graphene-navbar and so on.

    Regardless, any way to fix this other than editing css code and disconnecting it from your theme updates?


    Syahir Hakim


    The reference to .navbar in Graphene is because of the Bootstrap framework that provides much of Graphene’s layout backbone. Changing the navbar class to something else means we’ll need to make changes in all the Bootstrap framework styles and scripts that refer to that class. This makes it more difficult to maintain compatibility across different versions of Bootstrap and other libraries developed for it.

Viewing 2 posts - 1 through 2 (of 2 total)

  • You must be logged in to reply to this topic.