I believe that was the point LordIllidan was trying to make; that is, because Chrome doesn't use Nitro, it remained unaffected because (possibly) the issue is within Nitro.