[jsr-314-open] [jsf2.next] Proposal to support new semantic HTML5tags

[Simon Lessard]

Hi,
 
I would highly prefer adding all tags in the h: namespace, else some pages might end up with just too many imbricated panelGroup to be easily readable. Furthermore the renderer will be more complex and there would be a, albeit small, performance overhaul as the attribute has to be evaluated. The only thing that won't be supported with tags is dynamic change of the layout, but semantically it makes no sense anyway. I think it would also be time to add <h:paragraph/>,< h:fieldSet/>, <h:legend/>, briefly every single valid HTML tags.
 
 
Regards,
 
~ Simon

________________________________

From: jsr-314-open-bounces at jcp.org on behalf of Jim Driscoll
Sent: Fri 12/11/2009 5:41 PM
To: jsr-314-open at jcp.org
Subject: [jsr-314-open] [jsf2.next] Proposal to support new semantic HTML5tags



HTML5 has a number of new semantically meaningful tags.

See here for a painless introduction:
http://www.techradar.com/news/internet/why-html5-is-here-today-and-not-2022-654828

Block tags include:

article
aside
footer
header
nav
section

Inline tags include:

details
figure
mark
time

Then, there's the canvas, audio and video tags.

We can actually support many of these tags with only a minor change in
to the panelGroup tag.

In addition to the currently allowed "inline" and "block", I would add
the following:

span
div
article
aside
footer
header
nav
section
figure
mark

details and time deserve their own tags, I think, as do canvas, video
and audio, and are not part of this proposal.

We may wish to consider deprecating inline and block.  We've never
deprecated attribute values before, but hey, first time for everything.

Note that for backward compatibility with particularly lame (IE)
browsers, a shiv needs to be included in the page, as found here:

http://code.google.com/p/html5shiv/

Whether this would be included automatically, should, I think, be
implementation specific.

Please comment on this proposal, and I'll add it to the spec issue
tracker after we have consensus.

Jim

P.S.  Molly's HTML 5 talk at Rich Web was a good one - can you tell?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 5534 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jsr-314-open-mirror/attachments/20091214/b1ae0689/attachment.bin