Menu blocks are defined within nav tags, in the template file \themes\mayo\templates\block--system-menu-block.html.twig the closing nav is missing. This causes menu blocks to nest everything defined after in the same region - other menus, blocks, etc.

CommentFileSizeAuthor
1.jpg39.17 KBxevina
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

xevina created an issue. See original summary.

mermentau’s picture

The closing </nav> is there but it's furnished by the template that contains the output of \themes\mayo\templates\block--system-menu-block.html.twig. Using Firebug I can see it. I would need to know the set up you used to get that image to explore further.

xevina’s picture

Fresh install of Drupal 8.0.2, Mayo as theme, nothing else there. The problem seems to present only when menus are placed in sidebar first and second, not in the columns or footer.

johnc_uk’s picture

Similar issues - I don't understand it, but in case it helps someone identify the issue.

Setup used:
Core 8.0.4
Taxonomy menu 8.x-3.1+1-dev (2016-Jan-14)
MAYO 8.x-1.1

Sidebar 1 Custom text block and system tools menu (or any config I have tried) = nesting of blocks
Sidebar 2 Custom text block and system tools menu = no nesting of blocks
Sidebar 2 Menu produced by Taxonomy Menu and any other block = nesting of blocks

As far as I can tell in both cases closing Nav tags are there, but for some reason the 2nd (and other) blocks are being introduced before the closing tag of the first block

  • mermentau committed d11b026 on 8.x-1.x
    #2652536 menu blocks nav tags not closed
    
mermentau’s picture

Looks like there was a closing missing in block--system-menu-block.html.twig. Committed to 8.x-1.x-dev.
Please test.

mermentau’s picture

Status: Active » Closed (fixed)