Auto-Nav Block Overlapping Content in Design Mode
Permalink Browser Info Environment
In design mode the auto-nav lays out menu items vertically, and as I've added more items it gets longer and longer. It's probably about 800px now, and it's gotten where on a new page I have to delete the auto-nav to add the content items then add it back in from the clipboard. I've attached a screenshot.
Type: | Ticket |
---|---|
Status: | In Progress |
Sorry, I forgot about this until I needed to use it again. The live site ishttp://teaglu.com , and yes it only shows up in edit mode. I'm trying now to go through the inspector to see the difference between the working and non-working modes.
Edit: OK more progress. The <div class="navbar-collapse collapse custom-nav-class"> is not picking up the custom-nav-class in edit mode - spiking that class on the node in inspector seems to restore everything to the normal display, except the menus stay popped out.
As far as the menus staying popped out, the UL's under the top menu items appear to pick up their "display: none;" from ".navcontrol .custom-nav-class>.nav ul" in main.css. When you put C5 in edit mode it seems to put a bunch of "stuff" in the hierarchy so that the .custom-nav-class and .nav are no longer parent-child.
Getting rid of the ">" in main.css might do the trick but I'm not sure what else it would break, and it might come from one of those CSS compilers. And it's possible I'm reading the CSS wrong.
Edit: OK more progress. The <div class="navbar-collapse collapse custom-nav-class"> is not picking up the custom-nav-class in edit mode - spiking that class on the node in inspector seems to restore everything to the normal display, except the menus stay popped out.
As far as the menus staying popped out, the UL's under the top menu items appear to pick up their "display: none;" from ".navcontrol .custom-nav-class>.nav ul" in main.css. When you put C5 in edit mode it seems to put a bunch of "stuff" in the hierarchy so that the .custom-nav-class and .nav are no longer parent-child.
Getting rid of the ">" in main.css might do the trick but I'm not sure what else it would break, and it might come from one of those CSS compilers. And it's possible I'm reading the CSS wrong.
Can you send me the link to your live site? Is this issue only a problem on edit mode?
James