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 23252 - Using list markup inside <nav>, misleading example in 4.4.4
Summary: Using list markup inside <nav>, misleading example in 4.4.4
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: CR
Depends on:
Blocks:
 
Reported: 2013-09-16 10:23 UTC by Jukka K. Korpela
Modified: 2014-01-16 15:12 UTC (History)
4 users (show)

See Also:


Attachments

Description Jukka K. Korpela 2013-09-16 10:23:31 UTC
In "4.4.11 Usage summary", the example on <nav> contains three <p> elements, each containing only one <a> element:

<nav>
 <p><a href="/">Home</a>
 <p><a href="/biog.html">Bio</a>
 <p><a href="/discog.html">Discog</a>
</nav>

I think this violates the recommendation in "4.4.4 The |nav| element": "In cases where the content of a |nav <http://www.w3.org/TR/html5/sections.html#the-nav-element>| element represents a list of items, use list markup to aid understanding and navigation."

If the example is supposed to present breadcrumb navigation (which might be regarded as something else than a list), then this should be clarified. 

Otherwise, please change the example to the following:

<nav>
 <ul>
   <li><a href="/">Home</a>
   <li><a href="/biog.html">Bio</a>
   <li><a href="/discog.html">Discog</a>
 </ul>
</nav>
Comment 1 github bugzilla bot 2013-09-16 14:46:58 UTC
Commits pushed to master at https://github.com/w3c/html

https://github.com/w3c/html/commit/4febd84d46d25c447afdd69837d7240fa605f469
Fix bug 23252: Use <ul> for <nav> usage example instead of <p>s.

https://github.com/w3c/html/commit/5023d1206da43cf9f7cfdda93e157a4ba9a4313e
Merge pull request #15 from Osmose/fix-bug-23252

Fix bug 23252: Use <ul> for <nav> usage example instead of <p>s.
Comment 2 steve faulkner 2013-09-16 15:18:38 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: added list markup
Rationale: agreed with commenter
Comment 3 github bugzilla bot 2014-01-16 15:10:38 UTC
Commits pushed to CR at https://github.com/w3c/html

https://github.com/w3c/html/commit/4febd84d46d25c447afdd69837d7240fa605f469
Fix bug 23252: Use <ul> for <nav> usage example instead of <p>s.

https://github.com/w3c/html/commit/5023d1206da43cf9f7cfdda93e157a4ba9a4313e
Merge pull request #15 from Osmose/fix-bug-23252