Chrome doesn't do full revocation checking by default. Instead they have a non-standard implementation called CRLset which handles specific revocations. To me, revocations is a fundamental part of PKI, so the fact that they don't do it makes me question how secure https really is with Chrome anyway.
Uh? Chrome uses CRLset in addition to the usual revocation checks (CRL, OCSP).
They disabled OCSP by default in 2012 due to incurred latency and privacy concerns. Are you saying they changed it again?