Hi,
Or we can simply make the renderer aware of the agent and its version .
Those new tags exist to better describe a document and could very well have a meaning in
various render kit for their semantic value even if not yet in HTML.
Or we could have the default render kit display them as div/span with or withotu default
style class, leaving the opportunity to a third party to develop an HTML 5 render kit
and/or also provide a HTML 5 render kit out-of-the-box as well as the default one.
Briefly, I don't think the withdrawal is justified.
Regards,
~ Simon
________________________________
From: jsr-314-open-bounces(a)jcp.org on behalf of Dan Allen
Sent: Mon 12/14/2009 1:12 PM
To: jsr-314-open(a)jcp.org
Subject: Re: [jsr-314-open] [jsf2.next] WITHDRAWN Proposal to support newsemantic HTML5
tags
JD> So, given those problems, I withdraw the proposal. Since these problems
JD> occur in IE8, it looks like these tags may be as far as 5 years away
JD> from being usable. Tragic.
I'm not opposing the withdrawl, but I do want to say (on behalf of Molly Holzschlag)
that there is a JavaScript library called HTML5 Now that is supposed to
"upgrade" browsers to HTML 5 w/o them actually supporting it. I think this is
the script:
http://remysharp.com/2009/01/07/html5-enabling-script/ But there might be a
newer one. Just FYI.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com <
http://mojavelinux.com/>
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen