This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11487 - Include example of using <nav> paragraph-like. I.e. with inline links as seen on annevankesteren.nl.
Summary: Include example of using <nav> paragraph-like. I.e. with inline links as seen...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-06 22:52 UTC by contributor
Modified: 2011-08-04 05:15 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2010-12-06 22:52:38 UTC 
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
Comment 1 Peter Winnberg 2010-12-07 05:38:47 UTC 
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?
Comment 2 Anne 2010-12-07 09:50:24 UTC 
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.
Comment 3 Ian 'Hixie' Hickson 2011-01-11 01:03:29 UTC 
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>.
Comment 4 Anne 2011-01-11 09:33:00 UTC 
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.)
Comment 5 Ian 'Hixie' Hickson 2011-02-11 23:11:22 UTC 
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.
Comment 6 contributor 2011-02-11 23:15:36 UTC 
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
Comment 7 Michael[tm] Smith 2011-08-04 05:15:01 UTC 
mass-move component to LC1