4 ms·Did the same thing on my MBP; had to force-quit Safari. Worked sort of OK in FF though.by WiseWeasel 15y agoDid the same thing on my MBP; had to force-quit Safari. Worked sort of OK in FF though.