Out-of-band online CA checking is a weak design that doesn't work in practice. If revocation is required in a strict sense, then the solution will look something like "nuclear HSTS-style OCSP stapling". But to my mind, a simpler alternative would be for browsers to support something like TACK, so that instead of trying to knock down known-bad certificates, we just had a much better infrastructure for asserting which certificates are good.

All that aside though, it's awfully silly to kick Google for noticing and pointing out this security problem with revocation checking. Other browsers are often literally pretending to do revocation checks that aren't actually meaningful.