There are plenty. People are just coding to Chrome instead of standards, just like they coded to IE instead of standards.
> This was not the case for IE6.
It sure was. For years. IE6 was a _much_ better browser than the contemporary Netscape versions, for example.
Like what? If there’s a standard, Chrome follows it. If there’s no standard, they propose one. They used to have a lot of custom features with prefixes, but that rarely happens anymore.
That happens to not be true all the time. Some examples off the top of my head:
* https://bugs.chromium.org/p/chromium/issues/detail?id=102719... points to various places where Chrome's security checks don't match the spec and therefore can allow things that other browsers and the spec don't.
* https://bugs.chromium.org/p/chromium/issues/detail?id=878491 -- non-spec implemetation of document.close (shared with WebKit)
* https://bugs.chromium.org/p/chromium/issues/detail?id=100027... -- broken .complete attribute behavior, broken since forking from WebKit.
Those were all found due to sites coding to Chrome instead of the standard and therefore not working correctly in Firefox.
If you want something more long-standing, https://bugs.chromium.org/p/chromium/issues/detail?id=286670 is a clear bug in selector-matching optimization that leads to incorrect behavior and just turned 7 years old.
Or you could look at https://bugs.chromium.org/p/chromium/issues/detail?id=340414
Or https://bugs.chromium.org/p/chromium/issues/detail?id=352144
There have also been multiple cases in which everyone just gave up, and changed the standard and all other browsers to match Chrome's behavior in cases where it was causing serious compat problems for everyone else.