Re: itemheader names <h>

On Tue, Sep 22, 2009 at 8:18 PM, Tab Atkins Jr. <> wrote:
> On Tue, Sep 22, 2009 at 7:08 PM, Jim Jewett <> wrote:
>> On Tue, Sep 22, 2009 at 6:17 PM, Tab Atkins Jr. <> wrote:
>>> I am absolutely certain that you will see <h> rampantly misused to replace <h*>.
>> Is this a problem?
> Given the current spec text (where <h> is not a heading), yes.  Given
> appropriate changes, no, but there's already been a decision not to
> use <h> for headings, so the changes would have to fight against the
> existing reasoning against this.

What was that reasoning?  All I remember was that it wasn't worth
inventing a new (one-character) element when h1-h6 couldn't be
deprecated anyhow.

But that doesn't mean h would be a problem if it existed for other
reasons -- such as "header to nearest enclosing block element -- shows
up in the outline only if not inside a sectioning root"


Received on Wednesday, 23 September 2009 00:51:15 UTC