2 ms·

Ah, thanks for that info! The article made it seem like the entire implementation was done within chrome://