[html5] page element?

Fri Mar 19 05:05:23 PDT 2010

HTML is not a "multi-page" language. Each file is about a single page. To add a <PAGE> element, no matter the name, would also require you to add new <TITLE> and other <META> elements.

What you are describing is the reason <SECTION> exists. If you don't feel it is a section, then they should each be separate files pulled in via AJAX (that helps with your progressive enhancement as well).

The only reason I've heard for a <PAGE> element that makes sense is the wrapper functionality, and that's a design need, not semantic.

nz

On Mar 18, 2010, at 11:59 PM, Mike Schinkel wrote:

> On Thu, Mar 18, 2010 at 7:09 PM, Alastair Campbell <ac at alastc.com> wrote:
> On 18 Mar 2010, at 20:25, Mike Schinkel wrote:
>> It would be used for the visible portions of a page (vs. the non-visible portions that are contained in the body like <script> tags and the CSS visibility:hidden and display:none.
> 
> If they are hidden, does it matter if they are in the body/page?
> 
> Yes.  Example: (a multi-page wizard that uses Javascript to move from page to page):
> 
> <style>
> page {visibility:hidden;}
> page.current-page {visibility:visible;}
> </style>
> <body>
> <page id="1" class="current-page">...</page>
> <page id="2">...</page>
> <page id="3">...</page>
> </body>
>> A screen reader would read what's inside this <page> element and typically ignore what's outside. 
> As they do for body.
> 
> Are you making a counterpoint?  It seems that your point is valid but is not an argument against <page>, or did I miss something?
> 
> -Mike
> _______________________________________________
> Help mailing list
> Help at lists.whatwg.org
> http://lists.whatwg.org/listinfo.cgi/help-whatwg.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/help-whatwg.org/attachments/20100319/9098918f/attachment-0002.htm>