This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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>
Your example use is probably a misuse of <nav>. <nav> is intended for the primary navigation on the page. It's not meant for any random block of navigation links.
yes, but as I've tried to say, a navigation list can be also part of a phrase
What problem does this solve? You don't _have_ to use <nav>. Why would you use it for inline stuff? The whole point of <nav> is to provide a hint to accessibility tools that the block is a section that can be skipped unless the user wants navigation, and a hint to outline creators that this is a section. I don't see why you'd use <nav> in your example at all.
ok I have thought it through. Now I agree sorry! I'm closing