W3C home > Mailing lists > Public > public-html@w3.org > September 2012

Re: maincontent element

From: Cameron Jones <cmhjones@gmail.com>
Date: Mon, 10 Sep 2012 21:52:54 +0100
Message-ID: <CALGrgetba6BQxu1qAFFDHCDYfTbn=h=hnio0HqBVX7c9W61hoQ@mail.gmail.com>
To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Cc: Steve Faulkner <faulkner.steve@gmail.com>, HTMLWG WG <public-html@w3.org>
On Mon, Sep 10, 2012 at 9:49 PM, Leif Halvard Silli
<xn--mlform-iua@xn--mlform-iua.no> wrote:
> Cameron Jones, Mon, 10 Sep 2012 21:26:56 +0100:
>> On Mon, Sep 10, 2012 at 9:08 PM, Leif Halvard Silli wrote:
>>> Cameron Jones, Mon, 10 Sep 2012 20:48:46 +0100:
>>>
>
>>>> "Ooh, this <p> is some main content, better wrap it in a
>>>> <maincontent> tag!".
>>>>
>>>> "Ooh, this <span> is also main content, better make sure i wrap it in
>>>> a <maincontent> tag too!!".
>>>
>>> To which it can be said: <maincontent> is a block level element. That
>>> rules out a lot of elements, by itself. Specifically, <p> would spit it
>>> out. While validators would go jingle bell if one placed it inside e.g.
>>> <span>.
>>>
>>> So at least, I'd suggest you make more modest claims ...
>
>> And how many people use a HTML validator?
>>
>> And mostly those who do have already read the spec and care about
>> accessibility too.
>>
>> These are not the 90%, so i maintain my initial postulation to the
>> expectation of gross misuse to the negation of its purpose.
>
> Now I am waiting for what you say to the fact that <p> is literally
> going to spit <maincontent> out of itself. Just like it spits <div> out
> itself. That is something that authors are going to see  - without
> validator.
> --
> leif halvard silli

maincontent {
    display: inline;
}

Thanks,
Cameron Jones
Received on Monday, 10 September 2012 20:53:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 10 September 2012 20:53:22 GMT