As per title, discussion and changes are probably going to pend on use of the new HTML5 elements such as <section> and <nav>. There could be a case here for the inclusion of a block--menu.tpl.php in core that uses the <nav> element as opposed to the <section> element.

Comments

zachattack’s picture

zachattack commented

Jeff,

Would a third template need to be introduced for the tag?
The spec mentions it for the purpose of having tools that are functional. What do you think?

Jeff Burnz’s picture

Jeff Burnz commented

There's some discussion heating up over the way in which to handle wrapping elements, right now I'm not sure how that is going to pan out - could be that templates are content or module aware and we use a dynamic wrapper, or that we set a sensible default (div) and have a UI for changing it - quite possibly it could be both. So I can't really answer that right now, it could be that for now block.tpl.php stays exactly how it is.

barbi’s picture

barbi commented

subscribe

jessebeach’s picture

jessebeach commented
Status: Active » Needs review
Issue tags: +html5

Blocks are way too generic to make a generic assertion about semantics. Barring a more comprehensive solution for determining wrapping elements through the UI (which should probably be hashed out in contrib first), I vote we close this issue as considered and won't fix.

jessebeach’s picture

jessebeach commented
Assigned: Unassigned » jessebeach
Status: Needs review » Closed (won't fix)

The HTML, as it stands in this template, is adequate for the purposes of the HTML5 initiative.

It was noted that this issue might be reopened pending work by the WSCCI initiative if ever we can vary the markup according to the context of the block's environment. Until then, we're mothballing this issue.