From what I understand from the articles about this, it was found that different JavaScript code (without any delay added) was served in the HTTP response if Firefox was spoofed to look like the request came from Chrome, so it seems the issue only occurs on non-chrome browsers.
Easy now, fuzzy lil’ man-peach!
Happened to me in work once… I was connected via SSH to one of our test machines, so I could test connection disruption handling on a product we had installed.
I had a script that added iptables rules to block all ports for 30 seconds then unblock them. Of course I didn’t add an exception for port 22, and I didn’t run it with nohup, so when I ran the script it blocked the ports, which locked me out of SSH access, and the script stopped running when the SSH session ended so never unblocked the ports. I just sat there in awe of my stupidity.