12442 2011-04-07 00:28:20 +0000 I think that for the first level of article h1 {�}, the size should be left as normal. 2011-08-23 05:04:16 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#fonts-and-colors P3 normal --- 1 contributor ian cyberskull ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 47222 0 contributor 2011-04-07 00:28:20 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html Section: http://www.whatwg.org/specs/web-apps/current-work/#fonts-and-colors Comment: I think that for the first level of article h1 {…}, the size should be left as normal. For example, If I start my article immediately after the body then I would put an h1 in with the title of the document on the page, often followed by an h2 with a subtitle or author. Since I would be using h2s for the subsections of the article (h3s for sub-subsections, etc), I would want a difference in the sizes of the headers to differentiate sections to the reader. If I had a long document with several articles in it (sequential, not nested) I think this h1 being the size of an h2 would add confusion to what precisely is nested. Posted from: 71.198.1.49 User agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_5_8; en-us) AppleWebKit/533.20.25 (KHTML, like Gecko) Version/5.0.4 Safari/533.20.27 47223 1 cyberskull 2011-04-07 00:30:38 +0000 A little cleanup of my comment: I think that for the first level of article h1 {}, the size should be left as normal. For example, If I start my article immediately after the body then I would put an h1 in with the title of the document on the page, often followed by an h2 with a subtitle or author. Since I would be using h2s for the subsections of the article (h3s for sub-subsections, etc), I would want a difference in the sizes of the headers to differentiate sections to the reader. If I had a long document with several articles in it (sequential, not nested) I think this h1 being the size of an h2 would add confusion to what precisely is nested. I should clarify, that I think shrinking an h1 in a nav, section or aside is fine. But just not in an article. 50959 2 ian 2011-07-13 07:13:42 +0000 But then how would you distinguish the header of the articles from the header of the page? 51000 3 cyberskull 2011-07-14 07:04:51 +0000 (In reply to comment #2) > But then how would you distinguish the header of the articles from the header of the page? Simply, make an h1 inside of an article slightly smaller than an h1 outside of an article, but still larger than an h2. 51130 4 ian 2011-07-15 18:39:51 +0000 That would mean that this: <body> <h1>My blog</h1> ... <h2>My post</h2> ... <h3>My subsection</h3> ... </body> ...would have different results than this: <body> <h1>My blog</h1> ... <article> <h1>My post</h1> ... <section> <h1>My subsection</h1> ... </section> </article> </body> ...despite having the same semantics. That doesn't really make sense. The simpler solution is to just only use <h1>, like in the second example above, instead of mixing both styles. Or, use CSS to make sure the headers work as you want them to. 53561 5 mike 2011-08-04 05:15:08 +0000 mass-move component to LC1 54939 6 ian 2011-08-14 06:56:02 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: see comment 4 55168 7 cyberskull 2011-08-16 03:41:08 +0000 (In reply to comment #4) > That would mean that this: > > <body> > <h1>My blog</h1> > ... > <h2>My post</h2> > ... > <h3>My subsection</h3> > ... > </body> > > ...would have different results than this: > > <body> > <h1>My blog</h1> > ... > <article> > <h1>My post</h1> > ... > <section> > <h1>My subsection</h1> > ... > </section> > </article> > </body> > > ...despite having the same semantics. That doesn't really make sense. > > > The simpler solution is to just only use <h1>, like in the second example > above, instead of mixing both styles. Or, use CSS to make sure the headers work > as you want them to. I'd rather not fiddle with header styles except in the broadest cases (setting the basic styles for the site). Besides, In the example you cite above they are not semantically identical, wrapping the content in article and section tags changes the semantics of the document. I think it is simplest if an H1 is always larger than an H2. 55652 8 ian 2011-08-23 05:04:16 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: Having <h1> be the automatically-sizing element is an intentional design decision intended to make <h2>-<h6> irrelevant. Authors should either use <section> and <h1> only (not <h2>-<h6>), or use <h1>-<h6> only (no sectioning elements), or be prepared to style the elements carefully in CSS.