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 13114 - nav element "typical default display properties" wrong
Summary: nav element "typical default display properties" wrong
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5: The Markup Language (editor: Michael(tm) Smith) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael[tm] Smith
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2011-07-01 13:37 UTC by George Lund
Modified: 2011-07-06 18:48 UTC (History)
3 users (show)

See Also:


Description George Lund 2011-07-01 13:37:09 UTC
The CSS suggested for the nav element is wrong.

Presumably the intention is that nested nav element should get smaller. The commas separating the element name should not be there, in that case they should be space-separated.

nav { ...
nav nav { ...
nav nav nav { ...

Also, using ems like this is a bit weird. Nav elements inside nav elements get even larger (i.e. 1.17 x 1.5) and then the same size (i.e. 1 x 1.17 x 1.5) and then a little smaller (.83 x 1.17 x 1.5). ems don't look back to the outside parent as this example suggests. A single rule: nav { font-size: smaller; } might in fact sum up what you're trying to do here?

I can't actually see the use case for nesting nav elements, so I have no idea why this is a sensible presentation suggestion anyway!

It would certainly be best if screen browsers didn't have any default presentation other than display: block for nav elements, otherwise it will be very difficult for authors to predictably use this element given the cascade.
Comment 1 Tab Atkins Jr. 2011-07-01 19:22:40 UTC
What part of the spec are you referring to?  There is nothing similar to what you're suggesting anywhere in the Rendering chapter that I can find.
Comment 3 Tab Atkins Jr. 2011-07-06 18:48:20 UTC
Ah, durp, should have paid attention to the component; I was looking at the HTML spec's rendering section.  Sorry for the noise.