[MatthewPhillips]

The other vendors choose when/if they merge Google's commits. The grandparent's comment made WebKit sound like a single entity when it's actually several competing companies with overlapping but also differing views on things. They just happen to be working from a common code base.

[alexchamberlain]

Some of Google's engineers have Webkit priveleges. Webkit is a single rendering engine - this should not be confused. It is used by several browsers, who of course, use slightly different compilation configurations, but I doubt that the web designer ever needs to concern themselves with that!

[MatthewPhillips]

No Alex, not all WebKit browsers have feature parity with each other.

[alexchamberlain]

Example please.

[MatthewPhillips]

Touch events - Android (any version) vs. iPhone (any version).

IndexedDB - Chrome Mobile has it (outdated version), Android and iPhone do not.

Chrome will have Dart support at a later date, no other WebKit vendor is going to implement it.

There are literally dozens, just go to caniuse.com and play around for a bit.

[alexchamberlain]

The first 2 are simply version issues, whilst the 3rd is nothing to do with the rendering engine. Chrome uses V8, Safari does not.