3 ms·

Yes, the browser wasn't sure if its render engine would get stuck, but there was a big chance it would only end up dumping a bunch of garbled text on screen any

by krono 5y ago

Yes, the browser wasn't sure if its render engine would get stuck, but there was a big chance it would only end up dumping a bunch of garbled text on screen anyway (of a different sort than usual :) ). Therefore it decided to simply not load the file at all. In other words, Firefox literally blocked the website from loading and that's precisely what I said.

db48x 5y ago
No, Firefox did not block anything. Firefox contacted the server, and the server sent back a 7–byte text/plain response containing “Blocked”. Since no encoding was specified, Firefox guesses and displays “Blocked” on the screen. Hopefully it was in an encoding you could read, but in case it shows up as mojibake or something Firefox also put a warning in the dev console. The warning isn’t for end users, it is for the developer of the site who is wondering why their site shows up as mojibake.