On Feb 8, 2011, at 2:33 PM, Jukka K. Korpela wrote: > I still haven't found a statement in HTML5 drafts saying that <header> must, > or even should, be treated as having display: block by default, even though I > intuitively expect it to be treated that way.
One can infer it from the prose: http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#sectioning-root The Rendering (presentation) section is formal: http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html#display-types For Gecko 2.0b, it is specified in the UA stylesheet: http://mxr.mozilla.org/mozilla-central/source/layout/style/html.css Compare to the UA stylesheet for Gecko 1.9.2 (fx 3.6): http://mxr.mozilla.org/mozilla1.9.2/source/layout/style/html.css (or load: resource://gre-resources/html.css) For current WebKit: http://trac.webkit.org/browser/trunk/WebCore/css/html.css?rev=73613 > But this is just yet another reason for explicitly setting its display > property: > > ... > The same seems to apply to the other new block-like elements in HTML5: > article, aside, footer, hgroup, nav, section should all have display: block > in an author's style sheet if he uses them (unless, of course, he has a > special reason to have them rendered otherwise). Indeed. Philippe --- Philippe Wittenbergh http://l-c-n.com/ ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
