Web Standards
This is the result of a standards process running in reverse: <i>first</i> the specifications, <i>then</i> the implementation. There was a time when the "Internet" could if you squinted right be defined as "the collection of people who make fun of that process and do the opposite"; their motto was (literally) "loose consensus and working code".<p>First you get things working. Then you standardize on them.<p>Complain when the Webkit team refuses to implement standards. Have they shown any unwillingness to support W3C standards once published? No? Then what's the gripe? The browser vendors are doing <i>exactly what they're supposed to do</i>: come up with new things. If the W3C was doing its job, it would watch those new things carefully and, when enough momentum existed, start ratifying them as standards.<p>It's not enough to say, "you could have used the same argument to defend Internet Explorer". To indict someone for "embrace & extend", you need both halves of the behavior: creation of new features, <i>and unwillingness to support subsequent standards for those features</i>.