4 ms·Should be fixed, try hard refreshing.by ibdknox 10y agoShould be fixed, try hard refreshing.ronjouch 10y agoFix confirmed!