because the browser makers are innovating so quickly. Also, much of the
new functionality can be replicated with JavaScript in browsers that don’t
yet have support. The
HTML5 is designed to degrade gracefully, so with clever JavaScript and
some thought, all content should be available on older browsers.
“My Browser Supports HTML5, but Yours Doesn’t”
There’s a myth that HTML5 is some monolithic, indivisible thing. It’s not. It’s
a collection of features, as we’ve seen above. So, in the short term, you
cannot say that a browser supports everything in the spec. And when some
browser or other does, it won’t matter because we’ll all be much too excited
about the next iteration of HTML by then.
What a terrible mess, you’re thinking? But consider that CSS 2.1 is not yet a
finished spec, and yet we all use it each and every day. We use CSS3,
happily adding border-radius, which will soon be supported
everywhere, while other aspects of CSS3 aren’t supported anywhere at all.
Be wary of browser “scoring” websites. They often test for things that have
nothing to do with HTML5, such as CSS, SVG and even Web fonts. What
matters is what you need to do, what’s supported by the browsers your
client’s audience will be using and how much you can fake with JavaScript.