- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Mon, 27 Dec 2010 22:33:40 +0100
- To: Lars Gunther <gunther@keryx.se>
- Cc: HTML WG <public-html@w3.org>
Lars Gunther on 27 Dec 2010 20:17:33 +0100 suggested:
> 2. Introduce an attribute:
> 3. Encourage usage of inline span elements
> the *content* issue. Even if it is stylable through CSS, the
> subtitle is not *hidden* from AT technologies, external parsers,
> etc. [...] A combination of 2 and 3 would solve that problem
>
> <h1>My terrific idea <span subtitle>How I saved HTML5 from
> being a mess</span></h1> [...]
3 issues:
1) Examples like this look messy:
<h1><span subtitle>A </span> B <span subtitle>C </span></h1>
2) Whitespace concatenation is left to author to handle:
<h1><span subtitle>A</span>B<span subtitle>C</span></h1>
3) Stray text/Split headings, like this:
<h1>A <span subtitle>B</span> C </h1>
All the above problems are solved by <hgroup>: the @subtitle variants
focuses on what is to be *eliminated* from the ToC algorithm. In
contrast, <hgroup> is focused on what *is* to be considered by the
algorithm as title. <hgroup> also avoids the problem of stray text.
<hgroup> also do not permit text directly inside itself - it has to be
placed in a heading element, thus the white space problme is avoided.
I believe an attribute solution must at the very least focus on the
element to be *included* in the algorithm, rather than on the ones to
be excluded, if it is to have a chance.
--
leif halvard silli
Received on Monday, 27 December 2010 21:34:19 UTC