The Amazon Kindle reader was a nice example of that, working on Chrome and Safari, but not Firefox, due to competing web-database standards being implemented.
H.264 vs WebM is another one. Google made a lot of noise about dropping H.264 for WebM, Firefox actually did so (because they had no choice, anyway), but Chrome still ships with H.264 support.
So I don't have the impression there are real fronts as far as promoting web standards are concerned. For better or worse.
Just because they're using WebKit today doesn't mean they will forever (or for everything). Gecko is valuable as an alternative and as a way to "keep web standards honest". A WebKit monoculture would eventually bake in too many hidden assumptions.
I'm still surprised that no one has written an IndexedDB shim on top of Web SQL DB.