[jsr-314-open] Fwd: [jsf2.next] Proposal to support new semantic HTML5 tags

[Jim Driscoll]

For the most part, no.  The exceptions appear to be noted in the article 
(but, I haven't reviewed the HTML5 spec - it ironically causes Firefox 
to crash whenever I try).

So instead of saying <div class="nav">, you instead say <nav>

However, it turns out that there's serious problems  with using these 
tags, at least according to John Resig (I attended a talk he gave on 
Friday).

While the HTML5 shiv referenced below will allow these tags to work in 
IE in the basic case, there are still two problems:  1) they won't nest, 
and 2) innerHtml won't work with these tags.

So, given those problems, I withdraw the proposal.  Since these problems 
occur in IE8, it looks like these tags may be as far as 5 years away 
from being usable.  Tragic.

In the unlikely event that someone figures out how to work around this, 
we can always go back to trying to support it.


Jim

On 12/12/09 9:23 PM, Martin Marinschek wrote:
> So the new tags don`t add any new attributes in comparison to a normal
> span/div?
>
> regards,
>
> Martin
>
>
> On Fri, Dec 11, 2009 at 11:41 PM, Jim Driscoll <Jim.Driscoll at sun.com
> <mailto:Jim.Driscoll at sun.com>> wrote:
>
>     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?
>
>
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces