This is what I call the death of a name. HTML5 started out it's life as a designator for a WhatWG specification, and cut its teeth in the nice, little world of the browser developers. It was badly surprised when it entered the world of the web, and realized that browsers implemented different parts, and other scary things (like audio codecs).
Now, at the end of its life, HTML5 has become a buzzword. The true sign of buzzwordiness is when a game company uses it to describe their entire system. In this case, the developers of whateverthatwas took advantage of new hardware to let them make an engine that only looked like shit. Then, they covered it up with the word "HTML5," ignoring all the work that was actually done to make it possible, both on the hardware and software ends.
It's interesting that they felt that the graphics in the new engine were anything to talk about. My first real engine, one I wrote about 3 years ago now, supported a better lighting model (deferred pipeline + phong) and everything else they mentioned. It's really interesting that they thought that any of the graphical changes that they made were anything to emphasize - I think it's telling about how much time they had to spend on it to get it working properly. In my experience with WebGL, I found it to be a clunky (OpenGL isn't known for being a clean interface), slow (I think I had 15-30 frames/s less than in C#), and nearly unusable (OpenGL again) interface.
BTW, I think that people had been complaining about downloading Java, and they were saying that the in-browser solution made it easier to use in comparison.
'
[It might help if you started with HTML1. Making a blank line between paragraphs requires two <br> tags. (Or a <p> tag, but fuck that.) -TheShadowMod]