[whatwg] maincontent element spec updated and supporting data provided (Henri Sivonen)

[Steve Faulkner]

Hi Henri,

<bikeshed>A single-word element name would me more consistent with
> other HTML element names. <content> would be rather generic, so I
> think <main> would be the better option.</bikeshed>
>

Have changed name [1]:

 After consideration of feedback I have changed the name of the element
from <maincontent> to <main>. The reasoning for the change:

Feedback indicates preference for a shorter one word element name.
Most commenter's proffered <main> as a name.
The element name <content> is already proposed for use in the shadow DOM
specification [2]
As the element maps onto the ARIA role=main it seems an appropriate name to
use.

It would probably make sense to add
> main { display: block; }
> to the UA stylesheet.
>

have added.

If Hixie had added this element in the same batch as <section>,
> <article> and <aside>, he would have made the parsing algorithm
> similarly sensitive to this element. However, I'm inclined to advise
> against changes to the parsing algorithm at this stage (you have none;
> I am mainly writing this for Hixie), since it would move us further
> from a stable state for the parsing algorithm and, if the <main>
> element is used in a conforming way, it won't have a <p> element
> preceding it anyway.
>

have captured your feedback on parsing in  bug:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19591

[1]
https://dvcs.w3.org/hg/html-extensions/raw-file/tip/maincontent/index.html
[2]
http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#content-element


>
> ------------------------------
>
> Message: 4
> Date: Thu, 18 Oct 2012 09:12:41 +0300
> From: Henri Sivonen <hsivonen at iki.fi>
> To: whatwg <whatwg at whatwg.org>
> Subject: Re: [whatwg] maincontent element spec updated and supporting
>         data    provided
> Message-ID:
>         <
> CAJQvAudR2qvCPd82S4zRiZ3iTSGq_y1q+Fi2S5vnmr++TxV0BA at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Wed, Oct 17, 2012 at 3:03 AM, Steve Faulkner
> <faulkner.steve at gmail.com> wrote:
> > I have updated the <maincontent> spec [1] and would appreciate any
> feedback
> > (including, but not limited to implementers).
>
> <bikeshed>A single-word element name would me more consistent with
> other HTML element names. <content> would be rather generic, so I
> think <main> would be the better option.</bikeshed>
>
> It would probably make sense to add
> main { display: block; }
> to the UA stylesheet.
>
> If Hixie had added this element in the same batch as <section>,
> <article> and <aside>, he would have made the parsing algorithm
> similarly sensitive to this element. However, I'm inclined to advise
> against changes to the parsing algorithm at this stage (you have none;
> I am mainly writing this for Hixie), since it would move us further
> from a stable state for the parsing algorithm and, if the <main>
> element is used in a conforming way, it won't have a <p> element
> preceding it anyway.
>
> --
> Henri Sivonen
> hsivonen at iki.fi
> http://hsivonen.iki.fi/
>
>
> -
>