W3C home > Mailing lists > Public > public-html@w3.org > October 2011

[Bug 14519] New: consider to make <nav> a non-sectioning element

From: <bugzilla@jessica.w3.org>
Date: Thu, 20 Oct 2011 09:29:32 +0000
To: public-html@w3.org
Message-ID: <bug-14519-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14519

           Summary: consider to make <nav> a non-sectioning element
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: giorgio.liscio@email.it
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


hello, I think that <nav> should not be a sectioning element

for example:

<h1>Mysite222.org</h1>
<p>Welcome to my homepage</p>
<p>My interests are:</p>
<nav>
<ul>
<li><a href="#">Programming</a>, because I love logic and math</a></li>
<li><a href="#">Collecting beer cans</a>, because I love beer</a></li>
</ul>
</nav>

in practice, can be at the same time:

- a navigation list
- contextualized inside one expression

so I suggest to make <nav> a non sectioning element, in favor of

<section || aside>
<nav>non contextualized navigation (for sidebars, for example)</nav>
</section || aside>

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 20 October 2011 09:29:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:40 GMT