[html5] page element?

Fri Mar 19 04:55:16 PDT 2010

<page>
     <div id="wrap">
        <!--content -->
    </div>
</page>

?

Bob

----- Original Message ----- 
From: "a2h" <a2h at live.com.au>
To: <help at lists.whatwg.org>
Sent: Friday, March 19, 2010 11:19 AM
Subject: Re: [html5] page element?


>
> I've got a beef with this idea of <page> as a replacement for <div 
> id="wrap"> - what if you have a structure similar to this?
>
> <div id="wrap2">
>   <div id="wrap">
>      <!-- content -->
>   </div>
> </div>
>
> -a2h
>
> --------------------------------------------------
> From: "designer" <designer at gwelanmor-internet.co.uk>
> Sent: Friday, March 19, 2010 10:16 PM
> To: "Chris Taylor" <Chris.Taylor at figureout.com>
> Cc: <help at lists.whatwg.org>
> Subject: Re: [html5] page element?
>
>> Hi Chris & all,
>>
>>>Or is it an overall wrapping element around all "visible" parts of the 
>>>page
>>
>> Yes. It does the same as <div id="wrapper">, and in the same way.
>>
>> So why have it at all? - well, in html5 we have <nav> now, which 
>> (nomatter
>> how you dress it up and make it sound like a big step forward) is the 
>> same
>> as <div id="nav"> (or it can be).  What the use of <nav> does is:
>>
>> 1. It makes for consistency of code.  Everyone uses <nav>, whereas
>> previously, we used 'nav' , 'menu', 'links' etc. etc., somewhat
>> indiscriminately.
>>
>> 2. It encourages the usage to be semantic and it's easier to set up 
>> 'rules'
>> or guidelines.
>>
>> <footer> vs. <div id="footer"> is a similar case.
>>
>> <page> vs. <div id="wrapper"> is another. [:-)]
>>
>> As to Mike's multiple pages, this can be very handy for documents which 
>> are
>> collections of related but separate content.  We can also 'paginate' and
>> link by using
>> <a href="#x"> and I've no doubt other things will come with usage.
>>
>> HTML5, as far as I can see, provides 3 distinct areas of improvement:
>>
>> 1. New elements which enable us to do things we couldn't do before -
>> <canvas> being the  obvious example.
>>
>> 2. New elements which don't make it possible to do 'new' things, but make
>> the doing of those things more structured, organised and semantic. 
>> <figure>
>> and <figcaption> are an example. We've all been doing that for years:
>>
>> <div class="figure">
>> <img href="etc.
>> <p>title</p>
>> </div>
>>
>> cf:
>>
>> <figure>
>> <img href="etc.
>> <figcaption>title</figcaption>
>> </figure>
>>
>> In my view of the world, <page> would be another one of those examples:
>>
>> <div id="wrapper">
>> bla bla
>> </div>
>>
>> cf:
>>
>> <page>
>> bla bla
>> </page>
>>
>> N.B.  You don't HAVE to use <page>.  If you don't have a need to use <div
>> id="wrapper">, you CAN use <body>. However there are a VERY large number 
>> of
>> us (wish I had figures!) who prefer to wrap their visible content in a 
>> box,
>> and it is for these people that <page> would be good.
>>
>> Bob
>>
>>
>>
>>
>
> _______________________________________________
> Help mailing list
> Help at lists.whatwg.org
> http://lists.whatwg.org/listinfo.cgi/help-whatwg.org
>
>