Omega does a great job of using the HTML5 semantic elements, but there are some times where it's just not possible for Omega to determine the semantic content, and therefore just uses a generic div. For instance, putting a menu block into a region should wrap the ul in nav, but since Omega doesn't know that it's a navigation menu, it renders a generic div. Simply allowing which wrapper tag to use would solve everything.

Comments

Argus’s picture

Just like the Semantic Views approach. +1

Didn't I see a place to add tags? I will have to check when I get home.

Ryan258’s picture

If you want somewhat of a hacky work around I usually just forego using menus, build out the html in an editor, create a block, paste it in. Typically I'm building menus that have to be precise so the end user isn't going to be adding new menu links because the css that's going on pretty much wouldn't allow for it. At least this way you can put in that nav tag you've always wanted :)

Anonymous’s picture

Another workaround is to copy the block.tpl.php found in the original omega templates folder, put it in your subtheme's templates folder, rename it to match your block and change the first line to:

$tag = 'nav';

If you're using http://drupal.org/project/menu_block to output your menus you can simply rename the template file to block--menu-block.tpl.php and all your menu blocks will have the nav wrapper.

apaderno’s picture

Version: 7.x-3.0 » 7.x-5.x-dev
Component: Feature Request » Code
Issue summary: View changes