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

Re: maincontent element

From: Bruce Lawson <brucel@opera.com>
Date: Tue, 11 Sep 2012 10:50:29 +0100
To: "Jirka Kosek" <jirka@kosek.cz>, "Silvia Pfeiffer" <silviapfeiffer1@gmail.com>
Cc: "Cameron Jones" <cmhjones@gmail.com>, "Steve Faulkner" <faulkner.steve@gmail.com>, "HTMLWG WG" <public-html@w3.org>
Message-ID: <op.wkgtmfeyh8on37@bruce-pc>
On Tue, 11 Sep 2012 10:40:30 +0100, Silvia Pfeiffer  
<silviapfeiffer1@gmail.com> wrote:

> On Tue, Sep 11, 2012 at 7:17 PM, Jirka Kosek <jirka@kosek.cz> wrote:

>> That's true. On the other shouldn't be everything inside <body> except
>> <footer>, <header>, <menu> and <aside> aside considered as a  
>> "maincontent"?
>
> That's the real question, indeed.
>
> Or asked the other way around: is it possible to mark up a page such
> that everything that is not main content can be contained in an
> existing "semantic" tag or do we still have the need to create our
> pages/applications with many <div> elements? If the latter is true,
> then it can make sense to pick one <div> as the one to start reading
> at.
>
> Silvia.

I had a go, just this morning, at marking up a gmail page with new  
elements to see if I could.  
(http://www.brucelawson.co.uk/2012/scooby-doo-content-element/#comment-1016360)

It might be a good idea to collect examples of "app-like" web pages to see  
if it's possible. My colleague Mike Taylor wrote a small script to add a  
class to the first element that's not <footer>, <header>, <nav>, <aside>  
to check whether that does correspond with the "Main content" of a page  
http://pastie.org/4663081.

I wonder whether the (so-far unsupported anywhere) <menu> element  
shouldn't be added to the list of tags to "skip" before main content is  
reached.

-- 
bruce
Received on Tuesday, 11 September 2012 09:51:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 September 2012 09:51:11 GMT