views:

1239

answers:

10

From searching SO, this question was already asked, almost a year ago now.

So now with the new FF, Opera, IE, is it finally time to start developing sites with HTML5 or is it still a little premature and will cause compatibility issues?

Is using HTML5 just going to require us to use more and more JS on websites to 'trick' older browsers into working properly?

+4  A: 

If you add nice features to your site, it is possible it will be talked about and reach the news sites for some free publicity.

Aside from that, It would make a good beta site and give you a head start for when it becomes the new technology. However, until HTML 5 enabled browsers are widespread (at least 20% of the market, possibly 50%) it makes little sense to alienate nearly the whole internet.

Wil
Just checking my recent reputation and I got -2 from this, which I answered ages ago? Do people normally rate down old posts?
Wil
Ryan Doherty
... But they didn't almost half a year ago when I wrote that answer!...
Wil
If your answer -becomes- wrong, and you don't update it, shouldn't you expect it's rating to reflect the current best answer? That's the benefit of stackoverflow over a static forum, questions are more likely to be a better reflection of current best practices.
Tchalvak
+1  A: 

I would leave it for now since HTML 5 browser support comes out fully. There really is no reason to put it in a operational site since many people will not be able to view it properly. I really can't wait till it becomes standard. It will make life even easier for web developers.

codedude
+1  A: 

Bruce Lawson of Opera gave an interesting presentation on this at OSCON, see his slides; the verbal conclusion was that it's OK, though there was some debate. Of course that's from somebody working for a browser maker so they're going to be less worried about older browsers (since everybody upgrading is to their advantage;-). The more you need to worry about older browsers, the worse your life is in general of course, but html 5 wouldn't help you there, sigh!-(

Alex Martelli
+3  A: 
David Dorward
+6  A: 

It's a great idea if used in a "Progressive Enhancement" way. ie. Code your website to work in "standard" HTML 4.01 mode, and then add some fancy HTML 5 bits to give it some extra flourishes in browsers that support HTML 5

Frozenskys
+3  A: 

Assess your target audience. Are they likely to be early-adopters? Is it critical that all visitors to your site are catered for? Or will a few not mind being met with an inconvenient, yet polite "please upgrade your browser" message?

For business sites I'd say no. Not yet, anyway. You probably can't afford to lose users of older browsers.

For a personal website or project, why not? It'll be great experience learning the latest HTML5 features, and you'll be ahead of the curve when it does become mainstream. Besides, more people writing sites conforming to HTML5 means more pressure on users of older browsers to upgrade, benefitting all of us in the long run.

Sam Wessel
+1  A: 

I have begun developing pages with the new HTML5 DOCTYPE:

<! DOCTYPE html>

This new DOCTYPE essentially puts the browser into a sorta "standards-based mode." Obviously this is all pretty new to most browsers but creating pages under this DOCTYPE will allow sites to last longer than ever. This also degrades gracefully within every browser I have tested in and no noticeable HTML or CSS downsides.

W3C has began using an experimental validator for HTML5 which can be used the exact same way as all of their other validation engines. An intersting side note: According to the W3C validator, you do not need to close the BODY or HTML tag at the end of the page; allowing for very minimal load time decreases.

As HTML5 continues to make its way to the forefront, I plan to begin implementing more advancements that just the DOCTYPE. For now that seems to be all that is new and widely supported.

Hope this helps. -B

Brad
""you do not need to close the or tag at the end of the page"" - Sorry which tag are you referring too?
Sorry the site removed the tags automatically. Now Editted. -B
Brad
Mode switching using Doctypes has been around since IE6. The HTML5 "Doctype" adds nothing new to this. If anything, it takes things away (i.e. the DTD that could be validated against using a generic SGML or XML validator). Likewise, the optional end tags for the HTML and BODY elements have been a feature of the language forever, HTML 4.x certainly has them. I've never bothered to read the DTDs for earlier versions to see.
David Dorward
A: 

This site has a pretty good HTML5 shiv for IE. Just include it on you page and you can then style the HTML5 elements.

http://html5.adamhunter.me/examples/html-shiv

Fred Clown
+1  A: 

The answer is most certainly YES. Firefox, Safari, Chrome and Opera make up more than 30% of the market and they support many HTML5 standards:

  • Audio & video tag
  • New tags (footer, header, section, etc)
  • Canvas
  • HTML5 doctype (<!DOCTYPE html>)

validator.w3.org supports HTML5 validation (it's experimental, but it seems stable)

For IE you can use these things to make some HTML5 elements work:

Hope that helps, and gets you started using HTML5!

Ryan Doherty
and +1 for the links too :-)
namespaceform
BUT when printing a page using IE its CSS doesn't get interpreted properly, because during printing JavaScript isn't processed, so there's no HTML5 shiv. Look at this: http://doctype.com/arent-my-media-declarations-recognized-properly-across-browsers#answer_2910Does someone know a solution to this? Maybe I should ask a separate question.
Marcel Korpel
A: 

FF 3.6, IE 8 and other modern browsers have fairly good support of html5 by now. So decision is yours whether you want to go with these browsers or not. If not you can still use html5 but you should consider Progressive Enhancement in this case. Thanks

Sarfraz