We have investigated this issue, there is a bug in Chrome that caused this issue. The next Chrome update should resolve this issue. Please use Safari as a workaround for now. Here is the primary thread that shares the same update.
↧
We have investigated this issue, there is a bug in Chrome that caused this issue. The next Chrome update should resolve this issue. Please use Safari as a workaround for now. Here is the primary thread that shares the same update.