Our Top Ten HTML5 Wishes for 2011HTML5* (* and we mean HTML5 in the broadest sense, including CSS3, the HTML5 satellite specs and all the other technologies that have been bundled under the HTML5 banner). All mobile OS's are now shipping or about to ship HTML5 browsers with the exception of Windows Mobile. And to everyone's great surprise, IE9 is shaping up to be a fairly decent HTML5 browser too. But there's still a lot of work still to do. As the new year approaches, we're taking a stab at a HTML5 wish list for 2011. Some of these are web standards wishes, and the rest are browser wishes, so we just mixed them all in together and put them in a rough order of priority. So without further ado, here's what we'd like to see from the W3C, WhatWG and the browser makers this year:
10. Sustained effort to move more
Although WebKit has become the modern mobile device standard, we'd still like to rely a little less on
-webkit effects into CSS3
-webkitextensions to get our job done. Although many
-webkitextensions have made their way onto standards track over the last year there are still notable exceptions that need to get there. WebKit masks and background clipping to text are just a couple of the CSS3 effects we'd really really like to see in W3C working drafts in 2011. They're incredibly useful effects that we shouldn't need SVG or Canvas to accomplish.
9. CSS3: A Richer Effects ToolboxBlur effects (including motion blurs and filters) have been on the CSS wishlist since 1998. We can now do shadow blurs within WebKit, Mozilla and Opera, but we should have at least block-level blurs and filters within CSS. If we're going to be able to fully replace Flash with browser technology, this is one to work on. In addition, more general support of CSS3 3D Animations (cough Android) would be excellent. Firefox and WebKit both have great gradient support but now that we have that basic support, we're hankering for more. Gradients should be transitionable (according to standards track drafts), but today's
-webkit-gradientsare implemented as images which can't be transitioned. Gradients as border images are also an area for work since today they don't stay within their border areas. (And we know we can duplicate any of these effects with Canvas, but the answer to every CSS feature request shouldn't be "do it with Canvas". Not to mention that Canvas still needs performance work.)