11487 2010-12-06 22:52:38 +0000 Include example of using <nav> paragraph-like. I.e. with inline links as seen on annevankesteren.nl. 2011-08-04 05:15:01 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-nav-element P3 normal --- 1 contributor ian annevk ian mike peter.winnberg public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 43108 0 contributor 2010-12-06 22:52:38 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html Section: http://www.whatwg.org/specs/web-apps/current-work/#the-nav-element Comment: Include example of using <nav> paragraph-like. I.e. with inline links as seen on annevankesteren.nl. Posted from: 95.34.115.33 by annevk@opera.com 43120 1 peter.winnberg 2010-12-07 05:38:47 +0000 I disagree. The contents of the nav element on annevankesteren.nl is a *list* of links so it should be using an appropriate element for representing lists. In fact, why is inline content even allowed in the nav element? 43125 2 annevk 2010-12-07 09:50:24 +0000 Everything is a list if you think too long about it. Paragraph-level navigation is perfectly acceptable. Especially inside a <nav> element as the only thing that matters inside <nav> are <a>s. 44082 3 ian 2011-01-11 01:03:29 +0000 I'm not sure the inline links on your blog make that much sense (consider how it would read if the style sheet were disabled), but I agree that I should add an example of non-list content in <nav>. 44131 4 annevk 2011-01-11 09:33:00 +0000 Even with style sheets disabled should the <nav> element not be enough of an indication what to expect from the contents? (Visually you would get three links after each other, not really problematic.) 45404 5 ian 2011-02-11 23:11:22 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 45405 6 contributor 2011-02-11 23:15:36 +0000 Checked in as WHATWG revision r5877. Check-in comment: example for nav of using inline links rather than a list http://html5.org/tools/web-apps-tracker?from=5876&to=5877 53554 7 mike 2011-08-04 05:15:01 +0000 mass-move component to LC1