3 ms·And here I thought this was a Chrome bug...by steeve 14y agoAnd here I thought this was a Chrome bug...