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 9474 - Renaming hgroup to h would be better (like XHTML2), so we can deprecate 'h*' in the future without the "group" sounding strange
Summary: Renaming hgroup to h would be better (like XHTML2), so we can deprecate 'h*' ...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-10 04:50 UTC by contributor
Modified: 2010-10-04 14:28 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2010-04-10 04:50:51 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-hgroup-element

Comment:
'h’ would be better (like XHTML2), so we can deprecate 'h*' in the future
without the "group" sounding strange

Posted from: 90.136.87.139
Comment 1 Ms2ger 2010-04-11 11:35:59 UTC 

*** This bug has been marked as a duplicate of bug 9265 ***
Comment 2 Christoph P 2010-04-13 10:09:01 UTC 
Renaming hgroup to h is similar to, but not the same as adding h to the group of h1 through h6 (which is bug 9265). I think it has been discussed in the mailing lists, though, and wasnt accepted.
Comment 3 Ian 'Hixie' Hickson 2010-04-13 22:08:03 UTC 
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: We have <h> already, it's just spelt <h1>. Using <h1> rather than <h> has the benefit that it is backwards-compatible with legacy UA renderings.
Comment 4 Christoph P 2010-04-14 07:36:55 UTC 
No, this request was about *renaming* hgroup to h, not *adding* h.

One (at least I) wouldnt nest h1 inside h1:

  <h1><h1>Heading</h1><h2>Subheading</h2></h1>

instead of

  <hgroup><h1>Heading</h1><h2>Subheading</h2></hgroup>

since we wouldnt need hgroup then at all. The proposed alternative was this:

  <h><h1>Heading</h1><h2>Subheading</h2></h>

Unlike h, current hgroup with only text-node children would be awkward, because it didnt group h*.

  <hgroup>Heading</hgroup>
  <h>Heading</h>
Comment 5 Ms2ger 2010-04-14 08:24:42 UTC 
(In reply to comment #4)
> The proposed alternative was this:
> 
>   <h><h1>Heading</h1><h2>Subheading</h2></h>
> 
> Unlike 'h', current 'hgroup' with only text-node children would be awkward,
> because it didn't 'group h*'.
> 
>   <hgroup>Heading</hgroup>
>   <h>Heading</h>

That's the point. The element is meant to 'group h*'. The fact that 'hgroup' with only text-node children would be awkward, is actually a very good argument *against* renaming it.

I don't understand why you want to rename it.