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

[Lincoln Baxter, III]

I'm not sure I really see the need for special tags like this. What are the
advantages of turning every tag into a component?

Unless there is a new input type or tag that affects server side behavior,
but I don't see one... save perhaps the new inline editing feature of HTML
5.

Lincoln Baxter III
http://ocpsoft.com
http://scrumshark.com
Keep it simple.

On Dec 14, 2009 1:12 PM, "Dan Allen" <dan.j.allen at gmail.com> wrote:

> > JD> So, given those problems, I withdraw the proposal.  Since these
problems > JD> occur in IE8...
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/seaminaction
http://www.google.com/profiles/dan.j.allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jsr-314-open-mirror/attachments/20091214/1121b65b/attachment.html