13114 2011-07-01 13:37:09 +0000 nav element "typical default display properties" wrong 2011-07-06 18:48:20 +0000 1 1 1 Unclassified HTML WG HTML5: The Markup Language (editor: Michael(tm) Smith) unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 glund mike jackalmage public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 50556 0 glund 2011-07-01 13:37:09 +0000 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. i.e. nav { ... nav nav { ... nav nav nav { ... etc. 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. 50571 1 jackalmage 2011-07-01 19:22:40 +0000 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. 50633 2 mike 2011-07-04 08:37:00 +0000 Fixed now: http://dev.w3.org/cvsweb/html5/markup/nav.html.diff?r1=1.91;r2=1.92;f=h http://dev.w3.org/html5/markup/nav.html#nav-display Thanks for catching this. 50739 3 jackalmage 2011-07-06 18:48:20 +0000 Ah, durp, should have paid attention to the component; I was looking at the HTML spec's rendering section. Sorry for the noise.