Re: hgroup: a possible alternative

What about this :

<section>
  <hgroup>
    <h1>Search</h1>
    <h2>By City</h2>
  </hgroup>
   ... instructions and search form...
</section>

<section>
  <hgroup>
    <h1>Search</h1>
    <h2>By Zip Code</h2>
  </hgroup>
    ... instructions and search form...
</section>

There are of course other / better ways to markup this, but I don't see
anything wrong (yet) with this markup. Search can conceivably be seen as a
higher level than the h2 and is repeated for readability (depending on the
interface). The h2 should stay in the outline and is not a sub heading. The
two heading might be styled differently and are a group. If this kind of
markup is a good use case, then hgroup should continue to allow more than
one hx and keep them in the document outline. Even if not, I can imagine
people making this error.

-Benoit Piette

2011/1/12 Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>

> Dean Leigh, Wed, 12 Jan 2011 20:15:37 -0000:
> >>> -----Original Message-----
> >>> From: Leif Halvard Silli
> >
> >>>> I assume the next questions will be should we allow more than 1 <hx>
> >>>> within an <hgroup>?
> >>>
> >>> Doesn't fit with well with roles I proposed, to have more than hx.
> >
> > I agree - only 1 hx in <hgroup>
> >
> > Would you agree to allow multiple <sh> ?
>
> Bug 11737 [1] has taken that in from the very beginning: «Change
> content model of <hgroup> to single <hx> + zero or more <sh>
> (sub/suphead) elements».
>
> [1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=11737
> --
> leif halvard silli