I think it’s about time to start giving wider support for the next version of HTML. Is anyone already or will support HTML 5 in your projects past and future?
If developers start supporting it, it will help speed the adoption.
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
December 07, 2009 1:46am
Subscribe [8]#1 / Dec 07, 2009 1:46am
I think it’s about time to start giving wider support for the next version of HTML. Is anyone already or will support HTML 5 in your projects past and future?
If developers start supporting it, it will help speed the adoption.
#2 / Dec 07, 2009 2:01am
Considering the gorilla in the room (Explorer) has zero support for HTML5, strict HTML5 adoption is probably not a good idea at this point. Many “good” browsers don’t even support the spec to any significant degree. Some pieces of the spec are well defined and useful—canvas, for example—but other parts are confusing and pointless. Unfortunately, the project has suffered from a lot of the same issues that ECMA 4’s team did: bloat, creep, and delay. They started off on the right foot: they documented all the quirks of HTML and the popular build-outs from it (such as canvas and the localstore api) folded them into a coherent spec. Then they started adding. The next thing you know, a dozen new tags were added with no clear thinking behind many of them—these flaws are well-documented at this point, before the spec even has widespread adoption. This makes me a bit leery to jump ship from XHTML Transitional just yet.
At this point, switching to the HTML5 doctype is just a symbol that you’re ready for the next step, although it’s unlikely that full adoption will be a reality in the next couple years at least. A goal for the Explorer 9 project is to have support for HTML5, but what that means at this point is unclear, as is IE9’s release date.
#3 / Dec 07, 2009 6:11pm
I think of it quiete for a while, yesterday after discovering http://usesthis.com/ I decided to build in HTML5, whenever possible. I’ll stick to XHTML notation but I’ll experiment will all those nice new tags.
usesthis works on IE6 +, iPhone, FF and Safari and validates with W3C validator and html5.validator.nu.
Have to quit my SelfHTML which I used as reference, will start with http://www.w3schools.com/html5/html5_reference.asp.
#4 / Jan 22, 2010 2:29pm
I had an idea to build HTML5 helper. If anyone needs this, tell me.
#5 / Jan 22, 2010 5:51pm
I had an idea to build HTML5 helper. If anyone needs this, tell me.
What exactly would it do?
Adding support for <aside>, <header>, <footer> and such?
Is anyone using the current helpers for rendering anything but anchors and forms?
#6 / Jan 22, 2010 7:46pm
Personally not planning on working with HTML 5 until it’s finished. I’m not going to drive a car until it’s completely finished (or safe enough to use).
#7 / Jan 22, 2010 10:53pm
I declare now all my HTML as HTML5 and continue to use my XHTML markup, with every new site I try some of the new stuff, I keep what’s cross browser compatible.
#8 / Jan 23, 2010 3:01am
Yes, it will be like current HTML helper, but with support of HTML 5.
#9 / Jan 23, 2010 9:53am
If you can get away with using HTML5 then do - it will never become widespread unless people start using it. After all, even just making use of the HTML5 structural elements will make your markup a lot more semantic and easier to read. Not forgetting the fact that most modern browsers support a lot of the spec already, and there are JavaScript libraries available to emulate it for certain other browsers that don’t.
There’s a really interesting post over on the Newism blog (Leevi Graham’s company) that talks about their use of HTML5 on a piece of client work - http://newism.com.au/blog/post/102/a-real-world-case-study-on-html-5/.
Jamie
#10 / Jan 23, 2010 11:04am
If you can get away with using HTML5 then do - it will never become widespread unless people start using it. After all, even just making use of the HTML5 structural elements will make your markup a lot more semantic and easier to read. Not forgetting the fact that most modern browsers support a lot of the spec already, and there are JavaScript libraries available to emulate it for certain other browsers that don’t.
There’s a really interesting post over on the Newism blog (Leevi Graham’s company) that talks about their use of HTML5 on a piece of client work - http://newism.com.au/blog/post/102/a-real-world-case-study-on-html-5/.
Jamie
The problem with the javascript approach is that your website won’t work at all if the user’s browser doesn’t support HTML5 AND has Javascript turned off. Another problem with HTML5 is that it’s still in development, meaning a lot might change over time.
#11 / Jan 27, 2010 5:21am
actually i’m not really ready for this .. but we need to know what about this new html
#12 / Jan 27, 2010 5:59am
Just Google it.
#13 / Feb 01, 2010 1:27am
HTML 5 is not yet stable in the net.. There are some bugs in other browsers.
#14 / Feb 01, 2010 1:35am
IE?)