14481 2011-10-17 13:58:36 +0000 There should be a h element because h1..h6 imply semantics of level which are misleading when using nested sections. Btw.: I liked XHTML 2.0 much better than this stuff. Honestly, it's crap. 2011-10-18 08:43:00 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor ian jackalmage lrosenth mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 58289 0 contributor 2011-10-17 13:58:36 +0000 Specification: http://dev.w3.org/html5/spec/Overview.html Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: There should be a h element because h1..h6 imply semantics of level which are misleading when using nested sections. Btw.: I liked XHTML 2.0 much better than this stuff. Honestly, it's crap. Posted from: 193.108.184.61 User agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1 58311 1 jackalmage 2011-10-17 23:07:38 +0000 <h> has no backwards-compatibility. It's meaningless in old browsers. You can treat <h1> as <h> and use <section>s, or use <section>s and the full range of <h1>-<h6> to get full back-compat as well. 58329 2 zcorpan 2011-10-18 08:43:00 +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 1