While I can't provide a citation, I believe that the contrapositive is true: if it doesn't help Google, it's not going to be implemented. Right now, Google's interests are aligned with a standardised, compatible web, and when Google gets big enough, or greedy enough, it's going to take Chrome in its own direction. Opera still fares badly at Google's services, but they consider IE worth supporting.
> when Google gets big enough [..] it's going to take Chrome in its own direction
Hasn't Google already taken Chrome in its own direction? Chrome includes lots of non-standard technologies like Flash, NaCl, Pepper, Chrome Apps, and soon a Dart VM. Google believes these technologies are good, but no other browser does, and not even WebKit.
Maybe those are good and useful technologies, that is a separate matter. I'm just pointing out that Google is already well in the process of taking Chrome in the direction Google feels is best, regardless of what the rest of the web thinks.
Not blaming, but worrying about. There is plenty of software that can read Word's .doc files. Yet I store my data as plain text, as I imagine that the software will be killed or end-of-lifed in the future, even though I can use it fine right now. In the same way, I'd rather use a browser designed for an open, standardised Web.
Chrome doesn't have nearly enough market dominance for me to make accusations about it; I just want to minimise any future disaster scenarios.
