Going by the rest of the article, I'm assuming by native HTML5 they mean hardware accelerated compositing? Good for them if so, but 'native' is definitely the wrong word to use, and the development channel of Chrome has supported hardware accelerated compositing for quite some time.

https://sites.google.com/a/chromium.org/dev/developers/desig...

Can even try it out in the current stable channel if you enable it: about:flags

IE10 and WebGL is the big question for me, which will be interesting to see pan out given their obviously conflicting position with OpenGL.