Est. Reading Time: 2 minute
The subject of HTML5 has been the buzz amongst Beacon’s Web Designers, who are anxious to try it out. It’s been called “the future of the web” (see one of my developer’s articles about this). The problem is that we support such a wide variety of browsers that it’s hard to jump on the HTML5 bandwagon because none of the older browsers (IE 7/8, Firefox 3.0, etc.) fully support HTML5. However, now that IE 6 is out of our collective hair, IE 7′s grave plot is being dug, and Firefox 3.0 seems to be gone, so we’re slowly moving towards only supporting browsers that comply with HTML5 standards.
Another reason it’s hard to jump on the HTML5 bandwagon is that the W3C / WHATWG team hasn’t finished the standards for it yet, and likely won’t do so until 2014. I found all of this in an interesting article on CNET, “W3C officially opens HTML5 to scrutiny“. Essentially, the article says that the W3C thinks that the standards for HTML5 are solid enough to have organizations review them and see if they can garner support, so they put it out for “last call”. In other words, we’re a long way from having finalized standards.
Bits and pieces of HTML5 are supported in a lot of browsers (some browsers support more bits than others), but it’s hard as a Web development company with such a wide user base to code stuff that a good number of people couldn’t even see.
With that being said, as more browsers support HTML5 code, Beacon will be keeping a close eye on the progress of browser acceptance of new tags. Our CMS of choice, Cascade Server, now has limited support of HTML5 with its latest release (6.8), taking an important step towards becoming more compliant. Hopefully soon, I can turn my developers loose on HTML5…they’re all anxious to take on a new challenge.